incident postmortem
by Samuel Rose
Transform raw incident logs and Slack threads into blameless, structured postmortems and 5-Whys RCA reports.
Skills for READMEs, API docs, inline comments, changelogs, and technical writing. Keep docs accurate and up-to-date with minimal effort.
1,322 live technical documentation skills for Claude Code.
by Samuel Rose
Transform raw incident logs and Slack threads into blameless, structured postmortems and 5-Whys RCA reports.
Standardized accessibility descriptions and verified analysis for electronic, hydraulic, and pneumatic schematics.
Paste any Claude conversation and get a clean, complete PDF transcript — every message, every artifact, automatically formatted.
by Samuel Rose
Writes conventional commit messages by analyzing your staged git changes. Detects commit type, scope, and breaking changes automatically.
by Samuel Rose
Generates a complete, polished README.md by scanning your actual project structure, dependencies, and code.
by Samuel Rose
Writes clear pull request descriptions by analyzing your branch diff. Covers what changed, why, how, and what to test. Works with GitHub, GitLab, and Bitbucket.
by Rian O'Leary
Transform raw skill documentation into high-conversion, readable marketplace listings without losing LLM context.
by Samuel Rose
Generates user-facing changelogs from git history. Transforms developer commit messages into clear release notes that users actually understand.
Generate a README from your actual repo, not a hallucinated guess. Scans your manifests (package.json, pyproject.toml, go.mod, Cargo.toml) for real install steps, scripts, and dependencies across Node, Python, Go, Rust, and Java. Documentation that matches the code instead of drifting from it.
by Kevin Cline
Convert source code into OpenAPI 3.0 specs or Markdown docs via static analysis of Express, FastAPI, and more.
by Kevin Cline
Instantly convert Markdown files into polished, self-contained HTML slideshows with dark mode and navigation.
by Naor Sabag
Generate animated, step-by-step data flow diagrams for architectures, code paths, and user journeys.
by Sergey Leka
Generate professional Conventional Commits in Russian from staged Git changes.
Generate Conventional Commit messages from your staged git diff: auto-detects type and scope from the changed files, flags breaking changes, and keeps work-in-progress out of the message. Clean, searchable history that plays nicely with automated changelog tools.
by Kevin Cline
Deep project analysis to generate professional README.md files with API references, scripts, and stack detection.
by Edric Vale
Design CLI tools with the right flags, help text, and error messages users actually understand.
by Kevin Cline
Automate professional, Conventional Commits-compliant git messages via deep diff analysis.
by Kevin Cline
Automatically generate and update a professional CHANGELOG.md from your git history and Conventional Commits.
Generate Markdown release notes from local Git ranges, recent commits or tag comparisons. Review commit IDs, grouped changes and author-marked breaking changes. Version suggestions are limited to supported unreleased selections; the helper does not publish releases.
by Shandra
Transforms undocumented repositories into professional README files, setup guides, command maps, architecture notes, environment references, testing docs, and AI agent handoff files.
by Kevin Cline
Generate comprehensive repository analytics and contributor insights from your git history.
by LocoLoboZ
Draft, update, and convert professional Functional Requirements Specifications (FRS) for procurement and GRC.
Generate a complete pull request description from your staged changes, commits, and branch diff: summary, changes, test plan, and checklist, ready for GitHub, GitLab, or Bitbucket. Cross-checks the file list against what git actually reports, so reviewers get the why and what without hallucinated filenames.
Each skill on this page is a SKILL.md file built for technical documentation work and confirmed to run in Claude Code. Connect your agent through MCP and Claude Code follows the workflow the creator encoded instead of improvising from a short prompt.
Listings are ranked by uses, upvotes and reviews, so what surfaces first is what other Claude Code users actually keep. Free and paid skills compete on the same page, and every listing shows its security scan result before you use a skill.
Learn how it works: Best documentation skills for AI agents and How to install skills in Claude Code.
These are the jobs creators are actually shipping skills for in this category. Each one encodes a full workflow, so Claude Code follows the same method every time instead of improvising from a one-line prompt.
Start with the outcome, not the label. Open the listing and read the SKILL.md preview: a good technical documentation skill states exactly what it does, what it needs from you, and what it deliberately refuses to do. Vague descriptions usually mean vague output.
Then check three things: the number of uses and reviews (other Claude Code users voting with their setup), whether the creator ships updates, and whether the skill is universal SKILL.md or agent-specific. Free skills are a fine way to test a creator's style before buying their paid work.
Related categories for Claude Code: Writing & Content, Research & Analysis and Frontend & Web Apps.
Every paid creator is verified before they can sell, so skills come from practitioners, not scraped prompt packs.
Each version is scanned for prompt injection, credential exfiltration and destructive commands before it goes live.
Some skills are free, but most are paid. Paid skills show the price upfront and include future updates from the creator.
Connect your agent to Agensi once and the skill is ready to use. The latest version loads each time, and nothing is saved.
Questions, partnership ideas, or feedback on the platform? Tell us what's working and what isn't, we love to hear from you!
Founder & CEO of Agensi
Email UsBook a Callinfo@agensi.io
We typically respond within a few hours during business hours.