#SkillRepo stars
- 2401Skill Refactorjscraik/Agent-SkillsAnalyzes bounded skill evidence, classifies root causes, and recommends a lifecycle lane such as keep, observe, improve through Skill Factory hardening, merge with approval, or retire with approval. Use when a skill is not working, a skill is not triggering correctly, evals or Tessl disagree, repeated failures need debugging, or skill performance issues need evidence-backed repair handoff items.9
- 2402Sy Execution Planjscraik/Agent-SkillsPlan how to implement one approved slice, including file targets, validation gates, rollback, and proof lanes. Use when a slice spec is accepted and the user needs the implementation order before code changes.9
- 2403Talk Farley Vibe Coding Best We Can Dojscraik/Agent-SkillsSummarizes, explains, and answers questions about Dave Farley's talk 'Vibe Coding — Is this really the best we can do?', including key arguments, frameworks, and recommendations. Provides verbatim-cited explanations of Farley's three properties of programming languages, audits AI-coding setups against his three-problems framework, drafts BDD-style executable specifications, and outlines his continuous-delivery approach to AI-driven development. Use when the user asks about Dave Farley's talk on vibe coding, agentic programming, AI-generated tests, BDD-style executable specifications, problem-s9
- 2404Talk Foxwell Reinvention Dev Teamjscraik/Agent-SkillsAssists with questions about Hannah Foxwell's talk 'The Reinvention of the Dev Team'. Use when a user asks about Foxwell's arguments on agentic software development, engineering team composition, AI-driven velocity, dev-to-PM ratios, the three anchors (build something worth building, speed requires safety, people matter), the Keep/Trash/Try inventory, on-call sustainability, broken-comb skills, or wants to audit their own team against Foxwell's framework.9
- 2405Talk Martinelli Spec Driven Developmentjscraik/Agent-SkillsAnswers questions about, summarises key insights from, and helps apply concepts from Simon Martinelli's talk "Lessons from Spec-driven Development" — providing verbatim-grounded explanations, audits, and artifact drafts. Use when the user asks about the AI Unified Process, system use cases as specs (vs user stories), self-contained systems vs microservices, skills/MCP servers/guardrails, AI-assisted ERP modernization, drift management, how architecture style impacts AI coding agents, or applying his spec-driven approach to current work.9
- 2406Talk Podjarny Skills Are the New Codejscraik/Agent-SkillsAssists with questions about Guy Podjarny's talk "Skills are the new Code". Use when the user wants to understand, apply, audit, or explore frameworks from this keynote — including the five engineering disciplines for skills (static analysis, evals, security testing, dependency management, observability), the three challenge buckets, the agentic development stack, or concepts like skill authoring, context engineering, agent harnesses, and skill quality scoring.9
- 2407Talk Sloan Harness Engineering Beyond Codejscraik/Agent-SkillsSummarizes Rob Sloan's harness-engineering talk and creates safe design artifacts for agent context beyond code: product-intent packets, design constraints, acceptance criteria, context ownership, and review gates. Use when the user asks about making non-code context agent-ready or improving AI work with product/design intent.9
- 2408Typescriptjscraik/Agent-SkillsUse when authoring or reviewing TypeScript code that requires strict type safety, explicit module contracts, and predictable runtime boundaries.9
- 2409Uv Python Project Setupjscraik/Agent-SkillsCreate, repair, and validate uv Python project setup. Use when initializing Python apps or libraries, managing uv dependencies, virtual environments, or CI-ready uv workflows.9
- 2410Vacationrental Vibe Codermsg2ai/vacationrental-team-skillsActs as an AI Vibe Coder for a vacation-rental property management office — a fluent web developer who ships the direct-booking site, brand site, owner portal, and lead-capture pages fast. Use this skill when someone needs to build or update a direct-booking website, ship a per-property landing page, deploy a lead-capture page for new owners, scaffold a Next.js app for a vacation-rental brand, push to GitHub, or deploy to Vercel. Triggers on phrases like "build the direct-booking site", "ship a property landing page", "deploy to Vercel", "spin up a Next.js site", "create the owner portal", "bu5
- 2411Pilot API GatewayTeoSlayer/pilot-skillsExpose local APIs to the Pilot Protocol network. Use this skill when: 1. You need to expose local APIs to remote Pilot agents 2. You want to provide API access without public internet exposure 3. You're building API-based agent services on Pilot Do NOT use this skill when: - APIs are already publicly accessible - You need HTTP-only proxying (use pilot-http-proxy instead) - The daemon is not running9
- 2412Pilot API Gateway Manager SetupTeoSlayer/pilot-skillsDeploy an API gateway management system with 4 agents. Use this skill when: 1. User wants to set up API gateway management with service discovery, routing, auth, and monitoring 2. User is configuring agents for API request routing, rate limiting, or backend health tracking 3. User asks about API gateway pipelines, service registries, or request authentication workflows Do NOT use this skill when: - User wants a single load balancer (use pilot-load-balancer instead) - User wants to verify a single token (use pilot-verify instead) - User only needs health checks (use pilot-health instead)9
- 2413Pilot SandboxTeoSlayer/pilot-skillsGet a Pilot Protocol node online in a network-restricted agent sandbox (Meta Muse and similar VMs: no outbound UDP, poisoned DNS, egress only via an authenticating HTTPS proxy whose credentials rotate). scripts/pilot-up.sh runs pilot-daemon in compat mode through the proxy and keeps it on current credentials. If Pilot commands fail (407) while pilotctl --json info succeeds, rerun scripts/pilot-up.sh from a fresh shell. Use this skill when: 1. Pilot commands fail (407, connection errors) while pilotctl --json info succeeds 2. Setting up Pilot in Meta Muse, or the VM restarted and the node is of9
- 2414Codebase DesignPanPanFR/oh-my-openkiloUse when designing or improving a module's interface, finding deepening opportunities, deciding seam placement, or making code more testable - deep-module vocabulary9
- 2415Engage SDK IntegrationPanPanFR/oh-my-openkiloHelps developers integrate, debug, and resolve Play Engage SDK implementation issues. Use when adding Engage SDK support, generating publishing code, mapping data classes to entities, or fixing SDK-related errors.9
- 2416GraphifyPanPanFR/oh-my-openkiloUse for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.9
- 2417JuryPanPanFR/oh-my-openkiloScore any website the way an Awwwards jury would, from evidence alone. Screenshots every page type on desktop, a throttled phone and reduced motion, measures LCP, CLS, FPS, axe, keyboard focus and hover feedback, audits SEO and metadata, then a fresh critic that never sees the code scores Design, Usability, Creativity, Content and the six developer areas, with a ranked fix list. Use when someone asks to review, critique, score, rate or roast a website, portfolio or landing page, asks whether a site is good enough for Awwwards or Site of the Day, or wants design QA of a live URL or a local buil9
- 2418Play Billing Library Version UpgradePanPanFR/oh-my-openkiloUse this skill when upgrading or migrating an Android project from any legacy Google Play Billing Library (PBL) version to the latest stable version of PBL.9
- 2419Pwa DevelopmentPanPanFR/oh-my-openkiloProgressive Web Apps - service workers, caching strategies, offline, Workbox9
- 2420Rust Best PracticesPanPanFR/oh-my-openkiloGuide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership patterns, (4) implementing error handling with Result types, (5) optimizing Rust code for performance, (6) writing tests or documentation for Rust projects.9
- 2421Rust PatternsPanPanFR/oh-my-openkiloIdiomatic Rust patterns and best practices for readable, safe, maintainable Rust: ownership, borrowing, API design, enums/traits, error handling, iterators, concurrency, dynamic dispatch/plugins, and low-level/offensive patterns. Use when writing or reviewing `.rs` code, refactoring crates, porting non-idiomatic code into Rust, designing Rust APIs, or building Rust tooling that needs runtime composition or RE-resistance.9
- 2422Rust PerformancePanPanFR/oh-my-openkiloRust performance workflow: benchmark and profile first, identify hotspots, reduce allocations and contention, improve data layout, tune release profiles, and verify gains with repeatable evidence. Use only after you have a real Rust performance symptom, regression, or hotspot in `.rs` code.9
- 2423Rust TestingPanPanFR/oh-my-openkiloRust testing patterns for unit, integration, async, doc, property, snapshot, fuzz, and benchmark-adjacent tests. Use when writing or reviewing tests for `.rs` code, reducing flakiness, designing fixtures/fakes, improving CI confidence, hardening `unsafe`/FFI/parsers with Miri and sanitizers, or testing concurrent atomics and locks with Loom.9
- 2424Architectflurdy/agent-skillsArchitecture and implementation planning gate for complex or high-blast-radius work. Produces evidence-backed decisions, reviewable slices, acceptance evidence, and conditional human review ownership without editing code.9
- 2425Breakdownflurdy/agent-skillsRead-only overview for one Jira ticket, grounded in relevant code: Problem, Solution, Steps, and Open questions. Use before implementation; recommend architect for complex or high-blast-radius work.9
- 2426Clean Codeflurdy/agent-skillsFormat, lint, and fix all warnings across the entire codebase — including test files and pre-existing issues.9
- 2427Codeless Connectorsdstreefkerk/claude-skillsUse before writing any Microsoft Sentinel connector ARM template, DCR, KQL transform, or createUiDefinition.json. Provides the complete CCF (Codeless Connector Framework) reference for RestApiPoller, Push, and GCP connector types — including escaping rules, authentication, pagination, UI definitions, and deployment gotchas. Also use when debugging connector deployment failures or reviewing existing CCP templates.5
- 2428Developflurdy/agent-skillsLoad before authorized code changes: features, fixes, refactors, tests, and mechanical edits, including discussion-to-coding transitions. Read separately from edits. Skip read-only requests and implementation already owned by a specialist.9
- 2429Implement Solutionflurdy/agent-skillsUse before non-trivial coding with clear requirements: interacting behavior, state/error paths, or local design trade-offs. Also use when ongoing implementation becomes complex. Premium implementation; skip mechanical edits and unresolved diagnosis.9
- 2430Pair Programmingflurdy/agent-skillsOpt-in conversational pairing when the user explicitly asks to pair: the agent writes authorized code in small agreed steps, discussing decisions and results throughout. Not for ordinary implementation requests.9
- 2431Powershelldstreefkerk/claude-skillsEnterprise PowerShell coding standards. Use when writing, reviewing, or generating any PowerShell code, creating PS1 scripts or functions, debugging PowerShell, or asked to help with PowerShell. Enforces best practices for structure, error handling, security, performance, and output patterns.5
- 2432Linear Groom Ticketadelrioj/claude-skillsUse when a Linear ticket needs to be made ready to work on, or judged not worth working on. Analyses one ticket across four dimensions — whether its claims hold in the code, whether it is complete against the team template, whether it duplicates another ticket, and whether it is implementable — then proposes a corrected description and applies it to Linear only after you approve. Triggers on: groom this ticket, prepare NBS-123, is this ticket ready, revisa este ticket, ¿este ticket está listo?, deja el ticket listo para trabajar, candidato a borrar, dedupe this ticket.5
- 2433Linear Spec Ticketadelrioj/claude-skillsUse when a Linear ticket has been groomed and now needs a design spec written onto it so work can start — drafts the spec from the ticket and the codebase and uploads it to the ticket as a file attachment. Also refreshes that attachment after /spec-review-codex hardens the spec. Never changes the ticket state. Triggers on: add a spec to this ticket, write the spec for NBS-123, deja el ticket listo para trabajar, añade spec al ticket, adjunta la spec al ticket, prepare this ticket for work, spec this ticket, refresh the spec attachment, re-upload the hardened spec, linear-spec-ticket.5
- 2434Linear Triage Ticketadelrioj/claude-skillsUse when a Linear ticket needs a priority, a complexity rating and an effort estimate backed by evidence from the code — reads the repo the ticket is about, runs two read-only codex analysts, and after your explicit approval writes the priority, the estimate (when provable) and one living rationale comment to Linear. Triggers on: triage this ticket, size NBS-123, prioritize this ticket, estimate this ticket, how big is this ticket, how urgent is this, triaje este ticket, prioriza el ticket, estima el esfuerzo, linear-triage-ticket.5
- 2435Plan to Dexadelrioj/claude-skillsUse when running an already-hardened Superpowers implementation plan through the dex orchestrator (codex backend). Triggers on: convert plan to dex, plan to dex, dex from plan, run plan with dex, plan-to-dex.5
- 2436Review Codebaseadelrioj/claude-skillsUse to run a whole-system adversarial audit of the current repo across three lenses at once — codebase (defects, incoherences, affordance gaps), docs (drift, structure, coverage), and process (end-to-end workflow dead ends). Dispatches three fresh Claude subagents in parallel, each writing a ranked findings report to docs/audits/, then offers an optional fix pass on CRITICAL findings. Triggers on: review codebase, audit codebase, audit this repo, adversarial audit, codebase audit, docs audit, process audit, fable audit, three reviews, full audit, whole-system review, find everything wrong.5
- 2437Spec Review Codexadelrioj/claude-skillsUse when a brainstorming design spec has been written and needs adversarial review before implementation planning, using OpenAI Codex as the independent reviewer. Requires the codex CLI. Triggers on: spec review codex, codex spec review, review spec with codex, codex review, review spec, spec review.5
- 2438Spec Review Localadelrioj/claude-skillsUse when a brainstorming design spec has been written and needs adversarial review before implementation planning, using a local model served by LMStudio (via the pi CLI) as the independent reviewer. Works offline — no hosted API needed. Triggers on: spec review local, local spec review, review spec locally, lmstudio review, review spec, spec review.5
- 2439Acquire Codebase Knowledgesandbaseai/workbuddy-skillUse when the user asks to map, document, or onboard into an existing codebase and needs evidence-backed architecture, structure, conventions, integrations, testing, and concerns documentation.9
- 2440API Design Principlessandbaseai/workbuddy-skillUse when designing, reviewing, documenting, versioning, or migrating REST or GraphQL APIs and their client, security, performance, and compatibility contracts.9
- 2441API Documentationsandbaseai/workbuddy-skillUse when creating, editing, restructuring, or reviewing a service API document; keep operations, requests, responses, errors, types, routes, examples, and conventions precise and aligned with the authoritative contract.9
- 2442API Resilience Engineeringsandbaseai/workbuddy-skillUse when designing, implementing, reviewing, testing, or diagnosing API timeouts, retries, idempotency, rate limits, concurrency limits, circuit breakers, bulkheads, backpressure, load shedding, or ambiguous outcomes.9
- 2443Architectural Decision Recordsandbaseai/workbuddy-skillUse when documenting an important architecture or technology decision with context, constraints, alternatives, trade-offs, evidence, ownership, status, and a durable review path.9
- 2444Architecture Blueprint Generatorsandbaseai/workbuddy-skillUse when analyzing an authorized codebase to produce an evidence-backed architecture blueprint, dependency map, diagrams, implementation patterns, and evolution guidance.9
- 2445Architecture Decisionsandbaseai/workbuddy-skillUse when a technical choice changes system boundaries, contracts, quality attributes, data, or operations and has meaningful reversal cost.9
- 2446Architecture Decision Recordssandbaseai/workbuddy-skillUse when making, reviewing, or maintaining a significant technical or architecture decision that needs durable context, alternatives, consequences, and follow-up evidence.9
- 2447Architecture Friction Scansandbaseai/workbuddy-skillUse when assessing a codebase for evidence-backed opportunities to deepen shallow modules, improve locality and AI navigability, or reduce seam and testing friction before choosing a refactor.9
- 2448Architecture Patternssandbaseai/workbuddy-skillUse when designing or refactoring a backend module or service with Clean, Hexagonal, Onion, or Domain-Driven Design patterns; make boundaries, dependencies, ports, adapters, and test seams explicit before changing code.9