planned-task-runtime

Handles system follow-up turns: planned-task-follow-up (synthesize, replan, build-workflow, checkpoint), background-task-completed, running-tasks context, and create-tasks silence rules. Load whenever any of these tags appear or after calling create-tasks.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable instruction-only skill with clear sequenced workflows, explicit validation checkpoints, and feedback loops. The main room for improvement is light tightening of the densest sections and an optional overview header.

Dimension	Reasoning	Score
Conciseness	The body is dense and operational, assuming Claude's knowledge of the system with imperative directives and no padding about what tags or tools are; scored 4 rather than 5 because the synthesize and checkpoint sections pack many rules into long sentences that could be tightened slightly.	4 / 5
Actionability	It gives concrete, executable guidance throughout — exact tool calls with parameters such as `workflows(action="setup")`, `task-control(action="correct-task")`, and `complete-checkpoint(taskId, status, result)`, with specific conditions for each.	5 / 5
Workflow Clarity	Each follow-up type is a clearly sequenced process with explicit validation checkpoints (inspect → compare → verify → setup → complete-checkpoint) and feedback loops (patch and re-save on fixable errors; re-verify in the same turn; escalate to failed after two rounds).	5 / 5
Progressive Disclosure	A single cohesive file with no bundle files, organized into clearly headed sections and no nested references; scored 4 rather than 5 because there is no overview/summary framing and a few dense sections (checkpoint) could arguably be split out, though the cohesion justifies keeping them inline.	4 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states both the skill's purpose and its load triggers, with comprehensive enumeration of the turn types it handles. Its only weakness is that the trigger terms are technical system tags rather than natural user language.

Dimension	Reasoning	Score
Specificity	Names the domain ("Handles system follow-up turns") and enumerates multiple concrete actions/turn types — synthesize, replan, build-workflow, checkpoint, background-task-completed, running-tasks, and create-tasks silence rules — giving comprehensive coverage rather than a partial list.	5 / 5
Completeness	It explicitly answers both what ("Handles system follow-up turns: ...") and when ("Load whenever any of these tags appear or after calling create-tasks") with concrete trigger phrases.	5 / 5
Trigger Term Quality	It explicitly lists all relevant trigger tags (planned-task-follow-up, background-task-completed, running-tasks) plus "after calling create-tasks", giving strong coverage; scored 4 rather than 5 because these are technical system tag identifiers rather than natural-language synonyms a user would say.	4 / 5
Distinctiveness Conflict Risk	The trigger tags are highly specific system identifiers forming a clear niche, making conflict with unrelated skills minimal.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: n8n-io/n8n
Path: packages/@n8n/instance-ai/skills/planned-task-runtime/SKILL.md
Commit: 7700b76

Reviewed: ~5 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.