Productivity AI agent skills

4,613 skills in the archive. Read a skill’s instructions or open its original repository.

• Ln 56 Architecture Auditor

  by @levnikolaevich

  Audits implemented architecture boundaries, dependencies and ownership; not target design or plan review.

• Ln 31 Delivery Plan Builder

  by @levnikolaevich

  Builds dependency-ordered delivery plans from requirements and repository evidence; read-only.

• Ln 61 Repository Publisher

  by @levnikolaevich

  Commits, pushes and remotely verifies authorized repository changes; does not create releases.

• Ln 32 Test Strategy Planner

  by @levnikolaevich

  Plans risk-based test portfolios and acceptance evidence; does not write or execute tests.

• User Research

  by @rsmdt

  User research and insight synthesis for interviews, usability testing, personas, journey mapping, and actionable product/design recommendations. Use when planning studies, collecting evidence, synthesizing patterns, or…

• Specify Incremental

  by @rsmdt

  Decompose a single-feature specification into a linear, phase-by-phase implementation plan. Use this for medium-complexity work — single feature, one or two components — where transparent human-in-the-loop phase review is…

• Writing Skills

  by @rsmdt

  Use when creating new skills, editing existing skills, auditing skill quality, converting skills to markdown conventions, or verifying skills before deployment. Triggers include skill authoring requests, skill review needs, or…

• Specify Requirements

  by @rsmdt

  Create and validate product requirements documents (PRD). Use when writing requirements, defining user stories, specifying acceptance criteria, analyzing user needs, or working on requirements.md files in .start/specs/.

• Specify Solution

  by @rsmdt

  Create and validate solution design documents (SDD). Use when designing architecture, defining interfaces, documenting technical decisions, analyzing system components, or working on solution.md files in .start/specs/.

• Api Contract Design

  by @rsmdt

  REST and GraphQL API design patterns, OpenAPI/Swagger specifications, versioning strategies, and authentication patterns. Use when designing APIs, reviewing API contracts, evaluating API technologies, or implementing API…

• Architecture Selection

  by @rsmdt

  System architecture patterns including monolith, microservices, event-driven, and serverless, with C4 modeling, scalability strategies, and technology selection criteria. Use when designing system architectures, evaluating…

• Review

  by @rsmdt

  Multi-agent code review with specialized perspectives (security, performance, patterns, simplification, tests)

• Requirements Elicitation

  by @rsmdt

  Requirement gathering techniques, stakeholder analysis, user story patterns, and specification validation. Use when clarifying vague requirements, resolving conflicting needs, documenting specifications, or validating…

• Code Quality Review

  by @rsmdt

  Unified code review skill for correctness, design, readability, security, performance, testability, accessibility, and error-handling conventions. Use when reviewing changes, enforcing quality standards, or identifying technical…

• Implement Incremental

  by @rsmdt

  Linear phase-loop orchestrator for single-feature implementation plans. Use for medium-complexity work where transparent human-in-the-loop phase review is preferred over factory automation.

• Performance Analysis

  by @rsmdt

  Measurement approaches, profiling patterns, bottleneck identification, and optimization guidance. Use when diagnosing performance issues, establishing baselines, identifying bottlenecks, or planning for scale. Always measure…

• Feature Prioritization

  by @rsmdt

  RICE, MoSCoW, Kano, and value-effort prioritization frameworks with scoring methodologies and decision documentation. Use when prioritizing features, evaluating competing initiatives, creating roadmaps, or making build vs defer…

• Implement

  by @rsmdt

  Implementation entry point. Use to execute a completed specification. Auto-detects the decomposition tier (Direct, Incremental, or Factory) from spec artifacts and dispatches to the matching execution sub-skill.

• Boss

  by @echoVic

  可审计的 agent 团队：BMAD 全自动研发流水线编排器。编排 9 个专业 Agent（PM、架构师、UI Designer、Tech Lead、Scrum Master、Frontend、Backend、QA、DevOps）从需求到部署，每一步都有事件溯源 + 不可绕过门禁 + 确定性 eval——可验证测试真跑、门禁真过。支持单环节切片命令（/boss:plan /review /qa /ship）与无 CLI 纯 Markdown 降级。…

• Content Strategy Sms

  by @blacktwist

  When the user wants to plan a social media content strategy, decide what to post, or figure out topic clusters and content mix. Also use when the user mentions 'content strategy,' 'what should I post,' 'content ideas,' 'topic…

• Ai Short Drama Screenwriter

  by @POUND0423

  Use when developing, writing, formatting, reviewing, or revising short-form or vertical drama scripts and their episode structures, characters, scenes, dialogue, conflicts, hooks, reversals, or endings.

• Interview Framework

  by @tzachbon

  This skill should be used when a Ralph phase must identify critical user decisions, run a layered grill, persist partial answers, obtain explicit approval, or resume an interrupted phase interview before delegating artifact work.

• Interview Framework Codex

  by @tzachbon

  Internal Ralph Specum contract for Codex phase interviews, skill manifests, approval, and delegation gates. Phase coordinators load this skill directly; users do not invoke it as a workflow phase.

• Spec Workflow

  by @tzachbon

  This skill should be used when the user asks to "build a feature", "create a spec", "start spec-driven development", "run research phase", "generate requirements", "create design", "plan tasks", "implement spec", "check spec…

• Ralph Specum Implement

  by @tzachbon

  This skill should be used only when the user explicitly asks to use `$ralph-specum-implement`, or explicitly asks Ralph Specum in Codex to run implementation for approved tasks, quick mode, or an explicit continue request.

• Ralph Specum Prototype

  by @tzachbon

  This skill should be used only when the user explicitly invokes `$ralph-specum-prototype`, or explicitly asks Ralph Specum in Codex to run, resume, quick-run, or cancel an optional prototype.

• Ralph Specum Refactor

  by @tzachbon

  This skill should be used only when the user explicitly asks to use `$ralph-specum-refactor`, or explicitly asks Ralph Specum in Codex to revise spec artifacts after implementation learnings.

• Ralph Specum Triage

  by @tzachbon

  This skill should be used only when the user explicitly asks to use `$ralph-specum-triage`, or explicitly asks Ralph Specum in Codex to triage a large effort into multiple specs.

• Ralph Specum Index

  by @tzachbon

  This skill should be used only when the user explicitly asks to use `$ralph-specum-index`, or explicitly asks Ralph Specum in Codex to generate or refresh index artifacts.

• Ralph Specum Requirements

  by @tzachbon

  This skill should be used only when the user explicitly asks to use `$ralph-specum-requirements`, or explicitly asks Ralph Specum in Codex to run the requirements phase.

• Ralph Specum Cancel

  by @tzachbon

  This skill should be used only when the user explicitly asks to use `$ralph-specum-cancel`, or explicitly asks Ralph Specum in Codex to stop execution or remove a spec.

• Ralph Specum Status

  by @tzachbon

  This skill should be used only when the user explicitly asks to use `$ralph-specum-status`, or explicitly asks Ralph Specum in Codex for status or active spec progress.

• Ralph Specum Feedback

  by @tzachbon

  This skill should be used only when the user explicitly asks to use `$ralph-specum-feedback`, or explicitly asks Ralph Specum in Codex to draft or submit feedback.

• Ralph Specum Research

  by @tzachbon

  This skill should be used only when the user explicitly asks to use `$ralph-specum-research`, or explicitly asks Ralph Specum in Codex to run the research phase.

• Ralph Specum Help

  by @tzachbon

  This skill should be used only when the user explicitly asks to use `$ralph-specum-help`, or explicitly asks Ralph Specum in Codex for help or command guidance.

• Ralph Specum Switch

  by @tzachbon

  This skill should be used only when the user explicitly asks to use `$ralph-specum-switch`, or explicitly asks Ralph Specum in Codex to switch the active spec.

• Ralph Specum Start

  by @tzachbon

  This skill should be used only when the user explicitly asks to use `$ralph-specum-start`, or explicitly asks Ralph Specum in Codex to start or resume a spec.

• Ralph Specum Design

  by @tzachbon

  This skill should be used only when the user explicitly asks to use `$ralph-specum-design`, or explicitly asks Ralph Specum in Codex to run the design phase.

• Ralph Specum Tasks

  by @tzachbon

  This skill should be used only when the user explicitly asks to use `$ralph-specum-tasks`, or explicitly asks Ralph Specum in Codex to run the tasks phase.

• Speckit Workflow

  by @tzachbon

  Comprehensive understanding of the spec-kit methodology. Constitution-driven feature development with specify, plan, tasks, and implement phases.

• Delegation Principle

  by @tzachbon

  Core principle that the main agent is a coordinator, not an implementer. All work must be delegated to subagents.

• Smart Ralph

  by @tzachbon

  Core Smart Ralph skill defining common arguments, execution modes, and shared behaviors across all Ralph plugins.

• Communication Style

  by @tzachbon

  Output rules for all agents - concise, scannable, actionable. Based on Matt Pocock's planning principles.

• Learn This

  by @michalparkola

  Unified content extraction and action planning. Use when user says "learn-this <URL>", "learn this <URL>", "weave <URL>", "help me plan <URL>", "extract and plan <URL>", "make this actionable <URL>", or similar phrases…

• Scrum Sage

  by @michalparkola

  AI-powered Scrum Master and Enterprise Agility Coach based on Jeff Sutherland, Taiichi Ohno, and First Principles thinking. Use when user needs help with Scrum, sprint analysis, backlog refinement, scaling advice, impediment…

• Session Log

  by @michalparkola

  Summarize the current conversation session and append results to the weekly agent-log. Use when user says "log this", "session log", "summarize this session", or asks to write results to the agent-log.

• Docker Sandboxes Env

  by @docker

  Use this skill when authoring, planning, or running a declarative `sbxenv.yaml` file for Docker Sandboxes (`sbx env create/run/plan/exec/rm`), even if the user just says they want to "check in a sandbox config", "make onboarding…

• Skill Factory

  by @Romanescu11

  A meta-skill that silently watches your workflows and automatically generates reusable Hermes skills from them.

• Plan

  by @oliver-kriska

  Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban). Use when designing interconnected systems or converting review findings into tasks.

• Review

  by @oliver-kriska

  Review code with parallel agents — tests, security, Ecto, LiveView, Oban. Use after implementation to catch bugs and anti-patterns before committing.

• Full

  by @oliver-kriska

  Deliver a large, cross-domain Phoenix feature or complete end-to-end system through planning, implementation, verification, and review. Use when several coordinated workflows or contexts must ship together. NOT for an existing…

• Catchup

  by @oliver-kriska

  Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.

• Investigate

  by @oliver-kriska

  Investigate bugs and errors in Elixir/Phoenix — root-cause analysis for crashes, exceptions, stack traces, test failures. Use --parallel for deep 4-track investigation.

• Learn From Fix

  by @oliver-kriska

  Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.

• Examples

  by @oliver-kriska

  Provide Phoenix, LiveView, Ecto, OTP, or Oban examples. Use when asked for sample code, a walkthrough, a proper implementation, or expected workflow output. Pair with domain skills. NOT for debugging, direct changes,…

• Quick

  by @oliver-kriska

  Implement small Phoenix changes without planning — add validations, update routes, fix components, create migrations. Use for single-file edits under 50 lines.

• Api Design Reviewer

  by @oxbshw

  Use when reviewing a proposed REST or GraphQL API change before merge — checks contract clarity, backwards compatibility, errors, pagination, auth, and naming.

• Repo Auditor

  by @oxbshw

  Use before opening a PR to audit the changes for stale comments, unused imports, missing tests, and inconsistencies with neighboring code.

• Sprint Planner

  by @oxbshw

  Use when planning the next sprint — turns ticket intake + team capacity into a planned sprint with explicit non-goals.

• Coco Ads

  by @coco-research

  Turn the project you just shipped into a short, polished, shareable launch video (an "ad") using HyperFrames. Use when someone says "/coco-ads", "make a launch video", "brag about this", "turn this into a promo", "make an ad for…

• Coco Diagram

  by @coco-research

  Use for architecture, current-state, process, data-flow, medallion, or DP diagrams, including redrawing .drawio and Mermaid sources. Creates branded flowchart, sequence, ER, org, timeline, and chart visuals as standalone…

• Openai Agents

  by @coco-research

  Build AI applications with OpenAI Agents SDK - text agents, voice agents, multi-agent handoffs, tools with Zod schemas, guardrails, and streaming. Prevents 11 documented errors. Use when: building agents with tools, voice agents…

• Visual Explainer

  by @coco-research

  Generate self-contained HTML visual explanations for systems, code changes, plans, data, and technical concepts. Use for diagrams, architecture overviews, diff or plan reviews, project recaps, comparison tables, slide decks, and…

• Arch Index

  by @coco-research

  Build and validate .arch/index.json — a committed map from each architectural component of this repository to the real directories and files that implement it, pinned to a git commit, with every path verified to exist. Also…

• Brain

  by @coco-research

  Use when the user says brain, project knowledge, what do we know about, open tasks, or recent decisions, or runs /brain or /brain-update. SQLite project_brain.db tracker for entities, relationships, tasks, threads, decisions,…

• Pmstudio Nfr

  by @coco-research

  Detailed completeness audit of all project documents. Use when someone asks "are we ready for production", "audit our docs", "readiness check", "nfr tracker", or "what's missing". Do NOT use for a quick command listing — use…

• Skill Creator

  by @coco-research

  Use when the user asks to create, scaffold, update or package a skill, or asks how skill frontmatter, progressive disclosure or bundled resources should be structured. Walks through init_skill.py, writing SKILL.md and…

• Skill Evolution

  by @coco-research

  Use when running, reviewing or changing coco's self-evolution cycle: the 30-day loop that observes how skills are actually used, proposes evidence-backed edits to them as one branch and one pull request, and lands nothing…

• Api Design Principles

  by @coco-research

  Use when designing a new REST or GraphQL API, reviewing an API spec before implementation, setting team API standards, or migrating REST to GraphQL. Covers resources, HTTP semantics, pagination, error handling, and pitfalls.

• Project Docs

  by @coco-research

  Use when starting a new project, onboarding to an existing product, or auditing an existing folder structure against the standard. Scaffolds the 16-document set, folder structure, project memory and doc-sync config.

• Ui Ux Pro Max

  by @coco-research

  Use when designing, building or reviewing UI/UX for a web or mobile app: picking styles, color palettes, typography, layout, animation or charts, or checking accessibility and touch targets. Priority-ranked rules ordered by…

• Pmstudio Irp

  by @coco-research

  Use when the user asks for an incident response plan, IRP, escalation matrix or incident playbook. Writes an offline HTML plan with severities, escalation contacts and comms; DR restores service, IRP runs the incident.

• Task Prd Creator

  by @coco-research

  Use when the user says I want to add X, implement Y, create a task for Z, or plan this feature. Writes a task file plus a PRD under .agent/, links them, and waits for approval before any implementation starts.

• Pmstudio Comms

  by @coco-research

  Generate templated stakeholder communications from project context. Use when someone asks to "write a go-live email", "create a status update", "onboard someone", "write an announcement", "steerco update", "incident summary",…

• Pmstudio Dr

  by @coco-research

  Generate a Disaster Recovery plan with RTO/RPO targets. Use when someone asks to "create a DR plan", "disaster recovery", "business continuity", or "RTO RPO". Do NOT use for step-by-step restoration runbooks — use…

• Pmstudio Arb

  by @coco-research

  Generate an Architecture Review Board (ARB) presentation in Coco Inc's standard 11-slide format. Use when someone asks to "create an ARB deck", "architecture review presentation", "prepare for architecture review board", "ARB…

• Agent Lightning

  by @coco-research

  Train and optimize AI agents using Microsoft's Agent Lightning framework with reinforcement learning. Use when setting up agent training, instrumenting agents with tracing, configuring LightningStore, implementing reward…

• Coco Loop

  by @coco-research

  Start a safe, governed autonomous loop from a plain-language goal. Use when the user says /coco-loop, "run an autonomous loop", "keep my build green for N hours", "work on X autonomously for a while", or wants a bounded…

• Humanizer

  by @coco-research

  Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns…

• Cli Anything

  by @coco-research

  Wrap any command-line tool into a JSON-emitting agent skill. Use when you want to make a CLI reliably callable and parseable by an AI agent — introspect its --help, define a structured-output (--json) contract and a stable error…

• Coco Cli

  by @coco-research

  Install, update, version-check, or uninstall the Coco open-source AI workflow framework via bin/coco.js. Use when setting up Coco on a machine, checking out the pinned release tag into an existing clone, checking the installed…

• Goal

  by @coco-research

  Persistent project goal that survives across sessions and tools, with continuous-execution loop semantics. Use when someone asks to "set a goal", "what is my goal", "goal status", "keep working on X until done", "resume the…

• Clone Website

  by @coco-research

  Clone any website into a pixel-perfect single-file HTML prototype. Extracts design tokens, assets, CSS computed styles, interaction patterns, and content via Playwright. Outputs a self-contained HTML file with real data…

• Pmstudio

  by @coco-research

  PM Studio command center. Use for a quick overview of available commands and document inventory. Use when someone says "pmstudio", "show commands", "what can I generate", or "project status". Do NOT use for detailed completeness…

• Migrate To Skills

  by @coco-research

  Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use when the user wants to migrate rules or commands to skills, convert .mdc…

• Coco Ship

  by @coco-research

  Use when finished work needs to reach a coco-managed repository (coco-research/coco or similar) — verifies branch state, commits, pushes through the corporate DLP guard only when actually needed, opens a PR against main, waits…

• Brain:Update

  by @coco-research

  End-of-session brain flush. Scans the full conversation, extracts all new entities, decisions, tasks, events, relationships, and updates, presents a summary, and writes to project_brain.db after confirmation. Use at end of every…

• Openai Whisper

  by @coco-research

  Speech-to-text transcription via OpenAI Whisper. Supports two modes — Local CLI (no API key, runs on-device) and Cloud API (fast, scalable, requires OPENAI_API_KEY). Use when the user needs to transcribe audio files, translate…

• Context Budget

  by @coco-research

  Audit token consumption across agents, skills, MCP servers, and rules. Identifies bloat, redundant components, and produces prioritized token-savings recommendations. Use when the context window is filling up too fast or before…

• Create Rule

  by @coco-research

  Create Cursor rules for persistent AI guidance. Use when the user wants to create a rule, add coding standards, set up project conventions, configure file-specific patterns, create RULE.md files, or asks about .cursor/rules/ or…

• Generate Tests

  by @coco-research

  Use when asked to generate tests for a file, module or component, to raise coverage, or to bootstrap a suite for untested code. Detects the project's test framework and conventions first, then writes unit, integration and…

• Gsd Check Todos

  by @coco-research

  Use when the user asks what is pending, what to do next, or to list todos (optionally filtered by area). Lists pending todos, loads full context for the selected one, and routes to work now, add to a phase, brainstorm, or create…

• Gsd Add Tests

  by @coco-research

  Use when a completed phase needs unit or E2E tests, or the user asks to add tests for phase N. Classifies implementation files into TDD, E2E, or skip, gets plan approval, then generates RED-GREEN tests from SUMMARY.md and UAT…

• Brain:Rescan

  by @coco-research

  Use when project files changed since the last brain scan, CLAUDE.local.md was updated, or a periodic refresh is due. Rescans incrementally, writes new entities, decisions, and documents; needs project_brain.db (run /brain-init…

• Brain:Wiki

  by @coco-research

  Use when the user asks for a knowledge article, wiki page, or entity summary from the brain, or wants to search, list, or review merges across brain DB articles. Generates Wikipedia-style articles from entities, decisions, and…

• Pmstudio Sync

  by @coco-research

  Use when linked docs drift, when a source file changes and downstream PRDs, decks, or notes must follow, or when a .sync-report.md exists. Diffs the proposed edits, applies them only after approval, and never overwrites a target…

• Finishing A Development Branch

  by @coco-research

  Use when implementation is done and tests pass and the user must choose to merge locally, open a PR, keep the branch, or discard it. Presents those four options, executes the choice, and cleans up the worktree for merge and…

• Design Taste Frontend

  by @coco-research

  Use when the user asks for a landing page, marketing site, portfolio, or redesign, not dashboards or data tables. Infers a design read, sets the three dials, picks a real design system, and blocks generic AI patterns at…

• Gsd Audit Fix

  by @coco-research

  Use after /gsd-audit-uat when the user wants the findings fixed, not just listed. Classifies each issue as auto-fixable or manual and fixes the auto-fixable ones with test verification and atomic commits; --severity sets the…

• Brain:Export

  by @coco-research

  Use when the user asks to refresh CLAUDE.local.md, regenerate project context, or after a brain-update session flush. Rewrites only the sentinel-delimited auto-generated section from the brain DB, preserving manual behavior rules.