create-rfc
Create a new RFC (Request for Comments) technical specification
77
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/devops-data/skills/create-rfc/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear domain (RFC creation) but is too terse to be effective for skill selection. It lacks explicit trigger guidance ('Use when...'), misses common synonym terms users might say, and doesn't enumerate the specific capabilities beyond basic creation.
Suggestions
Add a 'Use when...' clause with trigger terms like 'RFC', 'request for comments', 'technical proposal', 'design document', 'tech spec'
Expand the capabilities list to include specific actions like 'draft sections, define requirements, structure technical proposals, outline implementation details'
Include file format or output details if applicable (e.g., 'generates markdown RFC documents following standard template')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (RFC/technical specification) and one action (create), but doesn't list multiple concrete actions like 'draft sections, define requirements, structure proposals, add diagrams'. | 2 / 3 |
Completeness | Describes what (create RFC) but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'RFC' and 'technical specification' which are relevant keywords, but misses common variations like 'design doc', 'tech spec', 'proposal', 'architecture document', or 'spec'. | 2 / 3 |
Distinctiveness Conflict Risk | RFC is somewhat specific, but 'technical specification' could overlap with other documentation or design skills; lacks explicit triggers to distinguish from general document creation. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that demonstrates best practices for command-based skills. It provides clear, actionable instructions with proper validation, error handling, and user feedback. The content is well-structured, appropriately concise, and references external resources correctly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete, executable guidance with specific file paths, naming conventions, directory structures, and exact output formats. The step-by-step instructions are copy-paste ready and unambiguous. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence with explicit validation requirements, error handling section, and confirmation output. The workflow includes appropriate checks (title validation, duplicate detection) and clear next steps for the user. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (Usage, Arguments, Execution Instructions, Examples, Validation, Error Handling). Appropriately references external template file rather than inlining it, keeping the skill focused. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- jpoutrin/product-forge
- Commit
0ebe7ae
- 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.