Skills
98,639 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Publish an ASC CLI plugin to the tddworks/asc-registry marketplace. Use this skill when: (1) User says "release plugin", "publish plugin", "upload plugin to registry" (2) User wants to make their plugin available via `asc plugins market list` (3) User built a .plugin bundle and wants to share it (4) User asks to update an existing plugin version in the registry Triggers on any mention of publishing, releasing, or submitting plugins to the asc-registry.
Generate or update Laravel plugin REST APIs in AureusERP for any module. Use when implementing new API resources or refactoring existing endpoints to match shared project conventions for routes, controllers, requests, resources, policies, Spatie QueryBuilder filtering/includes/sorting, soft-delete restore/force endpoints, and Scribe attributes/documentation.
Reports a bug or files feedback about the azuresql-db-* agent skills themselves, or about the Azure SQL Database container (Private Preview). Use when the user says a skill or the container "did not work", hit an error, behaved unexpectedly, or is missing something; and when they say "report a bug", "file an issue", "open a GitHub issue", "request a feature", "give feedback", or "tell the team". Also use when you, the agent, had to deviate from an azuresql-db-* skill or work around a defect in one to finish a task: that is a bug worth reporting even if the task succeeded. Decides whether the problem belongs to the SKILL or to the CONTAINER, since they use different issue templates, then builds a complete prefilled GitHub issue from context you already have. Never submits anything without explicit confirmation from the user.
Scandit Barcode Capture (`BarcodeCapture`) in web/browser (TypeScript/JavaScript) projects — the low-level, full-control single-barcode scanning mode (BarcodeCapture + DataCaptureView + overlay), without the pre-built SparkScan UI; not the Cordova or Capacitor hybrid plugins. Use for integration, scan settings, result handling, overlay and viewfinder customization, Scandit Web SDK version migration (v6→v7→v8), or troubleshooting.
Visible browser automation using Playwright MCP, CLI, and CDP without interrupting the user's foreground work. Use for navigation, forms, screenshots, durable file downloads, repeatable browser workflows, existing-session reuse, or troubleshooting CDP / iframe / modal / file chooser / passkey (WebAuthn) issues.
Build professional command-line interfaces in Python, Go, and Rust using modern frameworks like Typer, Cobra, and clap. Use when creating developer tools, automation scripts, or infrastructure management CLIs with robust argument parsing, interactive features, and multi-platform distribution.
This skill should be used when the user's request or requirement is ambiguous and needs iterative questioning to become actionable. Trigger on "clarify requirements", "refine requirements", "요구사항 명확히", "요구사항 정리", "뭘 원하는 건지", "make this clearer", "spec this out", "scope this", "/clarify". Turns vague inputs into concrete specs. For strategy blind spots use unknown; for content-vs-form reframing use metamedium.
Guides PHP project upgrades using Composer commands. Use when helping users upgrade PHP packages, check for security vulnerabilities with `composer audit`, prioritize which packages to upgrade first, understand dependency conflicts, interpret `composer outdated` output, use `composer why-not` to diagnose version constraints, use `composer why` to trace dependencies, use `composer bump` to harden version constraints after upgrading, plan safe upgrade paths, resolve package version conflicts in composer.json, or resolve merge conflicts in composer.lock. Trigger this skill whenever the user mentions composer packages, PHP dependencies, outdated packages, CVEs in PHP projects, or security advisories.
Integrate the Cartridge Controller wallet into Starknet applications. Use when setting up Controller for the first time, installing packages, configuring chains/RPC endpoints, or troubleshooting basic integration issues. Covers installation, Controller instantiation, choosing between ControllerConnector and SessionConnector, chain configuration, and package compatibility.
When organizing project structure, establishing patterns, or reducing configuration overhead. Use when the user says "how should I organize this," "what's the convention," "too much config," "project structure," "naming pattern," or "standardize this." For code-level structure, see separation-of-concerns.
Parallel/distributed computing for larger-than-RAM data. Components: DataFrames (parallel pandas), Arrays (parallel NumPy), Bags, Futures, Schedulers. Scales laptop to HPC cluster. For single-machine speed use polars; for out-of-core without cluster use vaex.
Expert guidance on building Swift database client libraries. Use when developers mention: (1) building a database driver, (2) wire protocol implementation, (3) connection pooling design, (4) state machines for protocol handling, (5) NIO channel handlers for databases, (6) backpressure in result streaming, (7) actor executor alignment with NIO.
DBOS Java SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing Java or Kotlin code with DBOS, creating workflows and steps, using queues, integrating DBOS with Spring Boot, using DBOSClient from external applications, or building JVM applications that need to be resilient to failures.
Generates structured technical documentation including API docs (OpenAPI/Swagger), README files, user guides, developer guides, and changelogs. Use when the user needs to create or improve project documentation, generate API reference docs, write onboarding guides, or structure documentation for a codebase.
Primary router skill for broad .NET work. Classify the repo by app model and cross-cutting concern first, then switch to the narrowest matching .NET skill instead of staying at a generic layer. USE FOR: general .NET requests without a narrower framework; C# implementation, debugging, review, or refactoring; routing to framework and tooling skills. DO NOT USE FOR: unrelated stacks; tasks already covered by a narrower .NET skill. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
CodeStable is an AI coding workflow for serious software engineering that keeps humans in the loop. Rather than centering on Agent orchestration, it organizes requirements, architecture, features, issues, and historical decisions to make development driven by Codex and Claude controllable, traceable, and continuously evolvable.
Workbench agent panel system — ef-edit CustomEvent pipeline, registry roll-up, selector grouping, and element property schema. Use when adding new GUI edit capture points, expanding the inspector schema, or continuing development of the EFAgentPanel feature.
Raw reference for ESPN's undocumented public JSON endpoints, for a sport, league, or operation that no dedicated sports-skills skill covers, or when a developer explicitly asks to work with raw ESPN endpoints. Prompt-only: endpoint catalog, documented league slugs, observed response shapes, pitfalls, and stdlib fetch helpers. Output is provider-native ESPN JSON, not normalized or canonical data. Use when: the requested league or operation is genuinely not covered by a dedicated skill (e.g. MMA, lacrosse, rugby, Australian football, NCAA volleyball, field hockey, water polo, IndyCar/NASCAR), or the user explicitly asks to write, debug, or inspect code against ESPN endpoints. Don't use when: a dedicated skill covers the league and job — nba-data, wnba-data, nfl-data, nhl-data, mlb-data, cfb-data (NCAA football), cbb-data (NCAA men's basketball), football-data (its listed soccer leagues), tennis-data (ATP/WTA), golf-data (PGA/LPGA/DP World), cricket-data, fastf1 (Formula 1); sports-news or sports-reporter for news and articles; betting, markets, kalshi, or polymarket for odds and prediction markets. volleyball-data covers Dutch Nevobo volleyball only, not NCAA. A dedicated skill's error, timeout, or empty result is not permission to switch to raw ESPN automatically — report it and ask first
Manage DAG execution lifecycles including start, stop, pause, resume, and cleanup. Activate on 'execution lifecycle', 'stop execution', 'abort DAG', 'graceful shutdown', 'kill process'. NOT for cost estimation, DAG building, or skill selection.
Codebase intelligence for TypeScript and JavaScript. Static analysis reports changed-code risk, cleanup opportunities, duplication, circular dependencies, complexity hotspots, architecture boundaries, design-system drift, feature flags, and opt-in security candidates. Optional local similar-code discovery finds functions that may implement the same intent despite different syntax. Runtime coverage can merge production execution data. Use when asked to audit PR risk, find unused code or dependencies, compare semantically similar functions, detect duplicates, inspect architecture boundaries, merge runtime coverage, auto-fix supported issues, or run fallow.
Opt-in writer (the /claude-db:fix command). Applies the safe, reversible schema/migration changes from an audit — adding indexes, NOT NULL/CHECK/UNIQUE constraints, missing FKs, type corrections, default/generated columns — as expand-contract migrations. Dry-run preview by default; writes only after explicit per-change confirmation, and only via the migration-writer subagent. Runs only when the user invokes it — never auto-triggered.
Analyzes an initial business requirements document for gaps, ambiguities, and missing information. Generates gap-analysis-worksheet.md with structured requirement/question/answer blocks grouped by category — designed to be completed by a business analyst before formal requirements gathering begins.
Visual and front-end development assistant powered by Google Gemini's multimodal models. Use for UI analysis, design comparison, accessibility audits, color palette extraction, screenshot-to-code conversion, generating UI assets, and text-based design assistance from briefs.
Create high-quality git commits: review/stage the intended changes, split them into logical commits, and write clear commit messages (following the Conventional Commits spec, with Emoji support). Use this skill when the user asks to commit code, write commit messages, stage changes, or split work into multiple commits. When the user mentions the 【breaking change】 keyword, you must write the commit message using the exclamation mark format per this skill's BREAKING CHANGE spec. Prefer committing the files in the git staging area (staged); only consider the entire working tree when the staging area is empty. When the user mentions the 【categorize】 keyword, you must carefully split multiple commits along this skill's multi-commit split spec, across the four dimensions of file type, business module, change type, and change scope.
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.