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.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%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 concise, well-sequenced preparation skill with concrete commands and clear file targets. The main weakness is the absence of any validation checkpoint confirming the relevant specs were actually located and read before proceeding.

Suggestions

Add a verification checkpoint after step 5 (e.g., confirm the Pre-Development Checklist items were all read before proceeding) to strengthen workflow clarity.

Trim the redundant framing — the intro line and the closing "This step is mandatory" sentence overlap; keep one to push conciseness toward anchor 5.

Give step 3 a concrete helper (e.g., a flag on get_context.py that lists applicable specs) so it is executable rather than a judgment step.

Dimension	Reasoning	Score
Conciseness	The body is lean with executable commands and no concept over-explanation, but the intro "Read the relevant development guidelines before starting your task", the closing "This step is mandatory before writing any code", and step 7 are mildly redundant, fitting anchor 4 rather than 5.	4 / 5
Actionability	Provides executable commands ("python3 ./.trellis/scripts/get_context.py --mode packages", "cat .trellis/spec/<package>/<layer>/index.md") and concrete file names, but steps 3 and 7 are judgment steps and the <package>/<layer> placeholders require substitution, placing it at anchor 4.	4 / 5
Workflow Clarity	A clear 7-step numbered sequence with concrete per-step actions, but no explicit validation checkpoints; since the task is read-only preparation rather than destructive/batch work, this is a minor gap at anchor 4 rather than the cap-at-3 case.	4 / 5
Progressive Disclosure	No bundle files exist and the body is under 50 lines with well-organized numbered sections; per the simple-skills note this scores 5 without external file references.	5 / 5
	Total	17 / 20 Passed

Description

83%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 that clearly states both its function and concrete trigger conditions in third person. Minor gains are possible by sharpening the action verbs and narrowing the trigger phrasing to reduce overlap with general coding-prep skills.

Suggestions

Tighten "Discovers and injects" into more concrete verbs (e.g., "Loads and applies") to push specificity toward anchor 5.

Add a Trellis-specific qualifier to the trigger clause (e.g., "Use when starting a task in a Trellis-managed repo") to reduce overlap with generic dev-prep skills.

Consider naming the spec file types users would mention (e.g., "spec indexes", "pre-dev checklists") as natural synonyms to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("Discovers and injects project-specific coding guidelines", "Reads spec indexes, pre-development checklists, and shared thinking guides"), but "discovers and injects" is slightly abstract and coverage is not exhaustive, fitting anchor 4 rather than 5.	4 / 5
Completeness	Explicitly answers both what ("Discovers and injects project-specific coding guidelines... Reads spec indexes, pre-development checklists, and shared thinking guides") and when ("Use when starting a new coding task, before writing any code, switching to a different package..."), matching the anchor-5 example.	5 / 5
Trigger Term Quality	Includes natural phrases a developer would say ("starting a new coding task", "before writing any code", "switching to a different package", "refresh project conventions and standards"), but lacks synonyms or file-extension variants, so it falls at anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	The .trellis/spec/ niche is distinct, but broad triggers like "before writing any code" and "starting a new coding task" create minor overlap with generic dev-prep skills, placing it at anchor 4 rather than a clean 5.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: EcoPasteHub/EcoPaste
Path: .claude/skills/trellis-before-dev/SKILL.md
Commit: 5139d30

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.