Build, run, and iterate on Pi agent graphs (pi-graph) — explicit-state multi-agent workflows with isolated/thread/shared context modes, schema-validated node handoffs, conditional routing, fan-out/barrier, durable checkpoints, and human approval gates. Use when the user wants to design a multi-agent workflow, set up a pi-graph, orchestrate specialized agents (researcher/writer/reviewer loops, parallel fan-out, idea tournaments, human-in-the-loop approval), define reliable structured outputs between nodes, author a graph JSON, or validate/run/resume/visualize a graph. Reach for this only when the task genuinely needs specialization, parallelism, independent review, or persistent role memory — otherwise prefer a single agent loop.
Run the quarter-boundary ritual — roll the quarter-scoped project folders, archive finished projects, grade the closing quarter's GOALS/OKRs, and draft the new quarter's goals behind an approval gate. Trigger on /quarter-rollover, "quarter rollover", "roll the quarter", "close out Q2", "new quarter setup", or when tools/quarter_path.py --check reports drift. Distinct from /triage-tasks (daily gate) and /audit (repo health check).
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Master product specialized skill 92 with comprehensive coverage of concepts, implementation, optimization, and production best practices. Essential skill for professionals working in product.
Build evaluation datasets, harnesses, baselines, and release gates for multi-agent systems. Use when testing topology choice, routing, interaction contracts, coordination, durability, dynamic membership, adversarial propagation, end-to-end quality, or system cost and latency.
Activate for technical questions about how the VTEX platform works — including platform mechanics, feature behavior, logistics and shipping strategies, OMS order lifecycle, catalog structure, promotions and pricing configuration, checkout behavior, and admin platform configuration. Use when the question is "how does X work" or "how do I configure X" on the VTEX platform. Do NOT activate for solution architecture decisions or system design trade-offs — use vtex-architect for those.
Autonomously execute SEO work for a local business client following proven local SEO guidelines. Use when user says "zrob SEO dla [klient]", "zacznij z [klient]", "uruchom SEO", "zrob mi SEO", or provides client details and asks to start SEO work. Produces: on-page fixes, service pages, schema markup, and a prioritized human TODO list.
Manage tasks, projects, areas, headings, and tags in the Things 3 macOS app via a local CLI (list Inbox/Today/Upcoming/Anytime/Someday/Logbook, search, create/update/complete/cancel items, open items in Things). Use when Codex needs to manage Things 3 on macOS.
Comprehensive guide for dependency injection (DI) in Golang. Covers why DI matters (testability, loose coupling, separation of concerns, lifecycle management), manual constructor injection, and DI library comparison (google/wire, uber-go/dig, uber-go/fx, samber/do). Use this skill when designing service architecture, setting up dependency injection, refactoring tightly coupled code, managing singletons or service factories, or when the user asks about inversion of control, service containers, or wiring dependencies in Go.
Retrieve real-time commodity price quotes using Octagon MCP. Use when checking current commodity prices, analyzing day ranges, comparing to moving averages, and tracking precious metals, energy, and agricultural commodity prices.
Land and deploy workflow. Merges the PR, waits for CI and deploy,
verifies production health via canary checks. Takes over after /ship
creates the PR. Use when: "merge", "land", "deploy", "merge and verify",
"land it", "ship it to production". (gstack)
Covers this repository's issue vocabulary: the labels in .github/labels.yml, what `blocked: design`, `blocked: dependency`, `blocked: external`, `on hold`, and `tracking` mean, and what an issue body must contain (a `path:line`, an observable close condition, a `Depends on: #N` line). Use when filing an issue, triaging or re-prioritizing the backlog, picking a `priority: P0`-`P3` label, choosing between `bug`/`enhancement`/`documentation`/`chore`/`security`, marking a tracking issue, running `just labels`, recording a problem found outside the task, or routing a daily-use request.
WSJ-like chart text and graphics practice. Use when writing the words on and around a chart or table: headline title that states the finding, subtitle with measure/unit/period/population, axis labels, tick formatting, direct labels, annotations, legend, and the source-and-notes line. Use for every figure in a report, briefing, paper or slide, and when a chart's title only names the metric ('Revenue by month').