CtrlK
BlogDocsLog inGet started
Tessl Logo

engineer-subagent

Guide for creating effective Subagents (custom agent definitions). Use when users want to create a new subagent, set up task-specific agents, configure code reviewers, debuggers, or domain-specific assistants. Works across IDEs (Cursor, OpenCode).

65

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/flowai-devtools/skills/engineer-subagent/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 highly actionable and well-sequenced, with concrete templates, path tables, and a clear multi-phase workflow. It loses points for verbosity in conceptual sections and for keeping all detail inline rather than splitting examples and references into separate files.

Suggestions

Move the four full subagent example templates and the frontmatter field-reference tables into separate files under references/ and link to them, reducing SKILL.md to a lean overview.

Trim or cut "About Subagents" and "Comparison with Skills" — these restate concepts Claude already knows and pad the token budget.

Add an explicit validate→fix→retry feedback loop in Phase 4 (e.g., re-check the YAML frontmatter and trigger the subagent before declaring it done).

DimensionReasoningScore

Conciseness

Mostly efficient with tables, frontmatter specs, and copy-paste examples, but sections like "About Subagents" and "Comparison with Skills" explain concepts Claude already knows and the ~280-line body could be tightened.

3 / 5

Actionability

Provides fully executable, copy-paste-ready guidance: exact file paths per IDE, YAML frontmatter templates, mkdir/touch commands, and four complete example subagent .md files covering common cases.

5 / 5

Workflow Clarity

A clear five-phase Discovery→Design→Implementation→Verification→Iterate sequence with a Phase 4 verification checklist; not a 5 because the verification step lacks an explicit validate→fix→retry feedback loop.

4 / 5

Progressive Disclosure

Well-sectioned and navigable, but monolithic: four full subagent templates and detailed field-reference tables are inlined in SKILL.md with no references to separate bundle files, and no bundle files exist.

3 / 5

Total

15

/

20

Passed

Description

87%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 strong: it clearly states what the skill does and when to use it with concrete, natural trigger terms and a distinct niche. Minor gaps in synonym coverage keep specificity and trigger_term_quality just below the top anchor.

DimensionReasoningScore

Specificity

Lists several concrete actions — "create a new subagent, set up task-specific agents, configure code reviewers, debuggers, or domain-specific assistants" — but they are variations of one create/configure verb rather than the breadth of a score-5 anchor.

4 / 5

Completeness

Explicitly answers both what ("Guide for creating effective Subagents") and when ("Use when users want to create a new subagent, set up task-specific agents, configure code reviewers, debuggers...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user phrases like "create a new subagent", "set up task-specific agents", "configure code reviewers, debuggers" are present, but synonym/extension coverage is incomplete (e.g., no mention of Claude Code despite the body covering it).

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche — authoring subagent definitions — with specific triggers unlikely to fire for unrelated skills, giving minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
korchasa/flowai-plugins
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.