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
documentation
thejustinwalsh/three-flatland
Use when authoring, restructuring, splitting, or auditing any docs page or content collection in this repo — choosing what type a page should be, deciding what belongs on it, or checking accuracy, structure, and completeness before a release.
Documentation
anotther/driva
Generate and update technical documentation
documentation
aws-samples/sample-claude-code-agent-team
Technical writing patterns for READMEs, runbooks, and architecture docs, with accuracy verification. Use when writing documentation, creating runbooks, or documenting system architecture.
documentation
acartine/osterman
Create clear, well-placed user documentation following project patterns.
documentation
newmindsgroup/ai-agent-skills-library
Documentation generation workflow covering API docs, architecture docs, README files, code comments, and technical writing.
documentation
jb-612/tirvi
Create, update, classify, and archive docs in docs/. Enforces naming, versioning, folder placement, and lifecycle rules.
documentation
laithalenooz/claude
Documentation generation workflow covering API docs, architecture docs, README files, code comments, and technical writing.
documentation
kunanonj/claude-skills-hub
Documentation generation workflow covering API docs, architecture docs, README files, code comments, and technical writing.
documentation
1ambda/dataops-platform
Technical documentation generation and maintenance. Creates API docs, code comments, READMEs, and changelogs. Use when documenting code, APIs, or creating project documentation.
documentation
taidaid/node-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
hk-vk/skills
Documentation documentation and resources. Use this skill when working with Documentation or when the user mentions documentation.
Documentation
mayurrathi/awesome-agent-skills
Documentation generation workflow covering API docs, architecture docs, README files, code comments, and technical writing.
documentation
kevinjian16/daemon
>-
documentation
projectious-work/aibox
Guides writing effective documentation — READMEs, API docs, inline comments. Use when creating or improving project documentation.
refresh-readme
emasoft/claude-plugins-validation
Refresh AUTO-* marker blocks in a plugin's README (auto-detected components table). Use when the README's components list has drifted from the filesystem. Used dynamically via the-skills-menu (TRDD-478d9687).
awesome-readme
aojdevstudio/agentic-utilities
Creates, improves, and reviews GitHub README files using a story-first, engagement-focused structure. Use when asked to write a new README, rewrite an existing README to be more compelling, or analyze a README for clarity, differentiation, and star-worthiness.
readme-skill
evol1228/readme-skill
Design and write beautiful, professional README.md files for any repo or project. Use this whenever the user asks to create, write, improve, redesign, or polish a README or project documentation page — including casual asks like "add a readme", "document this project", "make my repo look presentable", "my readme sucks", or when they're about to publish/open-source a project that lacks a proper README.
readme-writer
j4flmao/agent-skills
>
readme-sync
tygwan/ultra-codex-init
Automatically synchronize README.md with actual project components. Scans .codex directory and updates Agents, Skills, Hooks, Commands sections.
readme-writing
nvnunes/astro-agents
Write, revise, or review README.md files, including project overviews, folder-level README files, setup orientation, navigation, and entrypoint documentation. Use when the target file is a README, not general docs, plans, or prompts.
project-readme-writer
unimolecule/ai
Use when writing or updating project README files for repositories, apps, packages, libraries, CLIs, examples, monorepos, workspace packages, or README structure reviews. Use for repo inspection, README information architecture, project positioning, command documentation, architecture summaries, and contributor-facing setup guidance.
readme-update
bakaschwarz/agent-skills
>
updating-readmes
klefix/nightshift
Use when project structure, setup instructions, or capabilities change — updates README files at any level (root, packages, sub-modules) and detects stale content
readme-design
just-agent/readme-design-skill
Design and rewrite polished GitHub README homepages for repositories and profile READMEs, especially Chinese/English open-source projects. Use when the user asks to beautify, redesign, improve, package, market, add a README logo or wordmark, or make a README more professional, visual, persuasive, scannable, or GitHub Pages-like. Focus on README aesthetics, layout, badges, screenshots, logo/wordmark identity, project positioning, information architecture, and Markdown/HTML that renders well on GitHub.
compact-readme
tituskirch/skills
Compacts an existing, overstuffed README so the landing view leads to the install/run command in ~30 seconds, without losing any information — long feature walls and option tables move into <details> blocks, install+quickstart merge, and duplicated taglines/runtime-notes are deduped. Preserves the kirchDev house style (centered hero, emoji tagline, section emojis, Versioning/License closers). The complement to write-readme — write-readme scaffolds a new README from scratch; compact-readme slims down one that already exists. Use when a README is too long/dense/repetitive and the user wants it tightened, condensed, decluttered, or made scannable. Do not use to create a new README.
readme
nathan13888/nice-skills
>
readme-update
momentmaker/kaijutsu
Detect README staleness and propose a targeted update. Use when the user says "update readme", "is the readme out of date", "readme refresh", "/readme-update", or after merging a feature that likely changes installation, usage, or public API. Reads the README's last-touched commit, walks the commits since, and proposes a section-by-section diff.
readme
l0lxl0lw/claude-config
Read the README file in the current directory and execute the instructions or tasks described within it.
11ai-super-readme
rj11io/11ai
Audit, update, and repeatedly improve a repository's README files until they meet a high documentation bar — fix existing READMEs that no longer match the code, add missing information, create new READMEs in folders that need one, and keep running fresh review passes until no material issue remains. Use when Codex needs to refresh, audit, fix, or generate READMEs or repository documentation, when docs are stale or out of date, or when the user asks to \"update the readmes\" in any form and wants them iterated to a high-confidence quality bar. Stops and reports when the change set becomes unmanageable or troubleshooting outweighs progress.
update-readme
ranjankumarpatel/claude-code-multi-model
Analyze the codebase and regenerate README.md to reflect current project structure, commands, skills, MCP servers, and configuration. Use after code changes, new features, or when README is stale.
github-readme
jangtrinh/easeui-agent
Create or improve GitHub Profile READMEs and Project READMEs — from strategy to pixel-perfect markdown with dynamic stats, badges, and automation.
readme-score
giodl73-repo/giodl73-repo
Score any public-repo README per-section against the 50-point rubric documented in conventions.md, and (when target isn't the front-door repo) check alignment with giodl73-repo's README. Read-only — outputs a report and the row to paste into TRACKER.md. Use when refreshing a repo's README score or before deciding to rewrite a section.
create-readme
aicyberguardian/storycraftr-next
Create a README.md file for the project
create-readme
dhar174/numpy_game
Create a README.md file for the project
readme-sync
smorinlabs/smorinlabs-harness
Use when the user asks to "update README", "sync README", "check README", "is README up to date", "are docs consistent", "does README match the code", or any request to verify or update README.md to match the current state of the codebase.
readme-md
vladpazych/rig
Use when authoring or editing human-facing `README.md` files. Keeps them clear, present-tense, and oriented around purpose, usage, concepts, and navigation rather than governance.
readme-writing-weapon
jzferrell26/dm-skills
Authors, audits, and restructures README files so they convert visitors into users. Apply when the user says "write a README", "audit my README", "make my README better", "README for this project", "README-driven development", or when starting a new project and the README does not exist yet. Also apply when badges are broken or missing, the quickstart is not copy-paste runnable, or the user wants to differentiate between an OSS and an internal tool README. Do NOT apply for full documentation site architecture (library-guardian), per-entity code extraction (wiki-guardian), or CI badge pipeline wiring (devops-guardian).
readme-pls
devxit/skills
Creates, edits, and reviews README files using a structured 15-section guide with security rules, inferred-data confirmation, and deviation warnings. Use when drafting, rewriting, editing, or reviewing README.md, readme files, project documentation entry points, or when the user invokes readme-pls.
scan-repo-readme
nainishshafi/developer-productivity-skills
This skill should be used when the user asks to "scan the readme", "read the repo readme", "check the project documentation", "search the readme for X", "what does the readme say about Y", "summarize the readme", "find readme", "look up X in the readme", or wants to find relevant information from repository documentation files using keyword and semantic search.
blog-graphics
chiragagg5k/blog-graphics
Create stunning animated graphics for technical blog posts, modeled on the design ideologies of exceptional engineering blogs (Cursor, PlanetScale, samwho.dev, Josh Comeau, Bartosz Ciechanowski). Use when the user wants an animated diagram, illustration, or interactive figure for an article, README, or docs page. Routes to a style skill, then guides build + screenshot verification.
translate
zeabur/zeabur
Translate documentation pages to all missing locales. Use when a document exists in one locale but needs to be translated to others. Supports --dry-run, single-locale targeting, and incremental updates.
translate
ihorkatkov/pantheon
Accurate context-aware translation skill. USE THIS for any translation tasks including documentation, UI strings, comments, error messages, or any text that needs translation. Preserves formatting, code, and technical terms while adapting to domain and tone.
translate-docs
oxyflax/ai
Translate documentation (.md files) into another language. Use when: translating a markdown doc, updating an existing translation after source changes, localizing documentation, creating a french translation of a doc, keeping translations in sync with the source. Default target language is French. Translated files are placed in a folder named after the language (e.g. 'french/') mirroring the source path.
brave-search
alistairvu/dotfiles
Web search and content extraction via Brave Search API by using `bx context` followed by the query. Use for searching documentation, facts, or any web content. Lightweight, no browser required.
kagi-search
rytswd/skills.nix
Web search and content summarization via Kagi APIs. Use for searching the web, finding documentation, verifying facts, summarizing articles/videos/PDFs, or extracting key points from URLs.
markdown
umonkey/treemap
rules for formatting markdown documents and documentation. Use this whenever working with any files in the docs/ folder or any .md files.
qa-suggest
couimet/rangelink
Analyze CHANGELOG [Unreleased] against QA YAML test cases and suggest new TCs for uncovered features. Zero-argument — auto-discovers all inputs from the project.
changelog
ushkinaz/cbn-guide
This agent generates a CHANGELOG.md for the cbn-guide application by analyzing git history.
changelog
rlaope/bestwork-agent
Auto-generate changelog from git history
docbox-generation
coldbox/skills
Use this skill when configuring DocBox to generate API documentation, choosing output strategies (HTML, JSON, UML, CommandBox), setting up single or multiple source directories, running DocBox from BoxLang CLI or CommandBox CLI, customizing HTML themes, excluding files/folders from output, or building custom output strategies.
release
heltondoria/claude-code-sdd-kit
Create a semver release with version bump, changelog, and git tag (commitizen + git-cliff)
help
blerbz/blerbz-plugins
Show Inference Confidenz help and documentation
fs-mds-document
yanziyang/dotnet-skills
Scan an entire .NET repository (.NET 8–10, ASP.NET Core, workers, class libraries) and generate a Functional Specification (FS) and a Module Design Specification (MDS) as professional Word (.docx) documents, illustrated with rendered diagrams (context, feature map, process flows, state, module structure, class, sequence, ER) whose editable sources (Mermaid .mmd and draw.io files) are exported to a diagrams/ subfolder. Use this skill whenever the user asks for a functional spec, FS, module design spec, MDS, detailed design document, software/system specification, requirements documentation reverse-engineered from code, or any "spec" deliverable for a .NET system — especially when they mention Word, docx, or diagrams.
gen-pptx
shumingyang-opencode/opencode-lazy-packs
工程導向可編輯簡報產製技能。將技術主題、datasheet、spec 文件、FW/SW 架構筆記、SDK 文件、或另一個 repo 的 README/docs/code 轉為結構清楚的可編輯 .pptx 簡報。專為軟韌體工程師、半導體工程師、FAE/AE 團隊設計。說「做簡報」「產出簡報」「做成投影片」「generate presentation」「turn this into slides」時載入。
next
osagberg/finalwhistle
End-to-end workflow for shipping one MASTER_PLAN task. Picks the next unblocked task, drafts a task-spec, implements via the right subagent, runs `just test` + `just lint`, auto-runs pr-review-toolkit self-review on commits ≥100 LoC of code, commits with a structured message, updates STATUS/CHANGELOG/DECISIONS, and stops. Designed for braindead-easy iteration — the user types `/next`, this runs the full loop, returns one shipped commit, and waits for the next `/next`. Pauses on ambiguity, out-of-scope file touches, repeated test/lint failure, design-doc changes, schema drift, or unauthorized hash drift. Replaces FW v1 `/duo-implement`'s per-slice Codex review with per-task self-review + phase-gate Codex review.
gj-issue-split
thelastmagician/gj-gitlab-ai-workflow
Split confirmed requirements and solution plans into traceable GitLab work items. Use when creating development, test, documentation, release, bug, hotfix, or follow-up Issues with dependencies, labels, acceptance criteria, owners, and workflow states.