CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

build

Workflow orchestrator that chains existing skills for feature development

Quality

63%

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 ./.claude/skills/build/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

58%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 strong operational spec with excellent workflow sequencing, explicit checkpoints, and error-recovery loops, but it is a monolith: large, self-referential chunks (question flows, example transcripts, triple-defined chains) should live in reference files. Trimming duplication and splitting the illustrative material would materially cut token cost without losing actionability.

Suggestions

Define the skill chains once (the Modes table or the CHAINS dict) and derive the other presentations from it, removing the triplicated chain definitions and the Phase-0 option labels that restate them.

Move the three example sessions and the full question-flow YAML (including per-phase 'If Answer is Unclear' blocks) into references/ files (e.g. references/example-sessions.md, references/question-flow.md) and link to them from a short overview.

Replace '[Contents of X SKILL.md]' placeholders with a concrete instruction for how to load or inline sub-skill content, so the Task() templates are fully executable as written.

DimensionReasoningScore

Conciseness

The ~840-line body is noticeably padded: the skill chains are defined three times (Modes table, Phase-0 option labels, CHAINS python dict), every question phase carries a full 'If Answer is Unclear' YAML block, and ~150 lines of example-session transcripts restate what the orchestration steps already specify. Not 1 because it does not explain concepts Claude already knows; the padding is operational duplication rather than background.

2 / 5

Actionability

Concrete, mostly executable guidance throughout: real bash for session setup and orchestration.yaml creation, exact Task() prompt templates per skill, option-to-chain mutation rules, and specific error menus. Not 5 because placeholders like '[Contents of discovery-interview SKILL.md]', '<session>', and '<kebab-description>' prevent copy-paste readiness and leave gaps in how sub-skill contents are assembled.

4 / 5

Workflow Clarity

Steps 0-4 are clearly sequenced with explicit human checkpoints after plan-agent, validate-agent, and each implementation task, automated verification checklists, error-recovery feedback loops (retry/skip/abort/manual), and resume support reading orchestration.yaml. This matches the top anchor: clear sequence, explicit validation steps, and feedback loops for error recovery.

5 / 5

Progressive Disclosure

There are no reference files at all; everything (question flows, skill execution templates, three long example sessions, troubleshooting) is inlined in one monolithic SKILL.md. Content that clearly belongs in separate files (e.g. the example sessions and the full question-flow YAML) is inlined, matching anchor 2. Not 3 because there are no references to signal, and not 1 because section headers and a Related Skills list do provide some navigability.

2 / 5

Total

13

/

20

Passed

Description

53%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 states a clear, third-person 'what' but stops there. It reads more like a category label than an invocation guide: no trigger conditions, no enumeration of the modes it supports, and no natural user vocabulary beyond generic terms. Adding a 'Use when...' clause and naming the workflows (greenfield, brownfield, TDD, refactor) would move it up two anchors on completeness and trigger quality.

Suggestions

Add a 'Use when...' trigger clause, e.g. 'Use when the user asks to build, add, or refactor a feature and wants a multi-phase workflow rather than a single skill.'

Enumerate the concrete capabilities in the description (chains discovery → planning → validation → implementation → commit → PR across greenfield, brownfield, TDD, and refactor modes) to raise specificity.

Include natural user phrasing such as 'build a feature', 'new feature', 'test-first', or 'refactor this' instead of only jargon like 'orchestrator' and 'chains existing skills'.

DimensionReasoningScore

Specificity

"Workflow orchestrator that chains existing skills for feature development" names the domain (feature development) and one concrete action ("chains existing skills"), matching the anchor for 1-2 concrete actions without comprehensive coverage. Not 4 because it omits the several specific actions the body actually supports (greenfield chains, TDD, refactoring, PR creation).

3 / 5

Completeness

The 'what' is clear (chains existing skills for feature development), but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. Not 2 because the 'what' half is concrete rather than vague.

3 / 5

Trigger Term Quality

Terms like "workflow", "feature development", and "skills" are somewhat relevant, but the description misses the natural phrases a user would say ("build a feature", "new feature", "refactor", "TDD") and leans on jargon like "orchestrator" and "chains". Not 4 because natural keyword coverage has clear gaps, even though the frontmatter keywords list (build, greenfield, tdd, refactor) is not part of the description itself.

3 / 5

Distinctiveness Conflict Risk

The orchestrator niche (chaining other skills for feature development) is mostly distinct with only minor overlap risk against closely related skills like plan-agent or implement_plan. Not 5 because 'feature development' is broad enough that a plain feature-request could plausibly route here instead of to a single-purpose skill.

4 / 5

Total

13

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (844 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

parcadei/Continuous-Claude-v3

Path

.claude/skills/build/SKILL.md

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.