Development

Run and interpret coop's VM integration suite locally on Lima or remotely on Firecracker. Use when asked for integration testing or when guest-visible/lifecycle work needs its pre-merge gate.

Run the final scope-controlled review before committing, pushing, or opening a PR. Use for closeout review, readiness checks, or self-review of a completed branch.

Shepherd the current user's open PR through base updates, CI failures, and review feedback without rewriting history or merging. Use when asked to babysit, monitor, or fix an existing PR.

Build a throwaway HTML or in-app prototype that answers one design question. Use when the user wants to try a state model or UI idea before committing, or says "mock it up", "prototype", "what should this look like".

Use for conf/system-files.toml, tracked fragments under system/, or the task and resource that merge administrator-owned files below /etc. Not for user symlinks, systemd unit enablement, or Windows registry values.

Use for the Quickshell QML/JavaScript UI and Python helper under symlinks/config/quickshell/: bars, popups, workspace layout, shared state, and network actions. Not for Rust CLI output, shell bootstrap, or unrelated application configuration.

Set up, run and respect a machine-checked definition of done. Use when the user mentions a definition of done, finish-line or commit/push gates, "the agent said done but it wasn't", wants to audit what a repo enforces, wire a PreToolUse or pre-commit or CI gate, verify a patch before it touches the working tree, collect evidence files, or fix drift between CLAUDE.md, AGENTS.md, Cursor and Copilot instruction files. Also use before reporting work finished in a repo that has a .skillgate/done.y...

Work labelled Jira tickets unattended with idle Claude Code subscription quota — set up, preview, schedule, and report on a `burn process jira` run. Use when the user says "work my Jira tickets while I'm out", "auto pick labelled tickets", "burn my backlog", "run this over the weekend / overnight / while I'm OOO", or asks what happened during an unattended burn run.

Cut, normalize, caption, and inspect short-form video and audio with ffmpeg, or analyze a reel from its actual media. Use when a clip, recording, or reel URL is supplied and the deliverable is an edit or an analysis of the footage. Writing captions or posts needs no skill.

Build or repair a Codex pet sprite atlas with the deterministic assembly and QA pipeline. Use only for Codex pet assets; general image or media work needs no skill.

Diagnose and fix code-graph index issues. Use when: search returns unexpected/empty results, or after major codebase restructuring. Covers the health check and both rebuild paths from the CLI.

Understand code structure efficiently using the AST index. Use BEFORE reading files one by one — when starting work in unfamiliar code, exploring a module before changes, or finding the right file to edit. One overview call replaces 5+ Read calls and saves significant context.

Add PostHog MCP analytics to a TypeScript, JavaScript, or Python MCP server. Instruments the server so every tool call, agent intent, and failure is captured as a $mcp_* event — the @posthog/mcp Node SDK for TS/JS, or posthog.mcp (shipped inside the posthog package) for Python. Detects the server style (official MCP SDK Server/McpServer/FastMCP, mcp-handler, @rekog/mcp-nest, jlowin fastmcp, or a custom HTTP/edge dispatcher) and wires in the matching instrumentation, credentials, and graceful ...

Use this skill when the user wants to build tool/scripts or achieve a task where using data from the Hugging Face API would help. This is especially useful when chaining or combining API calls or the task will be repeated/automated. This Skill creates a reusable script to fetch, enrich or process data.

This skill should be used when users want to run any workload on Hugging Face Jobs infrastructure. Covers UV scripts, Docker-based jobs, hardware selection, cost estimation, authentication with tokens, secrets management, timeout configuration, and result persistence. Designed for general-purpose compute workloads including data processing, inference, experiments, batch jobs, and any Python-based tasks. Should be invoked for tasks involving cloud compute, GPU workloads, or when users mention ...

Add a new agent CLI start provider in threadbase-mobile (browse chips, health parser, badges, filters, i18n). Use when adding Cursor, Codex, Gemini, Amp, Aider, OpenCode, Goose, ClawCode, Hermes, cursor, start chips, provider badges, or when the user says add a provider. Live PTY and history indexing are other repos — see Companions.

Use when deciding which AI subscription to work on next — how much of each registered account's cap is gone, when each one resets, what continuing past a drained cap costs on each provider, and which need a re-login. Covers every account /quotas-setup registers — Claude, Codex, and Cursor (two monthly usage pools, reported as percent used, read with the token the Cursor IDE holds for the signed-in user). Display only — it never switches accounts, never buys anything, and never gates dispatch.

'Static Application Security Testing (SAST) for code vulnerability

Expert in launching small, focused SaaS products fast - the indie

Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.

Session replays, product events, error tracking, feature flags and HogQL over a connected PostHog project. Use when the user asks what a user did before a bug, for a session recording or replay, for product analytics, for who an exception hit, or about a feature flag's rollout.

Manage Fly.io machines, apps, volumes and app secrets through the Machines API. Use when the user asks what is running on Fly.io, or to start, stop, resize, move, redeploy or destroy a Fly machine.

Use when writing or fixing a build.zig: executables, libraries, modules, C sources, build options, test steps, custom steps, or build.zig.zon dependencies. Not for one-file builds: use zig-compiler.

Use when building a Zephyr app with west, picking a board target, editing prj.conf or a devicetree overlay, adding logging, running on native_sim, or using west debug. Not for FreeRTOS: use freertos.