Home / rudycity / superagent · GitHub

doc-coauthoring SKILL.md skillA

This file is byte-identical to the first copy the registry indexed, one of 19 indexed copies. Same content hash, so the same checks give both the same grade.

doc-coauthoring from rudycity/superagent is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add rudycity/superagent/doc-coauthoring@git:20260626.019dba9

Pins git:20260626.019dba9 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: rudycity/superagent
Path: .agents/skills/doc-coauthoring/SKILL.md
Versions recorded: 1
Latest version: git:20260626.019dba9, committed Jun 26, 2026
Size: 15,815 bytes
Repository stars: 64
License: MIT

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.

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

# Doc Co-Authoring Workflow

This skill provides a structured workflow for guiding users through collaborative document creation. Act as an active guide, walking users through three stages: Context Gathering, Refinement & Structure, and Reader Testing.

## When to Offer This Workflow

**Trigger conditions:**
- User mentions writing documentation: "write a doc", "draft a proposal", "create a spec", "write up"
- User mentions specific doc types: "PRD", "design doc", "decision doc", "RFC"
- User seems to be starting a substantial writing task

**Initial offer:**
Offer the user a structured workflow for co-authoring the document. Explain the three stages:

1. **Context Gathering**: User provides all relevant context while Claude asks clarifying questions
2. **Refinement & Structure**: Iteratively build each section through brainstorming and editing
3. **Reader Testing**: Test the doc with a fresh Claude (no context) to catch blind spots before others read it

Explain that this approach helps ensure the doc works well when others read it (including when they paste it into Claude). Ask if they want to try this workflow or prefer to work freeform.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add rudycity/superagent/doc-coauthoring@sha256:2e47d78846faeea4

The line at the top of this page pins the label git:20260626.019dba9, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_q7gngzfzifn7ab76.svg)](https://markdownregistry.com/a/art_q7gngzfzifn7ab76)

5 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Jun 26, 2026.

version	committed	commit	size	audit
git:20260626.019dba9 latest	2026-06-26	019dba9	15,815 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (15815 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

GitHub

rudycity/superagent · 64 stars · license MIT · pushed 2026-11-06 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_q7gngzfzifn7ab76
GET https://markdownregistry.com/api/v1/resolve?ref=rudycity/superagent/doc-coauthoring
GET https://markdownregistry.com/api/v1/blob/2e47d78846faeea4a56e9809c52700087a15a2155a3f293a3efbaded81398ef4

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.

More from rudycity/superagent

AGENTS.md@.agents AGENTS.md file

rudycity/superagent · .agents/AGENTS.md

git:20261029.6635862 · audit B · 64 stars

accessibility-compliance SKILL.md skill

rudycity/superagent · .agents/skills/accessibility-compliance/SKILL.md · Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology…