Index of every page on this site: llms.txt
All skills
nvidia avatar

/create-rfc

@c24fcd2
by NVIDIA Corporationnvidia/openshell22k stars
2,144
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/nvidia/openshell/create-rfc

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈79 tokens for metadata: the name and description. ≈564 when used: this file. ≈44 more on demand in 1 file.

Description uses 4.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈316 characters, or 4.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.
  2. Read rfc/0000-template/README.md before drafting. Follow its section guidance, including scope, expected detail, and suggested section length.
  3. Choose the next available NNNN from the existing rfc/NNNN-* directories unless the user provided a specific number.
  4. Create rfc/NNNN-short-title/README.md by copying the template and replacing placeholders. Use a short hyphenated folder title.
  5. 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.
  6. 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.
  7. Preserve uncertainty in Open questions instead of silently deciding unknowns. If a missing decision blocks a coherent RFC, ask the user for that decision.
  8. 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 published 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 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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts5mo3 checks · Risk SAFE
  • Gen Agent Trust Hub5mo

    The skill is safe. It outlines a procedure for drafting OpenShell RFC documents based on user design requests and provided templates within a repository, with no malicious patterns detected.

  • Socket5mo

    No alerts

  • Snyk5mo

    Risk: LOW · No issues

Signed by skilld at c24fcd2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
metadata
{
  "internal": true
}

README badge

README badge for nvidia/openshell/create-rfc