1,076 free skills
Writing & Documentation skills
Skills for technical writing — READMEs, API documentation, changelogs, ADRs, and release notes.
Sourced from real, public repositories — synced daily, never invented.
1,076 free skills
Skills for technical writing — READMEs, API documentation, changelogs, ADRs, and release notes.
Sourced from real, public repositories — synced daily, never invented.
15 tools across six categories
13 of them never send your data anywhere
Free · No signup · No trial clock
SEE THE DIRECTORY
readme-improvement
congdon1207/agents.md
Use when the user asks to create or improve a README file, project documentation, getting started guide, or installation instructions. Triggers on keywords like "README", "getting started", "installation guide", "project overview", "setup instructions".
create-readme
11philip22/skills
Create a README.md file for the project
iblai-readme
iblai/vibe
Write or refresh the README.md
summarization
upsonic/upsonic
Summarize documents, articles, conversations, code, and technical content into concise, accurate summaries. Use when user asks to summarize, condense, create a TL;DR, write an executive summary, extract key points, or distill content. Trigger when user says things like "summarize this", "give me the key points", "TL;DR", "what are the main takeaways", "condense this", "brief me on this", or provides long content asking for a shorter version. Also trigger for meeting notes summaries, research paper abstracts, and changelog summaries. Do NOT trigger for rewriting or paraphrasing at similar length, translation, or content generation from scratch.
changelog-automation
data-wise/claude-plugins
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
rust-development
cosmonic-labs/skills
Expert Rust development guidance covering naming conventions, type safety, error handling, documentation, and best practices based on official Rust guidelines.
technical-writing
andurilcode/craftwork
Apply whenever the user needs to write, draft, review, or improve technical documents — RFCs, design docs, ADRs, runbooks, postmortems, one-pagers, announcements, Slack threads, PR descriptions. Triggers on 'write a design doc', 'draft an RFC', 'help me write this up', 'write a runbook', 'review my doc', 'make this clearer', 'write a postmortem', or when technical information must be communicated to a specific audience. Also trigger when the user pastes a draft for feedback or needs to explain technical decisions to non-technical stakeholders.
changelog
codephobiia/claude-roblox-game-studio
Generate changelog from git history and design docs. Roblox update log format.
simple-english
alexander-danilenko/cortex-ai-skills
Write or audit technical text against ASD-STE100 Simplified Technical English so a tired, non-native reader understands it on the first pass: 20-word procedural and 25-word descriptive sentence limits, imperative steps, condition before command, one word for one meaning, and only the approved modals can/will/must. Use for READMEs, runbooks, procedures, error messages, release notes, incident reports, API guides, UI copy, and agent instructions. Trigger on: "STE", "Simplified Technical English", "ASD-STE100", "controlled language", "plain English", "make this clearer", "write for non-native readers", "prep this for translation", "cut the fluff", or any request to check text for compliance. Prefer this over general copy-editing whenever the text instructs, documents, or warns.
technical-writing
gwagjiug/technical-writing
Draft, review, restructure, and polish developer-facing technical documentation and technical articles. Use when Codex needs to work on tutorials, how-to guides, troubleshooting docs, API/reference docs, conceptual explanations, release or migration guides, or technical blog/article drafts; evaluate audience fit, information architecture, headings, overview, concrete examples, terminology consistency, compactness, and sentence-level clarity while preserving facts, code, commands, API names, versions, warnings, and product behavior.
technical-writing
milliondreamsblog/milliondreams-skills
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
readme-generator
jasperdevs/github-documentation-skills
Draft or rewrite GitHub README.md files for repositories, libraries, apps, CLIs, starters, cookbook repos, curated resource lists, and internal tools. Use when Codex needs to inspect a codebase, choose the right README shape for the repo type, answer what the project is and how to use it quickly, avoid duplicated top-of-file descriptions, and use GitHub Markdown features only when they improve comprehension.
readme-generator
sdc-ai-taskforce/sdc-agent-skills
PythonプロジェクトのREADME.mdを自動生成するスキル。コードベースを分析し、プロジェクト概要、使い方/API、ディレクトリ構造を含む日本語のREADMEを作成する。「READMEを作成して」「README.mdを生成して」「プロジェクトの説明ドキュメントを作って」などのリクエスト時に使用。
readme
alfredolopez80/multi-agent-ralph-loop
When the user wants to create or update a README.md file for a project. Also use when the user says "write readme," "create readme," "document this project," "project documentation," or asks for help with README.md. This skill creates absurdly thorough documentation covering local setup, architecture, and deployment.
api-documentation-generator
xfstudio/skills
Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices
changelog-gen
thinkfleetai/thinkfleet-engine
Generate changelogs from git history. Use when you need release notes fast.
changelog-generator
spiosifidis/my-claude-skills
Create user-facing changelogs from git commits — analyzes commit history, categorizes changes, and rewrites technical commits into clear, customer-friendly release notes. Use when the user asks for a changelog, release notes, "what changed since" a version or date, or a user-facing summary of recent commits.
context-network
jwynia/teach
Bootstrap, maintain, and evolve context networks across their full lifecycle. Use when starting a new project, when existing documentation feels scattered, or when agent effectiveness degrades due to missing context.
agents-md
getsentry/webvitals.com
This skill should be used when the user asks to "create AGENTS.md", "update AGENTS.md", "maintain agent docs", "set up CLAUDE.md", or needs to keep agent instructions concise. Guides discovery of local skills and enforces minimal documentation style.
public-docs
getsentry/junior
Create and maintain public, user-facing product documentation for this repo's `packages/docs` app. Use when asked to write, revise, or review docs pages (tutorial/concept/reference/troubleshooting), improve docs information architecture, fix docs frontmatter/linking issues, or align docs quality with Vercel/Sentry-style standards.
release-note-reviewer
microsoft/vscode-docs
Review VS Code release notes for style, structure, and completeness. Use for reviewing Insiders or Stable release notes against writing guidelines. Produces an actionable list of recommendations.
content-redirect
microsoft/vscode-docs
Create and manage redirects in VS Code documentation when pages are moved, renamed, or deleted. Use when moving docs pages, renaming files, restructuring content, or when the user asks about redirects.
write-changelog
microsoft/vscode-pull-request-github
Write a CHANGELOG.md entry for a new extension release. Use when: writing changelog, updating changelog, adding release notes, preparing a release, documenting milestone changes. Requires a milestone name and extension version number.
edit-changelog
clickhouse/clickhouse
Edit an auto-generated ClickHouse release changelog into the form that gets committed to CHANGELOG.md. Use when the user has the output of `utils/changelog/changelog.py` and wants it cleaned up and re-categorized for a release.
disting-nt-cpp-plugin-writer
thorinside/nt_mcp
Build and maintain Expert Sleepers disting NT C++ plugins with API v13, deliberate routing and polyphonic CV/gate design, click-safe voice transitions, tests, fact-checked player documentation, and verified GitHub releases. Use for new plugins, plugin fixes, hardware builds, nt_emu work, release preparation, or documentation audits.
doc-coauthoring
majiayu000/claude-skill-registry
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.
dbt-docs
altimateai/altimate-code
Document dbt models and columns in schema.yml with business context — model descriptions, column definitions, and doc blocks. Use when adding or improving documentation for discoverability. Powered by altimate-dbt.
documentation-bc-analysis-generator
fernandoartalf/al-copilot-skills-collection
Create well-structured Business Central feasibility analysis documents in the `openspec/analysis/` folder as the AL Analyst's working artefact backing a CCN, following the ANALYSIS-001 template structure. Captures references to the source user story / spec / CCN, change summary, scope & impact (objects added/modified, LoC, ID range usage), phased time estimate (Optimistic / Expected / Pessimistic with contingency and calendar duration), cost estimate at a stated EUR/h rate with assumptions, SWOT analysis (Strengths / Weaknesses / Opportunities / Threats), numbered risk register (`R-NN` with Likelihood / Impact / Mitigation), and a clear GO / NO-GO / CONDITIONAL-GO feasibility recommendation with non-blocking advisories and a handoff statement back to the Architect. Writes the file as `ANALYSIS-NNN-<kebab-title>.analysis.md` with frontmatter linking back to its spec, user story, and CCN. Use whenever the user asks to create, draft, generate, or write a feasibility analysis, ANALYSIS document, cost/time estimate, SWOT, risk assessment, or GO/NO-GO recommendation for a spec or change request, with trigger phrases such as "create analysis for SPEC-NNN", "draft feasibility analysis", "estimate cost and time for [feature]", "SWOT and risk for the spec", "GO/NO-GO recommendation", or "create an analysis file in openspec/analysis".
documentation
laurenceputra/agent-skills
Technical writer with expertise in creating clear, comprehensive, and user-friendly documentation. Use this skill when writing or reviewing documentation, creating README files, or documenting APIs and code.
documentation
vladncode/skills
Creates, structures, and reviews technical documentation following the Diátaxis framework (tutorials, how-to guides, reference, and explanation pages). Use when a user needs to write or reorganize docs, structure a tutorial vs. a how-to guide, build reference docs or API documentation, create explanation pages, choose between Diátaxis documentation types, or improve existing documentation structure. Trigger terms include: documentation structure, Diátaxis, tutorials vs how-to guides, organize docs, user guide, reference docs, technical writing.
documentation
0xsarwagya/ontoly
Draft graph-backed documentation from Ontoly summaries and traces. Use when asked to document architecture, APIs, modules, packages, or request lifecycles without re-parsing source files.
excel-auditor
leegonzales/aiskills
Analyze unknown or inherited Excel files to understand what they do, document their purpose, audit formulas for errors, and assess maintainability risk. Use when: (1) User uploads an Excel file asking 'what does this do?', (2) User needs to understand an inherited/legacy spreadsheet, (3) User wants formula auditing or error detection, (4) User asks about spreadsheet risk, complexity, or documentation, (5) User mentions 'inherited', 'legacy', 'undocumented', or 'someone left' regarding Excel files.
markdown
1mangesh1/dev-skills-collection
Markdown syntax, formatting, and document authoring for docs, READMEs, and technical writing. Use when user mentions "markdown", "write README", "format markdown", "markdown table", "markdown links", "GFM", "GitHub flavored markdown", "markdown linting", "MDX", "markdown to HTML", "table of contents", "markdown badges", "markdown checklist", or authoring documentation in markdown.
master-rules
mmtaee/ai_skills
Unified global rules for the agent, covering baseline architecture, implementation standards, documentation, and educational content.
api-documentation
camilooscargbaptista/cto-toolkit
**API Documentation & Design (OpenAPI/Swagger)**: Helps write and review API documentation, generate OpenAPI/Swagger specs, design RESTful APIs, and document GraphQL schemas. Use whenever the user mentions 'API docs', 'Swagger', 'OpenAPI', 'API specification', 'API design', 'REST API', 'endpoint documentation', 'API contract', 'API versioning', 'GraphQL schema', 'API reference', or asks to document their API, generate a Swagger spec, design API endpoints, or review API contracts for consistency.
changelog-generator
maslennikov-ig/claude-code-orchestrator-kit
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
add-cli-option
remotion-dev/remotion
Add a new Remotion CLI or config option by creating an AnyRemotionOption, registering CLI parsing, wiring config setters, and updating documentation. Use when adding or converting command-line flags or Remotion options.
add-new-package
remotion-dev/remotion
Add a new package to the Remotion monorepo, including package scaffolding, monorepo registration, documentation, build scripts, tests, and release checklist updates. Use when creating a new @remotion package.
technical-writing-pro
truongnat/simple-skills
Expert Technical Writing covering docs-as-code, information architecture, style guides, API documentation, and user education.
ronin-technical-writing
drrius/ronin
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /ronin-technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
readme-generator
johnefemer/skillfish
Generate README files that explain setup, usage, architecture, workflows, and contribution details with developer-friendly structure.
technical-writing
ffsshhttiikk/opencode-agents-skills
Creating clear, comprehensive technical documentation
technical-writing
kendrick/skills
Layered prose standard for developer-facing writing: commit messages, code comments, PR descriptions, API reference, changesets, and other technical docs, including the prose inside a README that already exists. Use when writing or reviewing a commit message, drafting or auditing code comments, describing a PR, or polishing developer documentation. Dispatches each artifact type to a profile that names which layers apply—Diátaxis document modes, Google developer style, STE sentence principles, Global English—and every draft finishes with a prose audit. Not for conversational answers, not for the code itself, and never for anything addressed to a person: emails, DMs, and other messages route to the setup's own voice process, which replaces the prose audit rather than layering on it. Authoring a whole README belongs to readme-coauthorship, and proposals and specs to doc-coauthoring. This skill governs prose style, not document-structure workflows.
technical-writing
kienbui1995/magic-powers
Use when writing documentation, READMEs, API docs, changelogs, ADRs, or user guides — ensures clarity, structure, and project consistency
changelog-generator
igordotti/awesome-claude-skills
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
changelog-generator
zircote/.claude
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
changelog-generator
jamait/awesome-opencode-skills
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
release-notes
pooriaarab/skills
Use when preparing release notes or a user-facing changelog for a new version — diffing branches, filtering to user-facing changes, and writing in a consistent product voice. Triggers include "write release notes", "draft the changelog", "release notes for v2.x", "what shipped this release".
agents-md
getsentry/dotagents
This skill should be used when the user asks to "create AGENTS.md", "update AGENTS.md", "maintain agent docs", "set up CLAUDE.md", or needs to keep agent instructions concise. Guides discovery of local skills and enforces minimal documentation style.
doc-coauthoring
getsentry/dotagents
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.
wiki-page-writer
microsoft/skills
Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating technical deep-dives, or documenting specific components or systems.
connection-properties
microsoft/aspire
Specialized agent for creating and improving Connection Properties in Aspire resource and README files
build-docs
microsoft/semantic-link-labs
Guide for building documentation and validating docstrings. Use this when asked to build docs, check docstrings, or validate documentation.
construction-docs
tibsfox/gsd-skill-creator
Generates complete construction documentation packages — BOM, installation sequences, commissioning checklists, and O&M manuals — from verified engineering designs.
grill-with-docs
flutter/skills
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
natural-writing
flutter/skills
Contains well-defined rules for creating natural, accurate, and readable writing. Use whenever authoring longer text, like analysis documents, PR or CL descriptions, or documentation.
upstash-search-js
upstash/search-js
Entry point for documentation skills covering Upstash Search quick starts, core concepts, and TypeScript SDK usage. Use when a user asks how to get started, how indexing works, or how to use the TS client.
etsi-spec
jr2804/prompts
Retrieving metadata and documentation for ETSI specifications. Use when you need to find latest version, full title, publication date, download URLs, or version history for any ETSI specification (EN, ES, EG, TS, TR, SR, GS, GR, PAS). Supports parts (e.g., -1, -2, -3).
csharp-standards
devbyray/github-copilot-starter
C# coding standards and conventions including naming, formatting, and best practices. Use when working with .cs files, writing C# code, or when the user asks about C# naming conventions, code structure, XML documentation, or .NET development patterns.
lua-binding-reference
cataclysmbn/cataclysm-bn
Quick reference for Cataclysm-BN Lua binding macros, Luna usertypes, libraries, documentation, type patterns, build steps, and common errors.