agentsclimarketplace

Plan & spec

10,724 rows, by stacks then stars

2,010 of these skill files have been read, by 1,360 distinct authors, and what they tell an agent counted. What Plan & spec authors agree on, and what they forbid

  • Spec

    mike-diff/ai-coding-configs/plugins/agent-team/skills/spec Skill

    no license1★ repo

    Generate a complete feature specification with user stories, requirements, and self-contained implementation phases. Use when you know what to build.

  • Test automation strategy

    almasumdev/awesome-mobile-testing-agent-skills/.github/skills/automation/test-automation-strategy Skill

    no license1★ repo

    Expert guidance on scoping test automation investments, assigning ownership, choosing quality metrics, and keeping a mobile test suite economically viable. Use when asked "what should our test strategy be?" or when the test suite is becoming a cost center.

  • E2e testing strategy

    almasumdev/awesome-mobile-testing-agent-skills/.github/skills/e2e/e2e-testing-strategy Skill

    no license1★ repo

    Decide when end-to-end tests pay off, how to budget flake, and how to split smoke vs full regression suites. Use when asked "should we add an E2E test for this?" or when an E2E suite has grown too slow or too flaky to trust.

  • Ansoff matrix

    jacob-balslev/skill-graph/marketplace/skills/ansoff-matrix Skill

    no license1★ repo

    Use when choosing or reviewing growth strategy options with the Ansoff product-market matrix: market penetration, market development, product development, diversification, existing vs new products, existing vs new markets, strategic distance, risk, assumptions, and sequencing. Covers growth-option framing, quadrant classification, evidence needs, option comparison, and handoff to deeper validation methods. Do NOT use for internal/external factor inventory (use swot-tows), macro-environment scanning (use pestel), industry profit-pressure diagnosis (use porters-five-forces), integrated strategy cascades (use playing-to-win), durable moat classification (use seven-powers), or quantified option valuation (use expected-value). Do NOT use for Allocate our R&D budget across existing business units based on market growth rate and relative market share. Do NOT use for Turn strengths, weaknesses, opportunities, and threats into SO, WO, ST, and WT options.

  • Balanced scorecard

    jacob-balslev/skill-graph/marketplace/skills/balanced-scorecard Skill

    no license1★ repo

    Use when building, reviewing, or applying a Balanced Scorecard for strategy execution and performance management: destination statement, strategy map, perspectives, strategic objectives, strategic readiness, measures/KPIs, targets, initiatives, owners, review cadence, cascading, and learning from performance gaps. Covers financial/stewardship, customer/stakeholder, internal process, and learning/growth or organizational-capacity perspectives, with sustainability/ESG embedded or added as a fifth perspective when strategic, and adaptation for business, nonprofit, public-sector, product, and transformation contexts. Do NOT use for upstream strategy formulation alone (use playing-to-win), quarterly goal-setting alone (use okrs), technical service thresholds (use performance-budgets), portfolio allocation (use bcg-matrix), generic internal/external factor inventory (use swot-tows), probability-weighted option valuation (use expected-value), or activity-level value/cost decomposition (use value-chain-analysis).

  • Bayesian reasoning

    jacob-balslev/skill-graph/marketplace/skills/bayesian-reasoning Skill

    no license1★ repo

    Use when updating beliefs, forecasts, diagnoses, or decision assumptions under uncertainty using Bayesian reasoning: priors/base rates, likelihood, evidence strength, posterior direction, and residual uncertainty. Covers base-rate discipline, likelihood-vs-posterior separation, independent evidence updates, natural-frequency examples, confidence calibration, and when to stop at qualitative probability instead of fake precision. Do NOT use for expected monetary value calculations, strategy-cascade choices (use playing-to-win), industry-structure analysis (use porters-five-forces), or generic task prioritization (use prioritization). Do NOT use for calculate the expected value of these three options. Do NOT use for turn this growth plan into a strategy cascade. Do NOT use for analyze supplier power and substitutes in this industry. Do NOT use for rank these roadmap items by impact and effort. Do NOT use for build a statistical model from a dataset.

  • Blue ocean strategy

    jacob-balslev/skill-graph/marketplace/skills/blue-ocean-strategy Skill

    no license1★ repo

    Use when creating, auditing, or pressure-testing a Blue Ocean Strategy: value innovation, strategy canvas, Four Actions Framework, ERRC grid, six paths, buyer utility, noncustomers, and commercial viability. Covers reconstructing market boundaries, breaking the value-cost trade-off, shifting from competitor benchmarking to alternative/noncustomer insight, and turning the result into a new value curve. Do NOT use for industry-structure diagnosis alone (use porters-five-forces), durable moat classification (use seven-powers), or integrated five-choice strategy cascades (use playing-to-win). Do NOT use for analyze supplier power, buyer power, entrants, substitutes, and rivalry in this industry. Do NOT use for classify which durable moat this company has using Seven Powers. Do NOT use for turn this company strategy into aspiration, where to play, how to win, capabilities, and systems. Do NOT use for rank these roadmap initiatives by impact and effort.

  • Database migration

    jacob-balslev/skill-graph/marketplace/skills/database-migration Skill

    no license1★ repo

    Use when planning or applying a raw-SQL database migration to a live PostgreSQL database — adding columns, renaming columns or tables, changing types, creating indexes, adding foreign keys, or running data backfills. Covers zero-downtime patterns (expand / contract, batched backfill, NOT VALID foreign keys, CONCURRENTLY indexes), the direct/unpooled connection requirement for migration tooling, branched-database workflows, and rollback strategy. Do NOT use for ORM-managed migrations driven by Prisma/Drizzle/TypeORM CLI scaffolding, for chasing a migration that has already failed in production (use debugging), for multi-release schema lifecycle planning outside one migration (use schema-evolution), or for designing the row-level-security model itself (use owasp-security). Do NOT use for design the row-level-security model for our new tenant table. Do NOT use for the migration crashed in production — find the root cause. Do NOT use for plan the full multi-release schema evolution for this domain.

  • Debugging

    jacob-balslev/skill-graph/marketplace/skills/debugging Skill

    no license1★ repo

    Use when behavior is broken, a test is failing, or runtime output contradicts expectations. Covers failure reproduction, scope reduction by bisection, evidence capture at the moment of failure, root-cause isolation (not symptom patching), fix verification against the same evidence path, and regression-test creation. Do NOT use for feature planning, architectural design, or behavior-preserving refactor. Do NOT use for plan test coverage for a new feature. Do NOT use for document what this function does for future readers. Do NOT use for refactor this messy code while the test suite is green.

  • Indexing strategy

    jacob-balslev/skill-graph/marketplace/skills/indexing-strategy Skill

    no license1★ repo

    Use when designing or auditing the maintained index set for a database workload: choosing index structures, matching access patterns, setting composite order, balancing read speed against write/storage cost, and deciding when to add, keep, or drop indexes. Do NOT use for tuning one slow query (use query-optimization), applying production DDL (use database-migration), isolation choices, schema design, or sharding. Do NOT use for choose a database schema (use entity-relationship-modeling). Do NOT use for decide how to partition data across nodes (use sharding-strategy).

  • Inversion

    jacob-balslev/skill-graph/marketplace/skills/inversion Skill

    no license1★ repo

    Use when a goal, plan, design, strategy, or assumption should be examined by reversing it: ask how to guarantee failure, how the opposite could be true, or what would have to happen for the desired outcome not to occur. Covers objective reversal, failure-path enumeration, obstacle-first planning, opposite-hypothesis testing, and prevention design. Do NOT use for decomposing a problem to irreducible premises (use first-principles-thinking), post-failure root-cause analysis (use debugging), recurring failure clustering (use pattern-recognition), or claim/source grounding (use epistemic-grounding). Do NOT use for Break this pricing model down to irreducible assumptions. Do NOT use for This incident already happened; find the root cause. Do NOT use for Score every webhook failure mode with severity, occurrence, and detectability. Do NOT use for Facilitate a team pre-mortem session with independent written generation.

  • Kano model

    jacob-balslev/skill-graph/marketplace/skills/kano-model Skill

    no license1★ repo

    Use when classifying product features, service attributes, customer needs, or roadmap candidates with the Kano model: must-be/basic quality, performance/one-dimensional quality, attractive/delighter quality, indifferent quality, reverse quality, and questionable responses. Covers paired functional/dysfunctional survey design, segment-specific classification, feature-priority implications, category migration over time, and the boundary between Kano analysis and general backlog scoring. Do NOT use for generic RICE/ICE/MoSCoW ranking without customer-response evidence (use prioritization), open-ended research synthesis (use user-research or research-synthesis), or product-market positioning (use positioning). Do NOT use for Rank this backlog by reach, impact, confidence, and effort. Do NOT use for Synthesize these interview transcripts into research themes. Do NOT use for Design a generic quality-improvement process with DMAIC or PDCA.

  • Lean startup

    jacob-balslev/skill-graph/marketplace/skills/lean-startup Skill

    no license1★ repo

    Use when applying Lean Startup methodology to validate a new venture, product, feature, program, or business model under high uncertainty: build-measure-learn loops, minimum viable products, validated learning, riskiest assumptions, actionable metrics, innovation accounting, learning milestones, and pivot/persevere decisions. Covers experiment design and learning discipline before scaling. Do NOT use for generative customer interviews alone (use user-research), synthesizing existing research (use research-synthesis), feature satisfaction classification (use kano-model), OKR goal-setting, product positioning, or quantified option valuation. Do NOT use for Plan interviews to discover what users need before we have a product concept. Do NOT use for Synthesize these interview transcripts into themes and insights. Do NOT use for Classify these roadmap items as must-be, performance, delighter, indifferent, or reverse features. Do NOT use for Turn this strategy into quarterly Objectives and Key Results.

  • Mutation testing

    jacob-balslev/skill-graph/marketplace/skills/mutation-testing Skill

    no license1★ repo

    Use when reasoning about mutation testing as a behavioral signal of test-suite quality: the mutant-operator vocabulary (replace operator, negate condition, flip Boolean, remove statement, alter constant), the mutation-score metric (killed mutants / total non-equivalent mutants), why mutation testing is a stronger signal than code coverage (coverage measures execution; mutation measures whether the tests would catch a defect), the equivalent-mutant problem (mutants that produce no observable behavior change despite syntactic difference), selective and incremental mutation strategies that make the technique practical for large codebases (PIT, Stryker), and the relationship between mutation testing and TDD. Do NOT use for the structural signal of how much code tests reach (use test-coverage-strategy), the construction of test doubles (use test-doubles-design), the strategic question of what to test at which level (use testing-strategy), or generic fault injection at runtime (use chaos-engineering).

  • Pestel

    jacob-balslev/skill-graph/marketplace/skills/pestel Skill

    no license1★ repo

    Use when scanning an external macro environment with PESTEL/PESTLE and variants such as STEEPLE, STEEPLED, PESTLIED, STEEP, DESTEP, and LoNGPESTLE: political, economic, social, technological, environmental, and legal forces; evidence quality and recency; geography/jurisdiction and local/national/global level; time horizon; uncertainty; weak signals; impact/probability scoring; factor interactions; bias checks; opportunity/threat implications; assumptions; action conversion; and monitoring triggers. Covers external-environment scanning before strategy choices, market-entry reviews, strategic planning, product/service context, policy-aware planning, and risk/opportunity surfacing. Do NOT use for internal capability diagnosis (use swot-tows), industry profit-pressure diagnosis (use porters-five-forces), value-curve redesign (use blue-ocean-strategy), integrated strategy cascades (use playing-to-win), product positioning (use positioning), or quantified option comparison (use expected-value).

  • Playing to win

    jacob-balslev/skill-graph/marketplace/skills/playing-to-win Skill

    no license1★ repo

    Use when turning a vague business strategy, product strategy, market-entry decision, or initiative plan into an integrated Playing to Win strategy cascade: winning aspiration, where to play, how to win, must-have capabilities, and management systems. Covers Lafley/Martin choice-making, fit across the five choices, trade-off pressure, reverse tests, capability-system alignment, and the difference between strategy and planning. Do NOT use for competitive-industry structure analysis (use a five-forces skill when available), generic backlog scoring (use prioritization), or broad process-gate design (use methodology). Do NOT use for analyze whether this industry has attractive supplier power and threat of substitutes. Do NOT use for score these ten backlog items by impact and effort. Do NOT use for design a quality gate process for this multi-step implementation. Do NOT use for write OKRs for this strategy after it has already been chosen.

  • Porters five forces

    jacob-balslev/skill-graph/marketplace/skills/porters-five-forces Skill

    no license1★ repo

    Use when analyzing an industry's competitive structure and profit pool using Porter's Five Forces: rivalry among existing competitors, threat of new entrants, bargaining power of suppliers, bargaining power of buyers, and threat of substitutes. Covers industry-boundary definition, force-by-force diagnostics, structural drivers, dynamic trends, profitability implications, strategic positioning options, and the distinction between industry attractiveness and firm-specific advantage. Do NOT use for creating an integrated strategy cascade (use playing-to-win), classifying durable moat sources (use Seven Powers when available), backlog scoring (use prioritization), or generic market sizing. Do NOT use for turn this vague product strategy into where-to-play and how-to-win choices. Do NOT use for rank these roadmap items by expected impact. Do NOT use for estimate the TAM for this market. Do NOT use for classify this company's durable moat source. Do NOT use for write OKRs for the chosen strategy.

  • Principled negotiation

    jacob-balslev/skill-graph/marketplace/skills/principled-negotiation Skill

    no license1★ repo

    Use when preparing, structuring, or pressure-testing a negotiation with principled negotiation / BATNA: separate people from the problem, focus on interests rather than positions, invent options for mutual gain, use objective criteria, define BATNA / reservation value / ZOPA, and decide whether to accept, improve, or walk away. Do NOT use for generic persuasion copy (use microcopy or writing-humanizer), unilateral conflict diagnosis without a deal table, competitive strategy analysis (use playing-to-win, porters-five-forces, or seven-powers), or broad decision scoring without counterparties (use expected-value or prioritization). Do NOT use for Write persuasive landing-page copy for this offer. Do NOT use for Analyze rivalry, supplier power, buyer power, entrants, and substitutes. Do NOT use for Choose our winning aspiration, where to play, and how to win. Do NOT use for Rank these initiatives by expected value and downside risk. Do NOT use for Give legal advice on whether this contract clause is enforceable.

  • Prioritization

    jacob-balslev/skill-graph/marketplace/skills/prioritization Skill

    no license1★ repo

    This skill provides prioritization frameworks for AI engineering: RICE-A (adding AI Ambiguity to RICE) for product features, ICE for research experiments, and MoSCoW for MVP/Release scoping. Use when ranking the backlog, deciding which model research path to follow, or defining the scope of a new feature. Do NOT use for one-off task sequencing (use task skill) or personal time management.

  • Problem locating solving

    jacob-balslev/skill-graph/marketplace/skills/problem-locating-solving Skill

    no license1★ repo

    Use when locating a bug in an unfamiliar codebase, tracing a failure from symptom to source, or choosing between candidate fixes after the symptom is observed but before a patch lands. Covers the locate-to-solve workflow: problem-statement contract, search-space reduction, boundary-based fault localization, good-vs-bad path comparison, binary search through a call chain, minimal repro, root-cause isolation, fix option comparison, blast-radius review, and post-fix verification. Do NOT use for broad task planning once the bug is localized, test-pyramid design, or performance forensics. Do NOT use for plan the next 6 weeks of work for the team. Do NOT use for review this PR for code quality. Do NOT use for this endpoint is slow under load — find the bottleneck. Do NOT use for scan this repo for OWASP top 10 vulnerabilities. Do NOT use for run scientific-method debugging on this stack trace. Do NOT use for I see the symptom but cannot find the root cause of this nil panic.

  • Query optimization

    jacob-balslev/skill-graph/marketplace/skills/query-optimization Skill

    no license1★ repo

    Diagnosing and tuning a specific slow relational-database query from plan evidence: workload impact, exact query context, EXPLAIN / actual execution plans, row-estimate accuracy, access path choice, join order, sort/hash spills, JIT/planning overhead, parameter-sensitive plans, plan regressions, statistics, and rewrite-vs-index-vs-operational response selection. Start from the actual plan and runtime evidence, not from the reflex to add an index; modern engine features such as Query Store, PSP/OPPO, SQL Plan Management, pg_stat_statements, auto_explain, MySQL histograms, Oracle DBMS_XPLAN, and PostgreSQL planner improvements are evidence sources and response tools, not replacements for diagnosis. Do NOT use for designing the durable index portfolio (use indexing-strategy), schema design (use entity-relationship-modeling), distributed partitioning (use sharding-strategy), isolation-level correctness (use transaction-isolation), or whole-system load testing (use performance-testing).

  • Scenario planning

    jacob-balslev/skill-graph/marketplace/skills/scenario-planning Skill

    no license1★ repo

    Scenario planning: a strategic-foresight method for making decisions under deep uncertainty by constructing and stress-testing several plausible future worlds. Do NOT use for Scan political, economic, social, technological, environmental, and legal forces for market entry. Do NOT use for We have three options with probabilities and payoffs. Compute expected value and recommend one. Do NOT use for Update our confidence in this forecast after new evidence arrived. Do NOT use for Balance our innovation portfolio across core, adjacent, and transformational bets. Do NOT use for Turn strengths, weaknesses, opportunities, and threats into SO, WO, ST, and WT options. Do NOT use for Answer the five Playing to Win choices for this business. Do NOT use for constructing and using alternative futures from critical uncertainties (use pestel). Do NOT use for deep-uncertainty exploration (use expected-value). Do NOT use for multiple plausible future worlds and strategic robustness (use bayesian-reasoning).

  • Seo strategy

    jacob-balslev/skill-graph/marketplace/skills/seo-strategy Skill

    no license1★ repo

    SEO implementation strategy for building pages that rank -- covering content strategy, programmatic SEO at scale, marketplace-specific SEO, and AI search optimization.

  • Seven powers

    jacob-balslev/skill-graph/marketplace/skills/seven-powers Skill

    no license1★ repo

    Use when diagnosing whether a business has, can build, or is falsely claiming durable strategic power using Hamilton Helmer's Seven Powers: scale economies, network economies, counter-positioning, switching costs, branding, cornered resource, and process power. Covers Power as benefit plus barrier, persistent differential returns, moat-source classification, Power Progression by company phase, false-positive checks, and strategy implications. Do NOT use for industry-structure analysis alone (use porters-five-forces), integrated strategy-cascade formulation (use playing-to-win), generic prioritization, financial valuation, or surface-level SWOT lists. Do NOT use for analyze the attractiveness of this industry using entrants, suppliers, buyers, substitutes, and rivalry. Do NOT use for turn this market-entry plan into a winning aspiration, where to play, how to win, capabilities, and systems. Do NOT use for rank these roadmap items by impact and effort. Do NOT use for make a SWOT table for this company.

  • Sharding strategy

    jacob-balslev/skill-graph/marketplace/skills/sharding-strategy Skill

    no license1★ repo

    Use when reasoning about horizontal partitioning of data across nodes for storage capacity and write throughput beyond a single node: the three foundational partitioning schemes (range, hash, directory/lookup), the shard-key choice that determines whether the system scales or hotspots, the resharding problem and how consistent hashing addresses it, cross-shard queries and the joins-and-transactions trade-off, the relationship to replication (sharding partitions data; replication copies each shard), and the failure modes (hot shard, skewed distribution, cross-shard transactions, range-end overload). Do NOT use for replicating the same data across nodes (use replication-patterns), the CAP/PACELC frame (use cap-theorem-tradeoffs), single-node performance tuning (use query-optimization), or indexing within a shard (use indexing-strategy).

  • Spec driven development

    jacob-balslev/skill-graph/marketplace/skills/spec-driven-development Skill

    no license1★ repo

    Use when starting a non-trivial feature, refactor, or agent implementation that needs a written spec, plan, task breakdown, and verification path before code changes. Covers Spec Kit-style SDD phases, requirements-vs-plan separation, task traceability, review gates, and spec-compliance verification. Do NOT use for one-line edits, README-only fixes, post-implementation code review (use `code-review`), or test-level decisions (use `testing-strategy`).

  • Swot tows

    jacob-balslev/skill-graph/marketplace/skills/swot-tows Skill

    no license1★ repo

    Use when turning internal/external situation analysis into strategic options with SWOT and TOWS: strengths, weaknesses, opportunities, threats, evidence quality, SO/WO/ST/WT option generation, and action hypotheses. Covers separating internal from external factors, avoiding unsupported laundry lists, crossing quadrants into strategy options, and naming what evidence or method should follow. Do NOT use for industry profit-pressure diagnosis (use porters-five-forces), durable moat classification (use seven-powers), value-curve redesign (use blue-ocean-strategy), integrated strategy cascades (use playing-to-win), or quantified option comparison (use expected-value). Do NOT use for Analyze supplier power, buyer power, entrants, substitutes, and rivalry. Do NOT use for Classify this company's durable moat source. Do NOT use for Create a strategy canvas and ERRC grid for a new market space. Do NOT use for Turn this strategy into winning aspiration, where to play, how to win, capabilities, and systems.

  • Task analysis

    jacob-balslev/skill-graph/marketplace/skills/task-analysis Skill

    no license1★ repo

    Use when auditing a route, defining a route contract, reviewing onboarding or setup flows, diagnosing why a page feels confusing, or when the user asks about top tasks, time-to-value, branching, dead ends, or task complexity. Provides goal-driven UX analysis that turns vague critique into explicit goal -> task -> subtask decomposition and a primary / secondary / supporting hierarchy contract for the first viewport. Do NOT use for control-pattern choice (use `interaction-patterns`), visual craft (use `visual-design-foundations`), responsive layout (use `layout-composition`), or accessibility-only QA (use `a11y`). Do NOT use for review this PR for code quality. Do NOT use for audit this UI for WCAG 2.2 violations. Do NOT use for decide the CSS grid layout for this hero section. Do NOT use for pick the right colors for this status badge. Do NOT use for build the navigation taxonomy for the whole product. Do NOT use for should we use a dropdown or a stepper here.

  • Test coverage strategy

    jacob-balslev/skill-graph/marketplace/skills/test-coverage-strategy Skill

    no license1★ repo

    Use when reasoning about code coverage as a strategic measurement rather than a quality target: structural reach versus behavioral verification (covered vs tested), the coverage-criterion hierarchy (function, line, branch, decision, condition, MC/DC, path) and matching the criterion to where a module's failure modes hide, Marick's floor-vs-ceiling distinction, Goodhart's Law applied to coverage and Goodhart-resistant policy (diagnostic use, diff/patch floors, risk-weighting, behavioral panels), denominator hygiene and cross-tool counter semantics, safety-critical MC/DC (DO-178C Level A required; ISO 26262 ASIL-D highly recommended) as requirements-based evidence, and interpreting coverage from AI-generated tests. Do NOT use for choosing test levels (use testing-strategy), mutation testing as a behavioral signal (use mutation-testing), test-double construction (use test-doubles-design), LLM eval iteration (use eval-driven-development), or specific coverage-tooling configuration (tool docs).

  • Testing strategy

    jacob-balslev/skill-graph/marketplace/skills/testing-strategy Skill

    no license1★ repo

    Use when planning tests for a bug fix, feature, or refactor — deciding what deserves a test, at which level, with what evidence. Covers test-scope decisions, test-level selection (unit / integration / contract / e2e), effort-to-risk matching, regression targeting, evidence quality, and failure-case coverage. Do NOT use for chasing a known failure (that is `debugging`), for pure doc writing (that is `documentation`), or for conceptual architecture discussion with no verification target (no dedicated skill — treat as strategy, not testing). Do NOT use for my existing test is failing — why? Do NOT use for write a testing-patterns guide for the contributor docs. Do NOT use for clean up this duplicated test setup across three files.

  • Three horizons

    jacob-balslev/skill-graph/marketplace/skills/three-horizons Skill

    no license1★ repo

    Use when balancing an innovation, growth, transformation, or venture portfolio across McKinsey's Three Horizons: Horizon 1 current core businesses, Horizon 2 emerging growth businesses, and Horizon 3 future options. Covers concurrent portfolio balance, resource allocation (the 70-20-10 benchmark and its caveats), evidence maturity, governance and metrics by horizon, metered funding, ring-fenced budgets, transitions from option to emerging business to core, the collapsed-time critique that disruption can now arrive on core timelines, and the risk that short-term core demands or incentives starve future growth. Do NOT use for BCG growth-share portfolio allocation (use bcg-matrix), Ansoff product-market growth path selection (use ansoff-matrix), Blue Ocean value-curve redesign (use blue-ocean-strategy), scenario construction and stress-testing across alternative futures (use scenario-planning), OKR goal-setting (use okrs), or quantified probability-weighted valuation (use expected-value).

  • Tool call strategy

    jacob-balslev/skill-graph/marketplace/skills/tool-call-strategy Skill

    no license1★ repo

    Use when an agent is making too many tool calls, when context is filling from verbose tool outputs, when the same operation could be a script instead of N individual calls, or when designing a tool-use protocol for a new agent or harness. Covers the three costs of every call (token, latency, context pollution), the script-vs-call decision gate, tool-selection decision trees (file-search vs content-search vs targeted-read vs full-read), call batching and parallelization, redundancy avoidance, the poka-yoke principle, subagent delegation for context protection, and cost-benchmark heuristics by task type. Do NOT use for prompt wording (use `prompt-craft`), broader context stack design across the five layers (use `context-engineering`), runtime tool failures or production debugging (use `debugging`), or behaviour-preserving refactor mechanics (use `refactor`). Do NOT use for improve this prompt's wording to get better outputs. Do NOT use for design what skills get loaded for which prompts.

  • Create spec

    itsyasirkhandev/spec-driven-development/skills/development/create-spec Skill

    no license1★ repo

    use this skill when the user ask you to create the spec file or to create the specification plan(spec.md).

  • To issues

    itsyasirkhandev/spec-driven-development/skills/matt pocock/to-issues Skill

    no license1★ repo

    Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

    The same file is in 12 other repositories

  • To prd

    itsyasirkhandev/spec-driven-development/skills/matt pocock/to-prd Skill

    no license1★ repo

    Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

    The same file is in 10 other repositories

  • Pptx slide specification

    kimtth/agent-pptify-kit/pptx-deck-creation-agentic-plugin/plugins/pptx-deck-creation/skills/pptx-slide-specification Skill

    1★ repo

    Use when authoring or repairing a coordinate-explicit JSON specification for an editable PPTX deck.

    The same file is in 3 other repositories

  • Pptx slide specification

    kimtth/agent-pptify-kit/pptx-deck-creation/skills/pptx-slide-specification Skill

    1★ repo

    Author or repair coordinate-explicit JSON specifications for editable PPTX decks.

  • Plan

    diamitani/rostr-agent/skills/software-development/plan Skill

    1★ repo

    Plan mode: write an actionable markdown plan to .hermes/plans/, no execution. Bite-sized tasks, exact paths, complete code.

    The same file is in 1 other repository

  • Caching strategy

    kwhorne/elyra-skills/skills/caching-strategy Skill

    1★ repo

    Design a caching strategy - decide what to cache, where, with what TTL and invalidation, and how to avoid the classic foot-guns (stampede, stale data, key collisions). Use when the user asks about caching, cache invalidation, Redis/Memcached design, HTTP caching, or fixing cache-related bugs.

  • Spec writing

    kwhorne/elyra-skills/skills/spec-writing Skill

    1★ repo

    Write a focused spec before building - problem statement, scope, acceptance criteria, edge cases, and open questions. Use when the user describes a feature to build, asks for a spec or PRD, or starts a task that is too vague to implement directly.

  • Task breakdown

    kwhorne/elyra-skills/skills/task-breakdown Skill

    1★ repo

    Break a feature or spec into small, atomic, independently verifiable tasks with explicit ordering and dependencies. Use when the user asks to plan implementation, create a task list, estimate work, or when a spec is ready and needs to become an executable plan.

  • Openapi to mcp skill

    Arnie016/codex-prompt-templates/skills/openapi-to-mcp-skill Skill

    1★ repo

    Convert OpenAPI/Swagger APIs into Codex-friendly MCP/tool workflows and generated skills. Use when the user wants to expose an API to agents, create a skill from API docs, use toolcast-style conversion, or design safe API tool schemas. Triggers: OpenAPI to MCP, Swagger to tools, API tool plan, generate MCP server from API spec. Skip when there is no stable spec or the user only needs one ad-hoc HTTP request.

  • Repo intelligence brief

    Arnie016/codex-prompt-templates/skills/repo-intelligence-brief Skill

    1★ repo

    Inspect a GitHub or local repository and produce a compact Codex-ready architecture/task brief. Use for repo onboarding, weekend project selection, fork analysis, setup discovery, extension ideas, or turning a source repo into a useful build plan.

  • To spec

    MarcoAntolini/cursor-sync/agents/skills/mattpocock/engineering/to-spec Skill

    no license1★ repo

    Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

    The same file is in 11 other repositories

  • To tickets

    MarcoAntolini/cursor-sync/agents/skills/mattpocock/engineering/to-tickets Skill

    no license1★ repo

    Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

    The same file is in 5 other repositories

  • Ralphify spec

    paulnsorensen/skillz-that-grillz/skills/ralphify-spec Skill

    1★ repo

    Generate a ralphify-approved ralph directory (RALPH.md + optional scripts) from a plain-English description of repetitive or iterative work. Use this skill whenever the user says "ralphify", "create a ralph", "ralph wiggum", "autonomous loop", "/ralphify", references Geoffrey Huntley's Ralph Wiggum method, or asks to wrap iterative work in ralphify (test-until-green, refactor-until-done, lint-until-clean, coverage-until-90, burn-down-todos, resolve-review-comments). Trigger even when the user does not explicitly name ralphify but describes an open-ended loop ("keep fixing tests until they pass", "port files one by one until the directory is done"). Do not trigger for one-shot tasks — ralphs exist for work that benefits from running N times against a stop condition.

  • Research strategy and project design

    jjfroehlich/agent-skills-for-academic-research/skills/research-strategy-and-project-design Skill

    1★ repo

    Agent skills for academia research: writing, dataviz, publishing, communication, career, and more.

  • Scientific feedback

    jjfroehlich/agent-skills-for-academic-research/skills/scientific-feedback Skill

    1★ repo

    Agent skills for academia research: writing, dataviz, publishing, communication, career, and more.

  • Token strategy

    almasumdev/awesome-mobile-backend-agent-skills/.github/skills/auth/token-strategy Skill

    no license1★ repo

    Choose between access+refresh tokens and opaque server sessions for mobile; design revocation and device binding. Use when deciding the token model for a new mobile backend or hardening an existing one.

  • Plan

    justincordova/agents/skills/plan Skill

    1★ repo

    Use when you have a spec and need to create a detailed implementation plan before touching code

  • Spec

    justincordova/agents/skills/spec Skill

    1★ repo

    Use when starting a new project or when design decisions need to be documented or updated. Creates and maintains the project-level specification.

  • Prd author

    geigermatic/claude-craft/skills/prd-author Skill

    1★ repo

    Interactively draft a Product Requirements Document from a problem statement. Walks the user through Problem, Current State, Design, Phases, Files, Metrics, Risks, and a Manual UI Test Checklist. Use when the user has a non-trivial feature, refactor, or initiative that needs alignment before implementation.

  • Multi pass planning

    zoidbergclawd/coherence/skills/multi-pass-planning Skill

    1★ repo

    Use when a task is non-trivial, spans multiple files, affects architecture, requires tests or docs, or has unclear assumptions, to prevent premature coding by running Plan, Audit, Repair, Align, and Code as five distinct passes.

  • Plan ceo opportunities

    ChristopherAlphonse/calphonse-skills/plan-ceo-opportunities Skill

    1★ repo

    Surfaces product expansion, reduction, trust, and positioning opportunities one decision at a time.

  • Plan ceo review

    ChristopherAlphonse/calphonse-skills/plan-ceo-review Skill

    1★ repo

    Founder-mode product review. Rethinks the problem, challenges scope, searches for stronger product opportunities, and chooses one of four review modes: SCOPE EXPANSION, SELECTIVE EXPANSION, HOLD SCOPE, or SCOPE REDUCTION.

  • Plan ceo strategy

    ChristopherAlphonse/calphonse-skills/plan-ceo-strategy Skill

    1★ repo

    Selects founder-mode review posture and challenges product strategy before execution.

  • Plan ceo wrapup

    ChristopherAlphonse/calphonse-skills/plan-ceo-wrapup Skill

    1★ repo

    Writes the founder/product review artifact under .planning/reviews and optional strategy doc under .planning/strategy.

  • Plan eng review

    ChristopherAlphonse/calphonse-skills/plan-eng-review Skill

    1★ repo

    Engineering-manager plan review. Locks in architecture, data flow, edge cases, tests, performance, rollout, and failure handling before implementation. Uses smaller local review skills for each review pass.

  • Plan research

    ChristopherAlphonse/calphonse-skills/plan-research Skill

    1★ repo

    Research how to implement a phase or planning topic before detailed planning. Produces RESEARCH.md for downstream plan and review skills.

  • Plan review architecture

    ChristopherAlphonse/calphonse-skills/plan-review-architecture Skill

    1★ repo

    Reviews architecture, data flow, dependencies, security boundaries, rollout, and failure scenarios.