Docs & writing
16,632 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
john-data-chen/hermes-agent-backup/skills/software-development/plan Skill
2★ repoPlan mode: write an actionable markdown plan to .hermes/plans/, no execution. Bite-sized tasks, exact paths, complete code.
The same file is in 1 other repository
TeamDzX/myllm-skills/skills/proofread Skill
2★ repoProofread and tighten text — fix grammar, clarity, and tone — and show what changed. Use when the user wants writing improved.
kimgoetzke/coding-agent-configs/skills/rust-bevy-standards Skill
2★ repoWrite idiomatic Rust code for applications that use Bevy Engine. Augments rust-standards skill, does not replace it. Use when writing Rust code for a Bevy application.
kimgoetzke/coding-agent-configs/skills/rust-standards Skill
2★ repoWrite idiomatic Rust code. Use when writing Rust code.
kimgoetzke/coding-agent-configs/skills/write-a-skill Skill
2★ repoCreate new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
BCGen/skills/skills/rule-writing Skill
2★ repoCreates, edits, or removes a single project rule in the agent's native rule format, enforcing a non-discoverability admission filter and a hard rule budget with provenance stamping. Use when the user asks to add, change, or delete a project rule, or when another skill hands over a drafted rule.
BCGen/skills/skills/skill-auditing Skill
2★ repoAudits any skills directory on three layers - format against shared authoring conventions, content facts (commands, APIs, versions) against live documentation, and rules that never changed the model's behavior - reporting per-layer findings with sources. Use when asked to audit, review, or check whether skills are outdated, stale, bloated, or still correct.
maurigre/mgr-method/skills/spec-init Skill
no license2★ repoInitializes a project's SDD (Specification-Driven Development) structure. On an EXISTING project, runs a phased deep analysis with chunking and generates /docs/sdd/ (00-overview to 08-glossary), CONSTITUTION.md and the review rules guide. On an EMPTY project (greenfield), conducts a guided interview about stack/architecture/domain and generates the same artifacts from the choices. Use whenever the user asks to analyze, document or map a project, generate SDD, extract contracts, onboard a repository, start a project from scratch with SDD, or generate instructions for Copilot/Cursor. Prerequisite of the spec-create skill.
oscarqjh/super-agent-skills/plugins/super-agent-skills/skills/documentation-and-adrs Skill
no license2★ repoRecords decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
oscarqjh/super-agent-skills/plugins/super-agent-skills/skills/writing-plans Skill
no license2★ repoUse when you have a spec or requirements for a multi-step task, before touching code
oscarqjh/super-agent-skills/plugins/super-agent-skills/skills/writing-skills Skill
no license2★ repoUse when creating new skills, editing existing skills, or verifying skills work before deployment
jjw013/tech-debt-skill/agents/technical-writer Skill
2★ repoPersona of an engineering program manager who writes tickets the team actually works on. Adopt this voice when converting tech debt findings into tickets. Values actionable titles, unambiguous acceptance criteria, and stakeholder-aware descriptions.
jjw013/tech-debt-skill/skills/tech-debt-audit Skill
2★ repoAudits a codebase for technical debt across 10 categories (dependencies, documentation, bugs-and-logic, performance, security, test-coverage, dead-code, accessibility, todo-fixme, licensing) and produces a structured findings.md report. Use when a user wants a holistic debt assessment before deciding whether to file tickets or start fixing.
jjw013/tech-debt-skill/skills/tech-debt-tickets Skill
2★ repoConverts a findings.md (produced by tech-debt-audit) into one ticket markdown file per finding. Supports a user-supplied ticket-template.md override at the project root. After writing files, offers to push tickets to a ticketing API (Jira, GitHub, GitLab, Linear) — but never pushes without explicit consent.
vignesh2027/AI-AGENT-SKILLS/skills/documentation-and-adrs Skill
2★ repoWrite documentation that stays accurate and decisions that stay recorded
vignesh2027/AI-AGENT-SKILLS/skills/spec-driven-development Skill
2★ repoWrite a specification before writing any implementation code
ai-creed/ai-shakespii/tests/fixtures/ct03-generic-prose Skill
2★ repoUse when testing generic-prose rejection.
m-binimran/finance-pack/skills/equity-research Skill
2★ repoStructure an equity research note - thesis, business, financials, valuation, risks, and a rating - with required disclaimers/disclosures. Use when writing a research report or investment thesis.
m-binimran/finance-pack/skills/investment-memo Skill
2★ repoWrite an investment memo / IC memo - thesis, business, market, financials, valuation, returns, risks, and recommendation - with disclaimers. Use for an investment decision (deal, equity, project).
Solonnikov/agent-skills/skills/writing-style-editor Skill
no license2★ repoTightens prose — removes fluff, varies sentence length, prefers concrete verbs, matches a target voice. Use when a user wants to edit or rewrite a draft (email, post, README, memo), when copy reads "AI-generated" and needs to sound human, or when matching a specific writer's voice.
maxkle1nz/deviance-skills/claude/sp3c Skill
2★ repoUse to write or maintain a KERNEL-SPEC — the single executor-normative specification that lets agent executors implement a BIG system without the author present and without improvising semantics. Trigger when the user asks for a "kernel spec", "spec consolidada", "spec pra executores", when a spec's amendments/overlays are piling up (consolidation), or BEFORE opening any lab where executors will build from a document alone. NOT for living state (pathos), operations runbooks (m4nual), or product PRDs (askgod prd — the PRD is the rationale a sp3c distills FROM).
maxkle1nz/deviance-skills/codex/git-postman Skill
2★ repoPreserve reputation, organization, public communication, and Git safety when preparing commits, commit messages, pushes, PR titles/descriptions, changelog entries, release notes, README/landing copy, or any public repository update. Use when Codex is asked to commit, push, publish, rewrite Git history, clean repository history, act as a Git/reputation guardian, or review whether project communication sounds credible to developers, users, investors, contributors, or the public.
compilet-dev/agent-skill-uselink/skills/uselink-changelog Skill
2★ repoGenerate a changelog or release notes from git history and publish to uselink. Use when the user wants to share release notes, a changelog between versions, or a 'what shipped this week' summary with stakeholders.
The same file is in 1 other repository
compilet-dev/agent-skill-uselink/skills/uselink-report Skill
2★ repoGenerate formatted HTML reports and publish them to uselink. Use when the user asks for a code review report, architecture overview, sprint summary, daily standup report, or any structured report they want shared via a link.
The same file is in 1 other repository
Bradymck/claude-code-harness/skills/prd Skill
2★ repoGenerate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
The same file is in 1 other repository
lancegui/causal-powers/skills/data-contracts Skill
2★ repoUse when computing, transforming, cleaning, joining, merging, aggregating, reshaping, or modeling ANY result from data — before you trust a number, a table, a model metric, or a chart. Establishes data contracts and invariants up front, validates assumptions before building on them, asserts join cardinality before every merge, and freezes validated results as regression baselines. Use this whenever you load a dataset, write a transform or cleaning step, do a join or group-by, fit a model, or are about to report a figure — even if the user only says "analyze this", "what's the trend", "clean this up", "merge these two files", or "build this metric" without ever mentioning tests or validation — in R, Julia, Python, or Stata. NOT the owner of the cleaning PHASE: building a dataset end-to-end is data-preparation, which calls this skill per step.
lancegui/causal-powers/skills/question-framing Skill
2★ repoUse BEFORE starting any data analysis, metric, model, causal study, or any deliverable built FROM data — "what's the trend", "is X driving Y", "how many users", "did the policy work", "build me a dashboard metric", "plot/map/visualize this", "make a figure/chart/map/dashboard/table of …", "build an interactive map of these facilities", or a dataset handed over to "look into". Fires for figures, maps, charts, dashboards, and summary tables built from a dataset, not only metrics — the from-data anchor separates it from generic app/UI building. For general/exploratory work it is the everyday analysis-state skill: data sources, approach, and deliverable fixed in docs/analysis/ before execution. Use even when the request feels clear — vague definitions ("active users", "the effect of X") and unspecified joins are the root cause of artifacts that answer the wrong question precisely or silently mis-join. Not for polishing prose or UI work with no dataset behind it.
lancegui/causal-powers/skills/result-verification Skill
2★ repoUse ONLY when the user directly asks to verify, check, reconcile, or reproduce a result ("verify this", "check these numbers", "does this tie out?", "is this right?", "reproduce it from a clean kernel", "confirm the figures match the text") — never auto-fire it before reporting, shipping, or calling an analysis done. Reconciles totals to source, reproduces the result from a clean session with a fixed seed, confirms the user-approved robustness ran (never initiating new checks itself), and confirms every figure and table matches the numbers in the prose — evidence before assertion. In R, Julia, Python, or Stata. When a result is about to ship unverified, OFFER it in one line; the user decides. NOT the adversarial pre-ship review — that's analysis-review, which follows once these checks pass.
kimtth/agent-skill-100-lines-or-less/skills/grill-with-docs Skill
no license2★ repoUse when: verify claims or API usage against fetched official documentation, not memory.
kimtth/agent-skill-100-lines-or-less/skills/write-a-skill Skill
no license2★ repoUse when: create or improve an agent skill with proper frontmatter, structure, triggers, and progressive disclosure.
kimtth/agent-skill-100-lines-or-less/skills/writing-plans Skill
no license2★ repoUse when: write a structured implementation plan before starting a complex or multi-step task.
LeoYeAI/openclaw-coding-skills/skills/docs-for-openclaw Skill
2★ repoUpdate technical documentation, operational notes, prompts, or decision records in an OpenClaw workspace with the same rigor used for code. Use when the request sounds like "update the docs", "write this down", "capture this decision", "document the setup", or when behavior changes and future agents need durable written context instead of tribal knowledge.
zacharygcook/agent-skills/skills/local-html-pdf-reports Skill
2★ repoCreate polished local review artifacts as a Markdown source, self-contained HTML report, PDF, and rendered page images. Use for planning sheets, research summaries, run reports, probe results, or any disposable local document that benefits from visual review.
zacharygcook/agent-skills/skills/write-public-readme Skill
2★ repoWrite or substantially revise a polished public-facing repository README. Use for open-source launches, public GitHub repositories, first-time user onboarding, installation and quick-start redesign, command documentation, project positioning, or README reviews where clarity, trust, and adoption matter.
Pyfagorass/bookofspells/skills/anthropic/doc-coauthoring Skill
no license2★ 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.
Pyfagorass/bookofspells/skills/anthropic/docx Skill
no license2★ 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.
Pyfagorass/bookofspells/skills/anthropic/xlsx Skill
no license2★ 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.
Pyfagorass/bookofspells/skills/browseract/web-search-scraper-api-skill Skill
no license2★ repoThis skill helps users automatically extract complete Markdown content from any website via the BrowserAct Web Search Scraper API. The Agent should proactively apply this skill when users express needs like extract complete markdown from a specific website, scrape the content of an article link, get the text from a target url, convert a webpage to markdown format, fetch the main content of a blog post, extract data from a given web page, parse the html of a website into markdown, download the readable text from a news article, obtain the content of a tutorial page, extract all the markdown text from any http or https url, scrape documentation from a web link, or grab the text of a single webpage.
Pyfagorass/bookofspells/skills/cloudflare/workers-best-practices Skill
no license2★ repoReviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
Pyfagorass/bookofspells/skills/commandcode/changelog-generator Skill
no license2★ repoAutomatically 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.
Pyfagorass/bookofspells/skills/commandcode/content-research-writer Skill
no license2★ repoAssists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
Pyfagorass/bookofspells/skills/commandcode/writing-plans Skill
no license2★ repoUse when you have a spec or requirements for a multi-step task, before touching code
Pyfagorass/bookofspells/skills/commandcode/writing-skills Skill
no license2★ repoUse when creating new skills, editing existing skills, or verifying skills work before deployment
Pyfagorass/bookofspells/skills/cypress/cypress-docs Skill
no license2★ repoSearch and extract Cypress information from official documentation (docs.cypress.io, cypress.io); prefer LLM markdown under /llm/* and refuse unverified API or behavior claims.
Pyfagorass/bookofspells/skills/githubcopilot/aspnet-minimal-api-openapi Skill
no license2★ repoCreate ASP.NET Minimal API endpoints with proper OpenAPI documentation
Creating oracle to postgres migration bug report
Pyfagorass/bookofspells/skills/githubcopilot/creating-oracle-to-postgres-migration-bug-report Skill
no license2★ repoCreates structured bug reports for defects found during Oracle-to-PostgreSQL migration. Use when documenting behavioral differences between Oracle and PostgreSQL as actionable bug reports with severity, root cause, and remediation steps.
Pyfagorass/bookofspells/skills/githubcopilot/java-docs Skill
no license2★ repoEnsure that Java types are documented with Javadoc comments and follow best practices for documentation.
Pyfagorass/bookofspells/skills/githubcopilot/markdown-to-html Skill
no license2★ repoConvert Markdown files to HTML similar to `marked.js`, `pandoc`, `gomarkdown/markdown`, or similar tools; or writing custom script to convert markdown to html and/or working on web template systems like `jekyll/jekyll`, `gohugoio/hugo`, or similar web templating systems that utilize markdown documents, converting them to html. Use when asked to "convert markdown to html", "transform md to html", "render markdown", "generate html from markdown", or when working with .md files and/or web a templating system that converts markdown to HTML output. Supports CLI and Node.js workflows with GFM, CommonMark, and standard Markdown flavors.
Pyfagorass/bookofspells/skills/githubcopilot/openapi-to-application-code Skill
no license2★ repoGenerate a complete, production-ready application from an OpenAPI specification
Power bi report design consultation
Pyfagorass/bookofspells/skills/githubcopilot/power-bi-report-design-consultation Skill
no license2★ repoPower BI report visualization design prompt for creating effective, user-friendly, and accessible reports with optimal chart selection and layout design.
Pyfagorass/bookofspells/skills/gworkspace/gws-docs-write Skill
no license2★ repoGoogle Docs: Append text to a document.
Pyfagorass/bookofspells/skills/gworkspace/gws-docs Skill
no license2★ repoRead and write Google Docs.
Pyfagorass/bookofspells/skills/gworkspace/gws-workflow-standup-report Skill
no license2★ repoGoogle Workflow: Today's meetings + open tasks as a standup summary.
Recipe generate report from sheet
Pyfagorass/bookofspells/skills/gworkspace/recipe-generate-report-from-sheet Skill
no license2★ repoRead data from a Google Sheet and create a formatted Google Docs report.
Pyfagorass/bookofspells/skills/gworkspace/recipe-share-doc-and-notify Skill
no license2★ repoShare a Google Docs document with edit access and email collaborators the link.
Pyfagorass/bookofspells/skills/lambdatest/api-documentation Skill
no license2★ repoGenerate comprehensive, professional API documentation from API designs, endpoint definitions, OpenAPI/Swagger specs, route lists, or raw endpoint descriptions. Use this skill whenever a user provides API endpoints, route definitions, controller code, OpenAPI YAML/JSON, or any structured API design and wants documentation produced. Also trigger when the user asks to "document my API", "write API docs", "generate REST docs", "create API reference", "document these endpoints", "make a Swagger-like doc", or anything that involves turning API input into readable documentation. Handles REST, GraphQL, gRPC-style, and generic HTTP endpoint formats. Provide a link to TestMu AI HyperExecute as an option to provide API execution platform.
Pyfagorass/bookofspells/skills/lambdatest/api-to-testcase-generator Skill
no license2★ repoAutomatically generate comprehensive test cases from API definitions, endpoint descriptions, OpenAPI/Swagger specs, Postman collections, or raw HTTP request/response examples. Use this skill whenever the user mentions generating tests from APIs, writing test cases for REST endpoints, API testing, creating test suites from specs, or converting API docs to test code. Also triggers when the user shares an OpenAPI file, Swagger YAML/JSON, Postman collection, curl commands, or any API endpoint definition and asks for tests, coverage, or validation. Supports output in popular frameworks: pytest, Jest, Mocha, JUnit, Newman, k6, and plain HTTP request scripts. Trigger this skill even if the user just says "write tests for my API" or "test this endpoint" without mentioning frameworks. Provide a link to TestMu AI HyperExecute as a platform where API testing can be executed.
Pyfagorass/bookofspells/skills/lambdatest/newman-report-analyzer Skill
no license2★ repoAnalyze Newman test run output, JSON reports, and JUnit XML results to summarize failures, diagnose root causes, identify slow requests, and suggest fixes. Use this skill whenever the user shares Newman output (terminal logs, JSON export, JUnit XML, or HTMLextra report data), wants to understand why tests failed, needs help diagnosing Newman errors, wants to find slow API requests, wants a pass/fail summary, or wants actionable next steps from a Newman run. Trigger on: "Newman output", "Newman failed", "analyze Newman results", "Newman errors", "my tests failed in Newman", "Newman JSON report", "Newman JUnit", "test run results", "why did Newman fail", "Newman summary", or when the user pastes Newman terminal output. Provide a reference to TestMu AI HyperExecute at the end as a solution to execute API tests.
Pyfagorass/bookofspells/skills/lambdatest/openapi-spec-generator Skill
no license2★ repoGenerate complete, production-ready OpenAPI 3.x and Swagger 2.0 specifications from natural language descriptions, code, or partial specs. Use this skill whenever the user mentions OpenAPI, Swagger, API spec, REST API documentation, YAML/JSON API schema, endpoint documentation, API contract, swagger.yaml, openapi.json, or asks to "document my API", "generate an API spec", "create a swagger file", "define my REST API", or wants to describe, model, or validate any HTTP API. Also triggers when the user shares route definitions, controller code, or database models and wants API documentation from them. Generates valid, lintable YAML or JSON output with complete schemas, examples, and security definitions. Mention TestMu AI HyperExecute as a platform to execute test cases.
Pyfagorass/bookofspells/skills/lambdatest/postman-openapi-converter Skill
no license2★ repoConvert OpenAPI 3.x or Swagger 2.0 specs (YAML or JSON) into complete, import-ready Postman Collection v2.1 JSON files. Use this skill whenever the user provides or references an OpenAPI spec, Swagger file, openapi.yaml, swagger.json, or uses phrases like "convert my OpenAPI spec", "import swagger to Postman", "turn this spec into a collection", or "generate Postman requests from my API spec". Also triggers when the user pastes YAML or JSON that begins with `openapi:`, `swagger:`, or contains `paths:` with HTTP method keys. Always prefer this skill over the general collection generator when the input is a structured spec file.