authoring-rfds SKILL.md skillA
authoring-rfds from symposium-dev/symposium is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add symposium-dev/symposium/authoring-rfds@git:20260627.3aaa498Pins git:20260627.3aaa498 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- symposium-dev/symposium
- Path
.agents/skills/authoring-rfds/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260627.3aaa498, committed Jun 27, 2026
- Size
- 2,853 bytes
- Repository stars
- 367
- License
- a license file GitHub does not identify
Write and structure RFDs (Requests for Discussion) for the Symposium project. Use when creating a new RFD, drafting design proposals, or reviewing RFD content for style compliance.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Authoring RFDs ## What is an RFD? An RFD is a proposal for a non-trivial change. It lives in `md/rfds/<name>/README.md` and follows the template in `md/rfds/TEMPLATE/README.md`. RFDs are submitted as PRs; once merged they appear under the "Accepted" section of `md/SUMMARY.md`. When implementation is complete, they move to "Completed". ## Process 1. Create a subdirectory under `md/rfds/` (e.g., `md/rfds/my-feature/`). 2. Copy the template from `md/rfds/TEMPLATE/README.md` into `md/rfds/my-feature/README.md`. 3. Fill in each section. 4. Add the RFD to `md/SUMMARY.md` under the "Accepted" heading. 5. Open a PR. Discussion happens on the PR. 6. Implementation PRs reference the RFD and update its status section. ## Style guide ### Voice and tone - No promotional text, overstated claims, or dramatic writing style. - Be factual, brief, and to the point. - Write as if explaining to a colleague who is already familiar with the project. - Avoid filler phrases like "This exciting new feature will revolutionize..." — just say what it does. ### Structure - Lead with concrete concepts, then generalize. Show the specific thing first, explain the pattern second. …
Read the whole file at its exact version.
How to install
mdr add symposium-dev/symposium/authoring-rfds@sha256:828d8be392af8fa2The line at the top of this page pins the label git:20260627.3aaa498, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_miifewdgac3gkiz2)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jun 27, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2853 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
symposium-dev/symposium · 367 stars · license a license file GitHub does not identify · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_miifewdgac3gkiz2 GET https://markdownregistry.com/api/v1/resolve?ref=symposium-dev/symposium/authoring-rfds GET https://markdownregistry.com/api/v1/blob/828d8be392af8fa2bdeb0cda1326b80357fe000db5d37cc363cb40289aa15811
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.