Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 38881–38910 of 48272 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| invalid-subjectjacob-balslev/skill-graphNegative fixture for the gate-conformance suite: valid v8 frontmatter except `subject` is set to a value outside the closed twelve-shelf enum. Activate only inside test-gate-conformance.js to prove the structural lint gate FAILS on an out-of-enum subject. Do NOT use as a production skill. | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| missing-scopejacob-balslev/skill-graphNegative fixture for the gate-conformance suite: identical to the minimal valid fixture except the required `scope` field is omitted. Activate only inside test-gate-conformance.js to prove the structural lint gate FAILS when a required protocol field is absent. Do NOT use as a production skill. | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| truth-source-brokenjacob-balslev/skill-graphNegative fixture for the gate-conformance suite: valid v8 frontmatter with a complete grounding block, except one declared truth source path points at a file that does not exist. Activate only inside test-gate-conformance.js to prove the truth/drift gate reports BROKEN. Do NOT use as a production skill. | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| missing-audit-status-verdictsjacob-balslev/skill-graphWarning fixture for the gate-conformance suite: the sidecar is schema-valid but omits the four durable Audit Status verdict fields. Activate only inside test-gate-conformance.js to prove lint warns without failing. Do NOT use as a production skill. | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| comprehension-fulljacob-balslev/skill-graphUse as the v8-conformant fixture exercising the full Understanding surface — the five flat top-level fields (mental_model, purpose, concept_boundary, analogy, misconception) in SKILL.md frontmatter, paired with comprehension_state: present in the audit-state.json sidecar. Activate this skill when verifying that the cross-file lint accepts the flat Understanding fields when the sidecar declares comprehension_state: present. Do NOT use as a production skill (use a real capability skill from the canonical library). | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| minimal-capabilityjacob-balslev/skill-graphUse as the smallest v8-compat capability fixture for skill-graph package tests. Activate this skill when verifying that lint, manifest generation, and routing accept the bare-minimum required frontmatter. Do NOT use as a production skill (use a real capability skill from the canonical library). | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| with-groundingjacob-balslev/skill-graphUse as the minimal v8-conformant project-grounded fixture for skill-graph package tests. Activate this skill when verifying that lint enforces the rule 'non-empty project[] requires grounding' (subject_matter, grounding_mode, truth_sources, failure_modes, evidence_priority). Do NOT use as a production skill (use a real grounded skill from the canonical library). | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| with-relationsjacob-balslev/skill-graphUse as the v8-conformant fixture exercising typed relation predicates (related, suppresses, verify_with, depends_on) using the live schema item shapes. Activate this skill when verifying that lint resolves cross-fixture relation targets without a sibling skills clone. Do NOT use as a production skill (use a real capability skill from the canonical library). | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| content-source-routerjacob-balslev/skill-graphUse when dispatching a content-fetch task across the multiple sources the site reads from — local markdown under `content/`, MDX with React components under `content/mdx/`, and a headless-CMS sync under `lib/cms/`. Activate this skill whenever the task says 'render this content' or 'where does this post come from' without naming a specific source, or when adding a new source to the routing surface. Do NOT use for the actual rendering of one source (use the per-source skill — `markdown-post-frontmatter-validation`, an MDX rendering skill, or a CMS-sync skill) or for chasing a specific routing bug (use debugging). | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| image-optimization-pipeline-configjacob-balslev/skill-graphUse when authoring or reviewing the build-time image pipeline config — defining responsive srcset breakpoints, picking output formats (AVIF / WebP / JPEG fallback), tuning compression quality per format, and ensuring the pipeline never produces a lossy artifact for source PNGs with transparency. Activate this skill whenever the task touches `lib/images/pipeline.config.ts`, `scripts/build-images.ts`, or any code path that resizes or recompresses content images. Do NOT use for runtime image rendering choices (use a frontend skill) or for chasing a specific build failure (use debugging). | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| link-rot-detectionjacob-balslev/skill-graphUse when authoring or reviewing a periodic-scan job that walks every external link in a markdown content set and flags 404s, redirects to unrelated content, and connection failures. Activate this skill whenever the task says 'check our links' or mentions a link-rot scan, broken-link audit, or link-health report. Do NOT use for live runtime link checking inside the rendered page (use a frontend a11y / UX skill) or for chasing a specific broken-link incident from a user report (use debugging). | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| markdown-post-frontmatter-validationjacob-balslev/skill-graphUse when authoring or reviewing the frontmatter of a markdown post — checking required fields (title, date, slug, tags), validating against the content schema in `lib/content/schema.ts`, catching ambiguous date formats or tags not in the controlled vocabulary, and ensuring the slug matches the file path. Activate this skill whenever the task touches files under `content/posts/**/*.md`, the `parsePostFrontmatter()` helper, or any code path that reads YAML frontmatter from a content file. Do NOT use for general YAML schema design (use a generic schema-design skill) or for chasing a specific build-time validation failure (use debugging). | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| migrate-posts-to-v2-frontmatterjacob-balslev/skill-graphUse when migrating every existing post in `content/posts/**/*.md` to the v2 frontmatter schema — adding the new required `summary` field, normalizing `tags` to the controlled vocabulary, converting bare-date `date` strings to ISO 8601 with timezone, and re-validating every post against the v2 schema before the next build runs. Activate this skill whenever the task references migration `0007-frontmatter-v2`, the v2 frontmatter rollout, or asks how to safely change a required-field set across a populated content tree without breaking the build. Do NOT use for unrelated migrations (use a generic content-migration skill or write a fresh one) or for general schema-design questions (use a schema-design skill). | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| migrate-orders-to-canonical-schemajacob-balslev/skill-graphUse when running migration 0004 that normalizes the orders table from a Stripe-specific shape (stripe_session_id, stripe_customer_id as top-level columns) to a canonical provider-agnostic shape (provider, provider_order_id, provider_customer_id). Covers the four-phase safe migration procedure — add nullable columns, backfill from existing data, validate, drop legacy columns — and the RLS policy update that must accompany the column rename. Do NOT use for unrelated schema migrations (write a fresh skill anchored to that migration's number), for designing a new canonical schema from scratch, or for the ongoing orgQuery access pattern (use postgres-rls-pattern). | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| nextjs-server-action-validationjacob-balslev/skill-graphUse when writing a Next.js Server Action that accepts user-submitted form data, mutation parameters, or any client-originated input. Every Server Action is a public HTTP endpoint regardless of how it is called — validate with Zod and check authentication as the first two operations before touching the database. Do NOT use for GET route handlers or Server Components that fetch data (those have no user-supplied input); do NOT use for Stripe webhook handlers (use stripe-webhook-signature-verification instead). | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| payment-provider-routerjacob-balslev/skill-graphUse when dispatching a verified payment event (Stripe webhook or future provider) to the correct downstream handler based on event type. Routes `checkout.session.completed` to subscription provisioning, `invoice.payment_failed` to dunning logic, and `customer.subscription.deleted` to cancellation. Do NOT use for signature verification of the incoming event (use stripe-webhook-signature-verification first) or for the actual subscription database writes (use the per-handler skill or postgres-rls-pattern). | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| postgres-rls-patternjacob-balslev/skill-graphUse when writing or reviewing Postgres queries in a multi-tenant SaaS where every table row must be scoped to a single organization. Enforces the FORCE ROW LEVEL SECURITY + USING + WITH CHECK triple on every tenant-bound table, and wraps application queries in an `orgQuery(orgId)` helper that sets `app.current_org_id` before each statement. Do NOT use for cross-org system queries such as billing cron jobs or admin panels (those bypass RLS intentionally via the service role); use a service-role query wrapper instead. | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| stripe-webhook-signature-verificationjacob-balslev/skill-graphUse when validating incoming Stripe webhook requests in a Node.js or Next.js backend before processing any payment event. Verifies the `stripe-signature` header against `STRIPE_WEBHOOK_SECRET` using Stripe's HMAC-SHA256 scheme, and rejects replays older than 300 seconds. Do NOT use for general HTTP signature validation (use a generic crypto-signature skill), for processing the webhook payload after signature is confirmed (use payment-provider-router), or for Stripe API calls that are not webhook-driven. | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| v3-1-skos-fixturejacob-balslev/skill-graphTest fixture exercising SKOS predicates (related, broader, narrower), routing-layer suppresses, the ADR 0006 split between routing exclusion and disjoint_with (OWL class-disjointness), and the io_contract composition hook. Used by scripts/__tests__/test-v3-1-skos-runtime.js to verify that the manifest generator, lint, and router all recognize the full canonical predicate set. Not a production skill. | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| a11yjacob-balslev/skill-graphUse when building or reviewing interactive UI, forms, navigation, or dynamic content. Covers semantic HTML, keyboard access, focus management, labeling, state-change announcement, and reduced-motion / high-contrast preferences. Do NOT use for color-palette creation, visual branding, feedback-state staging, or prose reading-level accessibility - those belong to `visual-design-foundations`, `interaction-feedback`, and documentation respectively. Do NOT use for rewrite this error message at a 6th-grade reading level. Do NOT use for clean up this accessibility code without changing how it behaves. | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| agent-engineeringjacob-balslev/skill-graphUse when designing or evaluating a production AI agent system, choosing a multi-agent coordination pattern (orchestrator/worker, fan-out, consensus, sequential chain, evaluator/optimizer), diagnosing coordination failures (claim races, silent stalls, context contamination, runaway loops), or auditing whether an agent loop is truly production-ready. Covers the four pillars (architecture and lifecycle, task decomposition, coordination patterns, production reliability), the six reliability requirements (observability, cost budgets, idempotency, failure recovery, safety caps, claim locks), the delegation decision framework with overhead crossover, and the most common anti-patterns. Do NOT use for prompt wording (use `prompt-craft`), per-call tool efficiency (use `tool-call-strategy`), context-stack design within a single agent (use `context-engineering`), or runtime debugging of a deployed system (use `debugging`). Do NOT use for improve this prompt's wording to get better outputs. | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| ai-native-developmentjacob-balslev/skill-graphUse when reasoning about agent autonomy levels, designing auto-improve loops, evaluating AI-generated code quality, or measuring agent productivity in an LLM-assisted codebase. Covers Karpathy's three eras of software (1.0 explicit / 2.0 learned / 3.0 natural-language), the vibe-coding-vs-agentic-engineering distinction, the 0–5 autonomy slider with task-type recommendations, the one-asset / one-metric / one-time-box AutoResearch loop, Software 3.0 productivity metrics, and the documented quality regressions of ungated AI-generated code (the 'vibe hangover'). Do NOT use for choosing a specific autonomy-loop topology (use `agent-engineering`), for the per-prompt authoring discipline (use `prompt-craft`), or for reviewing the AI-generated code that comes out of a Software 3.0 workflow (use `code-review`). Do NOT use for improve this specific prompt for the grader. Do NOT use for review this AI-generated PR for correctness. Do NOT use for design the checkpoint state machine for our loop. | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| ansoff-matrixjacob-balslev/skill-graphUse 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. | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| api-designjacob-balslev/skill-graphUse when designing or reviewing HTTP API surfaces: consumer tasks, audience class, protocol/paradigm fit, resources/actions, route taxonomy, request and response schemas, status codes in context, pagination, filtering, sorting, field selection, idempotency, auth and tenant boundaries, error envelopes, rate-limit signals, versioning, deprecation, discovery, and contract artifacts. Do NOT use for pure HTTP protocol semantics (use `http-semantics`), framework-specific route handler mechanics (use `route-handler-design`), non-HTTP system contracts (use `system-interface-contracts`), async event contracts (use `event-contract-design`), database design (use `entity-relationship-modeling`), inbound provider webhook mechanics (use `webhook-integration`), or post-failure diagnosis (use `debugging`). Do NOT use for define the broader contract between a job, service, and dashboard. Do NOT use for design database tables, foreign keys, and views. | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| architecture-decision-recordsjacob-balslev/skill-graphUse when writing, reviewing, or updating Architecture Decision Records: context, decision, options rejected, consequences, status, supersession, and follow-up verification. Do NOT use for general documentation prose (use `documentation`), code review findings (use `code-review`), or choosing between frameworks before a decision exists (use `framework-fit-analysis`). Do NOT use for write a general README section explaining how this module works. Do NOT use for choose which framework we should use for this project. Do NOT use for review this PR for bugs and regressions. Do NOT use for design the interface contract between these two services. | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| autonomous-loop-patternsjacob-balslev/skill-graphUse when designing, reviewing, or debugging an autonomous AI agent loop: repeated agent execution, completion signals, checkpoints, supervisor respawn, stall detection, safety caps, and human handoff rules. Covers the core loop patterns from simple bounded runs through sentinel-based continuation, checkpoint-resume, and external supervisor loops. Do NOT use for choosing a specific agent product command (use agent-engineering or the product's docs), writing ordinary task instructions (use prompt-craft), or optimizing individual tool calls (use tool-call-strategy). | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| background-jobsjacob-balslev/skill-graphUse when moving slow or failure-prone work out of a request path, designing job queues, retries, checkpoints, progress reporting, cancellation, or worker concurrency. Covers inline-vs-background decisions, queue contracts, state machines, idempotency, retry/backoff, progress signals, worker leases, and user-visible completion reporting. Do NOT use for time-based schedule design (use `cron-scheduling`), live browser transport choice (use `real-time-updates`), or async message schema ownership (use `event-contract-design`). Do NOT use for choose the cron expression for a daily run. Do NOT use for design an SSE or WebSocket browser update channel. Do NOT use for define an event envelope and topic naming standard. Do NOT use for debug why this already-running worker crashed. Do NOT use for model the database schema for the business entity being processed. | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| balanced-scorecardjacob-balslev/skill-graphUse 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). | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| bayesian-reasoningjacob-balslev/skill-graphUse 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. | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |
| bcg-matrixjacob-balslev/skill-graphUse when analyzing product, brand, business-unit, or investment portfolio allocation with the BCG Growth-Share Matrix: market growth, relative market share, stars, cash cows, question marks, dogs/pets, cash generation, invest/harvest/divest/reposition choices, portfolio balance, and modern limitations. Covers defining portfolio units and markets, choosing comparable metrics, plotting quadrants, interpreting cash-flow logic, challenging share-growth assumptions, and handing off to valuation or strategy methods. Do NOT use for product-market growth paths (use ansoff-matrix), macro-environment scanning (use pestel), industry profit-pressure diagnosis (use porters-five-forces), internal/external factor inventory (use swot-tows), durable moat classification (use seven-powers), or quantified option valuation (use expected-value). Do NOT use for Classify growth ideas as market penetration, market development, product development, or diversification. | Stars: 3 | Updated | Claude CodeCodex | Unverified | Install |