contributing-guide-creator
Contributing Guide Creator - Auto-activating skill for Technical Documentation. Triggers on: contributing guide creator, contributing guide creator Part of the Technical Documentation skill category.
36
Quality
3%
Does it follow best practices?
Impact
98%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/17-technical-docs/contributing-guide-creator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder with no substantive content. It relies entirely on the skill name without explaining capabilities, use cases, or providing meaningful trigger terms. The redundant trigger terms and lack of any action verbs make this description nearly useless for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Generates CONTRIBUTING.md files with sections for code style, pull request process, issue reporting, and development setup instructions.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks about contribution guidelines, CONTRIBUTING.md, contributor documentation, how to contribute, or open source contribution setup.'
Remove redundant trigger terms and add variations users would naturally say: 'contributing guidelines', 'contributor guide', 'open source contributions', 'PR guidelines'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Contributing Guide Creator' and 'Technical Documentation' without describing any concrete actions. There are no verbs indicating what the skill actually does (e.g., generates, creates, formats). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when should Claude use it' guidance. The 'Triggers on' field is not a proper 'Use when...' clause with contextual guidance. | 1 / 3 |
Trigger Term Quality | The triggers listed are redundant ('contributing guide creator' repeated twice) and overly specific. Missing natural variations users would say like 'CONTRIBUTING.md', 'contribution guidelines', 'how to contribute', 'contributor docs'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'contributing guide' is somewhat specific to a particular document type, the vague 'Technical Documentation' category could overlap with README creators, API doc generators, or other documentation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no actual instructional content. It consists entirely of generic boilerplate describing what the skill supposedly does without providing any concrete guidance on how to create contributing guides. There are no examples, templates, sections to include, or actionable steps.
Suggestions
Add a concrete contributing guide template with specific sections (Prerequisites, Development Setup, Code Style, Pull Request Process, etc.)
Include executable examples showing how to generate or structure a CONTRIBUTING.md file with actual content
Define a clear workflow: 1) Analyze project type, 2) Identify required sections, 3) Generate content, 4) Validate completeness
Remove all meta-description content ('This skill provides...', 'Capabilities include...') and replace with actual instructional content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about creating contributing guides. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens. | 1 / 3 |
Actionability | No concrete guidance whatsoever - no examples of contributing guide structure, no templates, no specific sections to include, no code or commands. The skill describes what it does rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for creating a contributing guide, no validation checkpoints, and no process to follow. The content is purely descriptive meta-information. | 1 / 3 |
Progressive Disclosure | No structure for progressive disclosure - no references to detailed materials, no links to examples or templates, and no organization beyond generic section headers that contain no useful content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
0c08951
- 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.