Docs & writing
16,621 rows, by stacks then stars
3,030 of these skill files have been read, by 1,951 distinct authors, and what they tell an agent counted. What Docs & writing authors agree on, and what they forbid
danielvogler/ai-skills-library/.agents/skills/fetching-dbt-docs Skill
0★ repoRetrieves and searches dbt documentation pages in LLM-friendly markdown format. Use when fetching dbt documentation, looking up dbt features, or answering questions about dbt Cloud, dbt Core, or the dbt Semantic Layer.
danielvogler/ai-skills-library/.agents/skills/provider-docs Skill
0★ repoCreate, update, and review Terraform provider documentation for Terraform Registry using HashiCorp-recommended patterns, tfplugindocs templates, and schema descriptions. Use when adding or changing provider configuration, resources, data sources, ephemeral resources, list resources, functions, or guides; when validating generated docs; and when troubleshooting missing or incorrect Registry documentation.
SunnyDevendranadh/Bloom/plugins/bloom/skills/bloom Skill
0★ repoPer-session sticky mode that makes markdown bloom into rich, self-contained .html artifacts — reports, reviews, plans, docs, comparisons, diagrams, editor UI. Activate with /bloom, /bloom-on, or phrases like "bloom on", "let it bloom". Deactivate with /bloom-off or "bloom off". Once on, it stays on for the rest of the session.
pngdeity/apm-user-repository/packages/agent-architect/.apm/skills/agent-architect Skill
0★ repoArchitect, write, structure, and maintain AI agent context files (AGENTS.md and SKILL.md). Use when creating new agent context configurations, scaffolding AGENTS.md files, designing SKILL.md modules, or determining where content belongs in the agent abstraction stack. Not for writing code or implementing features.
pngdeity/apm-user-repository/packages/find-docs/.apm/skills/find-docs Skill
0★ repoRetrieves up-to-date documentation via ctx7 for libraries, frameworks, SDKs, cloud APIs, and any tool where training data may be outdated. Prefer over websearch or webfetch for documentation lookups. For CLI tools installed on this system, try skill("local-first") first; if man pages and --help don't cover it, use ctx7.
pngdeity/apm-user-repository/packages/golang-core-style/.apm/skills/go-documentation Skill
0★ repoUse when writing or reviewing documentation for Go packages, types, functions, or methods. Also use proactively when creating new exported types, functions, or packages, even if the user doesn't explicitly ask about documentation. Does not cover code comments for non-exported symbols.
pngdeity/apm-user-repository/packages/golang-design/.apm/skills/go-testing Skill
0★ repoUse when writing, reviewing, or improving Go test code — including table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions with cmp.Diff. Also use when a user asks to write a test for a Go function, even if they don't mention specific patterns like table-driven tests or subtests. Does not cover benchmark performance testing.
pngdeity/apm-user-repository/packages/local-first/.apm/skills/local-first Skill
0★ repoDiscover and use man pages, --help, apropos, info pages, system logs, and kernel params before reaching for external documentation. Prefer over websearch or ctx7 for installed CLI tools, system utilities, and infrastructure commands. Local sources are version-matched and cost zero context tokens. When local sources are exhausted, fall back to skill("find-docs") → ctx7, then websearch last.
pngdeity/apm-user-repository/packages/microsoft-rust-guidelines/.apm/skills/microsoft-rust-guidelines Skill
0★ repoMicrosoft's Pragmatic Rust Guidelines for API design, crate architecture, library UX, resilience, FFI, performance optimization, documentation, and AI-oriented code. Invoke this skill when designing new Rust APIs, setting up crate structures, writing library code, implementing FFI, optimizing hot paths, authoring documentation, or making architectural decisions about Rust code organization.
pngdeity/apm-user-repository/packages/technical-documentation/.apm/skills/technical-documentation Skill
0★ repoComprehensive guidance for writing architectural and technical documentation. Use when the user asks to create or update Architecture Decision Records (ADRs) or Technical Design Documents (Micro-Leaves).
popsiclelmlm/skills-cn/skills/engineering/grill-with-docs Skill
0★ repo一场 grilling session,会用既有 domain model 挑战你的计划、打磨 terminology,并在 decisions crystallise 时内联更新 documentation(CONTEXT.md、ADRs)。当用户想用项目语言和已记录决策 stress-test 一个计划时使用。
popsiclelmlm/skills-cn/skills/engineering/setup-matt-pocock-skills Skill
0★ repo在 AGENTS.md/CLAUDE.md 和 `docs/agents/` 中设置 `## Agent skills` block,让 engineering skills 知道该 repo 的 issue tracker(GitHub 或 local markdown)、triage label vocabulary 和 domain doc layout。在第一次使用 `to-issues`、`to-prd`、`triage`、`diagnose`、`tdd`、`improve-codebase-architecture` 或 `zoom-out` 前运行;如果这些 skills 看起来缺少 issue tracker、triage labels 或 domain docs 上下文,也运行它。
popsiclelmlm/skills-cn/skills/in-progress/writing-beats Skill
0★ repo以 beats 旅程的方式塑造文章,类似 choose-your-own-adventure。用户从 raw material 中选择一个 starting beat,你只写那个 beat,然后提供下一步 pivot 选项,逐 beat 推进,直到文章自然结束。当用户有 raw material,并想把它组装成 narrative 而不是 argument 时使用。
popsiclelmlm/skills-cn/skills/in-progress/writing-fragments Skill
0★ repo一场 grilling session,从用户那里挖掘 fragments,即异质的写作 nuggets(claims、vignettes、sharp sentences、half-thoughts),并把它们追加到单个 document 中,作为未来文章的 raw material。当用户想在施加结构前发展 ideas,或提到 "fragments"、"ideate"、"raw material" 写作时使用。
popsiclelmlm/skills-cn/skills/in-progress/writing-shape Skill
0★ repo接收一个 raw material 的 markdown file,通过 conversational session 把它塑造成文章:起草 candidate openings,逐段增长文章,并在每一步争论 format(lists、tables、callouts、quotes)。当用户有一堆 notes、fragments 或 rough draft,并想把它变成可发布内容时使用。
popsiclelmlm/skills-cn/skills/productivity/write-a-skill Skill
0★ repo创建结构合适、具备 progressive disclosure 和 bundled resources 的新 agent skills。当用户想创建、编写或构建一个新 skill 时使用。
Techtide kubernetes allocation report
TechTideOhio/techtide-harness-kit/skills/finops/techtide-kubernetes-allocation-report Skill
0★ repoProduce OpenCost-compatible namespace, pod, and workload cost allocation tables from user-supplied cluster shape data and public cloud pricing. Input is cluster topology provided by the caller; no cluster credentials or live API access are required or accepted. Output maps to FOCUS v1.2 columns.
Techtide oci dbtools sql analyst
TechTideOhio/techtide-harness-kit/skills/oci/techtide-oci-dbtools-sql-analyst Skill
0★ repoUse OCI Database Tools and database documentation safely for SQL inspection, report definitions, table metadata, and controlled query execution. Use for DBTools connections, read-only SQL analysis, and schema/report exploration.
TechTideOhio/techtide-harness-kit/skills/techtide/techtide-agent-autopsy-report Skill
0★ repoPerform post-run analysis of failed or risky agent work by reconstructing goal, context, tool calls, failure mode, missing guardrails, and preventive skill updates. Use when an agent needs Alex Cinovoj / TechTide live-coding patterns, tool routing, guarded prototype-to-production workflows, or cross-harness prompt/skill adapters.
Pesty-Marketing/agent-skills/storybrand Skill
0★ repoApply the StoryBrand SB7 framework to create or evaluate customer-facing copy. Two modes — Write (homepage, landing page, email, ad, one-liner) and Audit (review existing copy against SB7 checklist). Invoke when user says "use StoryBrand," "SB7," "apply the framework," or requests help with brand messaging, homepage copy, or marketing copy where narrative structure matters. Not for blog posts, SEO articles, or general writing.
Pesty-Marketing/agent-skills/storytelling Skill
0★ repoApply Will Storr's Science of Storytelling framework (Sacred Flaw, theory of control, dramatic question, change-driven openings) to long-form narrative copy where engagement matters more than direct-response structure. Two modes — Write (founder narrative, brand story, About page, case study, blog hook, long-form sales) and Audit (review existing narrative for character flaw, change, curiosity gap, transformation arc). Invoke when user says "use Storr," "Science of Storytelling," "sacred flaw," "make this more compelling," or requests help with founder stories, About pages, case studies, brand origin, or any narrative where character + transformation is the point. Not for homepages, ad headlines, or scan-first marketing surfaces — use the storybrand skill for those.
Pesty-Marketing/agent-skills/website-launch-impact-report Skill
0★ repoBuild a client-facing before/after report answering whether a website relaunch or migration helped or hurt — SEO, conversions, and UX, pre-launch vs post-launch. Use when a site was relaunched, redesigned, or migrated to new URLs and someone asks 'did the new site help or hurt', 'new-site impact', 'before/after website report', or 'launch impact report for <client>'. Not for routine monthly SEO reporting or a report unconnected to a launch/migration event.
Pesty-Marketing/agent-skills/yt-structure Skill
0★ repoUse when turning a YouTube video, talk, podcast, or web article into a clean, citable Markdown document for an LLM knowledge library or RAG/OKF bundle — triggers like "transcribe and structure this video", "structure this transcript", "add this talk/article to the library". Covers pulling captions, faithful structuring, and editor's-note / [?] flagging.
marktantongco/opencodelinux/skills/case-study-writing Skill
no license0★ repoB2B case study writing with STAR framework, data visualization, and research. Covers structure, customer quotes, metrics presentation, and distribution formats. Use for: customer success stories, portfolio pieces, sales enablement, marketing content. Triggers: case study, customer story, success story, b2b case study, client testimonial, customer case study, portfolio case study, use case, customer win, results story
marktantongco/opencodelinux/skills/doc-coauthoring Skill
no license0★ repoGuide 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.
marktantongco/opencodelinux/skills/docx Skill
no license0★ repoUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
marktantongco/opencodelinux/skills/elevenlabs-dubbing Skill
no license0★ repoElevenLabs automatic dubbing - translate and dub audio/video into 29 languages while preserving speaker voice via inference.sh CLI. Capabilities: auto speaker detection, voice-preserving translation, video dubbing, audio localization. Use for: content localization, video translation, multilingual content, international distribution. Triggers: dubbing, dub video, translate audio, video translation, audio translation, localize content, elevenlabs dubbing, eleven labs dub, multilingual dub, voice translation, auto dub, language dub, content localization
marktantongco/opencodelinux/skills/github-actions-docs Skill
no license0★ repoUse when users ask how to write, explain, customize, migrate, secure, or troubleshoot GitHub Actions workflows, workflow syntax, triggers, matrices, runners, reusable workflows, artifacts, caching, secrets, OIDC, deployments, custom actions, or Actions Runner Controller, especially when they need official GitHub documentation, exact links, or docs-grounded YAML guidance.
marktantongco/opencodelinux/skills/grill-with-docs Skill
no license0★ repoGrilling 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.
marktantongco/opencodelinux/skills/newsletter-curation Skill
no license0★ repoNewsletter curation with content sourcing, editorial structure, and subscriber growth strategies. Covers issue formatting, link roundups, commentary style, and sending cadence. Use for: email newsletters, link roundups, weekly digests, curated content, creator newsletters. Triggers: newsletter, email newsletter, newsletter curation, weekly digest, link roundup, curated newsletter, newsletter writing, newsletter format, subscriber growth, newsletter strategy, content curation, newsletter template
marktantongco/opencodelinux/skills/press-release-writing Skill
no license0★ repoPress release writing in AP style with inverted pyramid structure. Covers formatting, datelines, quotes, boilerplates, and fact-checking. Use for: product launches, funding announcements, partnerships, company news, events. Triggers: press release, pr writing, media release, news release, announcement, product launch announcement, funding announcement, company news, media advisory, ap style, press statement, news wire
marktantongco/opencodelinux/skills/product-changelog Skill
no license0★ repoProduct changelog and release notes that users actually read. Covers categorization, user-facing language, visuals, and distribution. Use for: release notes, changelogs, product updates, feature announcements, versioning. Triggers: changelog, release notes, product update, version notes, what's new, feature announcement, product changelog, update log, release announcement, version release, product release, ship notes
marktantongco/opencodelinux/skills/readme-i18n Skill
no license0★ repoUse when the user wants to translate a repository README, make a repo multilingual, localize docs, add a language switcher, internationalize the README, or update localized README variants in a GitHub-style repository.
marktantongco/opencodelinux/skills/seo-content-writer Skill
no license0★ repoMerged opencode config + agents + accomplishments showcase — 217 skills, 17 agent profiles, 6 MCP servers, 78-server registry
marktantongco/opencodelinux/skills/setup-matt-pocock-skills Skill
no license0★ repoSets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.
marktantongco/opencodelinux/skills/technical-blog-writing Skill
no license0★ repoTechnical blog post writing with structure, code examples, and developer audience conventions. Covers post types, code formatting, explanation depth, and developer-specific engagement patterns. Use for: engineering blogs, dev tutorials, technical writing, developer content, documentation posts. Triggers: technical blog, dev blog, engineering blog, technical writing, developer tutorial, tech post, code tutorial, programming blog, developer content, technical article, engineering post, coding tutorial, technical content
marktantongco/opencodelinux/skills/write-a-skill Skill
no license0★ repoCreate new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
marktantongco/opencodelinux/skills/writing-plans Skill
no license0★ repoUse when you have a spec or requirements for a multi-step task, before touching code
marktantongco/opencodelinux/skills/writing-skills Skill
no license0★ repoUse when creating new skills, editing existing skills, or verifying skills work before deployment
marktantongco/opencodelinux/skills/xlsx Skill
no license0★ repoUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
specdd/plugin-junie/skills/specdd-docs Skill
0★ repoUse when Junie needs to write or update documentation from active SpecDD specs.
nyquistwilder/personal-pi/skills/go-docs Skill
0★ repoGo documentation workflow for README, package comments, Go doc examples, CLI help, HTTP API contracts, architecture notes, and keeping docs synchronized with greenfield behavior.
nyquistwilder/personal-pi/skills/python-docs Skill
0★ repoPython documentation workflow for README usage, docstrings, examples, CLI help, HTTP API contracts, architecture notes, and keeping docs synchronized with tested behavior.
nyquistwilder/personal-pi/skills/rust-docs Skill
0★ repoRust documentation workflow for README, crate-level docs, rustdoc, doctests, examples, CLI help, API contracts, architecture notes, and keeping docs synchronized with greenfield behavior.
cmdecker95/skills/skills/discussion-writer Skill
no license0★ repoWrite college discussion posts/replies from course notes. Rewrite placeholder in actual file. Trigger: user mentions writing discussion post, dir w/ placeholder (WRITE HERE / WRITE ME / TODO / <blank>). Also "write my discussion", "draft reply", "fill discussion section", markdown w/ Discussion heading + placeholder.
cmdecker95/skills/skills/docx Skill
no license0★ repoUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
The same file is in 31 other repositories
justinramos101/agent-skill-kit/skills/.experimental/docs Skill
0★ repoUse for documentation as a product surface, in either direction. Existing docs: audit or debug a README, CHANGELOG, quickstart, onboarding, API reference, examples, contributor guide, help center, or an agent-readable file like llms.txt that also serves human readers — friction, drift, staleness, findability, audience conflict. New docs: design the IA, page structure, source of truth, examples strategy, and versioning for a docs surface before it exists, or define how docs quality is measured — telemetry, CI gates, freshness checks, retrieval evals. Triggers: 'audit our docs/README/help', 'our quickstart fails', 'review our changelog', 'design our docs IA', 'how should we structure the quickstart/reference', 'set up docs CI gates or freshness checks', 'define docs metrics'. Do NOT use for API/SDK/CLI friction beyond the docs (install, error messages, flags), for prose craft on a piece of writing that is not a docs surface, or for standalone agent-native docs and retrieval design.
justinramos101/agent-skill-kit/skills/.experimental/writing Skill
0★ repoUse to write or fix prose in either direction. Existing draft: tighten wordy lines (revise), fix mechanics, grammar, and consistency while preserving voice (copyedit), or diagnose why a piece drags, buries the point, or fails to land. New piece: structure an argument or memo (PRD, RFC, recommendation), organize a task-oriented technical doc, get a rough first pass down without stalling, or give a talk, pitch, or narrative a persuasive arc. Triggers: 'tighten this', 'copyedit this', 'review my draft', 'why does this drag', 'help me outline this RFC', 'draft this announcement', 'make this pitch land'. Do NOT use for docs-as-product-surface work (a doc set's IA, retrieval, navigation, or README/quickstart design), for reviewing UI copy as a usability surface, for code comments or docstrings, or for visual/slide design.
justinramos101/agent-skill-kit/skills/eval-best-practices Skill
0★ repoAgent evals — design or audit the measurement program for an AI agent or skill: evaluation contracts, production-shaped datasets, task fidelity, calibrated LLM judges, outcome and trajectory tests, repeated-trial reliability, held-out release gates, production-feedback handoffs, and activation/trigger evals. Use for 'design our agent evals', 'is our judge trustworthy', 'are these tasks valid', 'which reliability metric fits', 'gate a model swap', or 'design the incident-to-regression loop'. Do NOT use for designing agent SDK/tool surfaces, writing agent-readable docs, scaffolding repo CI/hooks, reviewing human unit/integration tests, or operating production monitoring, triage, or drift response — this skill designs the eval contract and handoff.
justinramos101/agent-skill-kit/skills/research Skill
0★ repoUse for source-grounded research. Two frames, inferred from the request: report — open-ended topic or whole-domain research emitting a cited markdown report (primer, survey, deep-dive literature review, or domain landscape map); opportunity — validate a named product/business/feature idea into a go/no-go memo built on Facts/Assumptions/Decisions/Risks. Triggers: 'research X', 'primer on X', 'map the X landscape', 'what's known about X', 'get me oriented in X', 'should we build X', 'validate this opportunity'. Do NOT use to review an existing artifact (prompt, plan, spec, deck), to compare a fixed set of already-named options, or to brainstorm new ideas from scratch.
justinramos101/agent-skill-kit/skills/ux Skill
0★ repoEnd-user UX and UI, both directions: audit what exists, design what doesn't. Audit: 'UX review', 'accessibility audit', 'is this WCAG compliant', heuristic evaluation of a confusing flow, form friction and drop-off, navigation/IA review, error-and-recovery copy, keyboard/screen-reader/contrast passes. Design: 'design this dashboard/UI', build a screen, prototype, or slide deck, author a design system with tokens, add motion, elevate a working-but-generic app to feel premium ('add polish', 'make it feel premium', 'elevate the whole app'), run an 'anti-slop UI pass' on generated UI, prep an artifact for host embedding or export. Do NOT use for a go-all-out maximum-creativity showpiece where distinctiveness is the whole brief, retention or re-engagement strategy on its own, developer-facing surfaces (APIs, SDKs, CLIs, error envelopes), docs as a reading surface (READMEs, quickstarts), UX of surfaces an agent operates, or prose editing.
ievo-ai/skills/plugins/ievo/skills/handoff Skill
0★ repoiEvo — self-evolving plugin for Claude Code. Capture lessons, patch local agents and skills, replay logs on upstream updates.
AravindS-Wick/aravindhan-skills/skills/autodoc Skill
no license0★ repoManage and execute tasks for autodoc. Generate deep documentation for undocumented or poorly-documented areas of the Mailchimp monolith codebase. Use this skill whenever the user asks to document code, understand legacy code and write it up, produce a reference doc, create a current-state analysis, or says things like "document this", "write docs for", "I need docs on", "explain and document", or points at a file/directory/system and wants it documented. Works with file paths, directory paths, or natural language descriptions like "the campaign sending system" or "how automations work". Always use this skill rather than ad-hoc documentation — it produces docs that match this repo's conventions and places them correctly in docs/.
AravindS-Wick/aravindhan-skills/skills/brand-guidelines Skill
no license0★ repoWrite copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.
AravindS-Wick/aravindhan-skills/skills/firecrawl-download Skill
no license0★ repoManage and execute tasks for firecrawl-download. Download an entire website as local files — markdown, screenshots, or multiple formats per page. Use this skill when the user wants to save a site locally, download documentation for offline use, bulk-save pages as files, or says "download the site", "save as local files", "offline copy", "download all the docs", or "save for reference". Combines site mapping and scraping into organized local directories.
AravindS-Wick/aravindhan-skills/skills/grill-with-docs Skill
no license0★ repoForces grounding using live documentation (Redis, Postgres, external API docs, frameworks) fetched via curl or web search before generating integration code or database schemas.
AravindS-Wick/aravindhan-skills/skills/legal-docs-generator Skill
no license0★ repoGenerate Privacy Policies, Terms of Service, and other legal documents with 7-level verification.
AravindS-Wick/aravindhan-skills/skills/library/agents-md Skill
no license0★ repoThis 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. Enforces research-backed best practices for minimal, high-signal agent documentation.
The same file is in 1 other repository
AravindS-Wick/aravindhan-skills/skills/library/api-documentation-generator Skill
no license0★ repoGenerate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices
The same file is in 3 other repositories
AravindS-Wick/aravindhan-skills/skills/library/api-documentation Skill
no license0★ repoAPI documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.
The same file is in 2 other repositories