Software Development AI agent skills

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

• Human In The Loop

  by @mvschwarz

  Use when classifying a slice closeout (auto-continue / human gate / park), routing a real decision to a human, or designing a human queue/dashboard surface. Treats humans as durable network participants with attention surfaces,…

• Queue Handoff

  by @mvschwarz

  Use when ending a turn, finishing a slice, blocked on another agent's work, or escalating to a human — durable work handoff via queue items so the system keeps moving across compactions, missed messages, and interruptions.…

• Developing Openrig

  by @mvschwarz

  Use when changing OpenRig's own source in a clone of the openrig repository: finding which package or file owns a behaviour, choosing which tests to run, testing a change without disturbing the OpenRig daemon your own session…

• Openrig Skills

  by @mvschwarz

  Use when you're operating OpenRig and need the right skill or context for fleet recovery, seat handover, new-seat orientation, a watchdog wake, cross-host reach to an agent on another machine, rig packaging, an OpenRig upgrade,…

• Agent Operated Software

  by @mvschwarz

  Use when designing, building, operating, or diagnosing an ongoing application whose live backend or control loop includes OpenRig agents, including applications with a Markdown, YAML, or JSON agent control plane or a thin…

• Openrig User

  by @mvschwarz

  Use when a specific `rig` command, subcommand, or flag is already known and you need its exact syntax, JSON shape, defaults, or error meaning. NOT for natural capability discovery, open-ended how-do-I questions, or choosing…

• Verification Before Completion

  by @mvschwarz

  Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

• Ui Mockup

  by @mvschwarz

  Create UI mockups at three fidelity levels — ASCII wireframes for quick iteration, standalone HTML mockups for delivery with requirements, and live prototypes for interaction testing.

• Plan Review

  by @mvschwarz

  Multi-perspective review of a feature plan or requirements doc before development begins. Evaluates from strategy, design/UX, and engineering angles to catch gaps early.

• Software For Agents

  by @mvschwarz

  Use when older OpenRig instructions name software-for-agents or describe agent-in-the-middle or studio software under the former skill name.

• Development Team

  by @mvschwarz

  Use when a development pod begins or hands off implementation, QA, or design work.

• Review Team

  by @mvschwarz

  Use when assigned a review or when an authored review boundary is reached.

• Bat Story Eval

  by @homeassistant-ai

  Compare MCP tool behavior between target and baseline versions using pre-built and custom stories with diff-based triage.

• Issue To Pr Resolver

  by @homeassistant-ai

  Implement a GitHub issue end-to-end — create a worktree branch, implement the feature with tests, create a draft PR, then iteratively resolve all CI failures and review comments until the PR is clean. Use when you need to fully…

• Issue Analysis

  by @homeassistant-ai

  Deep analysis of a single GitHub issue with codebase exploration, implementation planning, and architectural assessment. Use when you need to analyze a GitHub issue, assess its complexity, plan implementation approaches, and…

• My Pr Checker

  by @homeassistant-ai

  Manage your own GitHub pull requests — check CI status, inline review comments, PR-level comments, resolve review threads, fix issues, and iterate until all checks pass and threads are resolved. Use for managing your own PRs…

• Bat Adhoc

  by @homeassistant-ai

  Run bot acceptance tests to validate MCP tools work correctly from a real AI agent's perspective. Use when testing PRs, detecting regressions, or verifying tool changes end-to-end with Claude/Gemini CLIs.

• Contrib Pr Review

  by @homeassistant-ai

  Review a contribution PR for safety, quality, and readiness. Checks for security concerns, test coverage, size appropriateness, and intent alignment. Use when reviewing external contributions.

• Contributors Update

  by @homeassistant-ai

  Find merged PR authors missing from README and update the contributors list after approval

• Wt

  by @homeassistant-ai

  Create a git worktree in worktree/ subdirectory with up-to-date master

• Hunt Ssti

  by @elementalsouls

  Hunt server-side template injection (SSTI) across Jinja2 (Flask/Django), Twig (Symfony), Freemarker (Java), ERB (Rails), Spring, Velocity, Mako, Thymeleaf, Smarty. Detection probes use double-curly and dollar-curly math…

• Ios Redteam Pipeline

  by @elementalsouls

  End-to-end iOS red-team pipeline — IPA acquisition (App Store extraction, TestFlight, enterprise/ad-hoc sideload), class-dump/Hopper/Ghidra static analysis, Info.plist + entitlements + Keychain secret extraction, App Transport…

• Supply Chain Attack Recon

  by @elementalsouls

  External recon for software supply-chain attack surface — package-namespace squatting candidates, dependency-confusion vulnerabilities, GitHub Actions injection openings, container image registry exposure, SBOM mining,…

• Recon Scope Triage

  by @elementalsouls

  Triage ASM/recon output for ownership before testing — separate the target's real assets from namespace-collision noise. Automated recon keyword-matches on the brand name, so for any target whose name is a common/dictionary…

• Okta Attack

  by @elementalsouls

  Okta-as-IdP red-team attack chain — tenant discovery, user enumeration (multiple vectors), authentication flow analysis (factors enumeration, push-notification fatigue, SMS bypass), password spray with lockout discipline,…

• Hunt Xxe

  by @elementalsouls

  Hunting skill for xxe vulnerabilities. Built from 10 public bug bounty reports including SVG-upload XXE, Office-doc (PPTX/DOCX) XXE, SOAP XXE, SAML AssertionConsumer XXE, blind OOB XXE via DTD callback, parameter-entity XXE,…

• Hunt Xss

  by @elementalsouls

  Hunting skill for xss vulnerabilities. Built from 174 public bug bounty reports. Use when hunting xss on any target. For markup injection that reflects raw HTML but does NOT execute JavaScript (no `<script>`/event-handler…

• Vibe

  by @mistralai

  Authoritative reference for Mistral Vibe — the CLI agent you (the model) are running inside. LOAD when the user: - asks anything about Vibe itself, even by indirect name ("this CLI", "this tool", "you"); - wants to change,…

• Create Plugin

  by @mistralai

  Create a Vibe plugin package — the Agent Plugins 1.0 format with optional Vibe extensions for skills, MCP servers, hooks, knowledge, agents, libraries, and connectors. Use when the user wants to create, scaffold, or author a…

• Skill Creator

  by @mistralai

  Load this skill before creating, updating, or deleting a Vibe skill, or whenever you plan to add or modify SKILL.md files under a skills directory. It explains Vibe's SKILL.md frontmatter, discovery order, support files, and the…

• Worktree

  by @mistralai

  Create, reuse, and clean up git worktrees under $VIBE_HOME/worktrees. Use when the user wants to work in an isolated git worktree, create a worktree for a task, or list/remove existing worktrees.

• Alphagbm Research Reader

  by @AlphaGBM

  Find published research and institutional views with sources, dates and related assets. Use when the user asks to research reports with AlphaGBM. Use the bundled Python runner; never silently replace real results with demos.

• Alphagbm News Impact

  by @AlphaGBM

  Separate reported claims from impact inferences, with related assets and next checkpoints. Use when the user asks to news impact with AlphaGBM. Use the bundled Python runner; never silently replace real results with demos.

• Alphagbm Smart Money

  by @AlphaGBM

  Aggregate user-supplied disclosed buys and sells by source without automatically copying trades. Use when the user asks to smart money tracking with AlphaGBM. Use the bundled Python runner; never silently replace real results…

• Alphagbm Dca Plan

  by @AlphaGBM

  Build a contribution schedule and calculate a supplied price-path cost basis without predicting returns. Use when the user asks to dollar-cost averaging with AlphaGBM. Use the bundled Python runner; never silently replace real…

• Alphagbm Etf Strategy

  by @AlphaGBM

  Score ETF trend, risk, liquidity, cost and available tracking and theme signals while preserving data gaps. Use when the user asks to etf strategy with AlphaGBM. Use the bundled Python runner; never silently replace real results…

• Alphagbm Momentum Following

  by @AlphaGBM

  Score observed price trend, confirmation, risk and participation without forecasting a price. Use when the user asks to momentum following with AlphaGBM. Use the bundled Python runner; never silently replace real results with…

• Alphagbm Options Research

  by @AlphaGBM

  Compare option candidates and score components, with funding, expiry and assignment risks. Use when the user asks to options strategies with AlphaGBM. Use the bundled Python runner; never silently replace real results with demos.

• Alphagbm Grid Plan

  by @AlphaGBM

  Build an auditable grid from a price range, current price and capital. Use when the user asks to grid plan with AlphaGBM. Use the bundled Python runner; never silently replace real results with demos.

• Client Reverse

  by @awarexone

  Client-side request-signing and anti-bot token reversal for bug bounty — when a request carries a sign/sig/hmac/token/nonce/timestamp/X-Sensor header that Burp Repeater cannot replay, recover the signer just enough to reproduce…

• Mobile Pentest

  by @awarexone

  Mobile app pentest for bug bounty (Android APK + iOS IPA) — runtime-first workflow: install app, proxy through Burp/mitmproxy, drive the UI, capture packets, then test the API exactly like a web target; escalate to decompile…

• Web2 Vuln Classes

  by @awarexone

  Complete reference for 26 web2 bug classes with root causes, detection patterns, bypass tables, exploit techniques, and real paid examples. Covers IDOR, auth bypass, XSS (postMessage), SSRF (11 IP bypass techniques), SQLi,…

• Argus

  by @awarexone

  Argus — the all-seeing scanner suite. Six automated scanners for high-value web + LLM bug classes — CORS misconfiguration (origin reflection / null / credentialed read), CRLF & host-header injection, NoSQL injection (operator…

• Web2 Recon

  by @awarexone

  Web2 recon pipeline — subdomain enumeration (subfinder, Chaos API, assetfinder), live host discovery (dnsx, httpx), URL crawling (katana, waybackurls, gau), directory fuzzing (ffuf), JS analysis (LinkFinder, SecretFinder),…

• Bb Methodology

  by @awarexone

  Use at the START of any bug bounty hunting session, when switching targets, or when feeling lost about what to do next. Master orchestrator that combines the 5-phase non-linear hunting workflow with the critical thinking…

• Web3 Audit

  by @awarexone

  Smart contract security audit — 10 DeFi bug classes (accounting desync, access control, incomplete path, off-by-one, oracle, ERC4626, reentrancy, flash loan, signature replay, proxy), pre-dive kill signals (TVL < $500K etc),…

• Agent Device

  by @callstack

  Automates Apple-platform apps (iOS, tvOS, macOS), Android devices, and Amazon Vega OS TV apps in Vega Virtual Devices. Use when navigating apps, taking snapshots/screenshots where supported, driving TV remotes, tapping, typing,…

• Android Emulator

  by @callstack

  Verify and debug native, React Native, Expo, or Flutter apps on an Android Emulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure…

• Ios Simulator

  by @callstack

  Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure…

• Dogfood

  by @callstack

  Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.

• Typescript

  by @EpicenterHQ

  Apply project conventions for TypeScript types, imports, generics, factories, and runtime schemas. Use when editing `.ts` files or reviewing TypeScript design and tests, including constraints that need to name an invalid literal…

• Collapse Pass

  by @EpicenterHQ

  Find and carry through worthwhile code simplifications across recent edits, named files, or a subsystem. Use for a collapse pass, a refactoring pass, another simplification pass, "simplify this", clean up code, or a hunt for…

• Testing

  by @EpicenterHQ

  Choose useful regression coverage and apply Epicenter test conventions for setup, Result assertions, type tests, naming, and pruning. Use when writing, reviewing, deleting, or reorganizing tests, especially `*.test.ts` files.

• Pull Request

  by @EpicenterHQ

  Draft and review Epicenter pull request titles and bodies, including changelog and merge details. Use when creating a PR or editing its text, not for local commits, branches, or issue replies.

• Consult Claude

  by @EpicenterHQ

  Assign Claude Code a read-only investigation, recommendation, or finished text draft. Use when asked to consult Claude or when a design-review workflow includes Claude. Completed edits and executable experiments belong to…

• Factory Function Composition

  by @EpicenterHQ

  Factory function patterns to compose clients and services. Use when wrapping resources with domain methods, refactoring mixed client/service/method options, or documenting returned factory methods.

• Services Layer

  by @EpicenterHQ

  Apply Whispering service-boundary patterns for UI-free capabilities, explicit inputs, Result fallibility, Live objects, lifecycle factories, and platform variants. Use when creating or refactoring services, contracts, provider…

• Prototype

  by @EpicenterHQ

  Build a throwaway prototype to answer a focused logic, state-model, or UI question before committing to production design. Use when the user asks to prototype, sanity-check a model, mock up UI, explore design options, or try a…

• Yjs

  by @EpicenterHQ

  Apply Epicenter’s Yjs 14 patterns for row documents, transactions, persistence, and synchronization. Use when working with `@y/y`, CRDTs, collaborative editing, awareness, or Yjs storage and providers.

• Conversation Hygiene

  by @EpicenterHQ

  Triage and archive accumulated Codex conversations without losing wanted work. Use when cleaning up old Codex threads, deciding which conversations still need attention, or resuming a large conversation cleanup. Do not use for…

• Tauri

  by @EpicenterHQ

  Tauri commands, permissions, capabilities, security config, path handling, cross-platform file ops, and native filesystem APIs. Use when mentioning Tauri, desktop apps, Rust commands, invoke, capabilities, permissions,…

• Diagnose

  by @EpicenterHQ

  Diagnose hard bugs and performance regressions with a reproduce-to-regression-test feedback loop. Use when the user reports broken, throwing, failing, or slow behavior or explicitly asks to diagnose or debug it.

• Standalone Commits

  by @EpicenterHQ

  Split work into reviewable, auditable commits ordered by dependency. Use when planning commit waves, staging changes, or deciding whether a commit is too broad, tiny, incomplete, or hard to revert.

• Cohesion Over Testability

  by @EpicenterHQ

  Collapse test-shaped production boundaries while preserving behavior and coverage. Use when a helper, wrapper, injected dependency, or export exists mainly to let a unit test reach internals.

• Specification Writing

  by @EpicenterHQ

  Write technical specs that let agents implement autonomously. Use for "write a spec", "plan this feature", "create a planning doc".

• Computer Use Driven Iteration

  by @EpicenterHQ

  Improve an interactive product through repeated computer-use simulations, bounded Claude implementation, verification, and reflection to find opportunities to collapse complexity. Use when asked to keep exercising and improving…

• Control Flow

  by @EpicenterHQ

  Linearize complex control flow with early returns, guard clauses, nested ifs, and natural-language conditions. Use when flattening nested conditions, linearizing try/catch logic, or separating mixed throw-and-return handlers,…

• Cloudflare Workers

  by @EpicenterHQ

  Cloudflare Workers patterns for Worker runtime APIs, Durable Objects, KV, R2, D1, Queues, WebSockets, streaming responses, bindings, wrangler configuration, and deployment limits. Use when users mention Cloudflare Workers,…

• Post Implementation Review

  by @EpicenterHQ

  Review cumulative implementation for structural collapse, invariant ownership, and correctness. Use for reviewing work after implementation, doing a second pass, or performing a final sweep. Independent structural verdicts…

• Delegate Claude

  by @EpicenterHQ

  Delegate a bounded implementation, prototype, benchmark, or file artifact to Claude Code, then verify and integrate its completed work. Use when the user explicitly authorizes Claude to own execution. Read-only advice belongs to…

• Tsconfig

  by @EpicenterHQ

  TypeScript config conventions for this monorepo: the two-base layering, the seven leaf tiers, and the never-redeclare list. Use when adding a package, editing any tsconfig.json, picking a tier for a new app, or debugging module…

• Worktree Hygiene

  by @EpicenterHQ

  Safely reap merged Git worktrees and branches across Epicenter harnesses. Use when cleaning `git worktree list`, removing orphaned or detached worktrees, or deciding whether one is safe to delete, not when creating branches or…

• Tanstack Table

  by @EpicenterHQ

  Apply TanStack Table UI-state patterns for Svelte data tables, including columns, rendering, sorting, filtering, pagination, and row identity. Use when building or reviewing data-table UI, not Epicenter workspace storage tables.

• Better Auth Best Practices

  by @EpicenterHQ

  Better Auth server/client setup: `auth.ts`, generated schema, DB adapters, sessions, cookies, env vars, and plugins. Use when mentioning Better Auth, betterauth, auth handlers, OAuth, email/password, or session configuration.

• Git

  by @EpicenterHQ

  Apply Epicenter Git conventions for commits, branches, and history. Use when staging files, writing or splitting commits, creating branches, or inspecting history, not for pull request text or merge guidance.

• Autumn

  by @EpicenterHQ

  Autumn billing in Epicenter: `autumn.config.ts`, `autumn-js` credit checks, `atmn` CLI, plan gates, and metered AI usage. Use when changing billing, pricing, credits, plan access, refunds, or usage events.

• Drizzle Orm

  by @EpicenterHQ

  Apply Drizzle ORM patterns for schemas, migrations, queries, branded types, and Postgres or D1 boundaries. Use when working with Drizzle or typed SQL, not raw `bun:sqlite` or non-Drizzle engines.

• Platform Seams

  by @EpicenterHQ

  Apply Epicenter’s `#platform/*` build-time seam across browser and host targets. Use when adding or changing a seam, build condition, typecheck leaf, or deciding whether code belongs behind one.

• Sveltekit

  by @EpicenterHQ

  Apply SvelteKit patterns for routing, server modules, form actions, hooks, cookies, adapters, and invalidation. Use when editing route files, hooks, `app.d.ts`, or SvelteKit behavior.

• Code Audit

  by @EpicenterHQ

  Find recurring Epicenter code smells and scope the cleanup they require. Use for periodic audits, cleanup PRs, post-refactor reviews, or reviews of a primitive’s consumers.

• Github Issues

  by @EpicenterHQ

  GitHub issue comment guidelines for community interaction. Use when: "respond to this issue", "reply to this bug report", "close this issue", or any GitHub discussion.

• Code Prose

  by @EpicenterHQ

  Apply Orwell's rules to the prose inside code — identifiers and comments — without changing behavior. Use when names, word choice, or comments need an editorial pass.

• Technical Articles

  by @EpicenterHQ

  Technical articles and blog posts with honest trade-offs. Use when: "write a blog post", "draft an article", "write about this", creating articles in docs/articles/.

• Documentation

  by @EpicenterHQ

  In-code documentation, folder READMEs, code comments. Use when: "document this", "add JSDoc", "write a README", "explain this code", or writing README.md/JSDoc.

• Arktype

  by @EpicenterHQ

  Arktype: runtime validation, discriminated unions with .merge()/.or(), spread keys. Use when mentioning arktype, type(), union types, command/event schemas.

• Logging

  by @EpicenterHQ

  Use for wellcrafted/logger, logger sinks, library diagnostics, typed logging, background errors, durable host logs, or replacing console.* in library code.

• Typebox

  by @EpicenterHQ

  TypeBox patterns for runtime schema validation and JSON Schema generation. Use when mentioning TypeBox, Standard Schema, or schema-based validation.

• React Mosaic

  by @nomcopter

  Build tiling window manager layouts in React with react-mosaic-component (v7) - resizable, drag-and-drop rearrangeable panels, splits and tab groups. Use when writing or changing code that imports react-mosaic-component, uses…

• Printing Press

  by @mvanhorn

  Set up a new integration, connector, or CLI binding for any API. Wrap or generate a ship-ready Go CLI from an OpenAPI, HAR, or Postman spec via the lean research -> generate -> build -> shipcheck loop. Use when the user says…

• Printing Press Amend

  by @mvanhorn

  Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts…

• Printing Press Score

  by @mvanhorn

  Score a generated CLI against the Steinberger bar, compare two CLIs side-by-side

• Build Iterated Agentic Loop

  by @humanlayer

  build a repo-local skill and install a matching iterated coding-agent GitHub Actions workflow, prompt, memory file, and reference templates

• Visual Pr

  by @humanlayer

  Only use when the user explicitly invokes this skill by name.

• Show Me

  by @humanlayer

  Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.

• Improve Claude Md

  by @humanlayer

  improve a CLAUDE.md file using <important if> blocks to improve instruction adherence

• Team Wiki Codebase

  by @Tencent

  让 AI 真正理解大型代码库。针对多仓库、多微服务、迭代多年的项目，通过架构逆向 + Graph RAG 图谱 + CLI 多语言 AST， 将海量代码压缩为结构化知识库——每条结论可回溯代码行，每条关系有置信度标注。 适用场景：项目有 10+ 仓库或微服务，AI 直接读代码无法全局理解、回答不准确、token 开销大。 产出：组件设计文档 × N + 架构总览 + 桥梁文档 + Graph RAG 图谱(G1~G9) + _manifest.json…

• Teamai Share Learnings

  by @Tencent

  Contribute — 分享 Session 经验到团队知识库

• Three Best Practices

  by @zebbern

  Three.js performance optimization and best practices guidelines. Use when writing, reviewing, or optimizing Three.js code. Triggers on tasks involving 3D scenes, WebGL/WebGPU rendering, geometries, materials, textures, lighting,…

• Test Suite Architect

  by @zebbern

  This skill should be used when establishing comprehensive QA testing processes for any software project. Use when creating test strategies, writing test cases following Google Testing Standards, executing test plans, tracking…

• Test Driven Dev

  by @zebbern

  Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.