escoffier-labs
- 78 skills
- 0 followers
- 4 repo stars
- yesterday last updated
- ▌ Publish Scrub · escoffier-labs bundleUse before any prose artifact goes public - a blog post, social post, README section, PR or issue body, commit message, release notes - to scrub identity and infrastructure leaks and apply writing conventions. Also use when the user asks to "scrub this", "is this safe to post", or "clean this up before it goes out". For repo and git-history leak scans use publish-readiness instead. (formerly plate)
- ▌ Work Handover · escoffier-labs bundleUse when in-flight work must change hands - the user says "pause", "stop here", "pause this so another agent can continue", or the context is about to fill or compact - or when taking over unfinished work with "continue where we left off", "pick up this branch", "resume the last session", or "what did the previous agent do". (formerly relief)
- ▌ Dependency Audit · escoffier-labs bundleUse when auditing, updating, or migrating project dependencies, runtimes, package managers, lockfiles, or toolchains. Requires reading authoritative release and migration notes, changing one compatibility boundary at a time, and verifying the resolved dependency graph. (formerly stocktake)
- ▌ Diagnose Session · escoffier-labs bundleUse only when the user asks why an agent run went wrong and wants evidence from the transcripts - "why did that take so long", "why was it so expensive", "it ignored the plan", "it kept redoing X", "that skill never fired", "what was it doing". Runs only when the user asks. Not for debugging product code (use superpowers:systematic-debugging).
- ▌ MCP Server Review · escoffier-labs bundleUse when asked to security-review an MCP (Model Context Protocol) server, either one you are building or one you are about to install, audit its tools for unsafe gating, exec, credential, transport, or tool-description risks, or decide whether a third-party MCP server is safe to connect to an agent. Read-only review. Whole-repo audits belong to security-sweep.
- ▌ Pr Security Review · escoffier-labs bundleUse when asked to security-review a pull request, a commit range, or staged changes, to check a diff for vulnerabilities or leaked secrets before merge, or to vet a PR from an outside contributor. Scoped to the diff. A whole-repo audit goes to security-sweep.
- ▌ Cross Vendor Worker · escoffier-labs bundleUse when the session needs an answer or work product from a model on ANOTHER vendor's stack - a second opinion from a different model family, a cheap fast model for bulk work, or a cross-model review. Triggers include "ask grok/composer/gemini/claude/codex what it thinks", "get a second opinion from a different model", "cross-model review", "run this by another model", "poll several models". If a Brigade roster exists, prefer `brigade run --worker`. (formerly stagiaire)
- ▌ Supply Chain Harden · escoffier-labs bundleUse when asked to harden a repository's software supply chain, pin GitHub Actions to commit SHAs, lock down workflow permissions, add Dependabot or secret scanning to CI, move npm publishing to trusted publishing with provenance, or pin Docker base images. Applies the changes as one reviewable branch per repo. Read-only audits belong to security-sweep.
- ▌ Verify Skill Builder · escoffier-labs bundleUse only when the user asks to create, audit, or refresh a project-local verify skill that drives the real app - "make a verify skill for this repo", "script how to prove this app works", "audit the verify skill", "the feature map is stale". Runs only when the user asks. Not for a one-off check (use superpowers:verification-before-completion). (formerly test-kitchen)
- ▌ Create Formal Verification Skill · escoffier-labs bundleUse only when the user explicitly requests a project-local formal verification skill, model checking, or a proof of a code-backed invariant. Do not trigger for ordinary test setup or application smoke checks.
- ▌ Maintain Formal Verification Skill · escoffier-labs bundleUse only when the user explicitly requests maintenance of an existing formal verification skill or asks whether its model, proof, or harness still matches changed code. Do not trigger on routine merges or ordinary application verification.
- ▌ Hone · escoffier-labs bundleUse when a prompt, worker brief, or task description is about to be sent to another agent or model and should be deeper first, or the user says "sharpen this prompt", "hone this brief", "make this deeper, not bigger", or "improve this before I dispatch it".
- ▌ Lineage · escoffier-labs bundleUse when asked why code exists or why it works the way it does - "why is this here", "why did we pick Y", "who added this and for what", "is it safe to remove", a regression's origin, a magic threshold, or a workaround with no comment - and before deleting or reshaping code whose reason you cannot see.
- ▌ Repo Audit · escoffier-labs bundleUse when asked to audit a repository, assess project health, find the highest-value improvements a repo needs, check whether a project is ready for contributors or coding agents, or decide what to work on next in a codebase. (formerly line-check)
- ▌ Statechart · escoffier-labs bundleUse only when the user explicitly asks for a Mermaid statechart, a user-visible chart of a TLA+ model or counterexample, a code/spec/fix chart comparison, or a TLA+ scaffold from an agreed chart.
- ▌ Merge Ready · escoffier-labs bundleUse when an open pull request must be driven to merge-ready - conflicts, unanswered review threads, or failing CI are outstanding - or the user says "babysit this PR", "get PR 123 green", "address the review comments", "is it mergeable yet", or "check on PR 123". Not for filing a PR (use superpowers:finishing-a-development-branch) or landing a campaign (use fleet-conductor). (formerly runner)
- ▌ Fix Findings · escoffier-labs bundleUse when the user wants to act on an audit, fix the findings in a repo-audit/bug-hunt/security-sweep/latent-premises/retry-safety report, work a prioritized backlog, or asks to "fix the findings", "work the backlog", "clear the audit", or "do the high-leverage items". The step after the audit skills. (formerly expedite)
- ▌ Issue Triage · escoffier-labs bundleUse when an issue, bug report, support thread, or user complaint arrives and needs triage before anyone fixes it - "triage this issue", "is this a duplicate", "can you reproduce this", "should we open an issue for this", "someone reported X". Not for fixing a confirmed bug (use superpowers:systematic-debugging). (formerly ticket-rail)
- ▌ Perf Measure · escoffier-labs bundleUse when investigating or improving performance, latency, throughput, memory use, CPU use, startup time, or bundle size. Establishes a repeatable baseline and profiles the measured bottleneck before any optimization. (formerly thermometer)
- ▌ SEO Metadata · escoffier-labs bundleUse when auditing or fixing discoverability metadata for a website before publication, including titles, descriptions, canonical URLs, robots policy, Open Graph, structured data, and sitemaps. Not for content strategy or keyword research. (formerly garnish)
- ▌ Feature Ideas · escoffier-labs bundleUse when asked what to build next, what features a repo is missing, where the opportunities are, or to suggest a direction or roadmap grounded in the code. Triggers on "what should we build next", "what's missing", "suggest features", "what's the next thing". Proposes opportunities, not fixes; for finding problems use repo-audit, bug-hunt, or security-sweep. (formerly special)
- ▌ Mistake Proof · escoffier-labs bundleUse when agents keep repeating the same mistake in a repository, the operator keeps correcting the same thing, or the user asks to "make this mistake impossible", "stop agents doing X", "harden the repo against agent errors", or audit which CLAUDE.md or AGENTS.md rules anything actually enforces. (formerly eighty-six)
- ▌ Fleet Hub Upgrade · escoffier-labs bundleUse when upgrading a Brigade Fleet Hub and the node clients that publish to it - Hub-first ordering, pre-flight diff of node-to-Hub payloads and SCHEMA_VERSION, snapshot-and-switch deploy with rollback, and node verification. Never downgrade code against a newer schema or edit the Hub database directly.
- ▌ Enforce · escoffier-labsUse when the user asks to turn on Brigade's full work loop (verification capture, raw-check blocking, and the handoff-before-stop gate) in the current repository.
- ▌ Brigade Work 2 · escoffier-labsUse at the start of any work session and whenever you verify a change in a Brigade Stack-wired repo or workspace - routes work through Brigade Stack so verification, outcomes, evidence export, and handoffs are captured (verify with capture → outcome from run → evidence brief next time) instead of leaving Brigade Stack installed-but-dormant. Triggers on starting a task, running tests/checks, or finishing a session.
- ▌ Check 2 · escoffier-labsUse when about to claim anything works, is fixed, is complete, or passes - before committing, replying to the user, or moving to the next task. Also use when relaying a subagent's or tool's success report, and especially at the end of a long session when the pull to say "done" is strongest.
- ▌ Taste 2 · escoffier-labsUse when implementing any feature, bugfix, or behavior change, before writing the implementation code. Especially use under pressure - production is down, "just make it work", "quick fix" - which is when it gets skipped.
- ▌ Reduce 2 · escoffier-labsUse when asked to simplify, clean up, tidy, or refactor code for clarity without changing what it does, or when the user says "simplify this", "clean this up", "make it readable", "reduce the complexity", or "tidy this". Behavior-preserving only; not a bug or security audit (use bug-hunt or security-sweep for those).
- ▌ Refire 2 · escoffier-labsUse when anything misbehaves - a failing test, a production bug, a build break, flaky or unexpected behavior - before proposing or attempting any fix. Especially under pressure ("CI is blocking everyone", "just get it green") and after a previous fix didn't hold.
- ▌ Bug Hunt 2 · escoffier-labsUse when asked to find bugs, hunt for correctness issues, sweep a codebase for defects, or verify a repo behaves as intended. Not for style or architecture review; this is defect-finding only.
- ▌ Retry Safety 2 · escoffier-labsUse when a diff carries side effects - database writes, migrations, file mutations, network calls, payments, queue messages - to check whether running it twice is safe. Also when reviewing retry logic, crash recovery, or anything a scheduler, queue, or impatient caller might re-run. Silent when the diff touches no side-effecting surface.
- ▌ Verify Brigade · escoffier-labs bundleProve a Brigade change works by driving the real `brigade` CLI against a throwaway temp target, then capture receipts as evidence. Use when you changed anything under src/brigade/ and need proof beyond pytest - init/doctor wiring, work-verify receipts, Grok Bot connector packs, feed manifests, handoff lint. Also use before claiming a CLI behavior in a PR body, handoff, or job report.
- ▌
- ▌ Note · escoffier-labs bundleCreate an Obsidian-formatted markdown note documenting the current session topic. Use when the user says /note, 'save this to Obsidian', 'write a note about X', or asks to document a troubleshooting session, system concept, coding pattern, or workflow. Writes to ~/notes/<slug>.md and syncs to the configured Obsidian inbox. If an argument is provided after /note, use it as the topic; otherwise review the conversation.
- ▌ Brigade Work · escoffier-labs bundleUse at the start of any work session and whenever you verify a change in a Brigade-wired repo or workspace - routes work through Brigade so verification, outcomes, evidence export, and handoffs are captured (verify with capture → outcome from run → evidence brief next time) instead of leaving Brigade installed-but-dormant. Triggers on starting a task, running tests/checks, or finishing a session.
- ▌ Card Refresh · escoffier-labs bundleUse when refreshing stale Brigade memory cards from the care refresh queue - category allowlist, grounded edits that cite on-disk sources of truth, archive-only retention, and reinforce-in-place instead of near-duplicate siblings (#724). Never delete, remove, or prune.
- ▌ Forward Plan · escoffier-labs bundleUse when turning Brigade's native ready set, outcome rank, and ROADMAP.md into a dependency-filed plan artifact under .brigade/work/plans/ - propose GraphTrail-derived edges (blocks from def/use, conflicts-with from write overlap) marked derived and requiring confirmation. Degrade cleanly when GraphTrail is unavailable. Never a subcommand.
- ▌ Ultra Work Scout · escoffier-labs bundleUse when the user asks for ultra work, scout work, broad pre-implementation scouting, or parallel investigation before a large Brigade task. Designed for Codex and other SKILL.md harnesses that can delegate or split work.
- ▌ Handoff Inbox Drain · escoffier-labs bundleUse when draining a Brigade handoff review inbox - triage drafts with allowlist-bound Brigade handoff commands, grounded edits that cite on-disk content, archive-only retention, and reinforce-in-place when ingest already matched a known fact (#724). Never delete, remove, or prune.
- ▌ Demi · escoffier-labs bundleUse before implementing, scaffolding, prototyping, or adding a feature when the work should start with the smallest useful code path, avoid speculative architecture, or prevent overbuilding before reduce would be needed.
- ▌ Fire · escoffier-labs bundleUse when a written implementation plan is ready to execute, when the user says "fire", "execute the plan", "build it", or hands over a plan file to implement. The step after recipe.
- ▌ Mise · escoffier-labs bundleUse before any creative or build work - a new feature, component, behavior change, or "let's build X" - to turn an idea into a design the user approved and a written spec, before a line of code. Mise en place for engineering: everything designed and in its place before you cook. Pairs with pressure-test for hardening decisions and hands off to recipe.
- ▌ Pass · escoffier-labs bundleUse before opening a pull request, before running gh pr create, or before pushing follow-up commits to an existing PR. Also use when the user asks "is this PR ready", "should I file this", or wants a change inspected before it goes out for review.
- ▌ Brief · escoffier-labs bundleUse when answering at a decision point - recommending an approach, reporting a verification result, finishing a task, proposing a fix, or assessing whether something is ready - so the judgment leads and the reader can evaluate it instead of only accepting it. Triggers on "brief mode", "bluf this", "give me the bottom line", "brief it", "stop burying the answer".
- ▌ Check · escoffier-labs bundleUse when about to claim anything works, is fixed, is complete, or passes - before committing, replying to the user, or moving to the next task. Also use when relaying a subagent's or tool's success report, and especially at the end of a long session when the pull to say "done" is strongest.
- ▌ Grill · escoffier-labs bundleUse when a technical writeup, blog post, war story, or "Show HN" is about to go to Hacker News, Lobsters, or any skeptical technical audience, or when the user says "grill this", "make it HN-ready", "harden this post", "is this ready to post", "will this survive the comments". Hardens facts, sourcing, voice, and comment-readiness. Not for identity/infra leak scrubbing (use plate) or repo publication (use publish-readiness).
- ▌ Plate · escoffier-labs bundleUse before any prose artifact goes public - a blog post, social post, README section, PR or issue body, commit message, release notes - to scrub identity and infrastructure leaks and apply writing conventions. Also use when the user asks to "scrub this", "is this safe to post", or "clean this up before it goes out". For repo and git-history leak scans use publish-readiness instead.
- ▌ Taste · escoffier-labs bundleUse when implementing any feature, bugfix, or behavior change, before writing the implementation code. Especially use under pressure - production is down, "just make it work", "quick fix" - which is when it gets skipped.
- ▌ Recipe · escoffier-labs bundleUse when an approved spec or design needs to become an implementation plan, after mise and before any code. Also use when the user says "write the plan", "plan this out", or the work will be executed later, by someone else, or in a fresh session.
- ▌ Reduce · escoffier-labs bundleUse when asked to simplify, clean up, tidy, or refactor code for clarity without changing what it does, or when the user says "simplify this", "clean this up", "make it readable", "reduce the complexity", or "tidy this". Behavior-preserving only; not a bug or security audit (use bug-hunt or security-sweep for those).
- ▌ Refire · escoffier-labs bundleUse when anything misbehaves - a failing test, a production bug, a build break, flaky or unexpected behavior - before proposing or attempting any fix. Especially under pressure ("CI is blocking everyone", "just get it green") and after a previous fix didn't hold.
- ▌ Review · escoffier-labs bundleUse when you want an independent review pass before merging or between plan tasks - dispatch a fresh reviewer with crafted context (not your session history) to catch what you cannot see in your own work. The second set of eyes that pass asks for and that hands off to sendback. Triggers on "get this reviewed", "request a review", "second opinion", after finishing a feature or task, before merge.
- ▌ Garnish · escoffier-labs bundleUse when auditing or fixing discoverability metadata for a website before publication, including titles, descriptions, canonical URLs, robots policy, Open Graph, structured data, and sitemaps. Not for content strategy or keyword research.
- ▌ Special · escoffier-labs bundleUse when asked what to build next, what features a repo is missing, where the opportunities are, or to suggest a direction or roadmap grounded in the code. Triggers on "what should we build next", "what's missing", "suggest features", "what's the next thing". Proposes opportunities, not fixes; for finding problems use line-check, bug-hunt, or security-sweep.
- ▌ T3 Code · escoffier-labs bundleUse when configuring or troubleshooting T3 Code projects, multi-machine environments, desktop or headless servers, project names or icons, updates, launchers, or private remote access. Trigger on stale project entries, wrong workspace identity, missing favicons, update banners, saved backend setup, server reachability, Tailscale exposure, SSH tunnel fallback, or T3 service setup.
- ▌ Bug Hunt · escoffier-labs bundleUse when asked to find bugs, hunt for correctness issues, sweep a codebase for defects, or verify a repo behaves as intended. Not for style or architecture review; this is defect-finding only.
- ▌ Expedite · escoffier-labs bundleUse when the user wants to act on an audit, fix the findings in a line-check/bug-hunt/security-sweep/latent-premises/retry-safety report, work a prioritized backlog, or asks to "fix the findings", "work the backlog", "clear the audit", or "do the high-leverage items". The step after the audit roster.
- ▌ Sendback · escoffier-labs bundleUse when code review feedback arrives - from a human reviewer, a bot, or a review agent - before implementing any of it. Especially when the feedback is partly unclear, technically questionable, or comes wrapped in authority ("senior reviewer says").
- ▌ Skillify · escoffier-labs bundleUse when the user wants to turn a script, repeated workflow, runbook, or hard-won procedure into a reusable agent skill, or asks "make this a skill", "extract this into a skill", or "I keep doing this manually".
- ▌ Stations · escoffier-labs bundleUse when facing two or more independent pieces of work - separate bugs, separate subsystems, separate repos - that could be executed by concurrent agents, before dispatching any of them. Also use when the user says "fan out", "parallelize this", or hands over a pile of unrelated failures.
- ▌ Worktree · escoffier-labs bundleUse when starting feature work that needs isolation from the current branch, or before executing a plan or fanning out parallel stations - sets up an isolated workspace using the harness's native worktree tool, falling back to a git worktree. Triggers on "worktree", "isolate this work", "don't touch my branch", "work on a copy".
- ▌ Stagiaire · escoffier-labs bundleUse when the current session needs an answer or a work product from a model on ANOTHER vendor's stack - a second opinion from a different model family, a cheap fast model for bulk work, or a cross-model review - by dispatching that vendor's own CLI as a one-shot worker. Triggers include "ask grok/composer/gemini/claude/codex what it thinks", "get a second opinion from a different model", "cross-model review", "run this by another model", "poll several models". No orchestration framework required; if a Brigade roster exists, prefer `brigade run --worker` instead.
- ▌ Stocktake · escoffier-labs bundleUse when auditing, updating, or migrating project dependencies, runtimes, package managers, lockfiles, or toolchains. Requires reading authoritative release and migration notes, changing one compatibility boundary at a time, and verifying the resolved dependency graph.
- ▌ Graphtrail · escoffier-labs bundleUse when answering structural code questions in an indexed repo - who calls this, what does this call, what breaks if I change it, what changed between two versions. Reach for it BEFORE grep whenever the question is about relationships between symbols rather than text. Triggers include "who calls", "what uses", "blast radius", "impact of changing", "callers of", "what depends on", and reviewing a diff's structural effect.
- ▌ Line Check · escoffier-labs bundleUse when asked to audit a repository, assess project health, find the highest-value improvements a repo needs, check whether a project is ready for contributors or coding agents, or decide what to work on next in a codebase.
- ▌ Reel Check · escoffier-labs bundleUse before a rendered reel, screen-recording, demo video, or GIF goes public (social, YouTube, a landing page) to catch identity and infrastructure leaks burned into the frames. Also use when the user asks "is this reel safe to post", "scrub this video", or before a video-publishing pipeline ships an MP4. For plain prose use plate; for repos use publish-readiness.
- ▌ Release Cut · escoffier-labs bundleUse when the user asks to cut a release, tag a version, publish a release, or roll up the changelog. Not for routine merges; releases happen on request, not per feature.
- ▌ Thermometer · escoffier-labs bundleUse when investigating or improving performance, latency, throughput, memory use, CPU use, startup time, or bundle size. Establishes a repeatable baseline and profiles the measured bottleneck before any optimization.
- ▌ Retry Safety · escoffier-labs bundleUse when a diff carries side effects - database writes, migrations, file mutations, network calls, payments, queue messages - to check whether running it twice is safe. Also when reviewing retry logic, crash recovery, or anything a scheduler, queue, or impatient caller might re-run. Silent when the diff touches no side-effecting surface. Read-only review. Applying the fixes belongs to expedite.
- ▌ Pressure Test · escoffier-labs bundleUse when an idea, plan, design, or scope needs to be stress-tested before anyone builds it, when the user says "pressure test this", "poke holes in this", or wants the fuzzy parts made concrete. Also use in sous mode when the user hands off and says to answer the open questions yourself, figure it out, or that they are going AFK.
- ▌ Using Skillet · escoffier-labs bundleUse when starting any conversation - establishes how to find and use skillet skills, requiring skill invocation before ANY response including clarifying questions.
- ▌ Memory Handoff · escoffier-labs bundleUse at the end of any session that discovered durable knowledge (architecture decisions, root causes, setup gotchas, workflow changes, security findings, reusable patterns), or when the user says "hand off", "write a handoff", or "save this for the memory system".
- ▌ Research Brief · escoffier-labs bundleUse when the user asks for researched, sourced, evidence-backed, or current findings, especially for a recommendation or factual brief. Do not use for a single-page summary, ordinary codebase inspection, review of an existing technical post, or decision pressure-testing when the request already supplies all evidence.
- ▌ Security Sweep · escoffier-labs bundleUse when asked to security-audit a repository, find vulnerabilities and prescribe fixes, check for leaked secrets, review dependencies for known CVEs, or harden a project before exposure. Read-only audit. Applying the fixes belongs to expedite.
- ▌ Fleet Conductor · escoffier-labs bundleUse when conducting a large backlog or multi-repository campaign across several worker lanes, especially when work needs bounded ownership, held dependencies, collision control, draft pull request gates, and evidence-based landing. Triggers on "conduct the fleet", "burn down the backlog", "run a multi-repo campaign", or "land these agent PRs".
- ▌ Latent Premises · escoffier-labs bundleUse when reviewing a diff or module for hidden assumptions - things the code takes for granted that nothing guarantees - or when asked "what could break this later", "what does this assume", or to harden code that works today. Complements bug-hunt: bug-hunt finds defects with triggers today; this finds the ones waiting for tomorrow. Read-only review. Applying the resolutions belongs to expedite.
- ▌ Brigade Handoffs · escoffier-labs bundleUse when setting up, checking, writing, linting, or troubleshooting Brigade memory handoffs for a repo or agent workspace, especially when a user wants durable agent memory, handoff inboxes, cross-harness memory routing, or a safe first Brigade setup.
- ▌ Publish Readiness · escoffier-labs bundleUse before making a private repository public, before the first push of a new public repo, or when the user asks "is this safe to publish", "check for leaks", or wants a pre-publication scan. Also use after discovering identifying content already leaked into a public repo's history.