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.

Quality

85%

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

82%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 comprehensive, highly actionable contributing guide with concrete commands, JSON snippets, and a PR checklist. Its main weaknesses are repeated navigation/registration blocks that inflate length and validation positioned as a global checklist rather than inline feedback loops per workflow.

Suggestions

Deduplicate the repeated docs.json navigation-update and index.json registration JSON blocks into a single templated example referenced by each section to improve conciseness.

Embed an explicit validation step (e.g., 'run pnpm verify; fix errors; re-run until clean') within each numbered workflow instead of relying solely on the end-of-document checklist.

Consider moving the lengthy docs.json structure and MDX component reference into a references/ file so SKILL.md acts as a leaner overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The body is project-specific and avoids explaining concepts Claude already knows, but it repeats similar navigation-update JSON snippets (Spec Templates, Skills, Showcase) and index.json registration blocks across sections. Not 5 because those repeated blocks could be tightened or templated; not 3 because the material is genuinely necessary and not padded.	4 / 5
Actionability	Provides copy-paste-ready commands (`cp showcase/template.mdx`, `npx skills add mindfold-ai/Trellis/marketplace -s your-skill`, `pnpm dev`), concrete JSON for index.json and docs.json registration, exact file paths, and frontmatter templates covering the common contribution cases.	5 / 5
Workflow Clarity	Each contribution type has a numbered 1-5 sequence, and a 'Checklist Before PR' plus `pnpm verify` and husky/verify-docs.py pre-commit hooks provide validation checkpoints. Not 5 because validation is consolidated at the end rather than embedded as explicit feedback loops (validate -> fix -> retry) within each individual workflow.	4 / 5
Progressive Disclosure	Content is organized into clear, navigable sections with well-signaled external links (Claude Code Skills docs, Mintlify docs). No bundle files (references/scripts/assets) exist, so there is nothing to progressively disclose; structure is good but the skill is a single monolithic file rather than an overview pointing to one-level-deep references. Not 5 because no reference files are used to split the substantial detail.	4 / 5
	Total	17 / 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, third-person description that clearly states what the skill covers and when to use it, with concrete contribution types and natural trigger phrasing. Minor room to broaden trigger-term synonyms and mention showcase/changelog contributions.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'adding spec templates, marketplace skills, documentation pages, and submitting PRs' — with only minor coverage gaps (e.g., showcase/changelog mentioned in body but not description). Not 5 because it does not enumerate the full range of contribution types comprehensively.	4 / 5
Completeness	Explicitly answers both 'what' ('Guide for contributing to Trellis documentation and marketplace. Covers adding spec templates, marketplace skills, documentation pages, and submitting PRs') and 'when' ('Use when someone wants to...') with concrete trigger phrases. Confirmed at 5 rather than 4 because the when-clause enumerates specific triggering scenarios.	5 / 5
Trigger Term Quality	The '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' clause gives natural phrasings a user would say. Not 5 because synonyms and variations (e.g., 'documentation', 'docs', 'contribute') are not exhaustively covered.	4 / 5
Distinctiveness Conflict Risk	Scoped to a named project ('Trellis documentation and marketplace', 'the Trellis main repo and docs repo') with distinct triggers, giving it a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	18 / 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: mindfold-ai/Trellis
Path: .claude/skills/contribute/SKILL.md
Commit: 64e6636

Reviewed: 5 days 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.