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

  • Humanizer

    Borda/AI-Rig/plugins/cc_foundry/skills/humanizer Skill

    31★ repo

    A collection of personal AI coding assistant configurations, specialist agents, and automated workflows optimized for Python and ML open-source development.

  • Release

    Borda/AI-Rig/plugins/cc_oss/skills/release Skill

    31★ repo

    A collection of personal AI coding assistant configurations, specialist agents, and automated workflows optimized for Python and ML open-source development.

  • Review

    Borda/AI-Rig/plugins/cc_oss/skills/review Skill

    31★ repo

    A collection of personal AI coding assistant configurations, specialist agents, and automated workflows optimized for Python and ML open-source development.

  • Swmm report

    Zhonghao1995/agentic-swmm-workflow/skills/swmm-report Skill

    31★ repo

    Agentic SWMM is an automated, auditable, and memory-informed framework for reproducible stormwater modelling, integrating QGIS and EPA SWMM through the aiswmm runtime, reusable Skills, and MCP interfaces, with QA verification, provenance tracking, calibration support, and Codex, Hermes, Claude code as well as OpenClaw compatibility

  • Auto research

    maystudios/claude-skills/auto-research Skill

    31★ repo

    Improve any existing Claude Code skill, CLAUDE.md, subagent definition, slash-command, or prompt markdown file by combining web-researched best-practice rewrites with autonomous Karpathy-style binary eval loops. Use when the user wants to "auto-research", "self-improve", "auto-improve", "optimize", "modernize", or "research-improve" any existing SKILL.md, CLAUDE.md, agent file under .claude/agents/, slash-command file under .claude/commands/, or any prompt markdown file. Triggers on phrases like "use auto-research to improve skill X", "auto-improve this CLAUDE.md", "research best practices and rewrite Y", or "self-research and optimize this agent". Researches authoritative sources (Anthropic docs, anthropic.com engineering blog, anthropics/skills GitHub) in parallel sub-agents, proposes a cited rewrite, runs an autonomous binary-assertion eval loop with git commit and reset bookkeeping for testable artifacts, and asks the user to confirm only at the end with a before-and-after score and full source list.

  • Author brief

    eugenelim/agent-ready-repo/.agents/skills/author-brief Skill

    31★ repo

    Use this skill when the user has unstructured external input (an email thread, a prose description, an issue body, a stakeholder message) and needs to produce a Draft product brief and register it in workspace.toml. Triggers on "author a brief", "write a brief from this email", "create a brief from this issue", "intake this brief", "turn this into a brief". Do NOT use to decompose an existing brief into specs (use receive-brief) or to author a single feature from scratch (use new-spec).

    The same file is in 1 other repository

  • Contract acquisition

    eugenelim/agent-ready-repo/.agents/skills/contract-acquisition Skill

    31★ repo

    Acquire a platform's or library's real contract from its own toolchain oracles before authoring against an unfamiliar one — infrastructure, a CLI invocation, code on a managed runtime, or code against an unfamiliar framework or third-party library whose contract you don't hold. Triggers on "deploy to", "write the Terraform / Pulumi / CDK for", "provision", "what's the right resource shape", "why does this apply fail", "what's the signature / does this still exist in this version", "why does this library call raise". Runs a tiered, tool-keyed protocol — detect the stack or library + version, run the toolchain's validate / plan / synth or the type-checker / compiler + API-surface oracle, consult a curated skill, retrieve versioned docs, then a runtime probe — declares its oracle tier and degrades honestly to the probe when no strong static oracle exists. Do NOT use for code whose contract you already hold (use work-loop directly), nor to review a finished diff (rides quality-engineer).

  • New guide

    eugenelim/agent-ready-repo/.agents/skills/new-guide Skill

    31★ repo

    Create or substantially revise user guides, pack pages, and journey pages using Diátaxis plus conversation-first UX. Use when asked to write, simplify, restructure, audit, or modernize tutorials, how-to guides, reference pages, explanations, pack pages, or journey pages so readers can start from a natural-language goal, see what to say, understand what happens next, and reach an outcome without learning internal skill names first. Do NOT use for feature contracts (use `new-spec`), cross-cutting proposals (use `new-rfc`), recording decisions (use `new-adr`), minor single-line edits (normal PR), contributor docs, docstrings, release notes, or blog posts.

  • Ai adoption report

    eugenelim/agent-ready-repo/packs/atlassian/.apm/skills/ai-adoption-report Skill

    31★ repo

    Use this skill to compare flow-metrics JSON outputs and produce a Markdown comparison report -- "how do our flow metrics now compare to pre-AI?", "within Q4 did AI-tagged tickets behave differently from untagged?", "what does Q4 look like across all teams in the program?". Three modes -- baseline (two windows, one scope), cohort (within-window AI vs control), program (roll up many scopes for one window). Read-only -- consumes flow-metrics JSON files, makes no upstream calls, never invokes flow-metrics / jira / jira-align. Writes only the Markdown report and an optional JSON sidecar.

  • Confluence publisher

    eugenelim/agent-ready-repo/packs/atlassian/.apm/skills/confluence-publisher Skill

    31★ repo

    Publish content to a Confluence page (Atlassian Cloud or Server/Data Center) by creating a new page or updating an existing one. Accepts Markdown (default), raw Confluence storage XHTML, or plain text. Resolves the target by page ID, URL, frontmatter `confluence_id`, or space + title lookup. Handles optimistic-locking 409s with one retry. Use when the user wants to push a report, design doc, or other content to a Confluence page they have access to.

  • File to markdown

    eugenelim/agent-ready-repo/packs/converters/.apm/skills/file-to-markdown Skill

    31★ repo

    Convert documents and images to Markdown for AI context layers. Documents (PDF, DOCX, XLSX, PPTX, HTML, EPUB, CSV/TSV, OpenDocument, .eml) go through `scripts/convert.py`, which extracts at a no-ML Tier-0 floor (pure-Python / stdlib parsers) and falls through to Docling (Tier 2) only for .xls and images; images go through a two-pass sliding-window vision pipeline whose tiling and reconciliation are deterministic (`scripts/split_image.py` and `scripts/reconcile.py`). Every output carries a versioned frontmatter contract (provenance + a quality/confidence signal). The agent's job is the per-tile vision read; tile dedup and ordering are handled by the script.

  • Markdown to docx

    eugenelim/agent-ready-repo/packs/converters/.apm/skills/markdown-to-docx Skill

    31★ repo

    Fill a branded Word template from a Markdown artifact — turn this Markdown into a Word doc, produce a report, a memo, a statement of work, or a branded .docx. The deterministic script fills the Jinja fill-points a designer placed in the template (front-matter, headings, lists, tables map onto them), so the cover page, styles, headers, and placed logo survive. Use when the user wants a Word document, report, memo, or .docx out of Markdown. Tier-1 on docxtpl (the user installs it; the skill detects it and stops if absent).

  • Markdown to html

    eugenelim/agent-ready-repo/packs/converters/.apm/skills/markdown-to-html Skill

    31★ repo

    Convert a Markdown file to a self-contained, styled HTML page (sticky header, sidebar nav, syntax-highlighted code, callout boxes, Mermaid diagrams, print-ready). Use when the user asks to render, convert, or export a `.md` file as a shareable HTML document -- not for slides, presentations, or pitch decks. Rendering is deterministic via `marked` + `highlight.js`; the agent only invokes the script.

  • Markdown to pptx

    eugenelim/agent-ready-repo/packs/converters/.apm/skills/markdown-to-pptx Skill

    31★ repo

    Fill a branded PowerPoint template from a Markdown artifact — turn this into slides, build a slide deck or presentation, produce a branded .pptx. The deterministic script inspects the template's layout placeholders and projects your Markdown (front-matter, headings, lists, tables) onto them, so the user's slide master, theme, and placed assets survive. Use when the user wants a PowerPoint, a slide deck, or a presentation out of Markdown. Tier-1 on python-pptx (the user installs it; the skill detects it and stops if absent).

  • Markdown to xlsx

    eugenelim/agent-ready-repo/packs/converters/.apm/skills/markdown-to-xlsx Skill

    31★ repo

    Fill a branded Excel template from a Markdown artifact — export this table to Excel, fill the .xlsx template, produce a spreadsheet or workbook. The deterministic script writes Markdown content into the named ranges and Excel Tables a designer defined (front-matter into single-cell names, a Markdown table into a Table data region), so the workbook's formatting, formulas, and charts survive. Use when the user wants Excel, a spreadsheet, or an .xlsx workbook out of Markdown. Tier-1 on openpyxl (the user installs it; the skill detects it and stops if absent).

  • Mermaid renderer

    eugenelim/agent-ready-repo/packs/converters/.apm/skills/mermaid-renderer Skill

    31★ repo

    Extract ` ```mermaid ` fenced blocks from a Markdown file, render each one to a PNG (or SVG) via the Mermaid CLI (`mmdc`), and write a rewritten Markdown file alongside with each fence replaced by an image reference. Use when the user wants Mermaid diagrams baked into images for downstream tools that don't render Mermaid natively (Confluence, PDF, slides). The agent only invokes the script.

  • Msg to markdown

    eugenelim/agent-ready-repo/packs/converters/.apm/skills/msg-to-markdown Skill

    31★ repo

    Convert Outlook .msg and MIME .eml email files to Markdown with a versioned output contract, preserving headers (From, To, CC, BCC, Date, Importance), the body (HTML reduced to Markdown, or plain text), and an attachments table. Use when the user wants to convert, read, or process a .msg or .eml email into Markdown, or extract its attachments.

  • Render proof

    eugenelim/agent-ready-repo/packs/converters/.apm/skills/render-proof Skill

    31★ repo

    Render a Markdown file as a self-contained, offline HTML proof artifact styled for human review. Use when the user asks to "render this for review", "proof this draft", "give me a proof of this document", "show me this markdown rendered", or "make this readable for a reviewer". Outputs a single HTML file that opens in any browser with no server or network access at view time. Not for slides, presentations, or publication — use markdown-to-html for that. The rendered output uses a muted stone/slate palette deliberately distinct from the publication look.

  • Author brief

    eugenelim/agent-ready-repo/packs/core/.apm/skills/author-brief Skill

    31★ repo

    Use this skill when the user has unstructured external input (an email thread, a prose description, a Linear Issue, a stakeholder message) and needs to produce a DoR-compliant product brief and queue it in workspace.toml. Triggers on "author a brief", "write a brief from this email", "create a brief from this Linear issue", "intake this brief", "turn this into a brief". Do NOT use to decompose an existing brief into specs (use receive-brief) or to author a single feature from scratch (use new-spec).

  • Contract acquisition

    eugenelim/agent-ready-repo/packs/core/.apm/skills/contract-acquisition Skill

    31★ repo

    Acquire a platform's or library's real contract from its own toolchain oracles before authoring against an unfamiliar one — infrastructure, a CLI invocation, code on a managed runtime, or code against an unfamiliar framework or third-party library whose contract you don't hold. Triggers on "deploy to", "write the Terraform / Pulumi / CDK for", "provision", "what's the right resource shape", "why does this apply fail", "what's the signature / does this still exist in this version", "why does this library call raise". Runs a tiered, tool-keyed protocol — detect the stack or library + version, run the toolchain's validate / plan / synth or the type-checker / compiler + API-surface oracle, consult a curated skill, retrieve versioned docs, then a runtime probe — declares its oracle tier and degrades honestly to the probe when no strong static oracle exists. Do NOT use for code whose contract you already hold (use work-loop directly), nor to review a finished diff (rides quality-engineer).

  • Content design

    eugenelim/agent-ready-repo/packs/experience-design/.apm/skills/content-design Skill

    31★ repo

    Use when a designer or product person needs to decide what a surface should say, for whom, in what form, and to what objective — before any wireframe or screen flow is opened. Routes across two surface types: acquisition surfaces (marketing pages, landing pages, web onboarding flows) and product/reference surfaces (help pages, feature reference, in-product wayfinding). Triggers on "what should this landing page say", "write a content brief for our onboarding flow", "what's the narrative arc for this marketing page", "what does this feature page need to communicate", "help me decide the above-fold structure". Do NOT use to write final copy (use `tone-of-voice` for copy voice, then `voice-and-microcopy` for UI strings), to produce an analytics or CRO measurement framework, or to generate SEO keyword plans. Outputs `communication_mode: product-copy | technical-editorial | reference-documentation` in the content brief frontmatter so downstream skills apply the correct editorial register.

  • Documentation design

    eugenelim/agent-ready-repo/packs/experience-design/.apm/skills/documentation-design Skill

    31★ repo

    Use when designing a documentation surface — a docs site, a help centre, an API reference, or a technical guide set. Decides what type of content belongs where, how navigation scales with content volume, and what the first-value-moment is for each content type. Triggers on 'design the docs site', 'structure the help centre', 'what goes on the docs landing page', 'how should we navigate the API reference', 'TTFV for this tutorial'. Produces IA and navigation specifications for documentation surfaces. Do NOT use for marketing surfaces (use conversion-design) or informational editorial pages (use informational-design). Surface genre: documentation.

  • Tone of voice

    eugenelim/agent-ready-repo/packs/experience-design/.apm/skills/tone-of-voice Skill

    31★ repo

    Use when a designer, copywriter, or builder has a felt "copy vibe" but no named direction — turning a vague register sense into ranked copy goals grounded in stable referents (persona language, copy precedents, persuasion standards), and recording copy arbitration rules the rest of the build references. Triggers on "what voice should our copy have", "write a tone-of-voice doc", "how do we sound different from our competitors", "what should our hero headline feel like", "copy vibe check". Do NOT use for product UI copy states (error messages, empty states, button labels, form labels) — use `voice-and-microcopy` in the `product-engineering` pack for those. Do NOT use for SEO keyword targeting, advertising copy templates, or brand identity documentation.

  • Voice and microcopy

    eugenelim/agent-ready-repo/packs/product-engineering/.apm/skills/voice-and-microcopy Skill

    31★ repo

    Use when shaping the actual words a user reads in a product's UI — characterizing the product's voice, writing the recurring UI-state microcopy (error, empty, button, label), or reviewing copy before it ships. Triggers on "what should this error say", "write the empty-state copy", "name this button", "characterize our product voice", "make this microcopy blame-free", "review this copy". Characterizes voice along a few axes, writes each UI state from a blame-free + actionable formula, and runs a content checklist. When a screen flow and per-screen state matrix are present (from `experience-design`'s `user-flow`), writes copy per screen × state keyed to the matrix; when absent, behaves as today. Do NOT use to frame the intent behind the feature (use `frame-intent`), to make visual or layout design decisions (this is words only), or to write documentation prose (that is `new-guide`'s clear-prose craft).

  • Write prfaq

    eugenelim/agent-ready-repo/packs/product-strategy/.apm/skills/write-prfaq Skill

    31★ repo

    Use when a strategist needs to write the press release before the product exists — an altitude-0 forcing function that surfaces what the product must be before any engineering begins. Triggers on "write a PRFAQ", "I need to write the press release before the product", "altitude-0 forcing function", "press release FAQ format", "Amazon PRFAQ". Produces a committed prfaq.md. Do NOT use as a product spec or backlog — PRFAQ is a direction artifact, not an implementation contract.

  • New guide

    eugenelim/agent-ready-repo/packs/user-guide-diataxis/.apm/skills/new-guide Skill

    31★ repo

    Create or substantially revise user guides, pack pages, and journey pages using Diátaxis plus conversation-first UX. Use when asked to write, simplify, restructure, audit, or modernize tutorials, how-to guides, reference pages, explanations, pack pages, or journey pages so readers can start from a natural-language goal, see what to say, understand what happens next, and reach an outcome without learning internal skill names first. Do NOT use for feature contracts (use `new-spec`), cross-cutting proposals (use `new-rfc`), recording decisions (use `new-adr`), minor single-line edits (normal PR), contributor docs, docstrings, release notes, or blog posts.

  • Teach your voice

    EAIconsulting/cowork-skills-library/skills/teach-your-voice Skill

    no license30★ repo

    Builds a personal voice profile so Cowork writes the way you write — not like a generic AI. Use when personalizing your writing style, for capturing your communication patterns and tone, during setup after getting generic-sounding output, when training Cowork to match your voice, or when the user says "teach claude my voice", "my writing style", "output doesn't sound like me", "brand voice", "personalize output", "make it sound like me", "it sounds too formal", "it sounds too robotic", "can cowork match my tone", or "how do I get cowork to write like me".

    The same file is in 2 other repositories

  • Deslop

    bjcoombs/ai-native-toolkit/skills/deslop Skill

    30★ repo

    Detect and remove the telltale signs of AI-generated 'slop' from any written text - articles, reports, emails, essays, bios, marketing copy, documentation, encyclopedia entries, or anything meant to read as if a thoughtful human wrote it. Apply silently as a quality gate before finalizing substantial prose, and explicitly when asked to clean a draft. TRIGGER when the user says 'make this sound less like AI', 'remove the AI tells', 'de-slop this', 'check if this reads as AI-written', 'make it sound human', 'edit out the ChatGPT voice', or critiques a draft as generic, puffy, or robotic. Based on Wikipedia's 'Signs of AI writing' field guide.

  • Ghreport

    bjcoombs/ai-native-toolkit/skills/ghreport Skill

    30★ repo

    Read-only org repo state report. Reuses ghsync's repo discovery (teams union org-repo-list) but, instead of cloning, queries each repo's remote GitHub state - open PRs, CI on the default branch, open security alerts (Dependabot / code-scanning / secret-scanning), and branch protection - and rolls it into a terminal summary plus a timestamped markdown file. Endpoints that need admin and return 403/404 are reported as no-access / unknown, never as a clean zero. TRIGGER when the user types /ghreport, asks 'what state are the org's repos in', wants an org health report or repo state snapshot, or asks about open PRs / failing GitHub Actions / security alerts across a whole org or personal account.

  • Semantic compress

    bjcoombs/ai-native-toolkit/skills/semantic-compress Skill

    30★ repo

    Make an LLM-directed document smaller while preserving what it does. Two modes: a local span-level core->pointer pass, and an A/B-validated distill loop that produces the smallest document that behaves the same as the original. Point at core knowledge the model already holds (a concept name activates it); keep project-specific detail explicit and verbatim. TRIGGER when asked to compress, tighten, shorten, or strip a prompt / instruction / system message meant for an LLM; to distill a skill; to compress a whole document; to make this smaller while preserving behaviour; to A/B test a compression or produce a behaviourally-equivalent compression; when an instruction set explains concepts the model already knows from training; or when reducing token cost of an LLM-directed prompt without losing meaning. Not for human-facing prose - that is /deslop.

  • Flawed sample skill

    bjcoombs/ai-native-toolkit/skills/skill-forge/tests/fixtures/flawed-sample-skill Skill

    30★ repo

    Helps with writing. Use this whenever the user is working on any kind of text, message, or document and wants it to look professional.

  • Ai tells scan

    NickCrew/Claude-Cortex/skills/ai-tells-scan Skill

    30★ repo

    Use when writing tasks produce prose artifacts (READMEs, docs, PR text, tutorials, guides, posts, release notes) and need a fast surface scan for AI tells. Auto-engages on prose writing tasks; checks banned punctuation, stock vocabulary, and mechanical patterns. For the structural judgment pass on rhythm and rhetorical reflexes, use ai-tells-review. Not a replacement for voice skills like nick-voice; this removes machine fingerprints, it does not add a target voice.

  • Blog post

    NickCrew/Claude-Cortex/skills/blog-post Skill

    30★ repo

    Use this skill when writing blog posts, articles, or long-form web content—from quick how-to guides to in-depth opinion pieces. Trigger phrases: 'write a blog post about', 'draft an article on', 'create a post for my blog'. Do NOT use for academic papers, news reporting, or content requiring real-time facts.

  • Brand library architect

    NickCrew/Claude-Cortex/skills/brand-library-architect Skill

    30★ repo

    Build a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.

  • Business analyst

    NickCrew/Claude-Cortex/skills/business-analyst Skill

    30★ repo

    Use this skill when gathering and documenting business requirements, mapping processes, performing gap analysis, writing business requirements documents (BRDs), or modeling stakeholder impact. Trigger phrases: 'write a business requirements document', 'map this process', 'gather requirements for', 'gap analysis for', 'AS-IS TO-BE process'. Not for writing user stories (use product-manager skill), conducting user research (use ux-researcher), or financial modeling.

  • Writing plans

    NickCrew/Claude-Cortex/skills/collaboration/writing-plans Skill

    30★ repo

    Structured plan-writing skill adapted from obra/superpowers. Produces actionable plans that map directly to cortex workflows and tasks.

  • Copywriter

    NickCrew/Claude-Cortex/skills/copywriter Skill

    30★ repo

    Use this skill when writing persuasive, conversion-focused copy—landing pages, product descriptions, ads, sales emails, or any content designed to move someone to action. Trigger phrases: 'write copy for my landing page', 'describe this product', 'write an ad for'. Do NOT use for informational content, technical documentation, or long-form editorial writing.

  • Doc architecture review

    NickCrew/Claude-Cortex/skills/doc-architecture-review Skill

    30★ repo

    Evaluate documentation information architecture: navigation paths, discoverability, progressive disclosure, cross-linking, and mental model alignment. This skill should be used when restructuring docs, adding new sections, or when users report difficulty finding information.

  • Doc claim validator

    NickCrew/Claude-Cortex/skills/doc-claim-validator Skill

    30★ repo

    Validate that claims in documentation match codebase reality. Extracts verifiable assertions (file paths, commands, function references, behavioral claims, dependencies) from markdown docs and checks them against the actual project. Use after code changes, before releases, or when docs feel untrustworthy.

  • Doc completeness audit

    NickCrew/Claude-Cortex/skills/doc-completeness-audit Skill

    30★ repo

    Audit documentation completeness by mapping what a doc set should cover against what it actually covers. Produces a prioritized gap report by topic, not just by file. This skill should be used after shipping features, before releases, or when users report missing documentation.

  • Doc health audit

    NickCrew/Claude-Cortex/skills/doc-health-audit Skill

    30★ repo

    Orchestrate a full documentation health audit across five dimensions: structural health, semantic accuracy, topic completeness, prose quality, and information architecture. Runs each phase in dependency order with phase gating. This skill should be used for pre-release audits, periodic health checks, or comprehensive documentation assessments.

  • Doc maintenance

    NickCrew/Claude-Cortex/skills/doc-maintenance Skill

    30★ repo

    Systematic documentation audit and maintenance. This skill should be used when documentation may be stale, missing, or misorganized — after feature work, refactors, dependency upgrades, or as a periodic health check. It prescribes folder structure for docs/ and manual/, dispatches haiku subagents for codebase/doc scanning, and routes doc creation to specialized agents (reference-builder, technical-writer, learning-guide) with docs-architect as quality gate.

  • Doc quality review

    NickCrew/Claude-Cortex/skills/doc-quality-review Skill

    30★ repo

    Assess documentation quality across readability, consistency, audience fit, and prose clarity. Produces a scored review with actionable findings. This skill should be used before releases, during doc reviews, or when documentation feels unclear or inconsistent.

  • Documentation production

    NickCrew/Claude-Cortex/skills/documentation-production Skill

    30★ repo

    Use when generating, updating, or organizing documentation (component/API docs, project indexes, diagrams, tutorials, learning paths) - provides structured workflows and references for docs generation, indexing, diagrams, and teaching.

  • Openapi specification

    NickCrew/Claude-Cortex/skills/openapi-specification Skill

    30★ repo

    OpenAPI 3.x specification design, schema patterns, and validation for REST API contracts. Use when creating or maintaining API specifications, generating documentation, or validating API contracts.

  • Product manager

    NickCrew/Claude-Cortex/skills/product-manager Skill

    30★ repo

    Use this skill when writing product requirements documents, prioritizing features, creating user stories, defining acceptance criteria, or setting product metrics. Trigger phrases: 'write a PRD for', 'prioritize this feature backlog', 'write user stories for', 'help me define acceptance criteria', 'what metrics should we track for'. Not for writing code, designing UI mockups, or conducting user research interviews.

  • Proofreader

    NickCrew/Claude-Cortex/skills/proofreader Skill

    30★ repo

    Use this skill when reviewing written content for grammar, spelling, punctuation, style consistency, and tone—before publishing, submitting, or sending. Trigger phrases: 'proofread this', 'check my writing', 'review this for errors', 'edit this email/report/essay'. Do NOT use when structural rewrites or content changes are needed—proofreading fixes surface errors, not substantive problems.

  • Reference documentation

    NickCrew/Claude-Cortex/skills/reference-documentation Skill

    30★ repo

    Create exhaustive technical references, API documentation, and searchable reference materials. Use when building API docs, configuration references, or complete technical specifications.

  • Repo cleanup

    NickCrew/Claude-Cortex/skills/repo-cleanup Skill

    30★ repo

    Use when a repository needs cleanup of dead code, build artifacts, unused dependencies, outdated docs, or stale tests - provides safe cleanup workflows, validation steps, and reporting templates for code, deps, docs, tests, and sprint archives.

  • Storyteller

    NickCrew/Claude-Cortex/skills/storyteller Skill

    30★ repo

    Use this skill when writing fiction, narrative nonfiction, brand stories, or any content where emotional engagement and narrative arc matter more than pure information delivery. Trigger phrases: 'write a short story', 'tell my brand's origin story', 'write a narrative about', 'create a character'. Do NOT use for purely informational content, technical writing, or persuasive copy without a narrative component.

  • Test review

    NickCrew/Claude-Cortex/skills/test-review Skill

    30★ repo

    Review test quality and audit test coverage for any module. This skill should be used when reviewing existing tests, auditing test gaps, writing new tests, or when asked to assess test health. It pipelines testing standards into the audit workflow to produce a prioritized gap report. The output is a report, not code — do not write test implementations until the report is reviewed.

  • Testing skills with subagents

    NickCrew/Claude-Cortex/skills/testing-skills-with-subagents Skill

    30★ repo

    Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes

  • Tutorial design

    NickCrew/Claude-Cortex/skills/tutorial-design Skill

    30★ repo

    Design and write hands-on tutorials with progressive disclosure, exercises, and troubleshooting sections. Use when creating learning content, workshops, or step-by-step guides.

  • Ux researcher

    NickCrew/Claude-Cortex/skills/ux-researcher Skill

    30★ repo

    Use this skill when planning or conducting user research, writing interview guides, designing surveys for UX insights, synthesizing qualitative findings, creating personas, or writing research reports. Trigger phrases: 'write a user interview guide', 'how do I conduct usability testing', 'synthesize research findings', 'create a user persona', 'design a UX survey'. Not for quantitative market sizing (use market-researcher), writing business requirements (use business-analyst), or product analytics.

  • Ux writer

    NickCrew/Claude-Cortex/skills/ux-writer Skill

    30★ repo

    Use this skill when crafting microcopy, UI text, or in-product writing—error messages, tooltips, button labels, empty states, onboarding flows, and confirmation dialogs. Trigger phrases: 'write microcopy for', 'write UI copy', 'write error messages', 'write onboarding text', 'button label for'. Do NOT use for marketing copy (use copywriter) or long-form documentation (use technical-writer).

  • Writing skills

    NickCrew/Claude-Cortex/skills/writing-skills Skill

    30★ repo

    Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization

  • Structured output contract designer

    AnthonyAlcaraz/agentic-graph-rag-skills/skills/reasoning-planning/structured-output-contract-designer Skill

    30★ repo

    Design the OUTPUT CONTRACT for a graph-agent node's seam, per Ch5 "Structured Generation: The Keystone of Reliable Communication" (Outlines). Most graph-agent failures are internode COMMUNICATION breakdowns, not bad reasoning — a node that emits free text is unreliable exactly where its output feeds the next node or a graph write. The designer picks an enforcement level (FREE_TEXT / JSON_SCHEMA / GRAMMAR_CONSTRAINED), emits a minimal contract for common DevOps-investigation node types, and validates a payload against that contract deterministically — the primitive that makes a seam verifiable. Use when wiring a node's output into another node, a graph write, or a tool call and free text would make the seam fragile. NOT for choosing WHICH pipeline shape to run (that is pipeline selection), NOT for terminal human-facing prose with no downstream parser, NOT for picking a model or a graph model class.

  • Grill with docs

    tt-a1i/matt-skills-with-to-goal/skills/grill-with-docs Skill

    30★ repo

    A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

    The same file is in 19 other repositories

  • Research

    tt-a1i/matt-skills-with-to-goal/skills/research Skill

    30★ repo

    Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

    The same file is in 11 other repositories

  • Writing great skills

    tt-a1i/matt-skills-with-to-goal/skills/writing-great-skills Skill

    30★ repo

    Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

    The same file is in 11 other repositories