agentsclimarketplace

Docs & writing

16,641 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

  • Brainstorm beagle

    existential-birds/beagle/plugins/beagle-analysis/skills/brainstorm-beagle Skill

    79★ repo

    Use when the user has a fuzzy idea and wants to shape it into a concrete project spec before planning or building. Triggers on: "brainstorm this", "I have an idea for...", "help me think through this project", "what should I build", "spec this out". Also catches vague feature descriptions needing structured questioning to clarify scope. Does NOT write code, plan implementation, review strategy docs, or run strategy interviews \u2014 produces a WHAT/WHY spec through dialogue, not a HOW plan.

  • Quick plan

    existential-birds/beagle/plugins/beagle-analysis/skills/quick-plan Skill

    79★ repo

    Use when you need a bite-sized, TDD-driven implementation plan but do NOT have a brainstorm-beagle spec to plan against. quick-plan reconstructs intent from the current conversation, fans out domain-expert exploration subagents across the codebase, and synthesizes the same plan format write-plan produces — without requiring `.beagle/concepts/<slug>/spec.md`. Triggers on: "quick plan", "plan this out", "plan what we just discussed", "turn this into an implementation plan", "plan this without a spec", "I don't have a spec, just plan it", "write-plan but no spec". Make sure to use this skill whenever the user wants an implementation or TDD plan and there is no spec to plan against — even if they just say "plan it" after discussing a feature. Writes to `.beagle/plans/<slug>/plan.md`. If a finalized spec already exists at `.beagle/concepts/<slug>/spec.md`, prefer write-plan. Does NOT brainstorm specs, write code, or execute the plan — produces the plan document (and an optional handoff prompt) only.

    The same file is in 2 other repositories

  • Web research

    existential-birds/beagle/plugins/beagle-analysis/skills/web-research Skill

    79★ repo

    Use when the user wants web research: gathering cited, multi-angle evidence on a specific question. Triggers on: "research X for me", "do web research on", "look up sources for", "find citations for", "gather evidence on", "what does the web say about X". Also invoked programmatically by other beagle skills (prfaq-beagle Ignition, brainstorm-beagle reference points, strategy-interview context grounding) via the companion contract. Does NOT trigger on codebase lookups ("find this function", "search the repo"), local file search, LLM-as-judge evaluation, or paywalled/auth-gated scraping. Produces a written plan, parallel-subagent findings, and a cited synthesis report on disk — never inline prose, never unsourced claims.

  • Write adr

    existential-birds/beagle/plugins/beagle-analysis/skills/write-adr Skill

    79★ repo

    Use when you want to generate Architecture Decision Records from this session. Triggers on "write ADRs", "document our decisions", "create decision records", "record the choices we made". Also useful after design discussions where decisions were reached but not documented. Does NOT extract decisions alone (use adr-decision-extraction) or provide MADR template (use adr-writing). Orchestrates the full workflow: subagent extraction, user confirmation, parallel generation, and verification.

  • Write plan

    existential-birds/beagle/plugins/beagle-analysis/skills/write-plan Skill

    79★ repo

    Use when you have a finalized brainstorm-beagle spec at `.beagle/concepts/<slug>/spec.md` and need a bite-sized, TDD-driven implementation plan before any code is written. Triggers on: "write a plan", "plan this spec", "turn the spec into a plan", "now plan the implementation", "write-plan". Reads the spec, designs the file structure, decomposes work into 2-5 minute TDD steps with exact paths and commands, self-reviews against the spec, gets user approval, then writes to `.beagle/concepts/<slug>/plan.md` and offers to generate an execution handoff prompt via the subagent-prompt skill. Does NOT brainstorm specs, write code, or execute the plan — produces the plan document (and an optional handoff prompt) only.

  • Gen release notes

    existential-birds/beagle/plugins/beagle-core/skills/gen-release-notes Skill

    79★ repo

    generate release notes for changes since a given tag

    The same file is in 1 other repository

  • Readme i18n

    xixu-me/skills/skills/readme-i18n Skill

    79★ repo

    Use 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.

    The same file is in 2 other repositories

  • Cometchat i18n

    cometchat/cometchat-skills/skills/cometchat-i18n Skill

    no license79★ repo

    Localization (i18n) across all CometChat UI Kit families — React, React Native, Angular, Android (V5/V6), iOS, Flutter (V5/V6). Covers CometChatLocalize.init signature differences (positional vs object), bundled languages, custom-language registration, RTL support, fallback to English, and cross-family drift risks. Cross-family — applies wherever the agent is configuring CometChat localization.

  • Corpus

    adewale/skill-eval-harness/tests/corpus/good-readme Skill

    79★ repo

    Create, improve, or audit README.md documents for GitHub projects. Use only when the user explicitly asks for a README, README quality/readability, README accuracy, or README examples. Do not use for full docs sites, API-reference-only work, general repo launch/readiness audits, topics/homepage metadata, or broad repository review.

  • Corpus

    adewale/skill-eval-harness/tests/corpus/guardrails-skill Skill

    79★ repo

    Code quality verification gates wired into the agent lifecycle. Use this skill whenever writing, modifying, reviewing, or debugging code — including new features, bug fixes, refactors, troubleshooting, CI/CD setup, or project bootstrapping. Also use when the user mentions "quality", "testing strategy", "CI pipeline", "guardrails", "debugging", or asks how to improve code reliability. If you're writing code or trying to understand why code isn't working, this skill applies. Do not use for README/prose-only edits, copywriting, or documentation wording changes unless the user asks for code/build/CI verification or the docs change affects generated/runtime output.

    The same file is in 1 other repository

  • Documentation lookup

    JasonxzWen/harness-hub/skills/documentation-lookup Skill

    no license77★ repo

    Load when a task needs current library, framework, SDK, API, CLI, or cloud-service documentation; fetch docs instead of relying on training data or ordinary repo evidence.

  • Effective interact

    JasonxzWen/harness-hub/skills/effective-interact Skill

    no license77★ repo

    Load when agent pauses to report relatively complex information needing Chinese-first clear complex communication, alignment, multi-option choice, status/incident, long-task fact ledgers, implementation plans, reviews, maps, explainers, evidence, risks, validation, handoff; choose plain text/Markdown/visual Markdown/HTML by decision cost; do not load merely because answer is long; skip trivial chat/bundled apps.

  • Grill me

    JasonxzWen/harness-hub/skills/grill-me Skill

    no license77★ repo

    Load when beginning every repository mutation task to run one dependency-layered batch interview; a fully aligned task takes the zero-question path, while durable documentation work uses grill-with-docs to reuse the same decision graph.

  • Grill with docs

    JasonxzWen/harness-hub/skills/grill-with-docs Skill

    no license77★ repo

    Load when a repository mutation creates or materially changes durable project contracts, OKF knowledge, specs, ADRs, or architecture/API/design documents; run a source-backed alignment pass that reuses grill-me's dependency-frontier batch protocol.

  • Stop slop

    JasonxzWen/harness-hub/skills/stop-slop Skill

    no license77★ repo

    Load when the user asks to draft, edit, or review English prose for AI-writing tells; do not load for code explanation, Chinese output, technical specs, or routine status reports.

  • External pr review

    postmelee/hyper-waterfall/templates/locales/en/mydocs/skills/external-pr-review Skill

    77★ repo

    Apply the external contributor PR review procedure. Collect PR information, write mydocs/pr/pr_{N}_review.md, verify, write pr_{N}_report.md, and move documents to archives/ when processing is complete. Use only for external contributor PRs, not internal tasks.

  • Task final report

    postmelee/hyper-waterfall/templates/locales/en/mydocs/skills/task-final-report Skill

    77★ repo

    Apply the final report and PR publication procedure for a Hyper-Waterfall task. Write the final report (`_report.md`), mark the daily task board complete, create the final commit, push the remote publish/task{N} branch, and create an Open PR to {BASE_BRANCH}. Invoke only immediately before PR publication after all stages are complete.

  • Task stage report

    postmelee/hyper-waterfall/templates/locales/en/mydocs/skills/task-stage-report Skill

    77★ repo

    Apply the stage completion procedure for a Hyper-Waterfall task. Write the stage report (`_stage{N}.md`), commit stage source and report together, and run stage verification commands. Invoke after a stage completes and before entering the next stage.

  • Task final report

    postmelee/hyper-waterfall/templates/locales/ko/mydocs/skills/task-final-report Skill

    77★ repo

    하이퍼-워터폴 타스크의 최종 보고와 PR 게시 절차를 적용한다. 최종 결과 보고서(`_report.md`) 작성, 오늘할일 완료 처리, 최종 커밋, publish/task{N} 원격 push, {BASE_BRANCH} 대상 Open PR 생성을 수행한다. 모든 단계 완료 후 PR 직전에만 호출.

  • Task stage report

    postmelee/hyper-waterfall/templates/locales/ko/mydocs/skills/task-stage-report Skill

    77★ repo

    하이퍼-워터폴 타스크의 단계 종료 절차를 적용한다. 단계별 완료 보고서(`_stage{N}.md`) 작성, 단계 소스와 보고서 묶음 커밋, 단계 검증 명령 실행을 수행한다. 한 단계가 끝나고 다음 단계 진입 직전에 호출.

  • Task final report

    postmelee/hyper-waterfall/templates/locales/zh-CN/mydocs/skills/task-final-report Skill

    77★ repo

    应用 Hyper-Waterfall task 的 final report 和 PR publication 流程。 编写 final report(`_report.md`),将 daily task board 标记为完成, 创建 final commit,push 远程 publish/task{N} branch,并创建面向 {BASE_BRANCH} 的 Open PR。 只在所有 Stage 完成后、PR publication 之前立即调用。

  • Task stage report

    postmelee/hyper-waterfall/templates/locales/zh-CN/mydocs/skills/task-stage-report Skill

    77★ repo

    应用 Hyper-Waterfall task 的 Stage 完成流程。 编写 stage report(`_stage{N}.md`),将 Stage source 和 report 一起 commit, 并运行 Stage 验证命令。在一个 Stage 完成后、进入下一 Stage 前调用。

  • Task final report

    postmelee/hyper-waterfall/templates/mydocs/skills/task-final-report Skill

    77★ repo

    하이퍼-워터폴 타스크의 최종 보고와 PR 게시 절차를 적용한다. 최종 결과 보고서(`_report.md`) 작성, 오늘할일 완료 처리, 최종 커밋, publish/task{N} 원격 push, {BASE_BRANCH} 대상 Open PR 생성을 수행한다. 모든 단계 완료 후 PR 직전에만 호출.

  • Task stage report

    postmelee/hyper-waterfall/templates/mydocs/skills/task-stage-report Skill

    77★ repo

    하이퍼-워터폴 타스크의 단계 종료 절차를 적용한다. 단계별 완료 보고서(`_stage{N}.md`) 작성, 단계 소스와 보고서 묶음 커밋, 단계 검증 명령 실행을 수행한다. 한 단계가 끝나고 다음 단계 진입 직전에 호출.

  • Docs style

    existential-birds/beagle/plugins/beagle-docs/skills/docs-style Skill

    75★ repo

    Core technical documentation writing principles for voice, tone, structure, and LLM-friendly patterns. Use when writing or reviewing any documentation.

  • Draft docs

    existential-birds/beagle/plugins/beagle-docs/skills/draft-docs Skill

    75★ repo

    Generate first-draft technical documentation from code analysis

  • Ensure docs

    existential-birds/beagle/plugins/beagle-docs/skills/ensure-docs Skill

    75★ repo

    Verify documentation coverage and generate missing docs interactively

  • Explanation docs

    existential-birds/beagle/plugins/beagle-docs/skills/explanation-docs Skill

    75★ repo

    Explanation documentation patterns for understanding-oriented content - conceptual guides that explain why things work the way they do. Use when writing an explanation doc, conceptual guide, understanding/background doc, design rationale, or architecture explanation, or when asked how/why something works. Builds on the docs-style core writing principles.

  • Howto docs

    existential-birds/beagle/plugins/beagle-docs/skills/howto-docs Skill

    75★ repo

    How-To guide patterns for documentation - task-oriented guides for users with specific goals. Use when writing a how-to/howto guide, task guide, procedural guide, step-by-step guide, or how-to documentation. Builds on the docs-style core writing principles.

  • Humanize beagle

    existential-birds/beagle/plugins/beagle-docs/skills/humanize-beagle Skill

    75★ repo

    Rewrite AI-generated developer text to sound human — fix inflated language, filler, tautological docs, and robotic tone. Use after review-ai-writing identifies issues.

  • Reference docs

    existential-birds/beagle/plugins/beagle-docs/skills/reference-docs Skill

    75★ repo

    Reference documentation patterns for API and symbol documentation. Use when writing reference docs, API docs, parameter tables, or technical specifications. Triggers on reference docs, API reference, function reference, parameters table, symbol documentation.

  • Review ai writing

    existential-birds/beagle/plugins/beagle-docs/skills/review-ai-writing Skill

    75★ repo

    Detect AI-generated writing patterns in developer text — docs, docstrings, commit messages, PR descriptions, and code comments. Use when reviewing any text artifact for authenticity and clarity, or when the user mentions ai writing, ai-generated or robotic writing, text that sounds like AI or ChatGPT, or writing quality. Builds on the docs-style core writing principles.

  • Tutorial docs

    existential-birds/beagle/plugins/beagle-docs/skills/tutorial-docs Skill

    75★ repo

    Tutorial patterns for documentation - learning-oriented guides that teach through guided doing. Use when writing a tutorial, learning guide, getting-started or onboarding guide, beginner/introductory guide, or any learn-by-doing hands-on guide. Builds on the docs-style core writing principles.

  • Elixir docs review

    existential-birds/beagle/plugins/beagle-elixir/skills/elixir-docs-review Skill

    75★ repo

    Reviews Elixir documentation for completeness, quality, and ExDoc best practices. Use when auditing @moduledoc, @doc, @spec coverage, doctest correctness, and cross-reference usage in .ex files.

  • Elixir writing docs

    existential-birds/beagle/plugins/beagle-elixir/skills/elixir-writing-docs Skill

    75★ repo

    Guides writing Elixir documentation with @moduledoc, @doc, @typedoc, doctests, cross-references, and metadata. Use when adding or improving documentation in .ex files.

  • Ios animation implementation

    existential-birds/beagle/plugins/beagle-ios/skills/ios-animation-implementation Skill

    75★ repo

    Write Swift animation code using Apple's latest frameworks — SwiftUI animations, Core Animation, and UIKit. Prefer first-party APIs over third-party libraries. Use when implementing iOS animations, writing animation code, building transitions, creating gesture-driven interactions, or converting animation specs/designs into working Swift code. Covers iOS 18 through iOS 26 APIs including KeyframeAnimator, PhaseAnimator, custom Transition protocol, zoom navigation transitions, matchedGeometryEffect, symbol effects, mesh gradients, and SwiftUI-UIKit animation bridging.

  • Rust best practices

    existential-birds/beagle/plugins/beagle-rust/skills/rust-best-practices Skill

    75★ repo

    Development guidance for writing idiomatic Rust. Use when: (1) writing new Rust functions or modules, (2) choosing between borrowing, cloning, or ownership patterns, (3) implementing error handling with Result types, (4) optimizing Rust code for performance, (5) configuring clippy and linting for a project, (6) deciding between static and dynamic dispatch, (7) writing documentation or doc tests.

  • Guideline writing

    alfadur7/llm-wiki-newsroom/.claude/skills/guideline-writing Skill

    75★ repo

    Guideline-authoring craft for instruction SoTs (.claude/ guides, CLAUDE.md, plan files) — operative rules vs recital, MUST/SHOULD/MAY force tiers, pruning, bloat control, blind review protocol, deliberation-narrative ban. Use when writing, editing, or reviewing an agent instruction file, policy, runbook, command SoT, or plan file, or when a guideline change needs a minimal-edit or blind review.

  • Journalism writing

    alfadur7/llm-wiki-newsroom/.claude/skills/journalism-writing Skill

    75★ repo

    Journalism and argumentation writing craft — inverted pyramid, lede, nut graph, kicker, explainer framing, PAGE frames, Toulmin argument (claim/rebuttal/qualifier), Hegelian dialectic, BBC due impartiality. Use when writing or reviewing news/explainer pieces, landscape overviews, or issue analyses that fairly juxtapose opposing views, or when a strong lede, sound argument structure, or balanced conclusion is needed.

  • Bug report

    tranhieutt/software_development_department/.claude/skills/bug-report Skill

    74★ repo

    Creates a structured bug report with reproduction steps, expected vs actual behavior, environment details, and severity assessment. Use when a bug or defect is found and needs to be formally documented.

  • Changelog

    tranhieutt/software_development_department/.claude/skills/changelog Skill

    74★ repo

    Generates a structured changelog from git history following Keep a Changelog format and conventional commits. Use when creating a CHANGELOG.md, preparing release notes, or when the user mentions changelog or release history.

  • Localize

    tranhieutt/software_development_department/.claude/skills/localize Skill

    74★ repo

    Generates or updates i18n localization files, translation keys, and locale configurations. Use when adding a new language, updating translation strings, or when the user mentions localization, i18n, translation, or l10n.

  • Markdown injection scanner

    tranhieutt/software_development_department/.claude/skills/markdown-injection-scanner Skill

    74★ repo

    Scans Markdown (.md) files for malicious code injection including XSS, prompt injection, script injection, obfuscated payloads, and supply chain attack vectors. Use when auditing .md files for security threats or when the user mentions scanning markdown for malicious content.

  • Postmortem writing

    tranhieutt/software_development_department/.claude/skills/postmortem-writing Skill

    74★ repo

    Writes blameless postmortems with root cause analysis, incident timelines, contributing factors, and action items. Use when conducting incident reviews or when the user mentions postmortem, root cause analysis, or blameless review.

  • Pr writer

    tranhieutt/software_development_department/.claude/skills/pr-writer Skill

    74★ repo

    Creates and formats pull request titles, descriptions, and linked issue references following conventional commit standards. Use when creating or updating a pull request or when the user mentions PR description, pull request, or opening a PR.

  • Reverse document

    tranhieutt/software_development_department/.claude/skills/reverse-document Skill

    74★ repo

    Generates missing design or architecture documentation by working backwards from existing code or prototypes. Use when documentation is missing for existing code or when the user mentions documenting existing implementation or reverse engineering docs.

  • Skill technical document

    tranhieutt/software_development_department/.claude/skills/skill-technical-document Skill

    74★ repo

    Generate a polished internal technical HTML document following the SDD visual design system. Use when asked to "tạo tài liệu kỹ thuật", "generate HTML reference", "visual report", "technical doc", "tạo report HTML", "làm tài liệu ná»™i bá»™", or when asked to document a subsystem (hooks, memory, agents, ADRs, audit findings) in a browser-readable format with sidebar navigation.

  • Source driven development

    tranhieutt/software_development_department/.claude/skills/source-driven-development Skill

    74★ repo

    Grounds framework, library, API, and platform-specific technical decisions in official documentation before implementation. Use when current docs, version-specific behavior, best practices, deprecations, or external API correctness matter.

  • Style review

    tranhieutt/software_development_department/.claude/skills/style-review Skill

    74★ repo

    Reviews Markdown prose against the pinned agent-style v0.3.5 rules and optionally writes a polished copy beside the source. Use for specs, ADRs, PR bodies, release notes, and technical docs when prose quality or evidence discipline matters.

  • Handoff

    oprogramadorreal/optimus-claude/skills/handoff Skill

    73★ repo

    Compacts the current conversation into one self-contained, tool-agnostic handoff document at docs/handoffs/<slug>.md so any fresh agent or teammate can resume the work from that file alone. References pushed artifacts by path or URL, inlines anything not on the remote, and redacts secrets and PII. Re-running on an existing handoff offers enhance or overwrite. Writes only that one file; never commits.

  • Init

    oprogramadorreal/optimus-claude/skills/init Skill

    73★ repo

    Bootstraps a project for Claude Code — generates CLAUDE.md and scoped docs from detected structure (single project, monorepo, or multi-repo workspace), installs auto-format hooks and test infrastructure, and reconciles existing docs against the source. Writes under .claude/ and subproject docs/. Replaces /init; safe to re-run.

  • Writing quality editor

    kyungseo/skillstead/skills/writing-quality-editor Skill

    73★ repo

    Practical, portable skills for agentic coding workflows — clearer diagrams, checked claims, safer GitHub releases, natural EN↔KO writing.

  • Learn

    withqwerty/nutmeg/skills/learn Skill

    no license73★ repo

    Learn about football analytics concepts and explore provider documentation. Use when the user asks what a metric means (xG, PPDA, expected threat, xT), wants learning resources, papers, or courses, is new to football analytics, or wants a learning path. Also use when the user asks about data provider documentation — qualifier IDs, coordinate systems, event types, API schemas, field mappings, identity surfaces, provider ID schemes — or wants to compare providers, look something up in the docs, or find out what data a provider offers.

  • Any2docx

    lovstudio/skills/skills/any2docx Skill

    72★ repo

    Convert Markdown documents to professionally styled DOCX (Word) files with python-docx. Handles CJK/Latin mixed text, fenced code blocks, tables, blockquotes, cover pages, TOC field, watermarks, and page numbers. Supports multiple color themes matching any2pdf (Configurable Academic, Nord, GitHub Light, etc.) and is battle-tested for Chinese technical reports. Use this skill whenever the user wants to turn a .md file into a styled Word document, generate an editable report from markdown, or create a DOCX from markdown content — especially if CJK characters, code blocks, or tables are involved. Also trigger when the user mentions "markdown to docx", "md2docx", "any2docx", "md转word", "md转docx", "生成word", or asks for an "editable document" from markdown source.

  • Document illustrator

    lovstudio/skills/skills/document-illustrator Skill

    72★ repo

    为文档原地插入 AI 配图。读取文档后全局规划插入点,并行生成所有图片, 异步插回原文。支持封面图、自定义比例和三种风格。 Use when: 用户要求为文档/文章/笔记生成配图、插图。 Also trigger when user mentions: 配图、插图、illustration、 generate images、document images、为文章加图。

  • Expense report

    lovstudio/skills/skills/expense-report Skill

    72★ repo

    Extract invoice data from images or text descriptions and generate a categorized Excel expense report. Supports receipt photos, scanned invoices, and manual text input. Auto-classifies into: business entertainment (客户餐费), travel-transport (机票/火车票/打车), travel-accommodation (酒店), travel-meals, office supplies, communication, and other. Use when the user mentions "发票报销", "expense report", "报销单", "发票整理", "invoice", "报销汇总", "发票分类", "reimbursement", or has invoice images to process.

  • Fill web form

    lovstudio/skills/skills/fill-web-form Skill

    72★ repo

    Top-level index for the Lovstudio skills ecosystem

  • Translation review

    lovstudio/skills/skills/translation-review Skill

    72★ repo

    Review Chinese-to-English translations for accuracy, grammar, terminology, and consistency. Produces a structured review report with prioritized issues. Trigger when: user provides a Chinese document and its English translation for review/checking/proofreading, or mentions "翻译检查", "翻译审校", "translation review", "translation check", "proofread translation".

  • Write professional book

    lovstudio/skills/skills/write-professional-book Skill

    72★ repo

    Write multi-chapter books (technical, tutorial, monograph, etc.) end-to-end. Handles outline planning, per-chapter drafting that stays coherent across long manuscripts, chapter review, and final HTML/PDF build. Trigger when user mentions "写书", "写一本书", "出书", "技术书", "book writing", "逐章写作", "O'Reilly", "mdbook", or wants to author a multi-chapter book.

  • Wiki ingest

    vanillaflava/llm-wiki-skills/wiki-ingest Skill

    72★ repo

    Process source files into synthesised wiki pages. Always use this skill when the user says /wiki-ingest, 'import these files', 'process my clippings', 'ingest this article', 'I have new articles to add', 'turn this PDF into a wiki page', 'what's in my raw/ folder', or 'what have I ingested'. Also use when the user mentions dropping a file somewhere to process, wants to turn any document, article, or PDF into a wiki page, or asks about files in raw/ or ingested/ - even if they don't say 'ingest'. Treats raw/ as a flat queue; scans all files, synthesises knowledge into wiki pages, and moves each source to ingested/ as an atomic commit. When in doubt whether source material processing is being requested, use this skill. Requires filesystem read/write/move access.