frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use when users ask to build web components, pages, or applications.
git-workflow
A skill that outlines best practices for using Git in a collaborative development environment, including branching strategies, commit conventions, and pull request workflows.
project-analysis
A specialist skill that analyses a codebase to understand its structure, dependencies, and architecture. This skill should be used at the start of a new project or when onboarding to an existing codebase.
performance-optimisation
Analyses and optimises performance across frontend, backend and database interactions. Identifies bottlenecks and implements solutions to enhance speed and efficiency.
security-review
A specialist skill for security reviews, threat modeling, and remediation guidance. Use for auth/permissions changes, secrets or PII handling, public endpoints, or dependency upgrades.
testing-strategy
A specialist skill that designs and implements a testing strategy for a codebase. This skill should be used after code development and before code review.
namecheap
Domain registration and management via Namecheap API.
create-script
Transforms content into a voiceover-ready script optimized for Chatterbox TTS. Use when the user provides ANY content for voiceover - URLs, raw text, video scripts, notes, or asks to "create a script" for audio.
voiceover
Generates audio narration from a text file using Chatterbox TTS. Use when the user wants to generate voiceover/audio from ANY text file.
relearning-content
Creates journal entries or project pages for a personal knowledge site. Use when the user wants to write, publish, or add content - journals, projects, or articles about cognitive engineering, productivity systems, or tool-driven growth.
cloudflare-deploy
Deploy the resume app to Cloudflare Pages using the documented build and wrangler steps. Use when deploying, troubleshooting deploys, or updating Pages-related CI configuration.
create-from-template
Create a new app or package from an existing template in the monorepo. Use when adding new apps or packages to the repository.
release-notes-generate
Generate LLM-backed release notes between git tags using the repo release-scripts. Use when asked for changelogs, release notes, or summaries between two tags.
resume-i18n-translate
Extract i18n keys and translate the resume app locales using the existing OpenRouter-based scripts. Use when updating translation keys, adding languages, or re-running translations for dev/apps/resume and its i18next locale files.
resume-pdf-generate
Generate the resume PDF with the existing Puppeteer-based script and blank-page trimming. Use when asked to regenerate the resume PDF, validate print styling, or troubleshoot PDF output in dev/apps/resume.
terraform-infra-ops
Operate and update the Terraform infrastructure in ops/infra, including init/apply flows, formatting, and linting. Use when modifying Cloudflare Pages/R2 resources, updating Terraform state config, or running infra operations.
fix-pr-automation
Work with the automated PR fixer and its CLI, including prompts and workflow configuration. Use when diagnosing failed CI auto-fixes, running the fix-pr CLI locally, or updating the fix-pr prompt or workflow.
service-monitor
Monitor service health at raspberrypi.local:8000. Check service status, add monitored services, view notifications, and manage health check configuration.
network-admin
Manage servers on the local network (ubuntu-box and raspberrypi). Execute commands remotely via SSH, manage services, view logs, and coordinate with other skills.
reverse-proxy
Manage incoming internet traffic and reverse proxy configuration on the home network gateway. Configure Caddy, OAuth2 authentication, fail2ban security, and traffic routing.
kysely-postgres
Write effective, type-safe Kysely queries for PostgreSQL. This skill should be used when working in Node.js/TypeScript backends with Kysely installed, covering query patterns, migrations, type generation, and common pitfalls to avoid.
nitro-testing
Test Nuxt 3 / Nitro applications - both API handlers (real PostgreSQL, transaction rollback) and frontend components (@nuxt/test-utils, mountSuspended).
nuxt-nitro-api
Build type-safe Nuxt 4 applications with Nitro API patterns. Covers validation, fetch patterns, auth, SSR, composables, background tasks, and real-time features.
contribute-skill
Contribute a lesson learned this session back to the gallop-systems/agent-skills repo as a PR. Use when capturing an error→fix, a behavior that contradicted a skill, or a workflow gap the skill didn't cover, and turning it into a generic, public-safe addition to an installed skill.
copier-template
Maintain a Copier project template and propagate updates to generated ("descendant") repos. Covers template anatomy (copier.yml, jinja, tasks), testing template changes, tagging/releasing versions, the automated update-notification PR pattern, and applying copier update in descendants — bringing a repo fully to the latest template version while preserving its app behavior, with conflict resolution an autonomous agent can run end to end.
doctl
Manage DigitalOcean resources with the doctl CLI. Covers auth contexts, App Platform (deployments, logs, env vars/secrets via app specs), mapping a git repo to its app, managed databases, Spaces keys, and droplets.
frontend-design
Apply the team's frontend design conventions across all repos — visual hierarchy, layout, spacing, typography, color usage, component structure, and UX patterns. Use this skill any time you're creating or modifying UI (new page, new component, restyling existing markup) so the result looks and feels consistent with the rest of our apps.
git-github
Git and GitHub (gh CLI) workflows for agents - the branch-to-PR loop, reading PR and CI state, debugging failed GitHub Actions runs, getting unstuck from rejected pushes and rebase messes, gh api recipes, and release flows.
linear
Create, triage, and manage Linear issues at Gallop Systems following the team's workflow conventions — cycle placement, issue templates, project/milestone hierarchy, and project refresh / cycle rebalance procedures. Use whenever the user asks for Linear work (creating issues, planning cycles, refreshing projects) on a Gallop client.
tailwind-v4
Work effectively with Tailwind CSS v4 (the CSS-first model) in a Nuxt/Vite + PrimeVue/Volt stack. Use when editing Tailwind CSS, configuring @theme/@source/@import, setting up dark mode, defining design tokens, or debugging classes that silently don't apply. Covers the v3→v4 traps an LLM trained on v3 falls into.
volt-primevue
Build UIs with Volt (unstyled PrimeVue + Tailwind). Covers adding components, pt: pass-through customization, choosing components, and the two-layer color model for prefers-color-scheme dark mode.
vue-nuxt
Author Vue 3 components inside a Nuxt 4 app. Covers Nuxt auto-import rules, component authoring (props/emits/withDefaults/generics), v-model/defineModel, slots, composables, reactivity, when watch is a code smell, reaching for VueUse over hand-rolled effects, page structure, display formatting, and Vue-shaped template idioms.
caveman
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says \"caveman mode\", \"talk like caveman\", \"use caveman\", \"less tokens\", \"be brief\", or invokes /caveman.
cohesion-har-qa
Tests browser analytics events for Cohesion/Tagular integrations using HAR-first capture, request-body parsing, and duplicate-call analysis. Use when validating sessionStarted, PageViewed, DomCompleted, PageEngaged, PageScrolled, Identify, ElementClicked, ElementViewed, addressCaptured, ConsentCaptured, cohesion_init, GPC consent behavior, or similar Beacon events; keywords include Cohesion, Tagular, Tealium, Beacon, /v2/t, HAR, event QA, duplicate events, and payload verification.
design-control-loop
interview the user to design an agentic control loop (sensor, controller, actuator under disturbances) tailored to their codebase, then build it as locally-runnable components plus a scheduled coding-agent workflow
find-skills
Discover and install agent skills from the open ecosystem. Use when the user asks \"how do I do X\", \"find a skill for X\", \"is there a skill that can...\", or wants to extend agent capabilities with installable skills. Triggers on skill discovery, skill search, skill installation.
goal-setting
Turn vague personal, research, learning, or project intent into honest, stable, detailed, falsifiable, incremental goals. Use when the user wants to define success, choose direction, prioritize open-ended work, avoid scope drift, recover motivation, or clarify what they are actually trying to accomplish. Keywords: goal-setting, goals, define success, north star, scope drift, priorities, tradeoffs, motivation, stuck, falsifiable, incremental, what am I trying to do.
improve-claude-md
improve a CLAUDE.md file using <important if> blocks to improve instruction adherence
loop-engineering
Design agent loops instead of one-off prompts: scheduled or goal-driven automation, worktree isolation, durable state, skills/policies, connectors/MCP, maker-checker subagents, cost budgets, safety gates, and human approval boundaries. Use when setting up recurring AI engineering workflows, repo maintenance loops, CI/PR/issue triage loops, long-running agents, autonomous or semi-autonomous coding tasks, or when replacing repeated manual prompting with a system that discovers, acts, verifies, records state, and escalates.
micro-app
Create polished local-first HTML playgrounds and micro-apps for exploration, workshops, demos, and manager-ready artifacts. Use when the user asks for a playground, interactive HTML artifact, static GitHub Pages lab, self-guided exercise, visual explorer, copy/paste AI workflow, slide deck, diagram, data explorer, code review artifact, comparison matrix, timeline, throwaway editor, brainstorm grid, mind map, design token showcase, spec/planning doc, or HTML instead of markdown/slides. Keywords: playground, micro-app, static HTML, GitHub Pages, Alpine, Tailwind CDN, Popover API, View Transitions, local-first, copy prompt, export markdown, slide deck, kanban, ERD, mind map, data explorer, spec, implementation plan.
npm-publish
Publish npm packages with OIDC trusted publishing, GitHub release workflows, and version synchronization. Use when setting up npm publish CI/CD, configuring OIDC/trusted publishers, fixing version sync issues (package.json vs git tag), troubleshooting npm publish 403/404/ENEEDAUTH errors, creating release workflows, or publishing scoped/monorepo packages. Triggers: npm publish, npm release, OIDC, trusted publisher, package.json version, npm 403, npm 404, ENEEDAUTH, publish workflow, changesets publish, lerna publish.
output-style
Apply writing discipline to agent output: make it scannable when structure is needed, use prose when it's not. Use when user asks to make writing clearer, more scannable, easier to read, or references 'Don't Make Me Think.' Also triggers for requests like 'simplify this,' 'make this scannable,' 'cut the fluff,' 'help people skim this,' 'stop over-formatting,' 'sound less robotic,' 'less corporate,' 'write naturally,' 'just talk normally,' or when editing docs, emails, proposals, or technical writing for busy readers. Keywords: output style, write clean, scannable, simplify, cut the fluff, over-formatted, tone, formatting, prose-first, natural tone, conversational, minimum formatting, less corporate.
pk
Disabled: pk is now invoked explicitly through the /pk prompt template. Kept only as archived documentation for the former skill workflow.
plan
Create and maintain lightweight Markdown plans in locally excluded .ai/plans/ for complex, ambiguous, risky, or multi-session work. Use when the user asks for a plan, PLAN.md-style artifact, implementation plan, design plan, migration plan, execution plan, roadmap, handoff, or when reasoning, decisions, discoveries, validation, or recovery context should survive the chat. Tasks and checklists are optional, not required.
product-strategy
Evaluate product/app ideas before and after MVP using north-star one-pagers, core-tech leverage, defining constraints, success criteria, opportunity mapping, RICE, and growth horizons. Use when deciding whether to build, continue, pivot, prioritize post-MVP work, define product success, or avoid feature-factory drift. Keywords: build or not, MVP, product idea, north star, product strategy, RICE, opportunity tree, roadmap, post-MVP, pivot, success criteria, narrative, one-pager, working backwards.
software-design
Diagnose architecture friction and design deeper modules/APIs, informed by domain language in CONTEXT.md and decisions in docs/adr/. Use when the user wants refactoring candidates, module/interface design, architecture review, testability improvements, or software-design reasoning about shallow modules, seams, information leakage, locality, and leverage. For implementing behavior test-first, use tdd; for turning conventions/design rules into deterministic linters/CI checks, use feedback-loop.
systems-thinking
Analyze organizational, technical, and strategic problems as interacting systems using Rumsfeld Matrix, causal loops, debt cascades, constraints, and resilience thinking. Use when problems involve feedback loops, hidden dependencies, legacy systems, architecture portfolios, repeated failures, unknown unknowns, or change resistance. Keywords: systems thinking, causal loop, Rumsfeld Matrix, unknown unknowns, Chesterton's Fence, debt cascade, theory of constraints, enterprise architecture.
tdd
Test-driven development with red-green-refactor loop. Use when the user explicitly wants test-first work, says TDD/red-green-refactor, asks for behavior tests before implementation, or wants a bug fix driven by a failing test. For architecture diagnosis, module boundaries, or refactoring candidates, use software-design first; for repo-wide automated quality gates, use feedback-loop.
thought-partner
Route conversational thinking requests to one focused framework. Three core modes: adversarial pushback (sycophancy), request investigation (root-ask), and plan/design interrogation (grill-me). Use when user wants a sparring partner, says 'help me think', 'think with me', 'push back', 'challenge', 'stress test', 'what am I missing', 'grill me', 'devil's advocate', 'root cause', 'behind the request', or has an ambiguous thinking-mode request. Route product strategy, goal-setting, systems thinking, stakeholder messaging, or parallel exploration to their dedicated skills instead.
typst-doc
Build token-efficient, consistently-styled PDF documents with Typst — reports, specs, status updates, incident post-mortems, slide decks, diagrams, flowcharts, Gantt charts, comparison matrices, one-pagers, and CVs — and answer Typst syntax questions (markup, math, code mode, set/show rules, page and table layout). Use for composed, paginated, or printable documents needing real layout, a table of contents with page numbers, headers/footers, tables, figures, or math that Markdown can't do — cheaper to share than an HTML micro-app, compiles to PDF. Routes Markdown vs Typst vs HTML, pins a prose typography preamble for consistent styling, and maps each document type to the right typst.app/universe package. Keywords: typst, PDF, document, report, spec, slide deck, diagram, flowchart, gantt, status report, incident report, comparison matrix, one-pager, CV, resume, print, typography, typst syntax, markup, math, set rules, show rules, layout, cetz, fletcher, touying.
Page 1202 of 1665 · 83215 results