opsMachine

Performs comprehensive, brutally honest full-codebase review as a grumpy but fair senior developer with 20+ years of experience. Use when the user asks for a grumpy dev code review, brutal code review, senior dev review, comprehensive codebase audit, hall-of-shame code smells, or a gut-check on the entire project (not just a PR diff).

Diagnose and fix OneCLI gateway issues — Docker not running, 407 proxy auth, 401 from API (MITM not active), stale aoc_ token, CA cert refresh, secret setup, version pinning. Use when onecliStart fails, update-fathom-db fails, proxy returns 407 or 401, mode=tunnel in logs, or after OneCLI container recreation.

ANY CRM or progress.md write, log call, add contact, pipeline lookup, paste transcript/email. Runs lifecycle routing in Step 0 — delivery work goes to progress.md not Won CRM Next Action. Query before create. For week view use week-scan not this skill. OM-Repo SKILLS-MAP.md.

Convenes a short virtual panel of 2–3 named advisers (verbatim bios below) for questions that merit deeper examination—strategy, ethics, shipping tradeoffs, growth, or inner alignment. Use when the user asks for a board of advisers, adviser panel, stress-test a decision, simulate a debate between perspectives, or when a question is multi-stakeholder and benefits from distinct lenses (not simple factual lookups). Supports two modes: (1) user questions the panel in turns, (2) advisers simulate a conversation with each other. Trigger phrases: adviser panel, board of advisers, simulate the advisers, council of advisers, who should weigh in on this.

Manages Mitch's Notion comedy writing database. Use this skill whenever Mitch wants to interact with his comedy material — creating new bit entries, updating existing bits as material develops, reading what's in the database, changing status, or adding notes. Trigger on phrases like: "add this to my comedy database", "save this bit", "update the vasectomy bit", "what bits do I have", "mark this as ready", "add these lines to that bit about X", "create a new entry for this premise", "what's in my comedy DB", or any time Mitch is developing stand-up material and wants it captured or retrieved. Also trigger when Mitch pastes raw material mid-conversation and wants it saved. Always fuzzy-search before creating — never assume a bit doesn't exist.

LinkedIn organic lead generation system based on the "comment keyword + DM" mechanic. Use this skill whenever Mitch wants to: write a LinkedIn post designed to generate leads, build a resource (checklist, template, list) to use as a CTA, research what topics are getting engagement in a niche, write a DM sequence for comment-based leads, or plan a weekly LinkedIn content cadence. Also trigger when Mitch says things like "write a LinkedIn post", "what should I post about", "make a lead magnet", "build a resource for LinkedIn", "DM sequence", or "keyword CTA". Source: https://www.reddit.com/r/EntrepreneurRideAlong/comments/1shgq8u/i_stopped_chasing_clients_and_let_linkedin_do_it/

Applies the Cognitive Operations Architecture — structured thinking recipes built from lenses (what to notice), operations (what to do), and recipes (specific sequences for specific problems) — to user queries. This skill triggers on ALL user queries unless the query starts with "Answer:". Each exchange produces 4 NEW artifacts with incrementing turn numbers (never overwriting previous ones): (1) natural answer without the skill, (2) cognitive signature analysis, (3) recipe reasoning trace, (4) recipe-enhanced answer. Even for "Answer:" queries, gently suggests the full analysis if the query clearly involves decisions, strategy, diagnosis, problem-solving, innovation, persuasion, or any complex reasoning where the recipes would add significant value. Use this skill extremely broadly — when in doubt, use it.

Guide users through creating Agent Skills for Claude Code. Use when the user wants to create, write, author, or design a new Skill, or needs help with SKILL.md files, frontmatter, or skill structure.

Day-1 onboarding interview that maps the user's existing tools and produces Setup-Decisions.md — the per-ability decision matrix that drives everything else in the seed. Use when the user says 'discover my stack', 'set up the workspace', 'onboard me', 'what should I install', 'help me configure this seed', or whenever Setup-Decisions.md is empty / missing. Non-blocking: produces a draft the user can edit; never installs anything itself.

Sister to `harvest-learnings`. Take a staged doc from `Strategy/to integrate/`, propose specific edits to canonical strategy docs (paths read from `.skill-config.yml`), get the user's explicit per-edit approval, apply approved edits, then archive the source to `Strategy/z-archived/`. Use when the user says: 'integrate the [topic] learnings', 'integrate from to-integrate', 'apply the staged learnings', 'merge into canonical', 'fold the [client] insights into strategy', or 'time to integrate'. **NEVER writes to canonical without explicit per-edit approval.** Supports preview-only mode + partial integration. Manual invocation only.

Orchestrate deep research across meeting transcripts in the local transcript vault. Use when the user asks to analyze client meetings, review sales calls, research a topic across meetings, build client personas, export transcripts for RAG, or says 'meetings', 'transcripts', 'call review', 'client analysis'.

Per-ability decision protocol for the seed workspace. Asks 'what's the marginal gain over what your live system already does?' for any proposed local subsystem (transcript vault, CRM index, drive index, custom MCP, scripted automation). Use when the user says 'should I build X', 'do I need a local index for Y', 'what's the gain', 'is this worth setting up', or whenever a row in Setup-Decisions.md is marked needs-gain-analysis. Outputs a recommendation with reasoning, not a decision — the user decides.

Extract transferable learnings from a client engagement (or strategic prep session) and stage them in `Strategy/to integrate/` for later canonical integration. Reads engagement artifacts from `clients/<client>/`, cross-references against the canonical strategy docs (paths read from `.skill-config.yml`), and drafts a properly-sourced staging doc using the to-integrate TEMPLATE.md. Use when the user says 'harvest learnings from [engagement]', 'what did we learn from [client]', 'feedback loop time', 'lessons from [client]', 'wrap up [engagement]', or 'extract insights from this work'. Does NOT modify canonical docs — that's the sister `integrate` skill's job. Manual invocation only.

Install one operational cadence at a time in Container/cadences/. The discipline is one-at-a-time, never bundled — past four sticky cadences you're over-instrumented. Use when the user says 'install a cadence', 'add a weekly review', 'set up the keystone review', 'scaffold a Friday review', 'add a monthly retro', or any 'install one operational ritual' request. Drafts the cadence file, names the calendar slot, defines drift signals, and asks the user to commit to a 4-week trial.

Orchestrate deep research across Fathom meeting transcripts. Use when the user asks to analyze client meetings, review sales calls, research a topic across meetings, build client personas, export transcripts for RAG, or says 'fathom', 'meetings', 'transcripts', 'call review', 'client analysis'.