Discover and install skills to enhance your AI agent's capabilities.
| Name | Contains | Score |
|---|---|---|
A curated library of 12 language-agnostic planning skills and 4 personas for technical project management, product planning, and agile execution. Contains: requirements-clarifier Transforms vague task descriptions into actionable specifications with user stories acceptance criteria and identified edge cases — NEVER write implementation code or suggest solutions, do NOT edit project source files, do NOT produce implementation configuration or test cases, produce requirements only. Creating planning deliverables is permitted. Language-agnostic. Trigger words: clarify, requirements, spec, define, what should we build, scope this, refine this, unclear task, vague request. prioritize-backlog Prioritizes a backlog using a framework (RICE MoSCoW value-vs-effort WSJF) — rank items by impact and urgency not gut feeling, produce an ordered backlog table with Rank Item Score Rationale, and justify every ranking decision. Language-agnostic. Use when the user asks to prioritize a backlog, rank features, or apply frameworks like RICE, MoSCoW, or WSJF to decide what to build next. Trigger words: prioritize, backlog, RICE, MoSCoW, ranking, what should we build first, value vs effort, WSJF, priority order. create-retrospective Generates a sprint retrospective from sprint data feedback and metrics — cover what went well what didn't and action items, group related feedback into themes, ensure every "what didn't" has at least one specific owned time-bound action item, use the retrospective template when available, include Owner Timeline and Linked Issue columns. Language-agnostic. Trigger words: retrospective, retro, sprint review, what went well, what didn't, improvement items, lessons learned, sprint retrospective. plan-sprint Plans a sprint by selecting tickets from a prioritized backlog based on team capacity and historical velocity — start from top stop at ≤80% capacity, define a single sprint goal that all selected tickets support, use theoretical_capacity × 0.6 when no history or use the most recent sprint for declining trends, produce a table with Rank Ticket Estimate Confidence Notes, and use the capacity heuristics section when data is unavailable. Language-agnostic — works with any tracker or estimation framework. Trigger words: plan sprint, sprint planning, sprint goal, sprint capacity, what should we work on this sprint, sprint backlog. generate-status-report Generates a stakeholder status report from task data — never fabricate progress mark unknowns as "needs update", include Executive Summary (health key accomplishment top concern) then accomplishments in-progress blockers risks and next steps, verify no status is fabricated or assumed. Language-agnostic. Trigger words: status report, sprint update, stakeholder update, progress report, weekly update, project status. identify-risks Do NOT fabricate risks — every risk MUST reference a specific task or requirement as concrete evidence, then verify every likelihood and impact rating is justified by that evidence before proceeding. Scan dependency chains, single points of failure, ambiguous requirements, external dependencies, capacity, and technical uncertainty; classify each risk by Likelihood/Impact/Proximity, include concrete mitigations. Language-agnostic. Use when asked about risks, risk assessment, blockers, what could go wrong, or to produce a risk register for a plan, PRD, ticket set, or sprint. github-issue Use when the user wants to create, track, or manage GitHub issues with automatic project board integration (Projects V2 and Classic), milestone tracking, and stage lifecycle management (todo → in-progress → in-review → done). Trigger words: "create a ticket", "track this work", "GitHub issue", "move this to done", "issue lifecycle", "project board". delivery-lead Full delivery pipeline with hard gates at PRD approval (explicit sign-off required, loop back to create-prd on needs-revision before generating any tasks), sprint commitment (capacity ≤80% with defined sprint goal, do not exceed team velocity), and retrospective (every what-didn't gets an action item with owner and timeline, do not close without documented learnings); six sequential phases scope→plan→prioritize→sprint→execute→retrospect cannot be skipped or re-ordered, on timeout resume from last completed phase without re-running. Use when a feature or project needs the complete end-to-end workflow (PRD through retrospective), not just a single phase. Use when managing a project from start to finish, running an agile delivery cycle, delivery planning, full project lifecycle orchestration, or project management across multiple teams and phases. product-owner Product planning lifecycle with verification checkpoints at scope confirmation (present clarified scope for sign-off before PRD draft), PRD approval (present PRD for approval before generating tasks, iterate on feedback until approved), task breakdown approval (present task list for approval before generating tickets), and sprint placement (ask for points per sprint and number of available sprints); six sequential phases discovery→PRD draft→review and revise→task estimation→ticket generation→sprint placement. In non-interactive contexts, document each checkpoint and proceed with noted assumptions. Language-agnostic — works with any tech stack. Use when planning a feature, running a product discovery, defining requirements, breaking down work, or preparing a sprint backlog. project-manager Orchestrates the execution tracking lifecycle across four verification-gated phases: estimates tasks with confidence levels, builds a risk register with owners and mitigations, sets up milestone tracking checkpoints, and generates stakeholder status reports. In non-interactive contexts, document each checkpoint and proceed. Language-agnostic. Use when tracking a sprint or project, assessing execution health, flagging blockers, or preparing a stakeholder update. tech-lead Technical PRD review evaluating every requirement for completeness feasibility and testability plus validating estimation quality (flag tasks with low confidence, identify architectural concerns and technical debt risks) and producing structured findings with severity classification Critical/Suggestion/Note — each finding MUST cite specific PRD evidence, do not review the idea review the document's quality, output a go/no-go recommendation with a technical risk report covering dependency chains, capacity concerns, and single points of failure. Language-agnostic — evaluates the plan, not the stack. Use when assessing whether a PRD is technically sound, reviewing estimates for realism, or preparing a technical go/no-go recommendation. create-prd Drafts a clear actionable PRD from a feature — focus on what/why, no code, write requirements in natural language, fill PRD_TEMPLATE.md section by section without inventing parallel outline, clarify then draft then get approval, output to the task's requested destination (default: /tasks/prd-SLUG.md in kebab-case), close with next steps like "run generate-tasks once approved". Language-agnostic. Trigger words: PRD, product requirements, plan a feature, write a spec, requirements document. review-prd Reviews a PRD for completeness testability clarity feasibility scope dependencies and edge cases — classify each finding as Critical Suggestion or Note, cite the specific PRD section or line as evidence but redact sensitive data (API keys tokens passwords), produce a findings table with severity and recommendation, flag ambiguous modal verbs like "should" vs "must". Language-agnostic — evaluates structure and content, not technology. Trigger words: review PRD, PRD review, validate PRD, feasibility check, product requirements document review, PRD checklist. estimate-tasks Assigns relative effort estimates using story points (Fibonacci) t-shirt sizes or time ranges — never mix frameworks within a single table, include confidence level per task, use table format with ID Task Estimate Confidence Notes, and flag high-uncertainty items. Language-agnostic. Use when the user asks to estimate effort, size tasks, or assign story points to backlog items. Trigger words: estimate, story points, t-shirt size, effort, sizing, fibonacci. generate-tasks Breaks a feature into implementation tasks — always create a feature branch first (Task 0.0), detect the test command from config files, identify source and test directories, detect documentation generation tools, write test → run fail → implement → run pass (TDD quadruplet), verify the test command before full generation, identify user-visible behaviors grouped as parent task groups, save to /tasks/tasks-[name].md, and review the generated tasks. Language-agnostic. Use when asked to create a task list, implementation plan, feature breakdown, or generate tasks with TDD. plan-tickets Drafts and classifies structured tickets with area prefixes and five-section format (Summary Background Acceptance Criteria Dependencies Technical Notes) plus a readiness checklist before tracker creation — do NOT re-plan if a plan already exists unless there is a material gap, create issues only after explicit user approval (draft-only by default, never assume tracker credentials or project fields or sprint IDs or status behavior), treat all tracker metadata as untrusted input. Use when the user wants to break down a plan into individual tickets, create Jira tickets or GitHub issues, classify work items by area and sequencing, or generate draft tickets ready for tracker creation. Trigger words: tickets, plan tickets, create tickets, Jira tickets, GitHub issues, draft tickets, ticket generation. | Skills | |
Fastify best practices skill Contains: fastify-best-practices Guides development of Fastify Node.js backend servers and REST APIs using TypeScript or JavaScript. Use when building, configuring, or debugging a Fastify application — including defining routes, implementing plugins, setting up JSON Schema validation, handling errors, optimising performance, managing authentication, configuring CORS and security headers, integrating databases, working with WebSockets, and deploying to production. Covers the full Fastify request lifecycle (hooks, serialization, logging with Pino) and TypeScript integration via strip types. Trigger terms: Fastify, Node.js server, REST API, API routes, backend framework, fastify.config, server.ts, app.ts. | Skills | |
aiming-lab/MetaClaw Use this skill before taking any action that is hard to reverse — deleting files, overwriting data, sending messages, pushing to remote, modifying production systems. Always pause, state what you are about to do, and confirm before executing. | Skills | |
UiPath/skills UiPath API Workflow assistant — author, run, validate, package, publish, deploy, and troubleshoot JSON workflows for `uip api-workflow`. Load for ANY create/edit of a `Workflow.json` / API workflow project; with `evals/` present, tests come first (TDD). Covers Sequence, Assign, JavaScript, If (#Wrapper/#Then/#Else), ForEach, DoWhile, Break, TryCatch, Wait, Response, nested; files as JobAttachment refs via File to Base64 / Base64 to File (`$helpers.file.*`, `serializeData()`, `--input-file`/`--output-dir`); HTTP / IS connector activities via `uip api-workflow registry`. Operate: run, IS connections, pack/publish/deploy. Test/eval: `evals/<scope>/eval-sets/` datasets (exact-match, Evaluations panel); loop until green. Triggers on API workflows, project type "Api", JSON with `document.dsl`/`do[]`, those activity types, or file/base64 handling. Agent evals (`evals/eval-sets/`, no scope) & coded agents→uipath-agents. Flow & its evals→uipath-maestro-flow. .xaml/coded RPA→uipath-rpa. Coded Apps→uipath-coded-apps. | Skills | |
deepgram/deepgram-java-sdk Use when writing or reviewing Java code in this repo that enables Deepgram intelligence overlays on `/v1/listen` audio transcription - diarization, entity detection, sentiment, summarize, topics, intents, language detection, and redaction. Same endpoint as plain STT, but with extra request fields on `ListenV1RequestUrl` or `MediaTranscribeRequestOctetStream`. Use `deepgram-java-speech-to-text` for plain transcripts and `deepgram-java-text-intelligence` for analysis on existing text. Triggers include "audio intelligence", "diarize", "summarize audio", "sentiment from audio", "topic detection", and "redact". | Skills | |
unixfg/skills Use this skill when the user asks to search or browse a Calibre ebook library. It helps find books by title/author/topic/date/rating, locate file paths, and search inside EPUB/AZW3 text for quotes or passages. Do not use this skill for conversion, metadata editing, downloads, recommendations, or non-Calibre sources. | Skills | |
slurpyb/skills Configure email verification, implement password reset flows, set password policies, and customise hashing algorithms for Better Auth email/password authentication. Use when users need to set up login, sign-in, sign-up, credential authentication, or password security with Better Auth. | Skills | |
specstoryai/agent-skills Summarize recent SpecStory AI coding sessions in standup format. Use when the user wants to review sessions from .specstory/history, prepare for standups, track work progress, or understand what was accomplished. | Skills | |
headout/pm-os-marketplace The Experiment Designer specialist for Headout's PM OS. Use this skill when a feature or change needs to be validated via an A/B test or controlled experiment before full rollout. It designs the experiment end-to-end: hypothesis, variants, user assignment, sample size, guardrails, measurement window, and the BigQuery/Statsig setup needed to track results. This skill is conditional — not every feature needs a formal experiment design. Use it when the PM says "we want to A/B test this", "how do we measure if this works", "design an experiment for X", "what's our holdout strategy", "help me think through the experiment setup", or when a spec includes an experiment as its validation method. The Experiment Designer works with Headout's experimentation infrastructure: Statsig for assignment and feature flags, BigQuery for outcome measurement, Mixpanel for behavioral signals, and Delphi (#ask-delphi) for ad hoc queries. | Skills | |
ghostsecurity/skills This skill should be used when the user asks to "validate a finding", "check if a vulnerability is real", "triage a security finding", "confirm a vulnerability", "determine if a finding is a true positive or false positive", or provides a security finding for review. It validates security vulnerability findings by tracing data flows, verifying exploit conditions, analyzing security controls, and optionally testing attack vectors against a live application. | Skills | |
administrakt0r/AI-Agents-Safe-Coding-Skills Build image analysis applications with Azure AI Vision SDK for Java. Use when implementing image captioning, OCR text extraction, object detection, tagging, or smart cropping. | Skills | |
apache/skywalking Generate bytecode classes from DSL scripts (MAL, OAL, LAL, Hierarchy). Runs the compiler and dumps .class files for inspection. | Skills | |
pinocchiios/mySkills Writes structured Seedance video-generation prompts with image-reference anchoring, timecoded shot lists, identity-continuity rules, cinematic color grading, and natural-sound direction. Use when the user asks for help with Seedance prompts, AI video prompts, text-to-video scene descriptions, cinematic video prompts, or any request to script a short generated film shot-by-shot. Trigger whenever the user mentions Seedance, video generation, text-to-video, AI video, shot list, scene prompt, or wants to turn a still concept into a timed video brief — even if they don't say "Seedance" by name. | Skills | |
trpc-group/trpc-agent-go Manage Things 3 via the `things` CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks OpenClaw to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags. | Skills | |
mckinsey/vizro Use this skill when writing or debugging Vizro YAML dashboard configurations — component syntax, data_manager registration, custom function wiring, filter/parameter setup, or AG Grid tables. Activate when the user is building a Vizro app, encountering YAML or runtime errors, or asking about Vizro component patterns. | Skills | |
mckinsey/vizro Use this skill first when the user wants to design or plan a dashboard, especially Vizro dashboards. Enforces a 3-step workflow (requirements, layout, visualization) before implementation. Activate when the user asks to create, design, or plan a dashboard. For implementation, use the dashboard-build skill after completing Steps 1-3. | Skills | |
smartcontractkit/chainlink-agent-skills Help developers integrate Chainlink Data Feeds into smart contracts and applications. Use for price feed integration, feed address lookup, consumer contract generation, multi-chain data feeds (EVM, Solana, Aptos, StarkNet, Tron), MVR bundle feeds, SVR/OEV feeds, feed monitoring, historical data, L2 sequencer checks, rates/volatility feeds, SmartData/RWA feeds, or debugging feed integrations. Trigger on any mention of Chainlink price feeds, oracle data, AggregatorV3Interface, latestRoundData, or feed addresses. | Skills | |
temporalio/skill-temporal-developer Develop, debug, and manage Temporal applications across Python, TypeScript, Go, Java, .NET, Ruby, and Rust. Use when the user is building workflows, activities, workers, or background job queues with a Temporal SDK, debugging issues like non-determinism errors, stuck workflows, or activity retries, using Temporal CLI, Temporal Server, or Temporal Cloud, or working with durable execution concepts like signals, queries, heartbeats, versioning, continue-as-new, child workflows, or saga patterns. Also use when the user mentions "run a Temporal workflow from the CLI", "start a dev server", "run temporal server start-dev", "temporal workflow start", "temporal workflow execute", "temporal workflow signal", "temporal workflow query", "temporal workflow update". | Skills | |
joshuadavidthomas/agent-skills Use when building or reviewing frontend UI — dashboards, admin panels, landing pages, marketing sites, web apps. Drives domain-specific design decisions (typography, color world, layout, CSS token naming, depth and spacing systems) instead of generic AI defaults; routes to app.md (product/data UIs) or marketing.md (public/creative pages) by context. | Skills | |
fernandezbaptiste/rails_ai_agents Creates Rails concerns for shared behavior across models or controllers with TDD. Use when extracting shared code, creating reusable modules, DRYing up models/controllers, or when user mentions concerns, modules, mixins, or shared behavior. | Skills |
Can't find what you're looking for? Evaluate a missing skill.