Skip to content

Explore skills

Search every indexed skill by name, description, repository or instructions, then narrow the results.

Showing 38041–38070 of 43673 skills

mental-modelsjacob-balslev/skill-graphUse when reasoning about how a system, user, or designer's internal model of behavior may diverge from reality — applies across UX, distributed systems, type systems, API design, and team collaboration. Covers the three-model frame (designer / system image / user), the two gulfs (execution and evaluation), analogy and metaphor as model-seeding, the five failure modes (transfer, overgeneralization, underspecification, drift, invariant blindness), the surface/operational/architectural/domain layering, and the discipline of validating a model against the system it claims to represent. Do NOT use for the visual representation of a model (use knowledge-modeling), for the formal-domain entities-attributes-relationships of conceptual modeling (use conceptual-modeling), for cognitive biases in decision-making (out of scope), or for empirically eliciting user models via research methods (use user-research). Do NOT use for name the React hook for managing form state (tactical implementation choice).Stars: 3Updated Claude CodeCodexUnverifiedInstall
merge-queuejacob-balslev/skill-graphUse when serializing merges across multiple agent branches, resolving conflicts between agent outputs, or cleaning stale task branches. Covers atomic locking, idempotency checks, non-fast-forward handling, and worktree cleanup. Do NOT use for ordinary git operations outside an agent merge queue (use `version-control`).Stars: 3Updated Claude CodeCodexUnverifiedInstall
methodicaljacob-balslev/skill-graphUse when disciplined, complete, evidence-backed execution matters more than brevity: audits, diagnostic reports, tracked-task creation from findings, acceptance-criteria verification, research briefs, and enumerated outputs future work depends on. Covers why agents fail at completeness (sycophancy, premise adoption, summary-first compression, instruction-density loss, long-horizon attention decay, self-critique echo chambers, reasoning-masked agreement, verification theater, delegation-as-proof) and countermeasures: pre-task scope declaration, count-preserving enumeration, evidence receipts, externally grounded critique, provenance labels, explicit completeness/partial receipts, and runtime enforcement. Do NOT use for shortest-route selection (use task-path-optimization), broad artifact-quality standards (use best-practice), scoring results (use evaluation), compact pre-output enforcement (use no-cutting-corners), or post-enumeration compression (use summarization).Stars: 3Updated Claude CodeCodexUnverifiedInstall
methodologyjacob-balslev/skill-graphUse when planning multi-step implementations, designing quality gates, establishing verification protocols, or building agent checklists calibrated to known failure modes. Covers methodology/method/process distinctions, Cleanroom, PSP/TSP, hypothesis-driven development, DMAIC, checklist design, V&V frameworks, EDDOps, quality gates, and PDCA. Do NOT use for code-review verdicts (use `code-review`), behavior-preserving implementation work (use `refactor`), or test strategy (use `testing-strategy`). Do NOT use for review this PR and decide whether to approve it. Do NOT use for refactor this file while preserving behavior. Do NOT use for decide unit vs integration vs e2e coverage for this feature. Do NOT use for write the eval cases and grader rubric for this router. Do NOT use for block this dangerous git command or secret-bearing tool call.Stars: 3Updated Claude CodeCodexUnverifiedInstall
microcopyjacob-balslev/skill-graphUse when writing or reviewing functional UI text: button labels, empty states, tooltips, dialogs, placeholders, loading/progress messages, toasts, inline validation, permission copy, or onboarding steps. Covers interface-copy patterns such as verb-first action labels, acknowledge-explain-guide empty states, one-sentence tooltips, consequence-first confirmations, progressive loading language, and blur/fix validation messages. Do NOT use for marketing persuasion, documentation prose/guide structure, feedback-state staging, or general linguistic rationale behind wording. Do NOT use for write the marketing headline for the pricing page. Do NOT use for review this WCAG 2.2 contrast violation on the dashboard. Do NOT use for explain the morphology rule behind verb-first function names. Do NOT use for restructure this help-center article into a tutorial. Do NOT use for decide the kebab-case format for this new CSS class. Do NOT use for rename this React component across all call-sites.Stars: 3Updated Claude CodeCodexUnverifiedInstall
middleware-patternsjacob-balslev/skill-graphUse when designing or reviewing Next.js middleware: the single middleware.ts request preprocessor, Edge Runtime constraints, matcher config, NextRequest/NextResponse APIs, redirects, rewrites, pass-through responses, direct responses, auth gates, locale routing, A/B rewrites, security-header delivery, geo routing, bot blocking, and request ID injection. Use for fast cross-cutting request concerns that apply across many routes. Do NOT use for per-route API handlers, Server Actions, HTTP semantics, full security policy design, streaming logic, or webhook signature handling. Do NOT use for implement a /api/posts POST endpoint (use route-handler-design). Do NOT use for implement a delete-comment mutation triggered from a form button (use server-actions-design). Do NOT use for explain what an HTTP 308 means vs 307 (use http-semantics). Do NOT use for design the full CSP policy and the rest of the security-header strategy (use security-fundamentals).Stars: 3Updated Claude CodeCodexUnverifiedInstall
mobile-responsive-uxjacob-balslev/skill-graphUse when designing mobile-specific UX for dashboards and operational web apps: touch-friendly targets, thumb-zone optimization, swipe gestures, condensed data display, bottom navigation, bottom sheets, mobile inputs, and pull-to-refresh. Load when adapting a desktop dashboard to phone use, implementing touch interactions, or checking whether a mobile layout serves quick-glance tasks rather than compressed desktop analysis. Do NOT use for general responsive layout structure across all breakpoints (layout-composition), accessibility compliance breadth such as ARIA, keyboard, and screen reader audits (a11y), or component/token architecture (design-system-architecture). Do NOT use for audit ARIA labels and keyboard focus order. Do NOT use for choose global page breakpoints and responsive grid tracks. Do NOT use for design reusable design tokens for mobile components. Do NOT use for create the product information architecture.Stars: 3Updated Claude CodeCodexUnverifiedInstall
mutation-testingjacob-balslev/skill-graphUse 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).Stars: 3Updated Claude CodeCodexUnverifiedInstall
naming-conventionsjacob-balslev/skill-graphUse when naming a new file, function, variable, type, route, database column, environment variable, or any other code or system artifact. Covers identifier morphology (verb-noun choice, plural vs singular, prefix/suffix conventions), kebab-case vs camelCase vs snake_case vs PascalCase per artifact kind, abbreviation rules, name-vs-path semantics, the rename-coordination workflow, and detection of names that lie. Do NOT use for content writing (use `documentation`), for restructuring already-named code (use `refactor`), or for human-language copy in product UI (separate skill, not in this library). Do NOT use for refactor this 200-line function into smaller pieces. Do NOT use for write a doc explaining our naming conventions. Do NOT use for review this PR's naming choices. Do NOT use for the variable named `userIsActive` is logging the wrong value. Do NOT use for scaffold a new skill that teaches naming conventions.Stars: 3Updated Claude CodeCodexUnverifiedInstall
no-cutting-cornersjacob-balslev/skill-graphEnforce five non-negotiable quality pillars as a pre-output gate: complete reporting (show ALL items, never filter unilaterally), verification (no claim of works/done/exists without a tool-call receipt in the same turn), thoroughness (every acceptance criterion verified with evidence; docs ship with the change), enrichment ('improve' adds capability, never trims), and anti-shortcut (exhaust deterministic lookup before guessing; findings demand action, not filing). Use when reviewing enumerated output for completeness, when an agent claims something works without evidence, when marking a task done, or when asked to 'improve' anything.Stars: 3Updated Claude CodeCodexUnverifiedInstall
observability-modelingjacob-balslev/skill-graphUse when designing telemetry semantics before or during implementation: logs, metrics, traces, events, spans, attributes, correlation IDs, SLOs, alert signals, and diagnostic questions. Do NOT use for domain/business event contracts (use `event-contract-design`), configuring an error tracker alone (use `error-tracking`), performance optimization (use `performance-engineering`), or debugging a current incident (use `debugging`). Do NOT use for set up Sentry error tracking for this app. Do NOT use for profile and optimize a slow endpoint. Do NOT use for debug the current production incident. Do NOT use for write application tests for this feature.Stars: 3Updated Claude CodeCodexUnverifiedInstall
okrsjacob-balslev/skill-graphObjectives and Key Results goal-setting methodology for turning strategy, quarterly priorities, product goals, or team focus areas into outcome-oriented Objectives, measurable Key Results, review cadences, and learning loops. Do NOT use for Decide our winning aspiration, where to play, and how to win. Do NOT use for Use constraint-awareness to identify hard constraints before choosing a strategy or goal.Stars: 3Updated Claude CodeCodexUnverifiedInstall
ontology-modelingjacob-balslev/skill-graphUse when formalizing domain meaning with classes, properties, constraints, RDF/OWL-style semantics, SHACL-like validation shapes, or reasoning-ready axioms. Do NOT use for simple category trees (use `taxonomy-design`), pre-implementation business entity sketches (use `conceptual-modeling`), database schemas (use `entity-relationship-modeling`), or broad representation choice (use `knowledge-modeling`). Do NOT use for make a simple browse category tree for skills. Do NOT use for identify the business entities and relationships before implementation. Do NOT use for design the SQL tables, keys, and indexes. Do NOT use for choose whether this knowledge belongs in rules, frames, a graph, or a hybrid.Stars: 3Updated Claude CodeCodexUnverifiedInstall
opencodejacob-balslev/skill-graphUse when deciding whether to run a task on the OpenCode agent runtime, how to invoke it non-interactively, how to pick a provider/model string, or how OpenCode differs from Claude Code and Codex. Covers terminal TUI, opencode run, ACP/IDE bridge, desktop beta, web UI, opencode serve, provider/model routing, OpenCode Zen and OpenCode Go lanes, config precedence, JSONL output, CLI command surface, build/plan agents, LSP code intelligence, permissions, Agent Skills, MCP, references, commands, plugins, local models, and scripting/automation. Do NOT use for choosing which free model fits a task (use opencode-free-models), writing the agent loop itself (use autonomous-loop-patterns), or GitHub Copilot premium-request economics (use github-copilot). Do NOT use for which free model should I use for this classification job? Do NOT use for how do I structure the autonomous agent loop itself? Do NOT use for how many Copilot premium requests will this burn?Stars: 3Updated Claude CodeCodexUnverifiedInstall
opencode-free-modelsjacob-balslev/skill-graphUse when deciding WHICH free or cheap agent model to route a piece of work to (e.g. MiniMax M3 Free, NVIDIA Nemotron, GLM, GPT-5 Nano, or another OpenCode Zen free-tier model), what each is good at, where its quality ceiling sits, and when to escalate the same work to a frontier model instead. Covers cost-routing: matching deterministic/mechanical/high-volume work to the cheapest model that clears its bar, and the hard rule that quality-creating and quality-judging work never goes to a free/cheap model. Do NOT use for choosing or operating the OpenCode runtime itself (use `opencode`), for authoring the agent loop (use `autonomous-loop-patterns`), or for GitHub Copilot premium-request budgeting (use `github-copilot`). Do NOT use for how do I invoke opencode from a script? Do NOT use for how do I write the retry loop for my agent? Do NOT use for how many Copilot premium requests will this cost?Stars: 3Updated Claude CodeCodexUnverifiedInstall
owasp-securityjacob-balslev/skill-graphUse when reviewing code for security vulnerabilities, threat-modelling a new feature, implementing authentication or authorization, handling user input, hardening dependencies or CI/CD against software-supply-chain compromise, or auditing a codebase against the current OWASP Top 10 (2025, with the 2021 mapping retained). Covers broken access control (incl. SSRF), security misconfiguration, software supply chain failures, cryptographic failures, injection (SQL, NoSQL, command, LDAP, XSS), insecure design, authentication failures, software/data integrity failures, security logging and alerting failures, and mishandling of exceptional conditions (fail-open error paths, error leakage). Do NOT use for general code review (use `code-review` for the holistic per-PR pass), for chasing a known production bug (use `debugging`), for defending an LLM against prompt/RAG injection or agent-tool-authority abuse (use `prompt-injection-defense`), or for writing a security policy doc (use `documentation`).Stars: 3Updated Claude CodeCodexUnverifiedInstall
pattern-recognitionjacob-balslev/skill-graphUse when auditing for recurring issues, clustering errors, detecting drift from conventions, or when an agent keeps fixing symptoms instead of root causes. Covers the Observe -> Cluster -> Name -> Codify -> Detect -> Prevent loop, grep-based audits, normalize-then-hash error clustering, board-health patterns, design-token and heading drift, domain-encoding patterns, eval-as-pattern-tests, 5 Whys, pattern lifecycle states, and drift traps. Do NOT use for one-off bug localization without recurrence, or for designing the classification system itself; this skill detects violations of conventions that already exist. Do NOT use for review this code for semantic correctness. Do NOT use for find where the user-auth helper is defined. Do NOT use for design a MECE classification taxonomy for our error catalogue. Do NOT use for investigate why this single failing test is breaking. Do NOT use for trigger an alert when CPU exceeds 80% for 5 minutes. Do NOT use for rewrite this function to be cleaner.Stars: 3Updated Claude CodeCodexUnverifiedInstall
performance-budgetsjacob-balslev/skill-graphUse when declaring, measuring, or enforcing performance thresholds as a quality contract rather than as an aspirational target. Covers the three budget axes (time, size, count), the four governing properties of a real budget (metric, threshold, percentile, consequence), the Core Web Vitals set (LCP, INP, CLS), the RAIL model, Lighthouse budgets.json, lab vs field measurement, and the discipline of treating budget breach as a build or deploy failure rather than a tracked metric. Do NOT use for the activity of profiling and optimizing a specific slow path (use performance-engineering), the choice of rendering model that bounds achievable budgets (use rendering-models), or the design of observability and telemetry signals (use observability-modeling).Stars: 3Updated Claude CodeCodexUnverifiedInstall
performance-engineeringjacob-balslev/skill-graphUse when measuring, diagnosing, budgeting, or improving performance: latency, throughput, Core Web Vitals, database queries, caching, bundle size, concurrency, resource use, and regression prevention. Do NOT use for telemetry schema design alone (use `observability-modeling`), error capture setup (use `error-tracking`), or premature micro-optimization without a measured bottleneck. Do NOT use for design logs, spans, metrics, and correlation IDs before implementation. Do NOT use for set up Sentry and error redaction. Do NOT use for make random micro-optimizations without measurements. Do NOT use for write general unit tests for this feature.Stars: 3Updated Claude CodeCodexUnverifiedInstall
performance-testingjacob-balslev/skill-graphUse when measuring a system's non-functional properties — latency, throughput, error rate, resource utilization, saturation — by running it under controlled load and verifying against explicit SLO thresholds. Covers the five primitives (load profile, workload, latency metric, throughput metric, SLO target), load-shape taxonomy (smoke, load, stress, spike, soak, breakpoint), latency-percentile vocabulary (p50, p95, p99, p99.9), why average latency and coordinated omission mislead, tool selection (k6, JMeter, Locust, Gatling, Vegeta), and offline controlled measurement versus production observability. Do NOT use for optimization itself (use `performance-engineering`), threshold contracts (use `performance-budgets`), production runtime measurement (use `observability-modeling` or `error-tracking`), single-function microbenchmarks, fault injection, or test-suite quality measurement (use `mutation-testing`). Do NOT use for decide which modules need more unit tests and what test coverage target to enforce.Stars: 3Updated Claude CodeCodexUnverifiedInstall
pesteljacob-balslev/skill-graphUse 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).Stars: 3Updated Claude CodeCodexUnverifiedInstall
playing-to-winjacob-balslev/skill-graphUse 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.Stars: 3Updated Claude CodeCodexUnverifiedInstall
porters-five-forcesjacob-balslev/skill-graphUse 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.Stars: 3Updated Claude CodeCodexUnverifiedInstall
positioningjacob-balslev/skill-graphUse when applying April Dunford-style product positioning to make a product's differentiated value obvious to the right buyers: competitive alternatives, unique attributes, value themes, best-fit target segments, market category, trend context, and reusable positioning output. Covers the Obviously Awesome 10-step workflow, positioning canvas logic, category choice, value-to-segment fit, and positioning-to-sales-message translation. Do NOT use for full strategy-cascade formulation (use playing-to-win), market-creating value innovation (use blue-ocean-strategy), industry-structure diagnosis (use porters-five-forces), or durable moat classification (use seven-powers). Do NOT use for Turn this whole company plan into winning aspiration, where to play, how to win, capabilities, and systems. Do NOT use for Create a blue ocean strategy canvas and ERRC grid for this market. Do NOT use for Analyze rivalry, buyer power, supplier power, entrants, and substitutes.Stars: 3Updated Claude CodeCodexUnverifiedInstall
principled-negotiationjacob-balslev/skill-graphUse 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.Stars: 3Updated Claude CodeCodexUnverifiedInstall
printifyjacob-balslev/skill-graphUse when working with Printify — the print-on-demand REST API, catalog model (blueprints, print providers, variants, print areas), product creation and publish lifecycle to connected channels, order routing, shipping cost queries, and HMAC SHA-256 webhook verification. Do NOT use for non-Printify POD vendors, generic Shopify storefront work, or print-file (artwork) generation. Do NOT use for Generate the artwork PNG file that gets uploaded as a print file. Do NOT use for Implement the Shopify side of the Printify-to-Shopify sync. Do NOT use for Design a generic POD-vendor-agnostic product schema.Stars: 3Updated Claude CodeCodexUnverifiedInstall
prioritizationjacob-balslev/skill-graphThis 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.Stars: 3Updated Claude CodeCodexUnverifiedInstall
problem-approach-routerjacob-balslev/skill-graphUse when facing a new problem and unsure which problem-solving methodology or foundational skill to apply first. Routes between first-principles-thinking, pattern-recognition, mental-models, constraint-awareness, and task-analysis by classifying the problem type. Activate before choosing any other foundational skill. Do NOT use to execute the selected approach (use the specific routed skill directly), for implementation work (use the relevant engineering skill), or when the correct approach is already known. Do NOT use for actually apply first-principles thinking to this specific problem. Do NOT use for analyze why this pattern keeps recurring in the codebase. Do NOT use for break down the constraints on this engineering decision. Do NOT use for map the mental model for this domain concept. Do NOT use for implement the algorithm we already decided on. Do NOT use for choose a testing strategy for this feature.Stars: 3Updated Claude CodeCodexUnverifiedInstall
problem-framingjacob-balslev/skill-graphUse when a team is converging on solutions before agreeing on the problem, when a brief reads as a feature request, when symptoms and root needs are tangled, or when assumptions need surfacing before design work proceeds. Do NOT use for code-level bug triage, runtime failure diagnosis, or root-cause analysis of system errors — those are engineering investigation tasks, not design problem framing. Do NOT use for Find the bug causing the 500 error in the checkout endpoint. Do NOT use for Why is the test suite flaky on CI? Do NOT use for Classify whether this agent request is high-risk before executing.Stars: 3Updated Claude CodeCodexUnverifiedInstall
problem-locating-solvingjacob-balslev/skill-graphUse 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.Stars: 3Updated Claude CodeCodexUnverifiedInstall