CtrlK
BlogDocsLog inGet started
Tessl Logo

create-rfc

Creates structured Request for Comments (RFC) documents for proposing and deciding on significant changes. Use when the user says "write an RFC", "create a proposal", "I need to propose a change", "draft an RFC", "document a decision", or needs stakeholder alignment before making a major technical or process decision. Do NOT use for TDDs/implementation docs (use technical-design-doc-creator instead), README files, or general documentation.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 skill body with a clear multi-step workflow, concrete interactive payload, and a properly signaled one-level reference file. The main weakness is conciseness — several trigger lists and the next-steps block are duplicated across sections.

Suggestions

Remove the multilingual 'Example Prompts that Trigger This Skill' section — the same triggers already appear in the frontmatter description and 'When to Use This Skill', making this block redundant padding.

Collapse the 'Output Summary Format' into Step 5's 'Offer Next Steps' block so the post-generation summary is defined once instead of twice.

Consider moving the 'Common Anti-Patterns to Avoid' BAD/GOOD examples into a reference file to reduce inline length while keeping the body as an overview.

DimensionReasoningScore

Conciseness

Mostly efficient but includes redundant sections — trigger phrases are restated in 'When to Use', the description, and the multilingual 'Example Prompts' block, and the 'Output Summary Format' duplicates Step 5's next-steps offer — so it sits at 'could be tightened' rather than 4.

3 / 5

Actionability

Provides copy-paste-ready AskQuestion JSON, an explicit mandatory-fields list, an RFC-type detection table, a concrete quality checklist, and BAD/GOOD anti-pattern examples — fully executable guidance covering common cases.

5 / 5

Workflow Clarity

Clear five-step sequence (Gather Context → Validate Mandatory Fields → Detect Type → Generate → Offer Next Steps) with a mandatory-fields validation checkpoint and a pre-finalize checklist, but lacks an explicit error-recovery feedback loop, so it stops at 4 rather than 5.

4 / 5

Progressive Disclosure

Good structure with a well-signaled one-level-deep reference ('Read references/section-templates.md ... contains complete Markdown templates for all 11 sections') that is a real file; minor gaps because anti-patterns and examples are inlined rather than referenced, keeping it below 5.

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 clearly states purpose and trigger conditions with extensive natural phrasing and explicit conflict-avoidance boundaries. The only weakness is specificity, which names the domain and one main action but does not list multiple distinct concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain and a concrete action ('Creates structured Request for Comments (RFC) documents for proposing and deciding on significant changes') but does not enumerate multiple distinct concrete actions, so it stops at the '1-2 concrete actions, not comprehensive' anchor rather than reaching 4.

3 / 5

Completeness

Explicitly answers both 'what' (creates structured RFC documents for proposing/deciding on significant changes) and 'when' (concrete 'Use when the user says...' trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases including synonyms ('write an RFC', 'create a proposal', 'I need to propose a change', 'draft an RFC', 'document a decision') that users would actually say, matching the 'comprehensive coverage including synonyms' anchor.

5 / 5

Distinctiveness Conflict Risk

Clear niche (RFC documents) with distinct triggers and an explicit 'Do NOT use for TDDs/implementation docs (use technical-design-doc-creator instead), README files, or general documentation' boundary, giving minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tech-leads-club/agent-skills
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.