Your list has subjects on it, not actions. Build a website is not a task but a project. Something with the blog is not even that. A vague line may be difficult to act on; its wording does not diagnose what a particular person’s brain does or why work is delayed. A hard rule applies here: an action is always a physical act you can literally carry out, and a project is anything that takes more than one step. So for every project it keeps asking until it reaches the first physical step.
Everything is dumped in one pile. Calls, emails, errands and thinking work are all mixed together, even though you can never do them at the same moment. GTD solves that with contexts: practical places or states in which an action is possible. As examples the file names @calls, @computer, @office, @home, @errands for shopping on the go, @low energy, @high energy, @with partner and @with team. If you are standing in a queue with ten minutes and a phone, you open @calls, not your whole list.
Small actions may be cheaper to finish during processing. Recording and revisiting a short action can add overhead. The guideline suggests doing it during processing only when it is appropriate, authorised and possible now. Otherwise record it; the duration estimate is not a measured universal saving.
There is no place for things that are not an action. An idea for two years from now, an article you want to keep, a thought that does not need to go anywhere: without a place for them, they keep floating around among your real tasks. GTD gives them their own destination, namely Someday/Maybe, Reference and Trash, and that separation is exactly why the action list stays readable afterwards.
Nobody checks the system. Every list goes stale. Projects slip, delegated things do not come back, and after two weeks your overview no longer matches reality. That is why the SKILL.md requires the skill to include a weekly review with every plan, and that review is concrete: go through the calendar two weeks back and two weeks ahead, go through every list, put the project list next to the next-actions list so each active project has a next action or an explicit waiting/calendar follow-up, clean up the waiting-for list and do a fresh mind sweep for whatever has come in since last week.
In diff form, with lines from the skill's example: what goes out and what comes back in its place.
--- tasklist.txt
+++ next-actions.md # this is how the skill rewrites lines, based on the example
write a blog post about SEO
@computer: write the blog outline and come up with three H2s (project: SEO blog post)
send VAT figures to the accountant
@computer: read the accountant’s request and clarify the required information and period
go to Japan someday
Someday/Maybe: trip to Japan, no action, no date, no guilt