CtrlK
BlogDocsLog inGet started
Tessl Logo

trellis-spec-bootstrap

Bootstrap project-specific Trellis coding specs with a platform-neutral single-agent workflow. Use when creating or refreshing .trellis/spec guidelines, analyzing a codebase with GitNexus, ABCoder, or source inspection, decomposing package/layer spec work, and writing real codebase-backed spec docs without placeholder text.

75

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 well-structured, token-efficient instruction skill: lean body, explicit verification step, and a clean routing table to real reference files. The only minor gap is that concrete execution detail lives in references rather than inline, keeping actionability at 4.

DimensionReasoningScore

Conciseness

Lean and efficient: no preamble explaining what specs or tools are; every line is instruction, routing, or a rule. Every token earns its place, matching the score-5 anchor.

5 / 5

Actionability

Guidance is concrete and actionable (named tools, file paths, real examples, anti-patterns) but delegates specific execution detail to reference files, leaving minor gaps versus the fully copy-paste-ready score-5 anchor.

4 / 5

Workflow Clarity

A clearly sequenced 5-step workflow with an explicit validation step (step 5: verify internal consistency, no placeholders) and a Done Criteria checklist acting as a feedback loop, matching the score-5 anchor.

5 / 5

Progressive Disclosure

Clear overview with a Reference Routing table mapping each need to a one-level-deep reference file; all four referenced files exist and are well-signaled, matching the score-5 anchor.

5 / 5

Total

19

/

20

Passed

Description

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

A strong description: it states a concrete purpose, lists several specific actions, and provides an explicit 'Use when' clause with natural trigger terms. Minor room for additional synonyms keeps trigger-term quality at 4 rather than 5.

DimensionReasoningScore

Specificity

Names multiple concrete actions (creating/refreshing .trellis/spec guidelines, analyzing with GitNexus/ABCoder/source inspection, decomposing package/layer work, writing codebase-backed docs) — comprehensive coverage matching the score-5 anchor.

5 / 5

Completeness

Clearly answers 'what' (bootstrap project-specific Trellis coding specs via single-agent workflow) and explicitly answers 'when' with concrete 'Use when...' trigger phrases, matching the score-5 anchor.

5 / 5

Trigger Term Quality

Good keyword coverage with natural trigger phrases ('Use when creating or refreshing', 'analyzing a codebase') and concrete tool names, but missing a few common synonyms/variants, landing between the 4 and 5 anchors.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Trellis spec bootstrapping) with distinctive triggers (GitNexus, ABCoder, .trellis/spec) and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mindfold-ai/Trellis
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.