michaellady

Use when user wants Buffer operational + engagement stats across channels — "buffer stats", "how is my buffer doing", "buffer analytics", "buffer queue health", "how did my buffer posts perform", "weekly buffer report", "buffer insights".

Use when user wants LinkedIn newsletter / profile / company-page stats — "linkedin stats", "how's my linkedin doing", "newsletter subscribers", "linkedin followers", "top linkedin posts", "linkedin dashboard", "weekly linkedin report".

Use when user wants to promote a beehiiv newsletter post on social media, create social posts from a newsletter, or schedule newsletter promotions to Buffer channels — "promote this newsletter", "share newsletter on social", "create posts for this article".

Use when user wants to promote a beehiiv newsletter as a 10-slide illustrated carousel to Buffer for Instagram, LinkedIn, Facebook, Threads — "carousel the newsletter", "swipe post", "newsletter carousel", "10-slide post". Generates on-brand EVC slides with AI-generated illustrations (Gemini 2.5 Flash Image / Nano Banana) and schedules them with a "comment 'newsletter'" CTA.

Use when user wants to promote a beehiiv newsletter on social media with teaser-style hooks (rather than verbatim quotes) that summarize the article without giving away the punchline — "tease this newsletter", "write teasers for the newsletter", "summarize and promote", "hook posts for the article". Each post ends with the standard "Comment newsletter…" CTA so commenters get the article DM'd to them.

Use when user wants a weekly dashboard of the Enterprise Vibe Code growth flywheel — "flywheel report", "weekly rollup", "how's the flywheel spinning", "am I on track", "week over week growth", "priorities check". Produces a single markdown report against the 5 growth-plan priorities.

Use when user wants to turn a long-form video (YouTube URL or local file) into short-form social clips via OpusClip — "clip this video", "opus clip my stream", "make shorts from this", "clip my latest YouTube longform", "clip the stream". Submits to the OpusClip API, polls until clips are ready, optionally strips the default brand overlay, and hands off to `/promote-newsletter` or `opusclip post` for scheduling.

Use when user wants to cross-post a beehiiv newsletter article on LinkedIn, Substack, Medium, Hacker News, or Reddit using browser automation — "crosspost this article", "cross-post newsletter", "publish to Medium", "post to hacker news", "submit to reddit", "share on HN", "crosspost to substack", "syndicate newsletter".

Use when the user wants Claude, Codex, agy, and the Cursor models Composer 2.5 and Grok Build to iterate together until they converge on a mutually-agreed result — or hit a deadlock the user must arbitrate — and for fresh-eyes adversarial review of drafted artifacts. Five modes — plan, implement, verify, review, and audit (the folded-in adversarial review). Triggers — "converge", "have claude and codex work it out", "iterate until you agree", "three-AI consensus", "multi-AI consensus", "deadlock me a decision", "adversarial review this", "audit my drafts", "fresh eyes on this", "review for fabrications".

Use when starting any substantial feature — the before/during/after development lifecycle: interview rounds, parallel blind-spot/references/reality-probe passes, a knowns matrix folded into the plan, an implementation-notes log during the build, and a compounding step after (explainer, quiz, memory/skill extraction). Triggers — "feature passes", "run the pre-build passes", "blind spot pass", "knowns matrix", "interview me about this feature", "compound the learnings".

Use before baking an external config value — a model id, endpoint, ARN, bucket, region, credential, API version, image tag — into code or a deploy. Invoke the real dependency ONCE against the target account/environment and read the response, so a dead/renamed/deprecated/permission-blocked value is caught at the source instead of failing in production. The config equivalent of "verify against reality, not the doc." Triggers — "probe before wire", "smoke the dependency first", "is this model/endpoint/ARN actually live", "verify the config before deploy", "does this id still work", "check it against the real account".

Use when an agent, workflow, or fan-out died mid-work — API connection drops, session/spend limits, forced structured-output timeouts — and work must be recovered without loss. Triggers — "resume the run", "the agent died", "hit the session limit", "recover the workflow", "connection closed mid-response".

Use when you need to maximally verify a piece of code — especially AI-generated code — by stacking every independent check it admits (differential/property/metamorphic/fuzz/concurrency/static/cross-model), anchored on the strongest available oracle, and breaking the correlated-failure trap (one agent wrote both code and tests). Triggers — "how do I maximally verify this", "make this bulletproof", "how should I test this", "make this safe to optimize/refactor with AI", "what oracle should I use", "I don't trust the agent's tests", "maximize verification", "is my test suite actually verifying anything".

Use when a deployed/wired integration is FAILING (silently or opaquely) and you're tempted to try a fix. The failure lives at one of several layers — your wiring, your env, your IAM, an org policy/SCP, an account-level enablement/subscription, or the provider's response format — and each layer has a DIFFERENT OWNER. Ladder down them, verify what you own is actually applied, and get to the ONE authoritative signal (the real log line, an elevated-creds probe, latency-as-discriminator) before attributing blame or attempting a fix. Triggers — "why is this silently failing", "it deployed but doesn't work", "ladder the failure", "localize before fixing", "read the real error", "is it my code or their config", "diagnose the integration", "AccessDenied but the IAM looks right".

Use when shipping a change through a gated pipeline (local verify → commit → push → CI → adversarial audit → auto-merge) and you must not let a check be claimed without being read. Turns the ship sequence into a hard READ-gate state machine — every gate's actual exit code / number / verdict must be read before the next step, and "run the audit" can never be co-scheduled with "arm the merge." Triggers — "ship this", "verified ship", "open the PR and merge", "gate this change", "ship with the discipline", "don't claim a number you didn't read", "read the audit before arming".

Use when you want Claude and Codex to work an artifact through an explicit thesis → antithesis → synthesis loop until a transcendent position emerges (or the dialectic stalls). Works in four modes — plan, implement, verify, review — same artifact types as /converge but with a structurally different rhythm. Triggers — "hegelian dialectic", "thesis antithesis synthesis", "dialectic this <plan|code|tests|PR>", "synthesize claude and codex on this", "transcend the disagreement".

Use when the user wants the closed-loop performance of an OpusClip clip batch across all the platforms it was posted to — "clip results", "how did the clips do", "cross-platform clip performance", "closed loop on the clips", "did the clips work". Pulls per-platform metrics natively (no API exists) and renders one consolidated report.

Use when the user wants to A/B test a YouTube video's title or thumbnail using YouTube Studio's native Test and Compare feature. Generates 3 candidate titles from the transcript and drives Studio via Claude-in-Chrome to set up the test. Triggers on "ab test", "a/b test", "test titles", "test thumbnail", "test and compare", "split test", "best title for this".

Use when user asks about YouTube analytics, revenue, subscribers, watch time, retention, video performance, title/tag analysis, duplicate detection, data-quality checks, or wants to fetch/view/export channel data. Also triggers on cohort grouping/tagging, hypothesis tracking, weekly/closed-loop reviews, and per-cohort performance. Triggers on "check analytics", "fetch latest", "youtube stats", "how are my videos doing", "best titles", "recent performance", "compare to last run", "since last fetch", "weekly review", "closed loop", "how is the X cohort doing", "what did we predict last week", "grade hypotheses", "cohort report", "insights pending".

Use when the user wants to set up monitoring for a freshly published YouTube video on the Enterprise Vibe Code channel. Tags the video into a cohort, writes a launch hypothesis to the insights ledger, and installs the daily launch-watch LaunchAgent. Triggers on "launch", "track this video", "monitor this drop", "watch the new one", "kick off launch monitoring".

Use when user wants a Discord invite (or other lead-magnet) URL with UTM parameters auto-filled from the latest live stream — "discord link", "discord invite", "give me the stream link", "UTM link for stream", "newsletter link for this stream".

Check that a DIALED-ified project's setup is still sound — state buckets, OIDC roles, workflow references, Makefile targets, optional shared-tier state. Triggers - "dialed verify", "check dialed setup", "verify deploy pipeline".

Wire a module into an existing DIALED shared tier. Supports DIALED-shipped modules (network, database) and custom modules authored in the project. Triggers - "add module to dialed", "dialed add module", "install RDS in dialed project".

Retrofit a shared infrastructure tier (VPC + fck-nat) to a DIALED project that set needs_vpc=false at setup. Use when a project has outgrown stateless PR stacks and needs a long-lived VPC. Triggers - "add shared infra", "add VPC to dialed project", "retrofit shared tier".

Bootstrap GitHub Actions + Terraform + AWS OIDC deploy pipeline in a project using DIALED. Per-PR ephemeral stacks, staged testing, dev→prod promotion. Triggers - "set up dialed", "dialed setup", "add deploy pipeline", "bootstrap CI/CD for this project".

Operate the Kai personal-knowledge pipeline — scan four sources (Apple Photos selfies, YouTube past livestreams, beehiiv RSS newsletter, recovered Vournal transcripts), transcribe via Gemini, file into monthly Google Docs, sync NotebookLM. Use when the user says "run kai", "kai ingest", "kai stats", "sync my knowledge base", "what's in kai", or names a specific source (apple / youtube / newsletter / vournal).