CtrlK
BlogDocsLog inGet started
Tessl Logo

cursor-agent-supervisor

Offloading tasks with a well-defined scope to sub-agents, for instance to use a sub-agent to implement a set of specs. Use this skill whenever a task should not need a broad knowledge of the whole project

90

1.59x
Quality

87%

Does it follow best practices?

Impact

91%

1.59x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 strong, lean, highly actionable skill with clear sequenced workflows, explicit verification checkpoints, and error-recovery guidance. It is well-structured and self-contained with no disclosure problems.

DimensionReasoningScore

Conciseness

The body is lean and instructional, using terse command snippets and compact do/don't lists without explaining concepts Claude already knows; nearly every token earns its place, matching the level-3 anchor despite a little emphasis-fluff ("YOU are in charge of bookkeeping, not them").

3 / 3

Actionability

It gives fully executable commands ("cursor-agent --print --model <model-name> create-chat", "cursor-agent --print --resume <conversation-uuid>\"...\""), a concrete model default (sonnet-4.5), a specific timeout value (600000), and a copy-paste-ready task template, matching the level-3 anchor.

3 / 3

Workflow Clarity

The multi-step process is clearly sequenced (start subagent, model selection, invocation, setup, instructions, verification) with an explicit validation checklist in "After Sub-agent Completes" and feedback loops in "When Things Go Wrong" (fix and retry, revert and retry with tighter constraints), matching the level-3 anchor.

3 / 3

Progressive Disclosure

This is a self-contained single-file skill with no external references and no nested/deep references, organized into clearly headed sections; per the simple-skill guidance, well-organized sections suffice for a level-3 score.

3 / 3

Total

12

/

12

Passed

Description

75%

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 clearly covers both what the skill does and when to use it, with a distinct sub-agent delegation niche. Its main weakness is moderate specificity and trigger-term breadth rather than any structural gap.

DimensionReasoningScore

Specificity

It names the domain and a concrete action ("use a sub-agent to implement a set of specs", "Offloading tasks with a well-defined scope to sub-agents"), but does not enumerate multiple specific actions as in the level-3 example, so it sits at level 2 rather than 3.

2 / 3

Completeness

It explicitly answers both what ("Offloading tasks with a well-defined scope to sub-agents...to implement a set of specs") and when ("Use this skill whenever a task should not need a broad knowledge of the whole project"), with an explicit "Use this skill whenever..." trigger, matching the level-3 anchor.

3 / 3

Trigger Term Quality

Terms like "sub-agents", "specs", and "well-defined scope" are reasonably natural, but coverage is narrow and misses common variations a user might say (e.g. "delegate", "spawn", "parallelize"), matching the level-2 anchor rather than full level-3 coverage.

2 / 3

Distinctiveness Conflict Risk

The trigger is tied to a specific mechanism (sub-agents) and a distinct gating condition (tasks not needing broad project knowledge), giving it a clear niche unlikely to fire for unrelated skills; it is not the generic "works with document files" style of level 2.

3 / 3

Total

10

/

12

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
YPares/agent-skills
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.