CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-factory

Run a full build-and-ship pipeline from a spec — use for hands-off project generation

Quality

73%

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/skill-factory/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A strongly structured procedural contract: an unambiguous 8-step sequence with concrete, executable commands, explicit validation gates, and thorough failure handling. Its main weaknesses are moderate redundancy (inline error handling repeated in a summary section, duplicated prohibition lists) and a long inline scenario-review prompt that could be externalized.

DimensionReasoningScore

Conciseness

The body is mostly commands and directives, but Step 4.5's justification prose ('A quick cross-provider challenge here can prevent wasting an entire factory run'), the Error Handling section restating per-step failure behavior already given inline, and Prohibited Actions duplicating the HARD-GATE list could be tightened.

3 / 5

Actionability

Nearly every step supplies concrete bash ('orchestrate.sh factory --spec "<spec_path>"', state-manager calls, find commands for the report and scores files) plus explicit flag mappings and AskUserQuestion options; minor gaps remain such as banner placeholders and template variables that keep it from being fully copy-paste ready.

4 / 5

Workflow Clarity

The 8-step sequence is explicitly numbered with validation gates in Steps 3, 5, and 6, stop conditions ('DO NOT proceed past this gate'), feedback loops (--max-retries, 'fix and re-validate' guidance in next steps), and a per-step error-handling map — squarely the top anchor; the batch-operation cap does not apply because validation is pervasive.

5 / 5

Progressive Disclosure

No bundle files exist and the body is well-sectioned with the heavy pipeline logic correctly externalized to referenced plugin scripts via explicit paths; only the inlined QA-adversary prompt in Step 4.5 (~20 lines) arguably belongs in a separate reference file, which keeps it below the top anchor.

4 / 5

Total

16

/

20

Passed

Description

62%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 compact, in third-person imperative voice, and answers both what the skill does and when to use it. It is under-specified on the action list (one composite action instead of several concrete ones) and on trigger vocabulary, relying on a few abstract phrases rather than the natural terms users would say.

Suggestions

Enumerate the concrete pipeline actions instead of one composite verb, e.g. 'Parses an NLSpec, generates test scenarios, implements the project via multi-provider agents, evaluates against a holdout, and reports a satisfaction score.'

Add natural trigger phrases users would actually say, such as 'Use when the user asks to build/generate a project from a spec, hands-off or autonomously, or mentions NLSpec.'

Mention the input artifact type ('NLSpec file') and the distinctive outputs (factory report, satisfaction score) to sharpen distinctiveness against generic scaffolding skills.

DimensionReasoningScore

Specificity

'Run a full build-and-ship pipeline from a spec' names the domain (spec-driven project generation) and 1-2 actions (build, ship), but enumerates no further concrete actions, matching 'Names domain and 1-2 concrete actions, but not comprehensive' rather than the several-action anchor above.

3 / 5

Completeness

It answers both parts: a clear 'what' ('Run a full build-and-ship pipeline from a spec') and an explicit 'use for...' clause ('use for hands-off project generation'), though the when is abstract rather than phrased as concrete user triggers, so it sits at 'both present, when could be more explicit' instead of the top anchor.

4 / 5

Trigger Term Quality

It includes some natural keywords ('spec', 'build-and-ship', 'hands-off', 'project generation') but misses common variations and synonyms a user might say, such as 'scaffold', 'implement from spec', 'NLSpec', or 'autonomous build', fitting 'Some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

'build-and-ship pipeline from a spec' carves a recognizable niche with minimal overlap risk, though it could still collide with generic project-scaffolding or build-automation skills, matching 'Mostly distinct; minor overlap risk with closely related skills'.

4 / 5

Total

14

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

nyldn/claude-octopus

Path

.claude/skills/skill-factory/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.