Skip to content

Explore skills

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

Showing 47341–47370 of 61237 skills

framework-fit-analysisjacob-balslev/skillsUse when choosing, replacing, or justifying a framework, library, SDK, runtime, database, UI kit, agent tool, or platform by fit: constraints, quality attributes, team skill, evidence, ecosystem maturity, maintenance health, migration cost, operability, performance, security, supply-chain posture, AI/codegen readiness, lock-in, reversibility, and exit cost. Do NOT use for routine dependency hygiene (use `dependency-architecture`), documenting an accepted decision (use `architecture-decision-records`), or framework-specific implementation work.Stars: 2Updated Claude CodeCodexUnverifiedInstall
state-machine-modelingjacob-balslev/skillsUse when modeling lifecycle states, transitions, guards, events, side effects, invalid states, retries, statecharts, and state invariants for workflows or domain objects. Do NOT use for broad event discovery (use `event-storming`), database schema design (use `entity-relationship-modeling`), frontend state-location decisions (use `state-management`), or observability instrumentation after the lifecycle already exists (use `observability-modeling`).Stars: 2Updated Claude CodeCodexUnverifiedInstall
system-interface-contractsjacob-balslev/skillsUse when defining or reviewing contracts between systems, modules, services, agents, jobs, events, APIs, or teams: ownership, inputs, outputs, invariants, compatibility, errors, idempotency, and versioning. Do NOT use for REST resource design alone (use `api-design`), async event contract detail (use `event-contract-design`), database schemas (use `entity-relationship-modeling`), or post-failure debugging (use `debugging`).Stars: 2Updated Claude CodeCodexUnverifiedInstall
canonical-repo-structurejacob-balslev/skillsUse when organizing or cleaning a project/repository so every script, command, prompt, doc, generated artifact, compatibility shim, and legacy path has one canonical home under version control. Covers owner selection, repo-boundary verification, generated-vs-authored separation, duplicate implementation cleanup, compatibility-shim registration, delete-to-git-history discipline, timestamped changelog explanations, and path-limited commits in the owning repo. Do NOT use for ordinary branching/rebase/tag strategy alone (use `version-control`), behavior-preserving code restructuring alone (use `refactor`), documentation-sync routing alone (use `doc-updater`), or controlled category taxonomy design alone (use `taxonomy-design`).Stars: 2Updated Claude CodeCodexUnverifiedInstall
ci-cd-pipelinesjacob-balslev/skillsDesigning continuous integration and continuous delivery pipelines that turn every commit into a verified, releasable artifact and move it safely toward production. Covers the CI/CD distinction (integration vs delivery vs deployment), the pipeline as a staged graph of fast-to-slow gates, trunk-based integration and short-lived branches, build-once/promote-the-same-artifact discipline, hermetic and reproducible builds, dependency and layer caching for fast feedback, the test pyramid mapped onto pipeline stages, required status checks and branch protection, quality and security gates (lint, type-check, SAST, dependency/SCA scanning, license checks) as blocking vs advisory, artifact and container registries with immutable versioning and provenance, environment promotion (build → test → stage → prod), deployment strategies the pipeline triggers (blue-green, canary, rolling, feature-flag-gated), pipeline secrets and least-privilege CI credentials (OIDC over long-lived tokens), DORA delivery metrics (deployment frequency, lead time, change-failure rate, MTTR), flaky-test quarantine, pipeline observability, and rollback/auto-revert on failed gates. Stack-agnostic across GitHub Actions, GitLab CI, Jenkins, CircleCI, and equivalents.Stars: 2Updated Claude CodeCodexUnverifiedInstall
debuggingjacob-balslev/skillsUse 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.Stars: 2Updated Claude CodeCodexUnverifiedInstall
diagnosisjacob-balslev/skillsUse when facing an unknown software failure, when symptoms point to different root causes, or when an initial debugging attempt has not converged. Provides a triage-first diagnostic routing framework: classify the failure, collect the right evidence, choose a technique, track confidence, and escalate when stuck. Do NOT use for executing scientific debugging after triage (use `debugging`), code-quality review (use `code-review`), or proactive observability setup.Stars: 2Updated Claude CodeCodexUnverifiedInstall
doc-updaterjacob-balslev/skillsEnforces the documentation-sync discipline: every code or behavior change ships its documentation in the SAME commit, never after. Provides the five-step workflow — diff the change, route each changed file to the doc that OWNS that behavior (document by ownership, not convenience), update each owning doc, verify the update actually landed, and report what was changed — plus the doc-type-purity and stale-reference gates that keep a docs corpus from drifting as code moves. Use at the pre-commit step of any task that changes code, when a change touches several docs, when renaming or deleting something that is referenced elsewhere, or whenever you are unsure which doc owns a change. Do NOT use for how to WRITE good documentation prose or pick a doc's Diátaxis type (that is a documentation-authoring skill), for choosing clear names (use `naming-conventions`), or for the broad cross-domain quality catalog (use `best-practice`).Stars: 2Updated Claude CodeCodexUnverifiedInstall
experimentationjacob-balslev/skillsDesigning, running, and interpreting controlled experiments to decide whether a change is genuinely better — online A/B tests, randomized controlled trials, and offline hypothesis tests. Covers hypothesis framing, randomization and unit-of-assignment, sample-size and statistical-power calculation, metric design (primary, guardrail, invariant, and the overall evaluation criterion), variance reduction (CUPED/CUPAC) for sensitivity, significance testing and confidence intervals, sequential and anytime-valid testing for the peeking problem, multiple-comparison correction, the trust checklist led by sample-ratio-mismatch, interference-aware designs (cluster and switchback), long-term holdouts and reverse experiments, bandit/adaptive-allocation boundaries, experiment ethics and blast-radius limits, quasi-experimental fallbacks when randomization is infeasible, and the validity threats that quietly invalidate results (novelty and primacy effects, interference/SUTVA violations, Simpson's paradox, and survivorship).Stars: 2Updated Claude CodeCodexUnverifiedInstall
merge-queuejacob-balslev/skillsUse 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: 2Updated Claude CodeCodexUnverifiedInstall
methodicaljacob-balslev/skillsEnforces disciplined, complete, evidence-backed execution for tasks where honesty and coverage matter more than brevity: audits, diagnostic reports, tracked-task creation from findings, acceptance-criteria verification, research briefs, and any enumerated output that later work will depend on. Teaches 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, and delegation-as-proof — and the structural countermeasures: pre-task scope declaration, count-preserving enumeration, step-level evidence receipts, externally grounded critique, provenance labels, explicit partial/completeness receipts, and runtime enforcement where available. Do NOT use for choosing the shortest task route (use `task-path-optimization`), broad artifact-quality standards (use `best-practice`), result scoring (use `evaluation`), the compact pre-output enforcement gate (use `no-cutting-corners`), or compression after complete enumeration (use `summarization`).Stars: 2Updated Claude CodeCodexUnverifiedInstall
methodologyjacob-balslev/skillsUse 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`).Stars: 2Updated Claude CodeCodexUnverifiedInstall
naming-conventionsjacob-balslev/skillsUse 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).Stars: 2Updated Claude CodeCodexUnverifiedInstall
no-cutting-cornersjacob-balslev/skillsEnforces five non-negotiable quality pillars that counter the shortcuts an agent takes under training pressure: 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 individually verified; docs ship with the change), enrichment ('improve' means add capability, never trim), and anti-shortcut (exhaust deterministic lookup before guessing; findings demand action, not just filing). Use when reviewing any enumerated output for completeness, when an agent claims something works without evidence, when marking a task done, when asked to 'improve' or 'clean up' anything, or when findings are filed without being acted on. Do NOT use for the deep explanatory model of WHY completeness fails or the step-level execution mechanics (use `methodical`), for the cross-domain quality-standards catalog like OWASP/WCAG/SOLID (use `best-practice`), for scoring whether a result is good enough (use `evaluation`), or for compression after a complete enumeration exists (use `summarization`).Stars: 2Updated Claude CodeCodexUnverifiedInstall
prioritizationjacob-balslev/skillsThis 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: 2Updated Claude CodeCodexUnverifiedInstall
problem-approach-routerjacob-balslev/skillsUse 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.Stars: 2Updated Claude CodeCodexUnverifiedInstall
problem-locating-solvingjacob-balslev/skillsUse 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.Stars: 2Updated Claude CodeCodexUnverifiedInstall
refactorjacob-balslev/skillsUse when reorganizing existing code without changing external behavior — extracting functions, reducing duplication, renaming for clarity, splitting modules, or tightening structure. Covers behavior preservation, duplication reduction, decomposition, naming improvements, structural reorganization, and before/after verification. Do NOT use for bug investigation, adding new product behavior, or writing documentation (even when the docs describe the refactored code).Stars: 2Updated Claude CodeCodexUnverifiedInstall
spec-driven-developmentjacob-balslev/skillsUse 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`).Stars: 2Updated Claude CodeCodexUnverifiedInstall
task-path-optimizationjacob-balslev/skillsThis skill provides decision frameworks for choosing the optimal execution path before starting work: plan-vs-act gates, agent architecture selection (chaining, routing, parallelization, orchestrator-worker, evaluator-optimizer), scope management heuristics, critical-path analysis across task networks, and context budget awareness. Use when deciding how to approach a task (plan first vs act immediately), decomposing complex work into parallelizable subtasks, choosing between subagent patterns, or when a task has failed twice and needs a fresh approach. Do NOT use for executing the chosen plan (use task-execution), debugging failures (use troubleshooting or diagnosis), or tool-level efficiency (use tool-call-strategy).Stars: 2Updated Claude CodeCodexUnverifiedInstall
version-controljacob-balslev/skillsUse when designing or maintaining the shape of a repository's git history — choosing a branching model, deciding rebase vs merge, sizing commits, linking commits to tracker tickets, tagging releases, running parallel work across worktrees, and resolving the merge conflicts that arise from any of the above. Covers trunk-based development, short-lived feature branches, atomic commit discipline, linear-history conventions (rebase + squash), release tagging with annotated tags and SemVer, hotfix flows from tags, and worktree lifecycle for parallel agents or contributors. Do NOT use for the words inside the commit message (Conventional Commits format, identifier naming — use `naming-conventions`), for chasing a release-pipeline failure (use `debugging`), or for reviewing a PR's content (use `code-review`).Stars: 2Updated Claude CodeCodexUnverifiedInstall
shotgunadamalshoomary/shotgunRun the shotgun handoff system in this project, so any agent can resume work another one stopped. Use for setting up the handoff files in a new project, taking over queue work from another agent or another session, saving progress before a new chat, archiving a finished round of work, reporting queue status, or updating shotgun. Triggers on "shotgun", "set up handoff", "continue the queue", "save before a new chat", "finish this round", "what is next in the plan", "take over this project".Stars: 2Updated Claude CodeCodexUnverifiedInstall
fidelity-translatorTasdax123/claude-fidelity-translatorStars: 2Updated Claude CodeCodexUnverifiedInstall
kochabbtmoriarty/kochabKochab, a personalized resume-based job-search assistant that runs a recurring scan and everything downstream of it. Use when the user wants to start or run a job search, shares a resume, or says "set up my job scan," "find roles that fit my resume," or "what should I apply to." Also use to tailor a resume, draft a cover note or application email, build a story bank, make a study plan for a gap ("what should I study," "how do I qualify for [role]"), prep for an interview, track the pipeline ("I applied to," "where does my search stand"), keep the search moving ("should I follow up," "I'm not interested in [role]"), get stage guidance or references, handle offers and negotiation ("I got an offer"), recover from a rejection or withdraw cleanly, adjust the coaching dial, or use the network ("do I know anyone at [employer]"). It drafts materials and tracks the whole search from discovery to offer; the user always sends.Stars: 2Updated Claude CodeCodexUnverifiedInstall
opportunity-briefbtmoriarty/kochabResearch a company and a specific role, then produce an honest brief on whether it is worth pursuing. Use this whenever the user mentions a recruiter reaching out, a job posting they found, a company someone told them about, or a role they are weighing. Triggers on "a recruiter contacted me," "should I apply to," "what do you know about [company]," "look into this company," "is this role real," "assess this posting," "vet this opportunity," "a friend mentioned a job at," or when the user pastes a job description, recruiter email, or LinkedIn InMail. Also triggers on "compare these two roles" and "what should I ask the recruiter."Stars: 2Updated Claude CodeCodexUnverifiedInstall
roadmap-interviewbtmoriarty/kochabRun a short product-discovery interview with a user of Kochab to surface what they actually need, then turn it into structured roadmap input. Use when someone says "interview me about features," "run the roadmap interview," "I have feedback on the tool," "what should this tool do next," or when a maintainer wants to gather feature ideas from a user. Produces per-user notes plus an append to a shared feature backlog, so requests that recur across users rise to the top.Stars: 2Updated Claude CodeCodexUnverifiedInstall
pmcoe-pmp-tutorpmcoe-ai1/pmp-tutor-skillPMP / CAPM / PMI-ACP / PMI-CP study companion built by PMCOE LLC — a PMI Authorized Training Partner. Use when the user asks about the Project Management Professional (PMP) certification exam, the Certified Associate in Project Management (CAPM), PMI-Agile Certified Practitioner (PMI-ACP), or PMI Construction Professional (PMI-CP). Covers the 2021 Exam Content Outline, eligibility requirements, scenario-based question practice, the 50/50 predictive-vs-agile mix, GI Bill funding (Chapter 31 / Chapter 33), WEAMS verification for veterans (facility code 46P05243), and PMI Authorized Training Partner standards. Skip for unrelated project management tooling questions (Asana, Jira, Microsoft Project), generic agile-methodology debates without an exam-prep angle, software engineering certifications, or non-PMI credentials (Six Sigma, ITIL, PRINCE2, CISSP).Stars: 2Updated Claude CodeCodexUnverifiedInstall
academic-prose-auditPoisoneddiety/claude-skills-for-humanitiesAudit and revise drafted academic legal prose for propositional compression, mechanical sentence rhythm, and AI register, while preserving formal academic voice and OSCOLA conventions. Fixes the defect where too much meaning is left for the reader to reconstruct. Use this on any draft paper, response paper, seminar piece, or long note before submission, and whenever the user says a draft reads mechanically, sounds like AI, or needs humanising. Do NOT use for first drafts, exam answers, or casual chat.Stars: 2Updated Claude CodeCodexUnverifiedInstall
doctrinal-explainerPoisoneddiety/claude-skills-for-humanitiesExplain a legal doctrine, concept, case, statutory provision, or assigned reading in full depth for note-making and comprehension. Produces the reasoning a summary leaves out — the problem the doctrine solves, the facts that shaped it, the competing formulation, and the boundary conditions. Use this whenever the user asks to explain, unpack, walk through, or make notes on a legal concept, reading, or judgment, even if they just say "explain X". Do NOT use for exam answers, drafting, or research.Stars: 2Updated Claude CodeCodexUnverifiedInstall
india-legal-researchPoisoneddiety/claude-skills-for-humanitiesResearch Indian law online — case law, statutes, regulatory material, recent doctrinal developments, or academic literature. Enforces a source hierarchy, targeted search operators, currency checks, and per-citation retrieval status so nothing unverified reaches the page. Use this whenever the user asks about Indian cases, statutes, sections, judgments, regulators (SEBI, RBI, MCA, CCI, IBBI), law reform, or wants sources for a paper or seminar — even if they do not say "research". Do NOT use for non-Indian law or for drafting prose.Stars: 2Updated Claude CodeCodexUnverifiedInstall