CtrlK
BlogDocsLog inGet started
Tessl Logo

contribute

Guide for contributing to Trellis documentation and marketplace. Covers adding spec templates, marketplace skills, documentation pages, and submitting PRs across both the Trellis main repo and docs repo. Use when someone wants to add a new spec template, add a new skill to the marketplace, add or update documentation pages, or submit a PR to this project.

72

Quality

88%

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

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced contribution guide with concrete examples and a pre-PR checklist. Its main weaknesses are length/repetition and the absence of any reference files to offload detail from the monolithic body.

Suggestions

Extract the full docs.json example and MDX component reference into a references/ file, keeping SKILL.md as a concise overview that links out one level deep.

Consolidate the repeated 'update docs.json navigation + update overview page + bilingual sync' steps into a single shared subsection referenced by each contribution type to reduce repetition.

Tighten or trim the large docs.json navigation block to the minimal shape needed to show where new pages are inserted.

DimensionReasoningScore

Conciseness

The ~415-line body is mostly efficient and free of concepts Claude already knows, but it repeats the 'update navigation in docs.json' / 'update overview page' / 'Do the same for Chinese' pattern per contribution type and includes a large full docs.json block that could be tightened.

2 / 3

Actionability

Provides copy-paste-ready guidance: concrete directory trees, index.json registration snippets, frontmatter, and executable commands (e.g. 'npx skills add ...', 'cp showcase/template.mdx ...', 'pnpm dev').

3 / 3

Workflow Clarity

Each contribution path uses a clear numbered sequence, reinforced by a 'Checklist Before PR' and a verify feedback loop ('pnpm verify', 'verify-docs.py checks docs.json and frontmatter').

3 / 3

Progressive Disclosure

Sections and tables are well organized, but the skill ships no reference files and keeps all detail (full docs.json example, MDX components, dev setup) inline in one long file, so content that could be split out is not.

2 / 3

Total

10

/

12

Passed

Description

100%

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 states concrete contribution actions and pairs them with an explicit 'Use when' trigger covering the skill's full scope. It is distinctive and unlikely to fire for unrelated skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'adding spec templates, marketplace skills, documentation pages, and submitting PRs' — matching the score-3 anchor of several specific concrete actions rather than the score-2 'some actions'.

3 / 3

Completeness

Explicitly answers both what ('Guide for contributing... Covers adding...') and when ('Use when someone wants to...'), with an explicit trigger clause, satisfying the score-3 anchor and avoiding the missing-trigger cap at 2.

3 / 3

Trigger Term Quality

The 'Use when' clause surfaces natural phrases users would say ('add a new spec template', 'add a new skill to the marketplace', 'add or update documentation pages', 'submit a PR'), giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Scoped narrowly to 'Trellis documentation and marketplace' / 'this project' with distinct, project-specific triggers, making conflict with other skills unlikely.

3 / 3

Total

12

/

12

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.