rfc-status

Show RFC details or update RFC status through lifecycle

Quality

55%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/devops-data/skills/rfc-status/SKILL.md

Quality

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 management) with basic actions but suffers from missing trigger guidance and incomplete keyword coverage. The lack of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill, and the description doesn't explain what RFC lifecycle stages or status transitions are supported.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about RFC status, wants to view RFC details, or needs to transition an RFC through approval stages'

Include natural trigger terms users would say: 'proposal', 'design document', 'approve RFC', 'reject RFC', 'RFC status', 'review RFC'

Expand the capability list to specify concrete actions: 'View RFC metadata and content, update RFC status (draft, review, approved, rejected), track RFC lifecycle progression'

Dimension	Reasoning	Score
Specificity	Names the domain (RFC) and two actions ('show details' and 'update status'), but lacks comprehensive detail about what specific operations are available or what 'lifecycle' entails.	2 / 3
Completeness	Describes what it does (show/update RFC) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes 'RFC' which is a relevant keyword, but misses natural variations users might say like 'request for comments', 'proposal', 'design doc', or specific status terms like 'approve', 'reject', 'draft'.	2 / 3
Distinctiveness Conflict Risk	'RFC' is somewhat specific terminology, but 'show details' and 'update status' are generic actions that could overlap with other document or workflow management skills.	2 / 3
	Total	7 / 12 Passed

Implementation

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured skill with excellent actionability and workflow clarity - the transition validation rules, pre-checks, and file movement logic are clearly specified with concrete examples. The main weaknesses are moderate verbosity (some redundant examples) and all content being inline rather than using progressive disclosure for the detailed reference tables.

Suggestions

Consider moving the detailed transition table and directory mapping to a separate REFERENCE.md file, keeping only the most common transitions inline

Remove the 'Example Usage' section as it largely duplicates information already shown in the execution instructions with output examples

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some redundancy - the example usage section repeats information already covered in the execution instructions, and some tables could be more compact.	2 / 3
Actionability	Provides concrete, executable commands with specific examples, clear argument syntax, and detailed tables showing valid transitions and directory mappings. The output format examples are copy-paste ready.	3 / 3
Workflow Clarity	Excellent multi-step workflows with explicit validation checkpoints (pre-transition checks), clear sequencing for status updates, and feedback loops for reviewer approval requirements. Error handling section addresses recovery scenarios.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but the skill is quite long (~150 lines) and could benefit from splitting detailed transition rules or directory mappings into separate reference files. All content is inline rather than appropriately distributed.	2 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

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: 29 days ago

Table of Contents

Discovery Implementation Validation

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.