Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill contributing-guide-creatorContributing Guide Creator - Auto-activating skill for Technical Documentation. Triggers on: contributing guide creator, contributing guide creator Part of the Technical Documentation skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder with no substantive content. It relies entirely on the skill name and category metadata without explaining what the skill actually does or when it should be used. The duplicate trigger term suggests auto-generation without human review.
Suggestions
Add specific actions the skill performs, e.g., 'Creates CONTRIBUTING.md files with sections for code standards, PR guidelines, issue templates, and development setup instructions.'
Include a 'Use when...' clause with natural trigger terms like 'contributing guide', 'CONTRIBUTING.md', 'how to contribute', 'open source contribution', 'contributor documentation'.
Remove the duplicate trigger term and replace with varied natural language phrases users would actually say when needing this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Contributing Guide Creator') without describing any concrete actions. There are no specific capabilities listed like 'creates contribution guidelines', 'documents code standards', or 'generates PR templates'. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only provides category metadata without any functional description or explicit usage triggers. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('contributing guide creator, contributing guide creator'). No natural user language like 'CONTRIBUTING.md', 'how to contribute', 'contribution guidelines', or 'open source documentation' is included. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Contributing Guide Creator' is a somewhat specific niche, the lack of detail means it could overlap with general documentation skills. The category 'Technical Documentation' is broad and doesn't help distinguish it from other documentation-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no actual instructional content. It describes what a contributing guide creator skill would do but provides zero actionable guidance on how to create contributing guides - no templates, no required sections, no examples, no best practices. The entire content could be replaced with actual instructions for creating CONTRIBUTING.md files.
Suggestions
Add a concrete template or structure for CONTRIBUTING.md files (sections like 'Getting Started', 'Code Style', 'Pull Request Process', 'Issue Reporting')
Include at least one complete example of a well-structured contributing guide that can be adapted
Provide a step-by-step workflow: 1) Identify project type, 2) Define contribution types accepted, 3) Document setup steps, 4) Specify code standards, 5) Describe review process
Remove all meta-description content ('This skill provides...', 'When to Use...') and replace with actual instructions Claude can execute
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about creating contributing guides. Phrases like 'automated assistance' and 'industry best practices' are vague filler that waste tokens without adding value. | 1 / 3 |
Actionability | No concrete guidance, code, templates, or examples are provided. The skill describes what it supposedly does but never shows how to actually create a contributing guide - no structure, no sections to include, no sample content. | 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 about the skill itself. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed resources, templates, or examples. No references to additional documentation or organized sections for different aspects of contributing guide creation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Reviewed
Table of Contents
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.