Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 19501–19530 of 21404 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| prd-v09-launch-channels-orbmattgierhart/PRD-driven-context-engineeringAllocate launch channels using the Owned / Rented / Borrowed (ORB) framework during PRD v0.9 Go-to-Market. Triggers on requests to pick launch channels, distribute the offer, build a channel portfolio, or when user asks "where do we launch?", "what channels?", "ORB", "owned vs rented vs borrowed", "channel allocation", "channel mix", "Corey Haines launch". Outputs GTM-* entries with Type=Channel, a channel-mix matrix, and a launch sequence. | Stars: 179 | Updated | Claude CodeCodex | Unverified | Install |
| prd-v09-launch-metricsmattgierhart/PRD-driven-context-engineeringDefine success criteria and tracking setup for launch during PRD v0.9 Go-to-Market. Triggers on requests to define launch metrics, set up tracking, or when user asks "how do we measure launch success?", "launch KPIs", "tracking setup", "success criteria", "analytics", "launch goals". Outputs KPI- entries specialized for launch measurement. | Stars: 179 | Updated | Claude CodeCodex | Unverified | Install |
| prd-v09-offer-construction-hormozimattgierhart/PRD-driven-context-engineeringConstruct a high-conversion offer using Alex Hormozi's value equation and Grand Slam Offer mechanics during PRD v0.9 Go-to-Market. Triggers on requests to design the offer, set up the pitch, build bonuses or guarantees, or when user asks "how do we package this?", "what's the offer?", "build a grand slam offer", "Hormozi", "$100M offers", "guarantee", "bonus stack". Outputs GTM-* entries with Type=Offer / Type=Guarantee and BR-PRICING-* updates. | Stars: 179 | Updated | Claude CodeCodex | Unverified | Install |
| prd-v09-positioning-dunfordmattgierhart/PRD-driven-context-engineeringDefine product positioning using April Dunford's 5-step framework during PRD v0.9 Go-to-Market. Triggers on requests to position the product, define category, frame against competitors, or when user asks "what category are we?", "how do we position?", "Dunford positioning", "obviously awesome", "market frame of reference", "positioning statement". Outputs GTM-* entries with Type=Positioning and BR-POS-* positioning rules. | Stars: 179 | Updated | Claude CodeCodex | Unverified | Install |
| prd-v10-case-study-buildermattgierhart/PRD-driven-context-engineeringBuild customer case studies as marketing and chasm-crossing reference assets during PRD v1.0 Market Adoption. Triggers on requests to build case studies, produce customer stories, create reference content, or when user asks "build a case study", "customer story", "reference account", "case study interview", "before/after story", "social proof page", "logo wall". Outputs CFD-CASE-* evidence entries, GTM-CASE-* marketing assets, and updates ADO-REF-* with story status. | Stars: 179 | Updated | Claude CodeCodex | Unverified | Install |
| prd-v10-continuous-discovery-torresmattgierhart/PRD-driven-context-engineeringEstablish weekly customer-discovery cadence and Opportunity Solution Tree practice using Teresa Torres's Continuous Discovery Habits framework during PRD v1.0 Market Adoption. Triggers on requests to set up discovery cadence, build opportunity solution tree, run weekly customer interviews, or when user asks "Torres", "continuous discovery", "opportunity solution tree", "outcomes vs outputs", "weekly interviews", "assumption mapping". Outputs CFD-* discovery entries and updates to ADO-STAGE-* and PER-* with new evidence. | Stars: 179 | Updated | Claude CodeCodex | Unverified | Install |
| prd-v10-mom-test-interviewmattgierhart/PRD-driven-context-engineeringApply Rob Fitzpatrick's Mom Test discipline to customer interviews during PRD v1.0 Market Adoption. Triggers on requests to interview customers, run discovery calls, validate ideas with users, or when user asks "how do I interview customers?", "Mom Test", "Rob Fitzpatrick", "customer interview", "user research without lies", "talking to humans", "discovery conversation". Outputs CFD-* discovery entries with Mom Test-calibrated confidence. | Stars: 179 | Updated | Claude CodeCodex | Unverified | Install |
| prd-v10-testimonial-collectormattgierhart/PRD-driven-context-engineeringSystematically harvest short testimonials from customers via NPS, milestones, post-purchase, and email during PRD v1.0 Market Adoption. Triggers on requests to collect testimonials, set up social proof harvest, gather customer quotes, or when user asks "how do we get testimonials?", "social proof harvest", "NPS responses", "testimonial wall", "customer quotes", "post-purchase survey", "milestone follow-up". Outputs CFD-TST-* testimonial entries and GTM-TST-* placement assets. | Stars: 179 | Updated | Claude CodeCodex | Unverified | Install |
| deepagents-architectureexistential-birds/beagleGuides architectural decisions for Deep Agents applications. Use when deciding between Deep Agents vs alternatives, choosing backend strategies, designing subagent systems, or selecting middleware approaches. | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |
| deepagents-code-reviewexistential-birds/beagleReviews Deep Agents code for bugs, anti-patterns, and improvements. Use when reviewing code that uses create_deep_agent, backends, subagents, middleware, or human-in-the-loop patterns. Catches common configuration and usage mistakes. | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |
| deepagents-implementationexistential-birds/beagleImplements agents using Deep Agents. Use when building agents with create_deep_agent, configuring backends, defining subagents, adding middleware, or setting up human-in-the-loop workflows. | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |
| langgraph-architectureexistential-birds/beagleGuides architectural decisions for LangGraph applications. Use when deciding between LangGraph vs alternatives, choosing state management strategies, designing multi-agent systems, or selecting persistence and streaming approaches. | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |
| langgraph-code-reviewexistential-birds/beagleReviews LangGraph code for bugs, anti-patterns, and improvements. Use when reviewing code that uses StateGraph, nodes, edges, checkpointing, or other LangGraph features. Catches common mistakes in state management, graph structure, and async patterns. | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |
| langgraph-implementationexistential-birds/beagleImplements stateful agent graphs using LangGraph. Use when building graphs, adding nodes/edges, defining state schemas, implementing checkpointing, handling interrupts, or creating multi-agent systems with LangGraph. | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |
| pydantic-ai-agent-creationexistential-birds/beagleCreate PydanticAI agents with type-safe dependencies, structured outputs, and proper configuration. Use when building AI agents, creating chat systems, or integrating LLMs with Pydantic validation. | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |
| pydantic-ai-common-pitfallsexistential-birds/beagleAvoid common mistakes and debug issues in PydanticAI agents. Use when encountering errors, unexpected behavior, or when reviewing agent implementations. | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |
| pydantic-ai-dependency-injectionexistential-birds/beagleImplement dependency injection in PydanticAI agents using RunContext and deps_type. Use when agents need database connections, API clients, user context, or any external resources. | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |
| pydantic-ai-model-integrationexistential-birds/beagleConfigure LLM providers, use fallback models, handle streaming, and manage model settings in PydanticAI. Use when selecting models, implementing resilience, or optimizing API calls. | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |
| pydantic-ai-testingexistential-birds/beagleTest PydanticAI agents using TestModel, FunctionModel, VCR cassettes, and inline snapshots. Use when writing unit tests, mocking LLM responses, or recording API interactions. | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |
| pydantic-ai-tool-systemexistential-birds/beagleRegister and implement PydanticAI tools with proper context handling, type annotations, and docstrings. Use when adding tool capabilities to agents, implementing function calling, or creating agent actions. | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |
| vercel-ai-sdkexistential-birds/beagleVercel AI SDK for building chat interfaces with streaming. Use when implementing useChat hook, handling tool calls, streaming responses, or building chat UI. Triggers on useChat, @ai-sdk/react, UIMessage, ChatStatus, streamText, toUIMessageStreamResponse, addToolOutput, onToolCall, sendMessage. | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |
| adr-decision-extractionexistential-birds/beagleUse when you need to mine a conversation, session transcript, or design discussion for architectural decisions before writing ADRs. Identifies problem-solution pairs, trade-off debates, technology choices, and explicit "[ADR]" tags. Triggers on "what decisions did we make", "extract decisions from this chat", "find the choices in our discussion", or "summarize architectural decisions". Also useful after long planning sessions to capture decisions that were made implicitly. Does NOT write ADR documents — use adr-writing or write-adr for that. | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |
| adr-writingexistential-birds/beagleUse when writing or formatting an ADR document using the MADR template, applying Definition of Done (E.C.A.D.R.) criteria, or verifying ADR completeness. Triggers on "write the ADR", "format as MADR", "check ADR quality", "mark gaps in ADR". Also triggers when a decision has been extracted and needs to become a document. Does NOT extract decisions from conversations (use adr-decision-extraction) or orchestrate the full extract-confirm-write workflow (use write-adr). | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |
| agent-architecture-analysisexistential-birds/beagleUse when auditing an agent codebase against the 12-Factor Agents methodology, reviewing LLM-powered system architecture, or assessing agentic app compliance. Triggers on "analyze agent architecture", "12-factor audit", "how compliant is this agent", or "evaluate this LLM app". Also applies when comparing frameworks or planning agent improvements. Not for quick checklists — this performs deep per-factor codebase analysis with file-level evidence. | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |
| artifact-analysisexistential-birds/beagleUse when the user wants a cited, structured read of local documents and project knowledge. Triggers on: "analyze these docs", "scan my project for context", "read the docs folder", "summarize what's in .beagle/concepts/", "extract context from docs/", "what's in this folder", "go read everything in X and tell me what's there". Also invoked programmatically by other beagle skills (prfaq-beagle Ignition, brainstorm-beagle reference points, strategy-interview context grounding) via the companion contract. Does NOT trigger on codebase lookups ("find this function", "search the repo"), web research (use web-research), LLM-as-judge evaluation (use llm-judge), or document editing (use humanize-beagle). Produces a written scan plan, parallel-subagent findings, and a cited synthesis report on disk — never inline prose, never unsourced claims. | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |
| brainstorm-beagleexistential-birds/beagleUse when the user has a fuzzy idea and wants to shape it into a concrete project spec before planning or building. Triggers on: "brainstorm this", "I have an idea for...", "help me think through this project", "what should I build", "spec this out". Also catches vague feature descriptions needing structured questioning to clarify scope. Does NOT write code, plan implementation, review strategy docs, or run strategy interviews — produces a WHAT/WHY spec through dialogue, not a HOW plan. | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |
| llm-judgeexistential-birds/beagleUse when comparing two or more code implementations against a spec or requirements doc. Triggers on "which repo is better", "compare these implementations", "evaluate both solutions", "rank these codebases", or "judge which approach wins". Also covers choosing between competing PRs or vendor submissions solving the same problem. Does NOT review a single codebase for quality — use code review skills instead. Does NOT evaluate strategy docs — use strategy-review. Requires a spec file and 2+ repo paths. | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |
| prfaq-beagleexistential-birds/beagleUse when the user wants to pressure-test a product, internal-tool, or OSS concept against Amazon's Working Backwards PRFAQ gauntlet before committing to a spec. Triggers on: "work backwards", "write a PRFAQ", "press release first", "is this idea worth building", "pressure-test this concept", "filter this before brainstorm", "is this a real product". Also catches solution-first pitches ("I want to build X that does Y") and technology-first pitches ("use AI to...") that need customer-first filtering. Produces a binary pass/fail verdict, not a polished doc. Hardcore coaching — direct, skeptical, concrete. On pass, hands off to brainstorm-beagle with a concept brief. Does NOT write code, plan implementation, scaffold projects, or draft specs. | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |
| quick-planexistential-birds/beagleUse when you need a bite-sized, TDD-driven implementation plan but do NOT have a brainstorm-beagle spec to plan against. quick-plan reconstructs intent from the current conversation, fans out domain-expert exploration subagents across the codebase, and synthesizes the same plan format write-plan produces — without requiring `.beagle/concepts/<slug>/spec.md`. Triggers on: "quick plan", "plan this out", "plan what we just discussed", "turn this into an implementation plan", "plan this without a spec", "I don't have a spec, just plan it", "write-plan but no spec". Make sure to use this skill whenever the user wants an implementation or TDD plan and there is no spec to plan against — even if they just say "plan it" after discussing a feature. Writes to `.beagle/plans/<slug>/plan.md`. If a finalized spec already exists at `.beagle/concepts/<slug>/spec.md`, prefer write-plan. Does NOT brainstorm specs, write code, or execute the plan — produces the plan document (and an optional handoff prompt) only. | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |
| resolve-beagleexistential-birds/beagleUse as the follow-up to brainstorm-beagle when a spec has an Open Questions section (or quietly carries latent gaps) that need closing before planning or implementation can begin. Triggers on: "resolve the open questions", "close the gaps in this spec", "research the open items", "finalize my spec", "make this spec implementation-ready", "answer the TBDs". Also triggers whenever the user points at a brainstorm-beagle spec and asks for research, proposals, or answers to unresolved items. Orchestrates parallel research subagents when available (falls back to inline sequential research otherwise), proposes answers one at a time for user approval, then rewrites the spec in place so it arrives at planning with no known gaps. Does NOT write code, design implementation, or create plans — it only produces a complete spec. | Stars: 88 | Updated | Claude CodeCodex | Unverified | Install |