SkillsAdd

nvidia/openshell

create-rfc

Create OpenShell RFC proposals in rfc/ from a design request.

First seen Jun 20, 2026

Installation

$ npx skills add nvidia/openshell --skill create-rfc
View on skills.sh ↗ GitHub repository ↗

Summary

  • 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.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from nvidia/openshell · top by installs.

npx skills add nvidia/openshell
openshell-cli 51 generate-sandbox-policy 25 debug-inference 22 debug-openshell-cluster 18 tui-development 17 sbom 16 create-github-issue 14 build-from-issue 14 sync-agent-infra 14 triage-issue 14

Browse all from nvidia/openshell

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 8.5K
License LICENSE
Default branch main
Open issues 399
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

More metadata
internal
1

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,647 B
  • docs SUMMARY.md 321 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 12 installs

SKILL.md

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.

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

RFC number, and how the lifecycle works.

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

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

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

unless the user provided a specific number.

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

placeholders. Use a short hyphenated folder title.

  1. 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.

  1. 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.

  1. Preserve uncertainty in Open questions instead of silently deciding unknowns.

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

  1. 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.