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

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

73%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 highly actionable, well-structured contribution guide with concrete templates, commands, and a pre-PR checklist. Its main weakness is verbosity from duplicated EN/ZH examples and the absence of an explicit verification step before PR submission despite batch bilingual edits.

Suggestions

Show one language variant (e.g., English) in each JSON/code example and state the zh/ prefix rule once, instead of repeating both EN and ZH blocks verbatim.

Add an explicit validation checkpoint to each workflow — e.g., 'Run pnpm verify and pnpm lint:md; confirm EN/ZH pages are in sync before committing' — before the push/PR step.

Collapse the full docs.json navigation listing into a shorter representative excerpt and reference the existing file for the complete structure to reduce inline bulk.

Dimension	Reasoning	Score
Conciseness	The body is accurate and well-organized but lengthy (~420 lines) with repeated JSON snippets for EN and ZH variants and verbose directory trees; it could be tightened by showing one language variant and noting the zh/ prefix pattern once.	3 / 5
Actionability	It provides fully concrete, copy-paste-ready guidance: exact directory layouts, index.json entries with real fields, navigation JSON blocks, shell commands (cp, pnpm), and MDX/Card examples covering each common contribution case.	5 / 5
Workflow Clarity	Each contribution type (spec template, skill, showcase, docs) is laid out as a numbered, sequenced workflow with a closing 'Checklist Before PR', but the bilingual/batch operations lack an explicit validation checkpoint (e.g., verifying zh/ parity or running pnpm verify) before submitting.	4 / 5
Progressive Disclosure	The body is a single overview file with no bundle references, organized into clear per-task sections with inline JSON/code blocks; appropriate for a single-file skill, though some long repeated EN/ZH blocks could be collapsed to tighten navigation.	4 / 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 description that pairs a concrete capability list with an explicit 'Use when...' trigger clause covering the four main contribution types. Trigger-term naturalness and minor PR-trigger overlap are the only things keeping it from a perfect mark.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete actions — adding spec templates, adding marketplace skills, adding/updating documentation pages, and submitting PRs — across both the Trellis main repo and docs repo, giving comprehensive coverage.	5 / 5
Completeness	It explicitly answers 'what' (guide for contributing spec templates, marketplace skills, docs pages, and PRs across two repos) and 'when' ('Use when someone wants to add...'), satisfying both halves with concrete triggers.	5 / 5
Trigger Term Quality	The 'Use when...' clause lists natural user requests ('add a new spec template', 'add a new skill to the marketplace', 'submit a PR'), but it relies on paraphrased full phrases rather than crisp natural shorthand or synonyms a user would casually say.	4 / 5
Distinctiveness Conflict Risk	The Trellis-specific framing (spec templates, marketplace skills, docs repo) carves a clear niche, but the broad 'submitting a PR' trigger could overlap marginally with a general PR/commit skill.	4 / 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: .agents/skills/contribute/SKILL.md
Commit: 88f4834

Reviewed: 8 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.