AI Agent Workflow Collection

Use when a change is architecturally significant and spans three or more repos — to thread a hard-won lesson through an entire ecosystem with a single approvable plan. Triggers on: "bake X into the whole ecosystem", "incorporate lessons across repos", "design a multi-repo program", or any cross-service plan that flows through a shared protocol or identity layer.

Use when designing a long-running agent loop, evaluation harness, or multi-session memory system with Fable 5 — covers self-correction loops, verifier sub-agents, and the memory progression pattern.

Use when you need to verify that a customer organization on your platform is healthy and getting full value — a live integration audit that probes real API signals across eight dimensions, not a code review. Triggers on: "audit this org", "is healthy", "health-check the integration", "why does this org feel off", or a scheduled pre-demo / weekly org check.

Use when you need a deep, honest audit of a repository with a prioritized improvement plan — before a refactor, before onboarding a new contributor, or before committing to a codebase.

Use when declaring or checking the token budget / model tier for this session. Triggers on: "set effort", "how much budget do we have", "low on tokens", "use opus", "use sonnet", "constrained this week", or any explicit model-tier selection. Can also be called mid-session to downgrade tier when tokens run low.

Ship a Claude Code skill marketplace safely when your default branch is live-publishing: run a local pre-push gate (test suites, manifest JSON parse, sanitization grep, gitignore-swallow check, optional live-URL sweep), bump plugin versions with content, and handle installed-cache desync and catalog site coordination. Use when a marketplace maintainer says "I'm about to push my marketplace", "gate my marketplace release", "release this plugin to my marketplace", "publish the new skill", "bump a plugin version", "why don't my marketplace's installed users see the change", or "is this safe to ship".

A written house style for Claude Code skill-marketplace SKILL.md and README.md files — frontmatter rules, trigger-rich descriptions, Phase/Step body skeletons, recurring honesty and Tests sections, a six-section plugin README template, and a conformance checklist you calibrate against your own repo's golden examples. Use when a marketplace maintainer says "set up a style guide for my skill marketplace", "does this skill match my marketplace's house style", "review a SKILL.md against my golden set", "write trigger-rich frontmatter for a new skill in my marketplace", or "style-check my marketplace's plugins" — in any marketplace repo you maintain.