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

1.59x

Quality

62%

Does it follow best practices?

Impact

91%

1.59x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./cursor-agent-supervisor/SKILL.md

Quality

Content

100%

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

This is a high-quality skill that efficiently teaches Claude how to supervise sub-agents. It provides concrete commands, a useful task template, clear workflow sequencing with validation checkpoints, and practical error recovery guidance. The content respects Claude's intelligence while providing non-obvious operational details like timeout requirements and model discovery.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It doesn't explain what sub-agents are conceptually or waste tokens on things Claude already knows. Every section provides actionable, non-obvious information like the timeout requirement, model selection trick, and the task template.	3 / 3
Actionability	Provides concrete, executable commands for creating and resuming sub-agent conversations, includes the specific timeout value needed, gives a copy-paste task description template, and lists explicit verification steps. The model discovery trick (`--model unknown-model`) is a practical, specific tip.	3 / 3
Workflow Clarity	The workflow is clearly sequenced: prepare the environment → give instructions → wait for completion → verify results. The 'After Sub-agent Completes' section provides explicit validation steps (check diff, review code, run tests), and the 'When Things Go Wrong' section provides error recovery feedback loops.	3 / 3
Progressive Disclosure	For a skill with no bundle files, the content is well-organized into logical sections (Model Selection, Invocation, Setup, Instructions, After Completion, Error Handling) with clear headers. The content is appropriately sized for a single file and doesn't need external references. The do/don't list and template are well-structured for quick scanning.	3 / 3
	Total	12 / 12 Passed

Description

25%

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

This description suffers from vague, abstract language and lacks concrete actions or natural trigger terms. While it attempts to define a 'when' condition, the guidance is too subjective ('should not need a broad knowledge') to be actionable for skill selection. The concept of sub-agent delegation is somewhat distinctive but poorly articulated.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Spawns sub-agents to execute isolated, well-scoped tasks such as implementing feature specs, running test suites, or generating boilerplate code.'

Include natural trigger terms users would say, such as 'delegate', 'parallel tasks', 'break down work', 'run in background', 'independent task', or 'isolated implementation'.

Strengthen the 'Use when' clause with explicit, objective triggers, e.g., 'Use when the user asks to delegate a self-contained task, break work into parallel subtasks, or implement a feature that doesn't require cross-project context.'

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'offloading tasks' and 'well-defined scope' without listing concrete actions. The example of 'implement a set of specs' is a single, loosely defined action rather than multiple specific capabilities.	1 / 3
Completeness	It partially answers 'what' (delegating tasks to sub-agents) and has a 'when' clause ('whenever a task should not need a broad knowledge of the whole project'), but the 'when' guidance is vague and subjective rather than providing explicit, actionable triggers.	2 / 3
Trigger Term Quality	The description lacks natural keywords users would say. Terms like 'sub-agents', 'offloading tasks', and 'well-defined scope' are internal/technical jargon rather than terms a user would naturally use when requesting this functionality.	1 / 3
Distinctiveness Conflict Risk	The concept of sub-agent delegation is somewhat distinctive, but the description is broad enough ('offloading tasks') that it could overlap with general task management or project orchestration skills. The trigger condition is too subjective to clearly delineate when this skill applies.	2 / 3
	Total	6 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: YPares/agent-skills
Commit: bc4c2ce

Reviewed: 9 days 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.