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
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 boilerplate template with no substantive content. It lacks concrete actions, natural trigger terms, and explicit guidance on when to use the skill. It reads more like auto-generated metadata than a useful skill description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates CONTRIBUTING.md files with sections for code style, pull request process, issue reporting, and development setup instructions.'
Add a 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a contributing guide, CONTRIBUTING.md, contribution guidelines, open source setup, or contributor documentation.'
Remove the redundant duplicate trigger term and replace with varied natural phrases users would actually say, such as 'contributing guidelines', 'how to contribute', 'contributor docs', 'open source contribution rules'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Technical Documentation') and a label ('Contributing Guide Creator') but does not describe any concrete actions. There are no specific capabilities listed such as 'generates contributing guidelines', 'adds code of conduct sections', or 'creates PR templates'. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of what the skill actually does beyond its name, and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'contributing guide creator' repeated twice, which is not a natural phrase users would say. Users would more likely say 'contributing guide', 'CONTRIBUTING.md', 'how to contribute', 'open source contribution guidelines', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The name 'Contributing Guide Creator' is somewhat specific to a niche task, which provides some distinctiveness. However, the vague 'Technical Documentation' category label could overlap with many other documentation skills, and the lack of concrete details makes it harder to distinguish. | 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 substantive content. It consists entirely of generic boilerplate that could apply to any skill topic, with the phrase 'contributing guide creator' substituted in. It provides zero actionable guidance on how to actually create a contributing guide—no templates, no structure recommendations, no examples, no commands.
Suggestions
Add a concrete contributing guide template (e.g., a complete CONTRIBUTING.md example) with sections like Prerequisites, Development Setup, Pull Request Process, Code Style, and Testing Requirements.
Include executable steps for generating a contributing guide, such as specific markdown structure, commands for linting the output, or a checklist of sections to include based on project type.
Provide at least one concrete input/output example showing how a user request maps to a generated contributing guide.
Replace all generic boilerplate ('Provides step-by-step guidance', 'Follows industry best practices') with actual best practices and specific guidance for contributing guide creation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the phrase 'contributing guide creator' excessively, and provides zero substantive information about how to actually create a contributing guide. | 1 / 3 |
Actionability | There are no concrete steps, code examples, commands, templates, or any executable guidance whatsoever. The skill describes what it claims to do in abstract terms ('provides step-by-step guidance') without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints—just vague claims about capabilities like 'validates outputs against common standards' with no actual process described. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no meaningful structure. There are no references to detailed files, no examples, and no organized sections beyond boilerplate headings that contain no real 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
4dee593
- 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.