How do I install the Sc Document skill?

Run npx skillmds add majiayu000/sc-document-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sc Document safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sc Document?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sc Document free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sc Document?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sc Document by majiayu000 — Agent Skill

Name: Sc Document
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

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 guide

Behavioral 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, @throws

API Reference

/sc:document src/api --type api --style detailed
# Full endpoint docs with examples

User Guide

/sc:document payment-module --type guide --style brief
# Quick-start tutorial with common patterns

Component Docs

/sc:document components/ --type external
# README.md for component library

Tool Coordination

Read - Component analysis
Grep - Reference extraction
Write - Documentation creation
Glob - Multi-file documentation

---name: sc-document-2description: Generate focused documentation for components, functions, APIs, and features. Use when creating inline docs, API references, user guides, or technical documentation.--- # Documentation Generation Skill Focused documentation for code, APIs, and features. ## Quick Start ```bash # 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 guide ``` ## Behavioral Flow 1. **Analyze** - Examine component structure and functionality 2. **Identify** - Determine documentation requirements and audience 3. **Generate** - Create appropriate documentation content 4. **Format** - Apply consistent structure and patterns 5. **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, @throws ``` ### API Reference ``` /sc:document src/api --type api --style detailed # Full endpoint docs with examples ``` ### User Guide ``` /sc:document payment-module --type guide --style brief # Quick-start tutorial with common patterns ``` ### Component Docs ``` /sc:document components/ --type external # README.md for component library ``` ## Tool Coordination - **Read** - Component analysis - **Grep** - Reference extraction - **Write** - Documentation creation - **Glob** - Multi-file documentation

Frequently asked questions