Server Documentation
Set up a documentation system that tracks changes and maintains server/project documentation with Claude Code hooks. Provides scripts and workflows for automatic change logging and infrastructure documentation.
Install
/plugin marketplace add Freddy-CHEN-ux/00_claude_skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Freddy-CHEN-ux/00_claude_skills --skill server-documentationgit clone --depth 1 https://github.com/Freddy-CHEN-ux/00_claude_skills.git /tmp/00_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/00_claude_skills/skills/server-documentation ~/.claude/skills/server-documentationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Server Documentation System
Set up a documentation system that tracks changes and maintains server/project documentation with Claude Code hooks.
## When to Use
- Setting up a new server or development environment
- Need to track configuration changes over time
- Want automatic documentation of work sessions
- Maintaining changelog for infrastructure
## Directory Structure
```
~/docs/ # User home directory (cross-platform)
├── changelog.md # Global overview with system info and changelog
└── YYYY-MM-DD/
├── changes.md # Daily quick change log (table format)
└── *.md # Detailed topic files as needed
```
### Platform-Specific Paths
| Platform | Docs Location | Command Location |
|----------|---------------|------------------|
| Linux/macOS | `~/docs/` | `~/bin/docchange` |
| Windows (Git Bash) | `~/docs/` | `~/bin/docchange` (bash script) |
| Windows (CMD/PS) | `%USERPROFILE%\docs\` | `%USERPROFILE%\bin\docchange.cmd` |
## Setup Protocol
### Step 1: Create Directory Structure
**Linux/macOS:**
```bash
mkdir -p ~/docs ~/bin
```
**Windows (PowerShell):**
```powershell
New-Item -ItemType Directory -Force -Path "$env:USERPROFILE\docs", "$env:USERPROFILE\bin"
```
### Step 2: Create Global Changelog
Create `~/docs/changelog.md` with this template:Details
- Skill name
server-documentation- Repository
- Freddy-CHEN-ux/00_claude_skills
- Path
skills/server-documentation/SKILL.md- Repo updated
- 10 January 2026
FAQ
What does the Server Documentation skill do?
Set up a documentation system that tracks changes and maintains server/project documentation with Claude Code hooks. Provides scripts and workflows for automatic change logging and infrastructure documentation.
How do I install the Server Documentation skill?
Claude Code plugin: /plugin marketplace add Freddy-CHEN-ux/00_claude_skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Server Documentation popular?
It lives in Freddy-CHEN-ux/00_claude_skills, which has 8 GitHub stars and 3 forks.
Related skills
Add Integration
8Freddy-CHEN-ux/00_claude_skills
Build a new API integration for Nexus. Load when user mentions "add integration", "new integration", "integrate with", "connect to [service]", or "build [service] integration". Interactive workflow that discovers API endpoints, plans the integration, and creates a project for implementation.
AI Agents
8Freddy-CHEN-ux/00_claude_skills
Production-grade AI agent patterns with MCP integration, agentic RAG, handoff orchestration, multi-layer guardrails, and observability (modern best practices)
AI LLM
8Freddy-CHEN-ux/00_claude_skills
Production LLM engineering skill. Covers strategy selection (prompting vs RAG vs fine-tuning), dataset design, PEFT/LoRA, evaluation workflows, deployment handoff to inference serving, and lifecycle operations with cost/safety controls.
Splitting User Stories
5vnovakovits/claude-skills
Split user stories into small, valuable, independently-shippable slices using INVEST (Bill Wake), Richard Lawrence's 9-pattern flowchart, Mike Cohn's SPIDR, Gojko Adzic's hamburger method, Jeff Patton's story mapping, and Henrik Kniberg's MVP analogies. Use when a story is too big to ship in one sprint, when "we'll do it all at once" feels risky, when carving an MVP, when planning incremental delivery, or when a story has hidden complexity that needs to be exposed in slices.
SEO Article Optimizer
5bolasblack/claude-skills
Optimize single articles or landing pages for SEO. Analyzes keywords, readability, headings, meta tags, internal links, E-E-A-T signals, featured snippets. Outputs scores, optimized draft, and publish assets. Use for blog posts, landing pages, or single URL optimization.
Ticket Writer
5vnovakovits/claude-skills
Draft, write, structure, or improve engineering tickets — user stories, bug reports, spikes, feature requests — for any tracker (Jira, Linear, GitHub Issues, Shortcut, Asana). Enforces a problem-first structure (outcome → context → constraints → acceptance criteria → dependencies → open questions) drawn from Daniel Starling's "Anatomy of a Software Ticket", Bill Wake's INVEST and SMART, and Marty Cagan / SVPG's "Empowered Product Teams". Actively rejects the standard anti-patterns — prescribed solutions / "files to change", missing outcome, untestable acceptance criteria, PM-supplied estimates
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.