all publishers

bbrysonelite-max

@bbrysonelite-max source repo

117 published skills · page 1 of 2

  1. ▌
    Doc Keeper 2 · bbrysonelite-max
    The project-agnostic Document Keeper. Use on ANY project when its living/dashboard docs have drifted from reality — after a PR merges, when a decision/convention is locked, at session close (after context-keeper), or when the user says "reconcile the docs" / "update the docs" / "the docs are stale". Runs the doc-keeper workflow directly; it DISCOVERS whatever living docs the project actually has (README, CHANGELOG, status/handoff docs, ADRs, docs/, a domain index, punch-lists) and reconciles them to current truth via ONE docs PR on the repo's default branch. Docs only — never code; never merges. For the Tiger Claw repo specifically, use the specialized `tiger-doc-keeper` instead (it knows that repo's SOTU/PROGRESS/CI guards).
    0 repo stars
  2. ▌
    Skill Miner 2 · bbrysonelite-max
    Mine Brent's past Codex session rollouts and context snapshots to surface recurring routines that should become reusable skills, deduped against what already exists, then SUGGEST the strongest new candidate(s) to Brent for a build decision. A read-only research loop — it proposes, it never auto-builds. Use when Brent says "run skill-miner", "mine my sessions", "what should be a skill", "find new skills", "auto research for skills", or on a monthly cadence via /schedule. Pairs with the BACKLOG.md ledger so each run mainly surfaces NEW routines.
    0 repo stars
  3. ▌
    Desktop Delivery 2 · bbrysonelite-max bundle
    Whenever a document is produced for Brent to READ or REVIEW — a spec, a PRD, a plan, a design doc, a report, an audit — copy it to his Desktop the moment it's ready, without being asked. He reads from the Desktop, not from repo paths. Invoke automatically any time you hand him a document for review; also when he says "put it on my desktop", "where's the doc", or "so I can find it".
    0 repo stars
  4. ▌
    Context Keeper 2 · bbrysonelite-max
    Write the append-only per-session flight recorder to the CURRENT project's .codex/sessions/ — a dated, numbered snapshot of what THIS session decided, discovered, shipped, verified (vs not), and the next step. Project-agnostic — works for any project; defaults to the current git repo root (override with CONTEXT_KEEPER_DIR). Records the session (the raw record); a separate docs-reconcile step then updates the project's living docs. Use at session close before reconciling docs, or when Brent says "context keeper", "save the session", "write the flight recorder", "snapshot this session", "record the session". Append-only — one new file per session, never edits prior snapshots, never overclaims.
    0 repo stars
  5. ▌
    Skills Librarian 2 · bbrysonelite-max
    Maintain Brent's INSTALLED skill library — audit ~/.codex/skills for integrity (name↔folder mismatches, missing SKILL.md, stray files, dead symlinks, inactive-profile leaks), reconcile it against the Git-backed codex-skills/SKILLS-INDEX.md (what's new vs stale), and regenerate that index preserving his categories. Read-only audit by default; fixes are per-item approved; it QUARANTINES cruft to the dump, never deletes. The maintenance complement to skill-miner (miner finds new skills; librarian keeps the shelf clean). Use when Brent says "skills librarian", "clean up my skills", "skills are a mess", "dedupe my skills", "update the skills index", "what skills do I have", or after building/installing skills.
    0 repo stars
  6. ▌
    Tiger Doc Keeper 2 · bbrysonelite-max
    The TIGER CLAW Document Keeper. Use when the Tiger Claw repo's living docs have drifted from reality — after a PR merges, when a decision/convention is locked, at session close, or when Brent asks to "reconcile the Tiger docs" / "update the Tiger docs". Runs the tiger-doc-keeper workflow directly to sync SOTU/NEXT_SESSION/PROGRESS/TO-DO/VERIFIED/ADRs/queues/Desktop punch-lists to current truth via ONE docs PR, respecting the repo's doc-CI guards. Docs only — never code. For ANY OTHER project, use the agnostic `doc-keeper` instead.
    0 repo stars
  7. ▌
    Assumptions Audit 2 · bbrysonelite-max bundle
    Use when a proposal, plan, or design needs its assumptions challenged against available evidence before implementation begins.
    0 repo stars
  8. ▌
    AI Evaluation Audit 2 · bbrysonelite-max bundle
    Use when an implemented AI feature needs its planned evaluation dimensions, guardrails, and evaluation infrastructure checked before deployment.
    0 repo stars
  9. ▌
    Integration Flow Audit 2 · bbrysonelite-max bundle
    Use when completed work needs an evidence-backed audit of end-to-end user flows, component boundaries, data propagation, and failure paths before release.
    0 repo stars
  10. ▌
    Threat Mitigation Audit 2 · bbrysonelite-max bundle
    Use when a declared threat model or risk register needs evidence that each recorded disposition and mitigation is implemented before release.
    0 repo stars
  11. ▌
    Codebase Pattern Mapping 2 · bbrysonelite-max bundle
    Use when an unfamiliar repository or proposed change needs evidence-backed analogs, conventions, and integration points before design or implementation.
    0 repo stars
  12. ▌
    Requirements Coverage Audit 2 · bbrysonelite-max bundle
    Use when requirements or acceptance criteria need traceability to tests and executable proof before work is declared complete.
    0 repo stars
  13. ▌
    Documentation Claim Verification 2 · bbrysonelite-max bundle
    Use when documentation, release notes, runbooks, or status reports contain factual claims that need verification against current implementation and executable evidence.
    0 repo stars
  14. ▌
    Gitnexus Impact Analysis 2 · bbrysonelite-max
    Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
    0 repo stars
  15. ▌
    Gws Workflow Meeting Prep 2 · bbrysonelite-max
    Google Workflow: Prepare for your next meeting: agenda, attendees, and linked docs.
    0 repo stars
  16. ▌
    Gws Workflow Email To Task 2 · bbrysonelite-max
    Google Workflow: Convert a Gmail message into a Google Tasks entry.
    0 repo stars
  17. ▌
    Gws Workflow File Announce 2 · bbrysonelite-max
    Google Workflow: Announce a Drive file in a Chat space.
    0 repo stars
  18. ▌
    Gws Workflow Weekly Digest 2 · bbrysonelite-max
    Google Workflow: Weekly summary: this week's meetings + unread email count.
    0 repo stars
  19. ▌
    Gws Workflow Standup Report 2 · bbrysonelite-max
    Google Workflow: Today's meetings + open tasks as a standup summary.
    0 repo stars
  20. ▌
    Gws Shared 2 · bbrysonelite-max
    gws CLI: Shared patterns for authentication, global flags, and output formatting.
    0 repo stars
  21. ▌
    Gitnexus CLI 2 · bbrysonelite-max
    Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"
    0 repo stars
  22. ▌
    Gws Workflow 2 · bbrysonelite-max
    Google Workflow: Cross-service productivity workflows.
    0 repo stars
  23. ▌
    Page Rethink 2 · bbrysonelite-max
    Use when an existing production web page (tigerclaw.io, brentbryson.ai, any live site) "reads like a wall of text", visitors wouldn't know what they're reading, the copy has too much "so what", Brent asks for design/copy mockups or "other options" for a page, or a page rethink needs to ship without disrupting live wiring. Not for brand-new sites (use design-consultation or intro-page) and not for bugs (use production-debugging-loop).
    0 repo stars
  24. ▌
    Gitnexus Guide 2 · bbrysonelite-max
    Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?"
    0 repo stars
  25. ▌
    Gitnexus Debugging 2 · bbrysonelite-max
    Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"
    0 repo stars
  26. ▌
    Gitnexus Exploring 2 · bbrysonelite-max
    Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"
    0 repo stars
  27. ▌
    Gitnexus Pr Review 2 · bbrysonelite-max
    Use when the user wants to review a pull request, understand what a PR changes, assess risk of merging, or check for missing test coverage. Examples: "Review this PR", "What does PR #42 change?", "Is this PR safe to merge?"
    0 repo stars
  28. ▌
    Gitnexus Refactoring 2 · bbrysonelite-max
    Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"
    0 repo stars
  29. ▌
    Agent Reach 2 · bbrysonelite-max bundle
    MUST USE when user wants to research/search/look up/find anything on the internet — e.g. "research this topic", "do a deep dive on X", "search the web for X", "see what people say about X", "look this up". Also MUST USE when user mentions any platform or shares any URL/link: Twitter/X, Reddit, Facebook, Instagram, YouTube, GitHub, Bilibili, XiaoHongShu, Xiaoyuzhou Podcast, LinkedIn/jobs/recruiting, V2EX, Xueqiu (stocks), RSS. 15 platforms, multi-backend routing (OpenCLI / per-platform CLIs / APIs). Zero config for 6 channels. Run `agent-reach doctor --json` to see which backend serves each platform right now. NOT for: writing reports/analysis/translation (this skill only FETCHES internet content); posting/commenting/liking (write operations); platforms that already have a dedicated skill installed (prefer that skill).
    0 repo stars
  30. ▌
    Allsup Leads Ssdi 2 · bbrysonelite-max bundle
    Run the monthly Allsup SSDI/SSI lead batch — the PROVEN process, end to end. Mines active claimants (Reddit + X, last 30 days), tiers them by claim urgency (best/better/good), writes ALLSUP-LEADS-{date}.csv/.md to the Desktop, builds a browsable "book" (searchable, tier-filterable HTML), publishes it to a permanent here.now link, and drafts the review email to Pat Sullivan (pat@contatta.com) for Brent to send on to Allsup. Use when Brent says "run the Allsup leads", "SSDI leads", "monthly claimant batch", "send Pat the leads", "run the refinery for Allsup", or "pull SSDI claimants". SSDI-ONLY and reachability-graded — never resolve individuals or chase emails/phones. For other (non-sensitive) Allsup verticals, build a separate skill; do NOT widen this one.
    0 repo stars
  31. ▌
    Claude Memory Debug 2 · bbrysonelite-max bundle
    Use when the user is debugging a regression, investigating unexpected behaviour, or wants to know the full change history of a component. Examples: "why did this break after the last deploy?", "what changed in the auth module recently?", "trace all changes to OrderService"
    0 repo stars
  32. ▌
    Claude Memory Index 2 · bbrysonelite-max bundle
    Use when the user wants to index a repository into claude-memory, start using claude-memory on a new project, or re-index after significant history. Examples: "index the lokumcu repo", "set up claude memory for this project", "re-index everything"
    0 repo stars
  33. ▌
    Claude Memory Search 2 · bbrysonelite-max bundle
    Use when the user asks about why code was written a certain way, wants to find commits related to a bug, feature or module, or needs historical context before editing. Examples: "why does the payment module use a state machine?", "what commits touched auth?", "find all discount-related bug fixes"
    0 repo stars
  34. ▌
    Claude Memory Status 2 · bbrysonelite-max bundle
    Use when the user wants to check what is indexed, how many commits are in memory, or whether claude-memory is set up correctly. Examples: "is claude memory set up?", "how many commits are indexed?", "check claude memory status"
    0 repo stars
  35. ▌
    Allsup Leads Veterans 2 · bbrysonelite-max bundle
    Run the Allsup VETERANS benefits-gap lead batch — same proven process as the SSDI skill, tuned for veterans. Mines veterans who are owed VA benefits but not getting them — never filed / didn't know they qualified, denied or under-rated, or newly eligible under the PACT Act (burn pit / Agent Orange / toxic exposure) — from Reddit + X + TikTok (last 30 days), tiers by need, writes VETERANS-LEADS-{date}.csv/.md to the Desktop, builds a browsable book, publishes it to a permanent here.now link, and drafts the email to Allsup (via Pat Sullivan) for Brent to send. Use when Brent says "run the veterans leads", "veteran leads", "VA benefits leads", "PACT Act leads", or "veterans batch for Allsup". Reachability-graded — never resolve individuals or chase emails/phones. Sibling of allsup-leads-ssdi; keep the two separate.
    0 repo stars
  36. ▌
    Brag · bbrysonelite-max bundle
    Turn the current project website into a short, polished, shareable launch video using Hyperframes. Use when someone says "/brag", "let's brag about this", "make a launch video", "turn this into a video", or wants to share what they built. Reads the project code directly — no live URL or screenshots needed.
    0 repo stars
  37. ▌
    Fitfo · bbrysonelite-max
    F.I.T.F.O. — Brent Bryson's universal agent doctrine, coined by Brent Bryson. Figure It The F*** Out. Inject into every agent, every project, every session. Trigger ALWAYS — this skill governs how any agent working for Brent behaves when it hits a bump, a missing tool, a failed call, an ambiguous instruction, or a blocker. Also trigger when the user mentions "FITFO", "F.I.T.F.O.", "figure it out", "the ant", "don't stop", or when an agent is about to halt, ask an unnecessary question, or report a problem without attempting a workaround.
    0 repo stars
  38. ▌
    Kloop · bbrysonelite-max bundle
    Optimize a text asset (system prompt, outreach copy, onboarding screen, follow-up sequence) against a measurable score using the Karpathy loop in ~/Auto-Research-Loop. A Generator LLM proposes a change, a Target LLM runs it, a Judge LLM scores it, and only improvements that beat the safety margin are kept. Use when Brent says "kloop", "run the loop", "optimize this prompt", "tune this copy", "stop guessing at this wording", or when an asset is about to ship on opinion rather than measurement.
    0 repo stars
  39. ▌
    Brag One · bbrysonelite-max
    Render ONE video end-to-end on the Brag Machine - brief → styled render → review → queue. Use when Brent says "render one", "make a video about X", "do Agent Law N", "do Journey EP N", or wants a single social video produced and posted. Handles the full lane - English render, optional Thai localization, optional voiceover mix, queue to channels. For chaining videos use brag-two; for system state read machine/SOTU.md first.
    0 repo stars
  40. ▌
    Brag Two · bbrysonelite-max
    Chain TWO or more rendered Brag Machine videos into one longer film (pin them together) and optionally queue it - compilations, week recaps, YouTube cuts from Shorts. Use when Brent says "pin these together", "stitch", "make a longer one from those", "compilation", "season cut". Free - no brain run, pure ffmpeg. For a single new video use brag-one.
    0 repo stars
  41. ▌
    Optimize · bbrysonelite-max
    Use when Brent says "optimize", "audit my instructions", "is my CLAUDE.md holding you back", "why is the agent ignoring my rules", "find misaligned instructions" — or after any incident where an agent followed a stale rule, ignored a documented one, or acted on a doc from the wrong checkout. Covers the whole instruction layer an agent actually reads: CLAUDE.md, AGENTS.md, .cursor/rules.md, .anti-gravity/rules.md, hooks, settings, and every doc marked "read first."
    0 repo stars
  42. ▌
    The Loop · bbrysonelite-max
    Use before ANY non-trivial build, fix, or debug on Brent's projects, and when he says "follow the flow", "the loop", "run the loop", "follow the pipeline". Also when work is starting without an audit, a spec, independent tests, or an independent review — skipping a step is vibe coding, skipping the audit is vibe debugging. For a confirmed production failure or incident, use /production-debugging-loop instead: this is the build pipeline, that is the closed-loop procedure the pipeline runs at the bug.
    0 repo stars
  43. ▌
    Brag Week · bbrysonelite-max
    Batch day - produce and schedule a full week of content on the Brag Machine in one sitting. Use when Brent says "we need a week of content", "do a batch", "batch day", "load next week". Renders the week's briefs, stages a numbered review folder, and on Brent's approval-by-number schedules everything into the 30-day-plan calendar slots (EN + Thai).
    0 repo stars
  44. ▌
    Tiny Team · bbrysonelite-max
    Runs work as "Tiny but Serious Inc." — one human plus four separated agent roles (Scout researches, Builder builds, Reviewer breaks, Agent Memory preserves), with Brent as the only goal-setter and gate. Use when Brent says "tiny team", "staff this", "run this as a team", "spin up the crew", or when a task is big enough to need parallel roles rather than one agent doing everything.
    0 repo stars
  45. ▌
    Brag Music · bbrysonelite-max
    Source, audition, and lock music for Brag Machine video series - licensed catalog tracks resolved as candidates Brent picks by ear. Use when Brent wants new/better/less generic music, a theme for a series, or says "find music", "the music is generic", "new theme". Never use commercial songs or covers (melody is copyrighted even instrumental - Content ID mutes/claims). Locked themes live in the machine's template assets and style files.
    0 repo stars
  46. ▌
    Brag Voice · bbrysonelite-max
    Brent's voice for any video or audio - local Voicebox clone (his ruling - "best generated voice I have ever had"). Use when adding narration/voiceover to a render, making a talking version of a video, generating Brent speech from text, or when Brent says "put my voice on it", "narrate it", "make it talk". Free, local, unlimited. HeyGen is for ON-CAMERA avatars only (separate YouTube system); this skill is voice-only.
    0 repo stars
  47. ▌
    Unfinished · bbrysonelite-max
    Use when Brent says "unskill", "what remains", "what's left", "what's unfinished/unverified/unconfirmed", "open debts", or at session close before a handoff — anything that asks what is still owed rather than what got done. Sweeps ground truth for every item that is UNFINISHED (started, not done), UNVERIFIED (claimed, no receipt), or UNCONFIRMED (awaiting his eyes or word). Session-end family: /closing-ritual runs the whole close and calls the others; /context-keeper writes the raw session record; /truth-keeper reconciles the standing docs. This one lists only the open debts — for the session snapshot use /context-keeper instead.
    0 repo stars
  48. ▌
    Agent Reach · bbrysonelite-max bundle
    MUST USE when user wants to research/search/look up/find anything on the internet — e.g. "research this topic", "do a deep dive on X", "search the web for X", "see what people say about X", "look this up". Also MUST USE when user mentions any platform or shares any URL/link: Twitter/X, Reddit, Facebook, Instagram, YouTube, GitHub, Bilibili, XiaoHongShu, Xiaoyuzhou Podcast, LinkedIn/jobs/recruiting, V2EX, Xueqiu (stocks), RSS. 15 platforms, multi-backend routing (OpenCLI / per-platform CLIs / APIs). Zero config for 6 channels. Run `agent-reach doctor --json` to see which backend serves each platform right now. NOT for: writing reports/analysis/translation (this skill only FETCHES internet content); posting/commenting/liking (write operations); platforms that already have a dedicated skill installed (prefer that skill).
    0 repo stars
  49. ▌
    Visit Jumbo · bbrysonelite-max
    Session-opening grounding ritual — pulls who Brent is, live lanes, last decisions, and open debts from Jumbo shared memory into a one-screen brief ending with a proposed anchor. Use when Brent says "visit jumbo", "visit jumbo for grounding", "ground yourself", "get up to speed", or at the start of any working session before taking on work. Fast (~30-60s). For the full per-lane dossier use /visit-jumbo-deep instead.
    0 repo stars
  50. ▌
    Brag Machine · bbrysonelite-max
    Use when Brent wants ANY video made or posted by the machine — motivational quote videos, coaching/teaching videos, a promo for any business or website, positive/personal/feel-good videos, chaining past videos together — or says "run the machine", "make a video about X", "post a video", "claw it". Siblings: /brag-one for one video end-to-end (Thai + voiceover), /brag-two to stitch renders into longer films, /brag-music to lock series themes, /wth-campaign to ship already-reviewed stock. NOT for editing footage or captioning existing video — use the hyperframes skills.
    0 repo stars
  51. ▌
    Jumbo Health · bbrysonelite-max
    On-demand health check of Brent's Jumbo memory system (containers, bridge, gateway, capture, backups, scheduled jobs, recall) ending in ONE loud GO / RED verdict with receipts. Use when Brent says "jumbo health", "check jumbo", "is jumbo up", "is my memory healthy", "memory health check", before relying on Jumbo in a new session, or after any machine restart / docker event / Anthropic outage. Read-only — never repairs, restarts, or deletes anything.
    0 repo stars
  52. ▌
    Wth Campaign · bbrysonelite-max bundle
    Use when Brent or Jill's schedule says "run the WTH campaign", "fill the WTH queue", "wth daily", "refill the social queue", on the daily WTH tick, or any time the WTH social queue is reported short, out of band, or its stock is questioned. Also use before scheduling anything to the 6 locked WTH surfaces. This skill only SHIPS already-reviewed stock — to render or make new video use /brag-machine instead. It is not the checker; the WTH-* rows in ~/daily-checks/run.sh grade this work independently.
    0 repo stars
  53. ▌
    Brag Personal · bbrysonelite-max
    Personal message videos - THE MACHINE personalized for one recipient with Brent's voice carrying his exact words. Use when Brent says "make one for <name>", "send a personal video", "do one like Chrissy's/Becca's", or gives a quoted message for a specific person. HIGH-VALUE lane (Brent - "a million uses"). NEVER queued to social - gift files only.
    0 repo stars
  54. ▌
    Longform Video · bbrysonelite-max
    Build a longform YouTube video for @BrentBrysonaios in the PROVEN mixed format — Brent's real on-camera footage interleaved with faceless HyperFrames teaching beats (Voicebox VO), optional blue-shirt clone appearances, and the LOCKED uniform cards from Youtube-system. Use for "make the video", "longform", "episode", "rework this cut". Shorts are cut FROM the output afterward (never sourced elsewhere). Proven end-to-end 2026-08-29 on what-is-a-flavored-agent-v5.mp4 (289.6s).
    0 repo stars
  55. ▌
    Beacon Protocol · bbrysonelite-max
    MANDATORY operating law for all BEACON work — Brent Bryson's visibility workstream (GEO/SEO, entity graph, citations, brentbryson.ai, YouTube channel packaging, backlinks, directories, baselines). Trigger this skill whenever a task touches getting Brent or Tiger Claw found or cited — search visibility, AI-answer citations, robots/sitemaps/llms.txt, JSON-LD/schema, sameAs, bios, YouTube titles or descriptions, directory listings, baseline query runs, or the brentbryson.ai site. If the work is about being FOUND rather than building the product, this skill governs it. Load BEFORE executing.
    0 repo stars
  56. ▌
    Loading Secrets · bbrysonelite-max
    Use when any task needs an API key, token, login, or password — before searching for credentials, asking Brent for a key, or wiring a service. Also use when a key is missing, an env file can't be found, or you're about to cat/echo a credentials file.
    0 repo stars
  57. ▌
    Desktop Delivery · bbrysonelite-max
    Whenever a document is produced for Brent to READ or REVIEW — a spec, a PRD, a plan, a design doc, a report, an audit — copy it to his Desktop the moment it's ready, without being asked. He reads from the Desktop, not from repo paths. Invoke automatically any time you hand him a document for review; also when he says "put it on my desktop", "where's the doc", or "so I can find it".
    0 repo stars
  58. ▌
    Two Brents Brand · bbrysonelite-max bundle
    Use whenever creating ANY content for Brent — YouTube scripts, hooks, social posts, landing pages, emails, community content — or when he says "Two Brents," "AI Brent," "Brent Classic," "the clone," "brand card," "video card," "Probe Academy," "AlienProbe," "in my voice," or "on brand." Also trigger before writing anything that teaches AI to non-technical audiences or network marketers on his behalf. Twin: this is the BRAND layer (voice, characters, story canon, compliance); for the requalification mission, the Mine, or the Flip the Script funnel use /the-rebuild instead.
    0 repo stars
  59. ▌
    Visit Jumbo Deep · bbrysonelite-max
    Deep grounding dossier — chains /visit-jumbo's quick brief first, then drills per-lane Jumbo queries, repo/PR states, and a full health verdict into a working dossier. Use when Brent says "visit jumbo deep", "deep grounding", "full dossier", "ground yourself deep", after a long gap between sessions, or before taking on a consequential build. Slower (several minutes). For a fast session start use /visit-jumbo.
    0 repo stars
  60. ▌
    Allsup Leads Ssdi · bbrysonelite-max bundle
    Use when Brent says "run the Allsup leads", "SSDI leads", "monthly claimant batch", "send Pat the leads", or "pull SSDI claimants". SSDI-only; never resolve individuals. Sibling: /allsup-leads-veterans for the VA benefits-gap batch — keep the two separate; any other Allsup vertical gets a third skill.
    0 repo stars
  61. ▌
    Brents Daily Checks · bbrysonelite-max bundle
    Use when Brent says 'daily checks', 'run my daily checks', 'Brent's daily checks', 'morning checks', 'check everything', or asks for the health of all the active businesses. Parent orchestrator over the whole portfolio. For Tiger-only health use /tigerclaw-daily-checks instead; for Alien Probe product planning use /alienprobe-product-puck instead.
    0 repo stars
  62. ▌
    Claude Memory Debug · bbrysonelite-max
    Use when the user is debugging a regression, investigating unexpected behaviour, or wants to know the full change history of a component. Examples: "why did this break after the last deploy?", "what changed in the auth module recently?", "trace all changes to OrderService"
    0 repo stars
  63. ▌
    Claude Memory Index · bbrysonelite-max
    Use when the user wants to index a repository into claude-memory, start using claude-memory on a new project, or re-index after significant history. Examples: "index the lokumcu repo", "set up claude memory for this project", "re-index everything"
    0 repo stars
  64. ▌
    Brent Office Manager · bbrysonelite-max bundle
    Use when Brent says 'office manager', 'weekly sweep', 'Monday sweep', 'what's on my plate', 'open loops', 'where's that file', 'organize this', 'file this', or drops a document that needs a home. Also when something is clearly about to fall through the cracks. For money questions and the Straight Truth numbers use /brent-cfo instead; for hunting revenue use /brent-cro instead.
    0 repo stars
  65. ▌
    Claude Memory Search · bbrysonelite-max
    Use when the user asks about why code was written a certain way, wants to find commits related to a bug, feature or module, or needs historical context before editing. Examples: "why does the payment module use a state machine?", "what commits touched auth?", "find all discount-related bug fixes"
    0 repo stars
  66. ▌
    Claude Memory Status · bbrysonelite-max
    Use when the user wants to check what is indexed, how many commits are in memory, or whether claude-memory is set up correctly. Examples: "is claude memory set up?", "how many commits are indexed?", "check claude memory status"
    0 repo stars
  67. ▌
    System Status Triage · bbrysonelite-max
    Use when the tiger-claw admin dashboard (wizard.tigerclaw.io/admin) shows YELLOW (DEGRADED) or RED (DOWN), a dependency card is red, a fire-test receipt FAILs, an ops banner/alert fires ("Stripe webhook not firing", synthmon heartbeat silent, worker stall, billing canary), or someone says "the system is down" / "X is not firing" — before concluding the system is down, panicking, or changing any code. For a confirmed hard outage where `/health` itself returns 503 or the front door is unreachable, use /production-debugging-loop instead — that is the fix loop, this is the read-only triage that decides whether there is anything to fix.
    0 repo stars
  68. ▌
    Allsup Leads Veterans · bbrysonelite-max bundle
    Run the Allsup VETERANS benefits-gap lead batch — same proven process as the SSDI skill, tuned for veterans. Mines veterans who are owed VA benefits but not getting them — never filed / didn't know they qualified, denied or under-rated, or newly eligible under the PACT Act (burn pit / Agent Orange / toxic exposure) — from Reddit + X + TikTok (last 30 days), tiers by need, writes VETERANS-LEADS-<date>.csv/.md to the Desktop, builds a browsable book, publishes it to a permanent here.now link, and drafts the email to Allsup (via Pat Sullivan) for Brent to send. Use when Brent says "run the veterans leads", "veteran leads", "VA benefits leads", "PACT Act leads", or "veterans batch for Allsup". Reachability-graded — never resolve individuals or chase emails/phones. Sibling of allsup-leads-ssdi; keep the two separate.
    0 repo stars
  69. ▌
    Alienprobe Product Puck · bbrysonelite-max bundle
    Run Alien Probe's evidence-backed product-discovery and 90-day planning discipline. Use for Alien Probe product strategy, deciding the next paid agent-to-agent data SKU, reviewing what agents buy or will pay for, checking whether NAICS/LEI have independent or repeat buyers, evaluating VIN/ICD-10/OSHA/USC/CFR/who/same/alive/changed candidates, answering where the agent-commerce puck is going, or as the Alien Probe planning item inside Daily Checks. Planning and read-only measurement only: never build, deploy, settle, purchase, list, contact buyers, or modify credentials unless Brent separately authorizes that action.
    0 repo stars
  70. ▌
    Mine · bbrysonelite-max bundle
    Run the agnostic Data Mine against a vertical — find raw "ore" (people/orgs showing a signal) from the configured surfaces over the last 30 days. Use when Brent says "run the mine", "mine {vertical}", "run the data mine against {X}", or wants raw leads for a vertical (e.g. ssdi-work-fear, network-marketers). The mine finds ore; the refinery grades it into high-value leads (separate step).
    0 repo stars
  71. ▌
    Production Debugging Loop · bbrysonelite-max
    Use when debugging any failure, regression, broken test, or production incident — including payment/Stripe bugs, webhook or queue/job failures, auth/session issues, tenant-isolation leaks, onboarding/wizard failures, UI regressions, or agent behavior bugs. Especially for the Tiger / tiger-claw-v4-core codebase, where it adds money/tenant/webhook invariants. For a build, or for a debug run inside Brent's full pipeline (audit → spec → plan → independent tests → PR → review → HIS merge → prove), use /the-loop instead — that is the pipeline, this is the procedure it runs at the bug.
    0 repo stars
  72. ▌
    Refine · bbrysonelite-max bundle
    Refine raw mine ore into resolved, contactable INDIVIDUAL leads — the refinery half that the /mine skill defers. Takes a Datamine ore .jsonl, confirms each handle's cross-platform presence with Sherlock, DROPS any orgs/lawyers/directories (zero value — never a deliverable), then resolves the individuals into identity + contact cards (name, profiles, verified email) with blue-healer. Individuals are the only target — never ask which group. Use when Brent says "refine the ore", "run the refinery", "resolve these handles", "turn ore into leads", or hands over a mine run's JSONL.
    0 repo stars
  73. ▌
    Ship It · bbrysonelite-max bundle
    Take a TigerClaw PR from green to live — watch CI to completion, merge on Brent's explicit per-PR approval, verify the merge landed (state MERGED + merged SHA), watch the Cloud Run deploy, and verify the live api.tigerclaw.io/health gitSha matches the merged SHA. Reports a timestamped GO / PARTIAL verdict. Use when Brent says "ship it", "merge and verify", "merge {PR#}", "watch CI then merge", "verify the deploy", "is it live", "verify health after deploy", or asks to take a PR to production. Encodes his rules: never push to main, verify MERGED, inspect the merged SHA's deploy (not the PR-head rollup), live health check, timestamp everything UTC.
    0 repo stars
  74. ▌
    Graphify · bbrysonelite-max bundle
    Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
    0 repo stars
  75. ▌
    Here Now · bbrysonelite-max bundle
    Publish files and folders to the web instantly. Static hosting for HTML sites, images, PDFs, and any file type. Use when asked to "publish this", "host this", "deploy this", "share this on the web", "make a website", "put this online", "upload to the web", "create a webpage", "share a link", "serve this site", or "generate a URL". Outputs a live, shareable URL at {slug}.here.now.
    0 repo stars
  76. ▌
    Blueprint · bbrysonelite-max bundle
    Use when defining the golden lead and money-in-hand buyer for a vertical BEFORE any scraping or enrichment is built — stage #1 of The Refinery. Runs a demand-first, recursive who/what/when/where/why/how inquiry (research + operator confirmation) and emits a Golden Lead Definition grounded in a confirmed paying buyer, plus an audit-trail inquiry tree. Trigger on "define the golden lead", "who would pay for this lead", "blueprint a lead for {industry}".
    0 repo stars
  77. ▌
    Doc Keeper · bbrysonelite-max bundle
    The project-agnostic Document Keeper. Use on ANY project when its living/dashboard docs have drifted from reality — after a PR merges, when a decision/convention is locked, at session close (after context-keeper), or when the user says "reconcile the docs" / "update the docs" / "the docs are stale". Runs the doc-keeper workflow directly; it DISCOVERS whatever living docs the project actually has (README, CHANGELOG, status/handoff docs, ADRs, docs/, a domain index, punch-lists) and reconciles them to current truth via ONE docs PR on the repo's default branch. Docs only — never code; never merges. For the Tiger Claw repo specifically, use the specialized `tiger-doc-keeper` instead (it knows that repo's SOTU/PROGRESS/CI guards).
    0 repo stars
  78. ▌
    Gws Shared · bbrysonelite-max bundle
    gws CLI: Shared patterns for authentication, global flags, and output formatting.
    0 repo stars
  79. ▌
    Intro Page · bbrysonelite-max bundle
    Builds a private, dignified one-page introduction/credibility website for a specific high-value recipient (e.g. introducing Brent to an incoming CEO, a leader, or a partner), then publishes it permanently to a custom domain. Use when Brent wants to introduce himself to someone important without reciting his résumé on a call, asks to "make an intro page / one-pager / credibility page / about-me link" for a named person, or wants a clean link to hand someone. Defers visual design to frontend-design and any fact-finding research to deep-research.
    0 repo stars
  80. ▌
    Signal Mine · bbrysonelite-max bundle
    Run the signal-mining pipeline — find public evidence of demand, fear, confusion, and intent before people become leads, then map communities, creators, and partner orgs with the safest contact path for each. Use when Brent says "signal mine", "run the signal mine", "mine signals", asks to refresh the Contatta/Pat org map, or starts demand-signal research for a new vertical.
    0 repo stars
  81. ▌
    Skill Miner · bbrysonelite-max bundle
    Mine Brent's past Codex session rollouts and context snapshots to surface recurring routines that should become reusable skills, deduped against what already exists, then SUGGEST the strongest new candidate(s) to Brent for a build decision. A read-only research loop — it proposes, it never auto-builds. Use when Brent says "run skill-miner", "mine my sessions", "what should be a skill", "find new skills", "auto research for skills", or on a monthly cadence via /schedule. Pairs with the BACKLOG.md ledger so each run mainly surfaces NEW routines.
    0 repo stars
  82. ▌
    Gitnexus CLI · bbrysonelite-max bundle
    Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"
    0 repo stars
  83. ▌
    Ground Truth · bbrysonelite-max bundle
    The first move of every task, and the doctrine every other skill inherits. You never act on, or say, anything about code, data, or system state until you have seen with your own tools that it is true — right now, in the real place. Memory, docs, assumptions, and the shape of code are never the starting point and never proof. Use at the start of any task, before reporting anything as done, before writing to a canonical ledger (VERIFIED.md/SOTU), and any time you are about to state something you have not directly observed. When Brent says "ground truth", "ground this", "is that grounded", "prove it", "how do you know", or "verify don't assume", invoke this first.
    0 repo stars
  84. ▌
    Gws Workflow · bbrysonelite-max bundle
    Google Workflow: Cross-service productivity workflows.
    0 repo stars
  85. ▌
    Page Rethink · bbrysonelite-max bundle
    Use when an existing production web page (tigerclaw.io, brentbryson.ai, any live site) "reads like a wall of text", visitors wouldn't know what they're reading, the copy has too much "so what", Brent asks for design/copy mockups or "other options" for a page, or a page rethink needs to ship without disrupting live wiring. Not for brand-new sites (use design-consultation or intro-page) and not for bugs (use production-debugging-loop).
    0 repo stars
  86. ▌
    Truth Keeper · bbrysonelite-max bundle
    Keep Brent's truth zero-drift across its TWO layers — the lean universal flyover at ~/Desktop/Truth/ (facts about Brent + things true across ALL projects) and each project's own detail living in its GitHub repo. Guards the boundary between them so neither rots. Use when the user says 'update my docs', 'update the truth', 'refresh the truth', 'keep the truth current', 'the truth is drifted', or right after a build session changed something a doc describes.
    0 repo stars
  87. ▌
    Failure Modes · bbrysonelite-max bundle
    A comprehensive, grounded method (FMEA + pre-mortem + red-team) that sweeps every failure surface of a target — software, module, process, or workflow — names every way it can fail from the micro level to the macro level, then INVERTS each failure into the specific designed strength that cancels it. Exhaustive by design; produces concrete security/UI/UX/reliability improvements as output. Distinct from blind-spots-audit (which finds unknown-unknowns) — this is the systematic sweep of mostly-known surfaces. Use when Brent says "failure modes", "how can/would this fail", "how do I fail", "FMEA", "pre-mortem", "fortify/harden this", "stress every surface", "where is this weak", "make it bulletproof", or before shipping / when designing for robustness.
    0 repo stars
  88. ▌
    Vault Hygiene · bbrysonelite-max bundle
    Use when performing daily vault maintenance, when indexes may be stale, when files are misplaced or missing frontmatter, when STATUS.md or memory files have drifted from reality, or when invoked by the daily scheduled trigger. Also use after any bulk ingestion or file reorganization.
    0 repo stars
  89. ▌
    Closing Ritual · bbrysonelite-max bundle
    Run the end-of-session closing ritual on ANY project so a working session ends clean and verified — all work merged, tests green, the project's living docs matching the code (zero drift), durable state saved to memory, git clean, and a short handoff. Project-agnostic: it locates whatever project you worked in and gathers ITS docs (you don't remember anything between sessions — collect the real artifacts). Use when the user says 'close out', 'closing ritual', 'wrap up', 'wind down', 'end of session', 'let's call it', or is otherwise ending a session.
    0 repo stars
  90. ▌
    Context Keeper · bbrysonelite-max bundle
    Write the append-only per-session flight recorder to the CURRENT project's .codex/sessions/ — a dated, numbered snapshot of what THIS session decided, discovered, shipped, verified (vs not), and the next step. Project-agnostic — works for any project; defaults to the current git repo root (override with CONTEXT_KEEPER_DIR). Records the session (the raw record); a separate docs-reconcile step then updates the project's living docs. Use at session close before reconciling docs, or when Brent says "context keeper", "save the session", "write the flight recorder", "snapshot this session", "record the session". Append-only — one new file per session, never edits prior snapshots, never overclaims.
    0 repo stars
  91. ▌
    Gitnexus Guide · bbrysonelite-max bundle
    Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?"
    0 repo stars
  92. ▌
    Cloud Run Reauth · bbrysonelite-max bundle
    Restore and use gcloud access to TigerClaw prod (Cloud Run + Cloud SQL + Secret Manager) when the daily-expiring tokens have lapsed. Run an auth pre-check up front so a task never half-stalls; on expiry, run the interactive reauth (one browser sign-in); start cloud-sql-proxy; and fetch Secret Manager secrets as RAW BYTES (encoding the trailing-newline gotcha so HMAC/encryption never silently mismatches). Use when a gcloud/Secret-Manager/Cloud SQL command returns expired/Unauthorized, before any prod-DB or Secret-Manager work, or when Brent says "reauth", "gcloud is expired", "run the cloud run reauth", "start the proxy", or asks to operate against prod. Companion to ship-it (which assumes GCP is already reachable).
    0 repo stars
  93. ▌
    Skills Librarian · bbrysonelite-max bundle
    Maintain Brent's INSTALLED skill library — audit ~/.codex/skills for integrity (name↔folder mismatches, missing SKILL.md, stray files, dead symlinks, inactive-profile leaks), reconcile it against the Git-backed codex-skills/SKILLS-INDEX.md (what's new vs stale), and regenerate that index preserving his categories. Read-only audit by default; fixes are per-item approved; it QUARANTINES cruft to the dump, never deletes. The maintenance complement to skill-miner (miner finds new skills; librarian keeps the shelf clean). Use when Brent says "skills librarian", "clean up my skills", "skills are a mess", "dedupe my skills", "update the skills index", "what skills do I have", or after building/installing skills.
    0 repo stars
  94. ▌
    Tiger Doc Keeper · bbrysonelite-max bundle
    The TIGER CLAW Document Keeper. Use when the Tiger Claw repo's living docs have drifted from reality — after a PR merges, when a decision/convention is locked, at session close, or when Brent asks to "reconcile the Tiger docs" / "update the Tiger docs". Runs the tiger-doc-keeper workflow directly to sync SOTU/NEXT_SESSION/PROGRESS/TO-DO/VERIFIED/ADRs/queues/Desktop punch-lists to current truth via ONE docs PR, respecting the repo's doc-CI guards. Docs only — never code. For ANY OTHER project, use the agnostic `doc-keeper` instead.
    0 repo stars
  95. ▌
    Tiger Whitepaper · bbrysonelite-max bundle
    Generate a branded Tiger Claw white paper as a print-ready PDF, anywhere on the technical-to-marketing scale — a science paper, a technology paper (with some marketing), or a marketing paper (with some technology). Every paper carries the same signature: a dark branded cover, a numbered + signable confidentiality receipt, the brand palette/fonts, bigger type, no emojis, and honest live/built/pending labeling. Use when Brent says "white paper", "make a white paper", "team white-label pitch", "science/technical white paper", references white-paper No. NNN, or asks to turn a pitch into a branded PDF for a leader/partner.
    0 repo stars
  96. ▌
    Whitelabel Radar · bbrysonelite-max bundle
    Turns a 30-day trend pulse into a segmented, contactable white-label / group-sale target list of network-marketing leaders for Brent's Tiger Claw. Chains the last30days skill (the pulse) to tiger-leader-hunt (deep scoring). Use when Brent says "whitelabel radar", "find white-label partners / targets", "who can I white-label Tiger to", "turn this trend into leads/targets", or wants to find NM coaches/trainers/authors to resell a branded Tiger to. Defers trend research to last30days and leader scoring to tiger-leader-hunt.
    0 repo stars
  97. ▌
    Assumptions Audit · bbrysonelite-max bundle
    Use when a proposal, plan, or design needs its assumptions challenged against available evidence before implementation begins.
    0 repo stars
  98. ▌
    Blind Spots Audit · bbrysonelite-max bundle
    Surface what Brent ISN'T asking, the assumptions in play, what the work missed, and what the agent itself got wrong — the inverse of grill-me (grill-me stress-tests a plan you have; this surfaces what you don't have). Produces a grounded, prioritized list of blind spots, each with the specific question to ask or thing to verify, ending with the top few to resolve before proceeding. Use when Brent says "what am I not asking", "what don't I know", "what should I ask", "what did I forget", "what did we miss", "what did you miss", "blind spots", "devil's advocate", "poke holes", or at the end of a build / before a consequential decision.
    0 repo stars
  99. ▌
    Gitnexus Debugging · bbrysonelite-max bundle
    Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"
    0 repo stars
  100. ▌
    Gitnexus Exploring · bbrysonelite-max bundle
    Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"
    0 repo stars