Repurpose content across channels. Use when: blog-to-social, webinar-to-article, pillar derivatives, format adaptation.

Documentation architecture, content planning, and maintenance strategies

Generate professional e-commerce marketing copy, descriptions, and blog posts. Use when the user needs text content.

Search context-mode's persistent FTS5 knowledge base for previously indexed local project content, documentation, or session memory. Trigger: /context-mode:ctx-search

Use for everyday coding tasks that involve writing or modifying source code.

Datadog docs lookup using docs.datadoghq.com/llms.txt and linked Markdown pages.

Pinpoints an audience's true search intent to create a strategic content roadmap. Use this skill to understand why an audience is searching, what questions they have, and what content will meet their needs, guiding them from visitor to customer.

Generate or update project documentation

DEPRECATED in v0.4.0. Use `/aidoc-flow:doc-validator` with scope=prose. This skill is a redirect stub and will be removed in v0.7.0.

Provides templates, standards, and best practices for writing clear, comprehensive technical documentation

Turn an ingested insight into a proper zettelkasten note with clean prose. Stage 2 of the processing pipeline.

Product description writing — keyword integration, benefit-focused copy, FAQ, formatting

Writes Python code following FiftyOne's official conventions. Use when contributing to FiftyOne, developing plugins, or writing code that integrates with FiftyOne's codebase.

Remove vague, corporate, or AI-sounding language and replace it with clear, specific, human wording. Trigger on "improve copy", "sounds generic", "too fluffy".

Use when an operation issue is an index refresh — typically the hourly index-refresh routine. Rebuild `wiki/index.md` so each entry has a tight, scannable one-line summary and the catalog tracks the actual contents of `wiki/`. Resolve drift between the index and recent log activity, but do not edit page content.

Turn a shaped project kickoff transcript into a reference document for the builder. Use when the user has a transcript (VTT, etc.) from a kickoff call and wants to produce a document that captures what was shaped and agreed.

Read the latest real-time transcription. Use when user asks to see, read, or show a transcription that was captured via live-transcribe. Triggers on: 'תקריא תמלול', 'מה תמללתי', 'התמלול האחרון', 'show transcription', 'what did I say', 'read the transcript', 'מה נכתב בתמלול', 'תראה לי את התמלול'. Also use when user references transcription content without being explicit — e.g. 'summarize what I said', 'translate the transcription'.

Load all open issues from GitHub and save them as markdown files

Maintains concise repository MEMORY.md notes for gotchas, stale memory corrections, and durable user preferences. Use at the start of repository conversations, when the user mentions MEMORY.md, when an error should be remembered to avoid repeating it, or when MEMORY.md content may be wrong.

Execute end-to-end migrations and consolidate docs/scripts (remove dead files, keep canonical runbooks). Use when changing runtime model, reorganizing repo, or doing “repo cleanup”.

Build recurring audience touchpoints with compelling newsletters. Use when building audience loyalty, establishing authority, or creating regular engagement with your subscribers.

Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.

OpenRewrite recipe test maintenance. Use when fixing test failures, import ordering issues, type validation problems, IDE warnings, or writing comprehensive recipe tests.

Create, organize, and distribute content across Workspace.

Pine Script v5/v6 indicator scaffold and patterns. Provides structure guidance and triggers doc-researcher for current syntax verification. Use when developing TradingView indicators.

Track and analyze portfolio company performance against plan. Ingests monthly/quarterly financial packages (Excel, PDF), extracts KPIs, flags variances to budget, and produces summary dashboards. Use when reviewing portfolio company financials, preparing board materials, or monitoring covenant compliance. Triggers on "review portfolio company", "monthly financials", "how is [company] performing", "covenant check", or "portfolio update".

Generate structured presentation outlines with bold statement slides, section dividers, and clear narrative arcs. Use when starting a new presentation, planning a deck structure, or asking "outline a presentation about...", "structure a deck for...", or "create a presentation flow for...". Outputs markdown outlines ready to translate into slides.

Document a business process — flowcharts, RACI, and SOPs

Use when writing tests for serialization, validation, normalization, or pure functions - provides property catalog, pattern detection, and library reference for property-based testing

This skill should be used when user asks to "fetch overleaf review comments", "address overleaf reviews", "apply overleaf comments", "review my overleaf paper", "sync overleaf feedback to local", "what comments are on my overleaf doc", or wants to act on Overleaf reviewer feedback in a local git-tracked LaTeX repo.

Rspress best practices for config, CLI workflow, content organization, frontmatter, MDX, themes, i18n, search, static assets, deployment, and debugging. Use when writing, reviewing, or troubleshooting Rspress documentation sites.

Search blog posts to find information about the project. Use when looking for documentation or information about this project.

Load a previous session to review its content. Use when resuming work or reviewing past sessions.

Shopify Markets — multi-currency, translation, duties/taxes, localized pricing, market-specific content

Export Slidev presentations to PDF, PPTX, and PNG. Use this skill for sharing, printing, and archiving presentations.

Master Slidev's extended Markdown syntax. Use this skill to write slides with advanced formatting, frontmatter, and special features.

Drafts engaging social media posts, writes hooks, suggests hashtags, creates thread structures, and generates companion images. Use when the user asks to write a LinkedIn post, tweet, Twitter/X thread, social media caption, social post, or repurpose content for social platforms.

Convert content between platforms (blog to Twitter thread, article to LinkedIn post, etc.). Optimize for each platform's format, tone, and best practices. Use when user wants to adapt content for different social media platforms.

Specification authoring with traceable paragraph IDs. Use when writing specifications, updating specs, adding new features to specs, or when implementing code that needs to reference spec paragraphs. Triggers on spec creation, implementation traceability, or coverage verification.

Foundational knowledge for writing Stan 2.37 models including program structure, type system, distributions, and best practices. Use when creating or reviewing Stan models.

Systematic TDD methodology for writing tests first. Use when implementing features or fixes with OMC_TDD_MODE enabled, when unsure how to structure tests, or when test-first discipline needs reinforcement. Triggers on: 'tdd', 'test first', 'test driven', 'red green refactor'.

Test-Driven Development guidance. Use when writing code, implementing features, or fixing bugs in projects that follow TDD methodology. Provides the Red-Green-Refactor cycle structure.

DEPRECATED in v0.4.0. Use `/aidoc-flow:doc-validator` traceability pass. This skill is a redirect stub and will be removed in v0.7.0.

Generates a technical blog post from code implementation. Use when asked to write a blog post about a feature, explain an implementation for a blog, document code as a blog article, or create technical content from source code. Triggers on phrases like "write a blog post about", "turn this into a blog", "create a technical article", or "explain this for a blog".

Generate or update project documentation

Fetch data from URLs. Use when asked to download content, fetch remote files, or read web data.

Reference standards for writing and maintaining GitHub issues in the tldraw repository. Use as supporting guidance when another skill or workflow needs issue title, body, type, label, or triage standards.

Write blog posts sharing knowledge about the project. Use when writing blog posts, capturing knowledge, or adding to the project knowledge base.

Grilling session that mines the user for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single document as raw material for a future article. Use when the user wants to develop ideas before imposing structure, or mentions "fragments", "ideate", or "raw material" for writing.

Methodology for creating effective skills using TDD principles. Use when creating new skills, editing existing skills, or authoring plugin components. Triggers on: 'create skill', 'write skill', 'new skill', 'skill authoring'.

Use for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages. Direct, brief style with no AI-speak. NOT for README.md, public docs, or blog posts.

Use when coding decisions depend on current library/framework APIs and you need version-accurate docs before implementation. AE.LTD workflow tuned for fast, verifiable doc grounding.

Corporate BS detector. Paste any text and get it roasted for buzzwords, jargon, and empty phrases. Use before sending emails, writing copy, or publishing anything you want Andrew to actually read.

Generate technical articles and documentation using AI. Use for writing blog posts, documentation, and technical content.

Clinical copy-editor that reviews text for communication issues. Use when user says review for prose or improve the prose

Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.

Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes

Foundational knowledge for writing BUGS/JAGS models including precision parameterization, declarative syntax, distributions, and R integration. Use when creating or reviewing BUGS/JAGS models.

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

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

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

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

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

Applies principles from Robert C. Martin's 'Clean Code'. Use this skill when writing, reviewing, or refactoring code to ensure high quality, readability, and maintainability. Covers naming, functio...

Use for evidence-based codebase documentation. Walks the repo, builds a map of components + responsibilities + interconnections. Output is hand-curated markdown with diagrams. Variants — codemap-fast, codemap-diff, codemap-trust, codemap-export.

Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue re...

Create pull requests following best practices. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows conventional commit and PR conventions.

Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

General reference documents by domain. Use when creating architecture docs, strategy documents, specs, or guides.

Generate and maintain documentation with drift detection

Distills everything Claude has learned in the current conversation into a structured Markdown knowledge document saved to disk. Use when the user wants to capture findings, decisions, architecture insights, or research from a session — phrases like "document what you know", "save your knowledge", "write up what we found", or "document this".

MUST BE USED for bug fixes that require test-first verification. Use when user says '/fix', 'fix this bug', 'fix the error', 'debug this', or provides an error/bug report. This skill mandates writing a failing test BEFORE implementing any fix, then loads the SDLC workflow.

Use when searching markdown knowledge bases, documentation, or notes for relevant context - provides qmd CLI syntax for keyword, semantic, and hybrid search across indexed collections

Fetch tweets, Twitter/X articles, and Reddit posts via proxy APIs. Use when the user provides a twitter.com, x.com, or reddit.com URL, or asks to read a tweet, post, article, or thread from Twitter/X or Reddit.

USE FOR getting AI-generated POI text descriptions. Requires POI IDs obtained from web-search (with result_filter=locations). Returns markdown descriptions grounded in web search context. Max 20 IDs per request.

Rewrite nonfiction prose in the style of Michael Lewis. Strips formula, scaffolding, and manufactured drama. Replaces them with earned narrative, invisible transitions, and evidence that draws its own conclusions.

Edit PDFs with natural-language instructions using the nano-pdf CLI.

Edit PDF text/typos/titles via nano-pdf CLI (NL prompts).

Edit PDFs with natural-language instructions using the nano-pdf CLI.

Edit PDFs with natural-language instructions using the nano-pdf CLI.

Skill where brain reference precedes a negation-prose mention

Write markdown documents and mermaid diagrams to Obsidian vaults.

Codifies the standards and conventions for the creation, organization, categorization, and aggregation of data in the DeLoDocs obsidian vault. Use this skill when asked to add something 'to my vault' or 'in my vault', when creating any reports, instructions, updates, or any markdown documents that are intended to be viewed, and are NOT part of a project or repository.

Fixing odoc documentation warnings and errors. Use when running dune build @doc, resolving reference syntax issues, cross-package references, ambiguous references, hidden fields, or @raise tags in OCaml documentation.

Create, organize, and distribute content across Workspace.

Find and reference PolicyEngine blog posts, research articles, and published analyses for evidence and proof points. Triggers: "find blog post", "PolicyEngine research", "published analysis", "proof point", "has PolicyEngine written about", "blog post about"

Write structured, opinionated PRDs that engineers actually read. Use when asked to write a PRD, product spec, feature requirements, or product requirements document. Creates concise, evidence-backed specs with clear scope boundaries and measurable success criteria.

Turn a product idea into a manual-first process you can start delivering today. Use when you have an idea and want to figure out how to deliver value by hand before writing any code.

Deep-dive data profiling for a specific table. Use when the user asks to profile a table, wants statistics about a dataset, asks about data quality, or needs to understand a table's structure and content. Requires a table name.

Converts a PRD or plan markdown file into prd.json format for ralph-json-start-loop to execute autonomously. Use when user wants to convert a PRD or plan to JSON stories.

User's README style preferences — ultra-terse, action-focused, <50 lines. Use when writing or reviewing any README file.

Generates Markdown release notes for the most recent release of a GitHub repository. Use when the user asks to "generate release notes", "write a changelog", or "summarize the last release" for a GitHub repo (owner/repo or full URL).

Release tweets: draft/copy/post from changelog, tags, npm/appcast, artifacts.

Template for creating router skills. Use as a starting point when building a new router that dispatches to multiple specialized skills. Copy and customize for your domain.

Use when writing, reviewing, or refactoring code that involves structural decisions. Provides SOLID principles, composition patterns, module organization, and side-effect boundary guidelines.

Use when writing or updating spec.yaml files. Defines requirement format and user story structure.