Create Rfc Agent Skill

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.

698 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

7973

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/NVIDIA/OpenShell --skill create-rfc

What comes with it

174 bytes besides the instruction

agents/openai.yaml

The instruction itself

4 sections, as written by the author

Create RFC

Workflow

Create RFCs by following rfc/README.md and rfc/0000-template/README.md.

Keep the template as the source of truth for section guidance.

Read rfc/README.md to confirm when an RFC is appropriate, how to choose the

RFC number, and how the lifecycle works.

Read rfc/0000-template/README.md before drafting. Follow its section

guidance, including scope, expected detail, and suggested section length.

Choose the next available NNNN from the existing rfc/NNNN-* directories

unless the user provided a specific number.

Create rfc/NNNN-short-title/README.md by copying the template and replacing

placeholders. Use a short hyphenated folder title.

Fill in front matter with the RFC author, state: draft, and any related

links the user provided. If the author is unknown, use the requesting user's

GitHub handle when available or leave the template placeholder.

Draft each section from the user's design context. Keep Summary concise,

Motivation readable by anyone, Non-goals explicit, Proposal focused on what

is being proposed, and Alternatives focused on credible competing approaches.

Preserve uncertainty in Open questions instead of silently deciding unknowns.

If a missing decision blocks a coherent RFC, ask the user for that decision.

Check the completed RFC against the template once more before finishing.

Writing Standards

Prefer concrete design statements over placeholder language.
Link to relevant issues, prior RFCs, and architecture docs when they provide

needed context.

Keep rejected or left-out designs in Alternatives, not Proposal.
Use Mermaid diagrams for architecture or data flow when a diagram would make

the proposal easier to review.

Do not update architecture/ or published docs just because an RFC was

drafted. Those updates belong with implementation or with an accepted RFC when

the user asks for them.

Validation

Before handing the RFC back to the user:

Verify the folder name and RFC number match the process in rfc/README.md.
Verify every template section is present or intentionally marked as not

applicable.

Run a Markdown formatting or lint check only if the repo already provides one

for Markdown-only changes.

Other skills for the same job

different authors, same section of the catalogue

Doc Coauthoring

by anthropics

vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Test Driven Development

by w95

×7

Use when implementing any feature or bugfix, before writing implementation code

Use when you have a spec or requirements for a multi-step task, before touching code

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts

Crafting Effective Readmes

by softaworks

×3

Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.

| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.

6k tokens

Opentrons Integration

by christophacham

×3

Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.

9k tokens scripts

How to use it

Copy the folder

Take nvidia/create-rfc from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.