CtrlK
BlogDocsLog inGet started
Tessl Logo

trellis-before-dev

Discovers and injects project-specific coding guidelines from .trellis/spec/ before implementation begins. Reads spec indexes, pre-development checklists, and shared thinking guides for the target package. Use when starting a new coding task, before writing any code, switching to a different package, or needing to refresh project conventions and standards.

69

Quality

83%

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

75%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 compact, actionable pre-development workflow with concrete discovery commands and a clear sequence. It would benefit from a verification checkpoint and trimming minor filler.

Suggestions

Add an explicit validation step (e.g., 'Confirm you have read every file in the Pre-Development Checklist before proceeding') to serve as a hard gate.

Replace the abstract step 4 with a concrete command or glob example for reading the listed guideline files.

Drop the redundant closing 'mandatory' line and step 6 filler; the numbered workflow already implies proceeding.

DimensionReasoningScore

Conciseness

The body is mostly lean with executable commands and no concept over-explanation, but step 6 ('Understand the coding standards... then proceed') and the closing 'mandatory' line could be trimmed.

4 / 5

Actionability

Provides concrete, executable commands (get_context.py, cat index.md) for discovery, though step 4 ('Read the specific guideline files') stays abstract without a command.

4 / 5

Workflow Clarity

Six clearly numbered steps form a coherent pre-development sequence with a 'mandatory before writing any code' gate, but there are no explicit validation checkpoints beyond that gate.

4 / 5

Progressive Disclosure

Short, self-contained body (~30 lines) organized into numbered steps with no bundle files needed; lacks section headers, leaving minor organization gaps.

4 / 5

Total

16

/

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, third-person description that explicitly answers both what the skill does and when to use it, anchored to a specific project convention directory. Trigger phrasing is natural though slightly short on synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Discovers and injects project-specific coding guidelines', 'Reads spec indexes, pre-development checklists, and shared thinking guides' — covering the workflow comprehensively.

5 / 5

Completeness

Clearly states what it does ('Discovers and injects...Reads spec indexes...') and gives an explicit 'Use when' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural triggers like 'starting a new coding task', 'before writing any code', 'switching to a different package' map to user phrasing, but synonym coverage is good rather than exhaustive.

4 / 5

Distinctiveness Conflict Risk

The '.trellis/spec/' niche and pre-implementation trigger phrasing make it clearly distinct with minimal overlap risk against 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.