CtrlK
BlogDocsLog inGet started
Tessl Logo

trellis-meta

Understand and customize the local Trellis architecture inside a user project. Use when modifying .trellis plus platform hooks, settings, agents, skills, commands, prompts, workflows, the channel runtime (trellis channel), bundled runtime agents under .trellis/agents/, selectable workflow templates, registry-backed spec refresh, cross-session memory (trellis mem) generated by trellis init, or AI-facing bundled skills (trellis-channel, trellis-session-insight, trellis-spec-bootstrap) and bundled-skill auto-dispatch flow.

68

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is trellis-meta in mindfold-ai/Trellis

SKILL.md
Quality
Evals
Security

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 well-organized, highly actionable orientation skill with concrete commands, paths, and config keys and a clear reading order. Its main weaknesses are two dead reference links (multi-agent-channel.md and bundled-skills.md are cited but absent from the bundle) and validation guidance that sits in Do Not rules rather than being wired into the numbered workflow.

Suggestions

Add the missing bundle files references/local-architecture/multi-agent-channel.md and references/local-architecture/bundled-skills.md (or remove/fix the citations at lines 26, 41, and 42) so the 'How To Use' reading path does not dead-end.

Fold the key validation guardrails (check .trellis/.template-hashes.json before overwriting, cross-check config.yaml and 'trellis --help' before claiming a knob, treat local files as authoritative) directly into the numbered How To Use steps as explicit checkpoints so destructive edits get a validate-before-act loop.

Tighten the v0.6 prose paragraph and de-duplicate content that already appears in the frontmatter description to lift conciseness toward the top anchor.

DimensionReasoningScore

Conciseness

The body is dense and substantive with no padding about concepts Claude already knows (no 'what is a hook'), but the long v0.6 prose paragraph and some overlap between the frontmatter description and the opening paragraph are minor instances of over-explanation that could be trimmed, matching the 'efficient; minor instances that could be trimmed' anchor.

4 / 5

Actionability

It gives fully concrete, executable guidance throughout: real CLI commands ('trellis workflow --template <id>', 'trellis channel spawn --agent <name>', 'task.py create --parent <slug>', 'trellis mem search|extract|context'), exact paths, and specific config keys ('channel.worker_guard.idle_timeout', 'codex.dispatch_mode'), so an instruction-only skill's absence of code is not penalized.

5 / 5

Workflow Clarity

'How To Use' is a clear numbered 1-5 reading/decision sequence and validation guardrails exist (read actual files before editing, cross-check config.yaml and 'trellis --help' before claiming a knob, check .trellis/.template-hashes.json before overwriting), but those checkpoints live in the Current Rules/Do Not sections rather than being integrated into the numbered workflow, leaving minor validation gaps.

4 / 5

Progressive Disclosure

Structure is otherwise good (clear sections, ~21 references one level deep, each with a one-line description, a 'How To Use' reading order), but two referenced files do not exist in the bundle: references/local-architecture/multi-agent-channel.md (cited at lines 26 and 41) and bundled-skills.md (cited at line 42), so navigation breaks for the channel/bundled-skill paths, exceeding the 'minor organization gaps' of the next anchor.

3 / 5

Total

16

/

20

Passed

Description

90%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, comprehensive, third-person description with an explicit 'Use when' trigger clause and a clear, distinct Trellis-specific niche. Its only weakness is that the actions ('understand', 'customize') are generic verbs riding on top of a long list of targets rather than several concrete named actions.

Suggestions

Replace or supplement the generic verbs 'Understand and customize' with a few concrete actions the skill performs (e.g., 'edit .trellis/workflow.md', 'add or change platform hooks and sub-agents', 'refresh registry-backed specs') to lift specificity toward the top anchor.

The trigger list is thorough but very long; consider grouping surfaces (workflow / platform / channel / memory) so a reader can scan the 'when' clause faster without losing coverage.

DimensionReasoningScore

Specificity

The description names the Trellis domain exhaustively ('.trellis', platform hooks, settings, agents, skills, commands, prompts, workflows, channel runtime, bundled runtime agents, workflow templates, spec refresh, cross-session memory, bundled skills) but only offers two generic verbs ('Understand and customize') rather than several specific actions, matching the anchor that names the domain with only 1-2 actions.

3 / 5

Completeness

It explicitly answers 'what' ('Understand and customize the local Trellis architecture inside a user project') and 'when' with an explicit 'Use when modifying ...' clause enumerating concrete trigger surfaces, matching the anchor for clearly answering both what and when with concrete trigger phrases.

5 / 5

Trigger Term Quality

It gives comprehensive, product-specific trigger terms a Trellis user would naturally say ('modify .trellis', 'platform hooks', 'agents', 'skills', 'commands', 'trellis channel', 'trellis mem', 'trellis init') including synonyms (skills/commands/prompts/workflows listed separately) and file paths (.trellis, .trellis/agents/), matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

The triggers are highly product-specific (.trellis, trellis channel, trellis mem, named bundled skills trellis-channel/trellis-session-insight/trellis-spec-bootstrap), carving a clear niche with minimal chance of firing for unrelated skills.

5 / 5

Total

18

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 missing, 27 deeper-than-1-level

Warning

Total

15

/

16

Passed

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.