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.

70

Quality

86%

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

86%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, actionable meta-skill with a clear sequenced workflow, concrete commands and paths, and excellent progressive disclosure through verified reference files. Minor tightening of redundant intro material and an explicit feedback loop would lift it further.

DimensionReasoningScore

Conciseness

Dense, information-rich body that assumes Claude's competence (no explaining what hooks/skills/agents are) and earns most of its tokens; minor redundancy between the v0.6 intro paragraph and the Current Rules section keeps it just below the lean anchor 5.

4 / 5

Actionability

Highly actionable for an instruction-only skill: concrete CLI commands ('trellis channel spawn --agent <name>', 'trellis mem list | search | context | extract | projects', 'task.py create --parent <slug>', 'trellis workflow --template <id>'), exact file paths, and specific config keys (hooks.after_create, channel.worker_guard.idle_timeout, codex.dispatch_mode) cover the common cases.

5 / 5

Workflow Clarity

The 'How To Use' section gives a clear 5-step sequenced navigation procedure with a verification checkpoint ('read the actual files... treat local content as authoritative'), and the Do Not section adds validation (check .template-hashes.json, cross-check trellis --help); no explicit validate->fix->retry feedback loop, so it sits at 4 rather than 5.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview pointing to well-signaled, one-level-deep references organized into three labeled categories (Local Architecture, Platform Files, Local Customization), each file described and verified present; navigation is easy and content is appropriately split.

5 / 5

Total

18

/

20

Passed

Description

87%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, explicit description that clearly states both capability and trigger conditions with concrete Trellis-specific surfaces. It is comprehensive and distinct, with only minor verbosity from jargon-heavy trigger terms.

DimensionReasoningScore

Specificity

Names the domain ('local Trellis architecture') and concrete actions ('Understand and customize') applied to many specific surfaces (.trellis, platform hooks, settings, agents, skills, commands, prompts, workflows, channel runtime, bundled agents, workflow templates, spec refresh, cross-session memory, bundled skills); only two action verbs keeps it just below the comprehensive multi-action anchor 5.

4 / 5

Completeness

Explicitly answers both 'what' ('Understand and customize the local Trellis architecture inside a user project') and 'when' ('Use when modifying .trellis plus platform hooks, settings, agents, skills, commands, prompts, workflows...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

The 'Use when modifying...' clause covers natural terms (hooks, settings, agents, skills, commands, prompts, workflows) plus tool names (trellis channel, trellis mem, trellis init); good coverage, though heavy on jargon like 'registry-backed spec refresh' and 'bundled-skill auto-dispatch flow' that users would rarely say verbatim.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear Trellis-only niche with distinct triggers (.trellis, trellis channel, trellis mem, bundled skills) and minimal conflict risk with 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: 27 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
EcoPasteHub/EcoPaste
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.