create-rfc

Create OpenShell RFC proposals in rfc/ from a design request. Use when the user asks to write, draft, start, create, or update an RFC, Request for Comments, architecture proposal, API proposal, process proposal, or cross-cutting design proposal that should follow the OpenShell RFC process and template.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-3

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

The body is concise, well-structured, and includes an explicit validation checkpoint, making it an effective overview that delegates section detail to the RFC template. Its main limitation is actionability: most executable detail lives in the externally referenced template rather than in SKILL.md itself.

Suggestions

Add a brief inline sketch of the required template sections (e.g. Summary, Motivation, Non-goals, Proposal, Alternatives, Open questions) so the skill remains actionable even before reading the template.

Include one short concrete example of a filled-in front-matter block (author, state: draft, related links) to make step 5 copy-paste ready.

Specify how to determine the "next available NNNN" (e.g. list existing rfc/NNNN-* dirs and increment) so step 3 is unambiguous without relying on rfc/README.md.

Dimension	Reasoning	Score
Conciseness	The ~50-line body is lean and instructional with no concept explanation Claude already knows (e.g. "Keep the template as the source of truth", "Keep Summary concise, Motivation readable by anyone"), matching the score-3 anchor where every token earns its place.	3 / 3
Actionability	Guidance is concrete with exact paths and front-matter specifics, but the executable per-section detail is delegated to the referenced template ("Follow its section guidance") rather than being self-contained here, matching the score-2 anchor for some concrete guidance with missing key details.	2 / 3
Workflow Clarity	An explicit 8-step sequence is followed by a Validation section acting as a checklist ("Verify the folder name and RFC number", "Verify every template section is present"), matching the score-3 anchor for a clear sequence with explicit validation steps.	3 / 3
Progressive Disclosure	No bundle files exist; the skill is self-contained and well-organized into Workflow, Writing Standards, and Validation, with one-level-deep clearly signaled references to repo RFC files, satisfying the simple-skill exception for scoring 3.	3 / 3
	Total	11 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 is strong: it explicitly answers what and when with a rich set of natural trigger terms and a clearly distinct OpenShell RFC niche. The only relative weakness is specificity, since it names one primary action (create proposals) rather than enumerating multiple concrete operations.

Dimension	Reasoning	Score
Specificity	"Create OpenShell RFC proposals in rfc/ from a design request" names the domain and a concrete action but lists only one primary action rather than multiple specific concrete actions like the score-3 anchor.	2 / 3
Completeness	Both "what" ("Create OpenShell RFC proposals in rfc/") and "when" (an explicit "Use when the user asks to..." trigger clause) are clearly stated, satisfying the score-3 anchor for answering both.	3 / 3
Trigger Term Quality	Broad natural-term coverage is explicit: "write, draft, start, create, or update an RFC, Request for Comments, architecture proposal, API proposal, process proposal, or cross-cutting design proposal", matching the score-3 anchor for good coverage of phrasings users would say.	3 / 3
Distinctiveness Conflict Risk	The OpenShell RFC process/template niche with its distinct proposal-type triggers is clearly scoped and unlikely to fire for unrelated skills, matching the score-3 anchor.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: NVIDIA/OpenShell
Path: .agents/skills/create-rfc/SKILL.md
Commit: deced87

Reviewed: 6 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.