sc-document
Skill19 starsChanged 8 months agoMITView on GitHub
Generate focused documentation for components, functions, APIs, and features. Use when creating inline docs, API references, user guides, or technical documentation.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- kreighmitchell/SuperClaudeword for word, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 1
- kreighmitchell/SuperClaude★ 4100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-data-engineerSkill
- agent-fullstack-developerSkill
- agent-kubernetes-specialistSkill
- agent-ml-engineerSkill
- agent-performance-engineerSkill
- agent-react-specialistSkill
- agent-security-engineerSkill
- agent-technical-writerSkill
- ask-multiSkill
- askSkill
- learned-skills-indexSkill
- sc-analyzeSkill
- sc-brainstormSkill
- sc-buildSkill
- sc-cicd-setupSkill
- sc-code-reviewSkill
- sc-designSkill
- sc-e2eSkill
- sc-estimateSkill
- sc-evaluateSkill
- sc-explainSkill
- sc-gitSkill
- sc-implementSkill
- sc-improveSkill
- sc-log-fixSkill
- sc-mcpSkill
- sc-pr-checkSkill
- sc-pr-fixSkill
- sc-principlesSkill
- sc-pushSkill
- sc-readmeSkill
- sc-researchSkill
- sc-tddSkill
- sc-testSkill
- sc-workflowSkill
- sc-worktreeSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Generate: - Create appropriate documentation content
- Distinctive: line 29
Integrate: - Ensure compatibility with existing docs
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Documentation Generation Skill
Focused documentation for code, APIs, and features.
Quick Start
# Inline documentation
/sc:document src/auth/login.js --type inline
# API reference
/sc:document src/api --type api --style detailed
# User guide
/sc:document payment-module --type guideBehavioral Flow
- Analyze - Examine component structure and functionality
- Identify - Determine documentation requirements and audience
- Generate - Create appropriate documentation content
- Format - Apply consistent structure and patterns
- Integrate - Ensure compatibility with existing docs
Flags
| Flag | Type | Default | Description |
--type | string | inline | inline, external, api, guide |
--style | string | detailed | brief, detailed |
Evidence Requirements
This skill does NOT require hard evidence. Deliverables are:
- Generated documentation files
- Inline code comments
- API reference materials
Documentation Types
Inline (--type inline)
- JSDoc/docstring generation
- Parameter and return descriptions
- Function-level comments
External (--type external)
- Standalone documentation files
- Component overviews
- Integration guides
API (--type api)
- Endpoint documentation
- Request/response schemas
- Usage examples
Guide (--type guide)
- User-focused tutorials
- Implementation patterns
- Common use cases
Style Options
Brief (--style brief)
- Concise descriptions
- Essential information only
- Quick reference format
Detailed (--style detailed)
- Comprehensive explanations
- Extended examples
- Edge case coverage
Examples
Inline Code Docs
/sc:document src/auth/login.js --type inline
# JSDoc with @param, @returns, @throwsAPI Reference
/sc:document src/api --type api --style detailed
# Full endpoint docs with examplesUser Guide
/sc:document payment-module --type guide --style brief
# Quick-start tutorial with common patternsComponent Docs
/sc:document components/ --type external
# README.md for component libraryMCP Integration
PAL MCP (Quality & Research)
| Tool | When to Use | Purpose |
mcp__pal__codereview | API docs | Review documentation accuracy |
mcp__pal__apilookup | External APIs | Get current API documentation |
mcp__pal__chat | Writing assistance | Get help with complex explanations |
mcp__pal__consensus | Style decisions | Multi-model validation of doc approach |
PAL Usage Patterns
# Verify documentation accuracy
mcp__pal__codereview(
review_type="quick",
step="Reviewing API documentation for accuracy",
findings="Parameter descriptions, return types, examples",
relevant_files=["/docs/api/auth.md"]
)
# Get current API docs for external integration
mcp__pal__apilookup(
prompt="Get current Stripe API documentation for payment intents"
)
# Writing assistance for complex topics
mcp__pal__chat(
prompt="Help me explain the OAuth2 authorization code flow clearly for developers",
model="gpt-5.2"
)Rube MCP (Publishing & Collaboration)
| Tool | When to Use | Purpose |
mcp__rube__RUBE_SEARCH_TOOLS | Doc platforms | Find Notion, Confluence, GitBook |
mcp__rube__RUBE_MULTI_EXECUTE_TOOL | Publishing | Push docs to platforms |
mcp__rube__RUBE_REMOTE_WORKBENCH | Bulk docs | Generate docs for large codebases |
Rube Usage Patterns
# Publish documentation
mcp__rube__RUBE_MULTI_EXECUTE_TOOL(tools=[
{"tool_slug": "NOTION_CREATE_PAGE", "arguments": {
"title": "API Reference: Authentication",
"content": "## Endpoints\n### POST /auth/login\n..."
}},
{"tool_slug": "CONFLUENCE_CREATE_PAGE", "arguments": {
"space": "DEV",
"title": "Auth API Documentation",
"content": "..."
}}
])
# Notify team of new docs
mcp__rube__RUBE_MULTI_EXECUTE_TOOL(tools=[
{"tool_slug": "SLACK_SEND_MESSAGE", "arguments": {
"channel": "#documentation",
"text": "New API docs published: Authentication endpoints"
}}
])
# Bulk generate docs
mcp__rube__RUBE_REMOTE_WORKBENCH(
thought="Generate JSDoc for all exported functions",
code_to_execute='''
import os
# Process all JS files and generate documentation
# Use invoke_llm for each function
'''
)Flags (Extended)
| Flag | Type | Default | Description |
--pal-review | bool | false | Use PAL to review doc accuracy |
--publish | string | - | Publish via Rube (notion, confluence, gitbook) |
--notify | string | - | Notify via Rube (slack, teams, email) |
Tool Coordination
- Read - Component analysis
- Grep - Reference extraction
- Write - Documentation creation
- Glob - Multi-file documentation
- PAL MCP - Accuracy review, API lookup, writing assistance
- Rube MCP - Publishing, notifications, bulk generation
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

