CtrlK
BlogDocsLog inGet started
Tessl Logo

next-task

Run one unattended IMPLEMENTATION iteration of the autonomous value-creation loop — steward any in-flight PR, fix interrupts (red CI / security / human bugs), or else build ONE queued `idea` issue on a branch off auto-dev and open a PR that squash-merges on green CI. Ideation lives in the next-idea skill; this skill consumes its queue. Use when the user says "次のタスク", "next task", "続きをやって", or wants autonomous progress without specifying what to do.

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/next-task/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

The body is a tight, highly actionable instruction skill with an exemplary guarded workflow featuring explicit validation checkpoints and feedback loops for its destructive merge operations. Conciseness and progressive disclosure are strong but not maximal, with a few trimmable justifications and external-doc references that could be organized more formally.

DimensionReasoningScore

Conciseness

Lean imperative prose that assumes Claude's intelligence with no basic-concept padding; a few parenthetical justifications ('a rotten integration branch produces unmergeable promotion PRs') could be trimmed but mostly earn their place.

4 / 5

Actionability

Highly concrete with specific commands, file paths, and labels throughout; minor gaps where flow is conditional narrative rather than copy-paste steps keep it just below fully executable.

4 / 5

Workflow Clarity

Clear numbered sequence (guard → interrupts → pick → build) with explicit validation checkpoints (CI green, 3-attempt limit, re-verify before building, quality gates) and error-recovery feedback loops (re-push on red, re-arm check-in, block-and-stop).

5 / 5

Progressive Disclosure

Well-organized into clear sections with one-level-deep, clearly-signaled references (docs/task-automation.md, IMPLEMENTATION_PLAN.md, next-idea/pr-to-main skills) and no nested chains; no bundle files exist, so structure relies on clean sectioning, which is solid but not exemplary enough for a 5.

4 / 5

Total

17

/

20

Passed

Description

75%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.

The description is concrete, well-triggered, and clearly delineated from its sibling ideation skill, covering both what the skill does and when to invoke it with natural multilingual trigger phrases. It sits solidly above the midpoint but the conditional, layered 'what' statement and slightly incomplete trigger synonym coverage hold it just below the top anchor.

Suggestions

Lead the description with a tighter flat capability list (e.g. comma-separated verbs) before the loop mechanics, to push specificity toward a 5.

Add a couple more common English trigger synonyms (e.g. 'keep going', 'continue the loop') alongside the existing phrases.

Tighten the conditional 'what' phrasing so the core capability reads as a single clear statement rather than a branching rule.

DimensionReasoningScore

Specificity

Lists several concrete actions ('steward any in-flight PR', 'fix interrupts (red CI / security / human bugs)', 'build ONE queued idea issue', 'open a PR that squash-merges on green CI'), but the conditional loop mechanics keep it just short of a flat comprehensive capability list.

4 / 5

Completeness

Explicitly answers both 'what' (steward PR / fix interrupts / build one idea → PR) and 'when' ('Use when the user says...'), but the 'what' is conditional and layered rather than a clean capability statement, keeping it below a 5.

4 / 5

Trigger Term Quality

Provides natural trigger phrases users would say ('next task', '次のタスク', '続きをやって', 'wants autonomous progress') including Japanese synonyms, though a few common English variations are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche as the implementation half of an autonomous loop with explicit separation from the next-idea ideation skill; distinct triggers and role boundaries leave only minor overlap risk with general CI/PR skills.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
breaking-brake/cc-wf-studio
Reviewed

Table of Contents

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.