CtrlK
BlogDocsLog inGet started
Tessl Logo

build-something-ask

Use when the user has an idea for an app, tool, or feature and wants to be interviewed in depth first — answering structured clarifying questions until the requirements are fully pinned down — before it gets built end-to-end. Triggers - "ask me questions then build", "interview me about my idea", "help me spec this out and build it", vague ideas the user wants to shape interactively.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

A highly actionable, well-sequenced build pipeline with strong validation checkpoints and lean directive prose. The only weak spot is progressive disclosure: all detail lives in one long monolithic SKILL.md with no reference files to offload depth.

Suggestions

Split the detailed per-step schemas (ledger template, story schema, evidence format contract) into a reference file such as references/templates.md and link to it from SKILL.md to reduce monolithic length.

Move the Adversary subagent lifecycle rules (4.1 step 5) and attempt-accounting table into a separate references/verification.md, keeping SKILL.md as a concise overview pointing one level deep.

Extract the Step 4.2 sweep checklist and 4.3 quality bar into references/sweeps.md so the core delivery loop stays scannable.

DimensionReasoningScore

Conciseness

The body is dense and directive, assuming Claude's competence ('Embody the senior engineer', 'answers are LAW') with no padding explaining concepts Claude already knows; every section earns its place for a genuinely complex multi-phase pipeline.

3 / 3

Actionability

Provides exact file layouts, a copy-paste ledger template, story schemas, a mandatory evidence format contract ('COMMAND:'/'EXIT_CODE:'), and exact commands like 'git log --grep "^US-<n>:"' — fully executable guidance.

3 / 3

Workflow Clarity

Clear sequenced phases (Step 0→4) with explicit validation checkpoints (citation-sync, Adversary re-run, regression and commit-integrity sweeps) and feedback loops (fail→fix→re-prove with attempt accounting).

3 / 3

Progressive Disclosure

Well-organized into clear sections but is a single ~190-line monolithic file with no bundle files or external references to split detail into; it exceeds the 50-line simple-skill threshold so well-organized sections alone do not reach 3.

2 / 3

Total

11

/

12

Passed

Description

100%

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 specific, third-person, and supplies both an explicit 'Use when' trigger and natural user-spoken phrases. It clearly delineates a niche (interview-then-build) with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'interviewed in depth', 'answering structured clarifying questions', 'requirements are fully pinned down', 'built end-to-end' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what (interview then build end-to-end) and when via a leading 'Use when' clause with concrete trigger guidance.

3 / 3

Trigger Term Quality

Provides natural quoted phrases a user would actually say — 'ask me questions then build', 'interview me about my idea', 'help me spec this out and build it' — plus 'vague ideas the user wants to shape interactively'.

3 / 3

Distinctiveness Conflict Risk

The 'interview-first, then build' niche is distinct with its own triggers, making overlap with pure-build or pure-interview skills unlikely.

3 / 3

Total

12

/

12

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
cindulasai/build-something
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.