
Give your agent persistent cross-session memory — recall what went wrong on similar tasks before starting, then capture whether the work succeeded or failed so repeated mistakes auto-promote into prevention rules. Runs locally via the ThumbGate MCP server (recall, capture_feedback, prevention_rules, feedback_stats) — no API key needed. Use when the user says "recall", "what went wrong last time", "remember this for next time", "capture feedback", "thumbs up/down on that", or at the start of a new task or session. Do NOT use when the user wants to force one specific mistake into an enforced block gate (use the thumbgate-guard skill), to list rules that already exist (thumbgate-rules), or to check ThumbGate wiring (thumbgate-doctor).
Course-correct from over-planning to execution — when the agent has produced a plan, research, or options instead of doing work the user already approved, drop the analysis and execute the smallest end-to-end action now (branch, run, deploy, verify). Use when the user says "stop planning, just do it", "why are you researching, execute", "just ship it", "enough analysis", or pushes back that you keep proposing instead of acting on an already-decided task. Do NOT use when the task is genuinely undecided and needs a plan first, when the user explicitly asked for research/options/a design, or for routine work where no over-planning has occurred — acting on an unscoped or destructive task is its own failure.
Turn the agent's most recent mistake into an enforced ThumbGate prevention rule (a PreToolUse block gate) so the same bad tool call is intercepted before it runs again, in this and every future session across Claude Code, Cursor, Codex, Gemini, Amp, and Cline. Captures the failure with the capture_feedback MCP tool, then force-promotes it via `npx thumbgate force-gate` so it is enforced, not just logged. Use when the user says "guard against this", "block this from happening again", "never do that again", "make that a rule", "stop the agent from repeating that", or right after a bad action or thumbs-down that should become a hard rule. Do NOT use to merely log a thumbs-up/down without enforcement (use the thumbgate-feedback skill), to recall prior context before starting work (use the Agent Memory skill), or to list rules that already exist (use the thumbgate-rules skill).
Health-check whether ThumbGate is actually wired into this agent — PreToolUse/SessionStart hooks installed, MCP server reachable, lesson store present, statusline, and overall agent-readiness — then report exactly what to fix. Runs the existing `npx thumbgate doctor` audit and the check_operational_integrity MCP tool. Use when the user says "is ThumbGate wired up", "thumbgate doctor", "check my guardrails are installed", "why aren't my gates firing", "is the MCP server connected", or "agent readiness". Do NOT use to view rules (use the thumbgate-rules skill), to view what was blocked (use the thumbgate-blocked skill), or to capture a new rule (use the thumbgate-guard skill) — this skill only diagnoses setup and wiring.
--- name: ThumbGate Brand Voice description: Make any ThumbGate-facing copy — landing/pricing/compare/guide pages, README, postinstall banners, CLI receipts, Reddit/LinkedIn/Bluesky/Threads posts, docs, outreach drafts, blog/launch content — sound like ThumbGate: direct, technical, honest, anti-hype. Use BEFORE writing or editing customer-facing or marketing text, and when the user says "write a landing page", "draft a Reddit/LinkedIn post", "write the README", "make this on-brand", "punch up th
Give your agent persistent cross-session memory — recall what went wrong on similar tasks before starting, then capture whether the work succeeded or failed so repeated mistakes auto-promote into prevention rules. Runs locally via the ThumbGate MCP server (recall, capture_feedback, prevention_rules, feedback_stats) — no API key needed. Use when the user says "recall", "what went wrong last time", "remember this for next time", "capture feedback", "thumbs up/down on that", or at the start of a new task or session. Do NOT use when the user wants to force one specific mistake into an enforced block gate (use the thumbgate-guard skill), to list rules that already exist (thumbgate-rules), or to check ThumbGate wiring (thumbgate-doctor).
# Skill: Verify Pricing Surfaces Repeatable skill for verifying all revenue-generating pages are live, have analytics, and have working Stripe links. Covers both ThumbGate and ApplyOps. ## When to use - Session startup (quick health check) - After any deploy to ThumbGate or ApplyOps - CEO asks "why aren't we making money?" or "is everything working?" - Before any pricing/checkout changes ## Steps ### 1. ThumbGate pricing surfaces ```bash # Homepage — all 3 analytics curl -sL https://thumbg
Capture thumbs up/down feedback into structured memories and prevention rules. Require one sentence of why before claiming memory promotion. Use when user gives explicit quality signals about agent work (e.g. "that worked", "that failed", "thumbs up/down"). Do NOT use for general questions, code generation, file operations, or any task that is not explicit feedback on prior agent output.
List the active ThumbGate prevention rules, reliability rules, and the promoted lessons behind them, so the user can see which guardrails are currently protecting this project and WHY each one exists. Reads the live rule and lesson stores via the prevention_rules, get_reliability_rules, and search_lessons MCP tools (CLI fallback `npx thumbgate rules`). Use when the user says "what is ThumbGate protecting me from", "show my rules", "show my gates", "what has the agent learned", "list active guardrails", or "what's blocked here". Do NOT use to CREATE a new rule (use the thumbgate-guard skill), to see runtime enforcement counts of what actually fired (use the thumbgate-blocked skill), or to diagnose whether ThumbGate is wired up at all (use the thumbgate-doctor skill).
Inspect this repo's branch and release governance (protected branches, release rules, protected-file globs) and, only when the user explicitly approves, grant a scoped, time-limited exception so a protected-file edit or publish can proceed under audit. Reads posture via the get_branch_governance MCP tool and records a narrow, expiring approval via the approve_protected_action MCP tool. Use when the user says "is main protected", "show branch governance", "what am I blocked from editing", "approve this protected change", or "let me edit a protected file just this once". Do NOT use to disable protection wholesale, to grant broad or standing exceptions, or to diagnose hook wiring (use the thumbgate-doctor skill) — this skill is for narrow, temporary, audited approvals only.
Capture thumbs up/down feedback into structured memories and prevention rules. Require one sentence of why before claiming memory promotion. Use when user gives explicit quality signals about agent work (e.g. "that worked", "that failed", "thumbs up/down"). Do NOT use for general questions, code generation, file operations, or any task that is not explicit feedback on prior agent output.
Show ThumbGate's enforcement record — how many risky actions were actually blocked versus warned, which gates fire most, the tokens/damage saved, and the full feedback to check to rejection pipeline. Reads live enforcement counters via the gate_stats and enforcement_matrix MCP tools (CLI fallback `npx thumbgate gate-stats`). Use when the user says "what has ThumbGate blocked", "show gate stats", "is enforcement working", "how many tokens did we save", "show the enforcement matrix", or "what got stopped". Do NOT use to list rule DEFINITIONS that exist (use the thumbgate-rules skill), to create a new rule (use the thumbgate-guard skill), or to check whether ThumbGate is installed and wired (use the thumbgate-doctor skill).
# Skill: Verify Pricing Surfaces Repeatable skill for verifying all revenue-generating pages are live, have analytics, and have working Stripe links. Covers both ThumbGate and ApplyOps. ## When to use - Session startup (quick health check) - After any deploy to ThumbGate or ApplyOps - CEO asks "why aren't we making money?" or "is everything working?" - Before any pricing/checkout changes ## Steps ### 1. ThumbGate pricing surfaces ```bash # Homepage — all 3 analytics curl -sL https://thumbg
Course-correct from over-planning to execution — when the agent has produced a plan, research, or options instead of doing work the user already approved, drop the analysis and execute the smallest end-to-end action now (branch, run, deploy, verify). Use when the user says "stop planning, just do it", "why are you researching, execute", "just ship it", "enough analysis", or pushes back that you keep proposing instead of acting on an already-decided task. Do NOT use when the task is genuinely undecided and needs a plan first, when the user explicitly asked for research/options/a design, or for routine work where no over-planning has occurred — acting on an unscoped or destructive task is its own failure.
List the active ThumbGate prevention rules, reliability rules, and the promoted lessons behind them, so the user can see which guardrails are currently protecting this project and WHY each one exists. Reads the live rule and lesson stores via the prevention_rules, get_reliability_rules, and search_lessons MCP tools (CLI fallback `npx thumbgate rules`). Use when the user says "what is ThumbGate protecting me from", "show my rules", "show my gates", "what has the agent learned", "list active guardrails", or "what's blocked here". Do NOT use to CREATE a new rule (use the thumbgate-guard skill), to see runtime enforcement counts of what actually fired (use the thumbgate-blocked skill), or to diagnose whether ThumbGate is wired up at all (use the thumbgate-doctor skill).
Inspect this repo's branch and release governance (protected branches, release rules, protected-file globs) and, only when the user explicitly approves, grant a scoped, time-limited exception so a protected-file edit or publish can proceed under audit. Reads posture via the get_branch_governance MCP tool and records a narrow, expiring approval via the approve_protected_action MCP tool. Use when the user says "is main protected", "show branch governance", "what am I blocked from editing", "approve this protected change", or "let me edit a protected file just this once". Do NOT use to disable protection wholesale, to grant broad or standing exceptions, or to diagnose hook wiring (use the thumbgate-doctor skill) — this skill is for narrow, temporary, audited approvals only.
--- name: ThumbGate Brand Voice description: Make any ThumbGate-facing copy — landing/pricing/compare/guide pages, README, postinstall banners, CLI receipts, Reddit/LinkedIn/Bluesky/Threads posts, docs, outreach drafts, blog/launch content — sound like ThumbGate: direct, technical, honest, anti-hype. Use BEFORE writing or editing customer-facing or marketing text, and when the user says "write a landing page", "draft a Reddit/LinkedIn post", "write the README", "make this on-brand", "punch up th
Show ThumbGate's enforcement record — how many risky actions were actually blocked versus warned, which gates fire most, the tokens/damage saved, and the full feedback to check to rejection pipeline. Reads live enforcement counters via the gate_stats and enforcement_matrix MCP tools (CLI fallback `npx thumbgate gate-stats`). Use when the user says "what has ThumbGate blocked", "show gate stats", "is enforcement working", "how many tokens did we save", "show the enforcement matrix", or "what got stopped". Do NOT use to list rule DEFINITIONS that exist (use the thumbgate-rules skill), to create a new rule (use the thumbgate-guard skill), or to check whether ThumbGate is installed and wired (use the thumbgate-doctor skill).
Health-check whether ThumbGate is actually wired into this agent — PreToolUse/SessionStart hooks installed, MCP server reachable, lesson store present, statusline, and overall agent-readiness — then report exactly what to fix. Runs the existing `npx thumbgate doctor` audit and the check_operational_integrity MCP tool. Use when the user says "is ThumbGate wired up", "thumbgate doctor", "check my guardrails are installed", "why aren't my gates firing", "is the MCP server connected", or "agent readiness". Do NOT use to view rules (use the thumbgate-rules skill), to view what was blocked (use the thumbgate-blocked skill), or to capture a new rule (use the thumbgate-guard skill) — this skill only diagnoses setup and wiring.
Turn the agent's most recent mistake into an enforced ThumbGate prevention rule (a PreToolUse block gate) so the same bad tool call is intercepted before it runs again, in this and every future session across Claude Code, Cursor, Codex, Gemini, Amp, and Cline. Captures the failure with the capture_feedback MCP tool, then force-promotes it via `npx thumbgate force-gate` so it is enforced, not just logged. Use when the user says "guard against this", "block this from happening again", "never do that again", "make that a rule", "stop the agent from repeating that", or right after a bad action or thumbs-down that should become a hard rule. Do NOT use to merely log a thumbs-up/down without enforcement (use the thumbgate-feedback skill), to recall prior context before starting work (use the Agent Memory skill), or to list rules that already exist (use the thumbgate-rules skill).
# Skill: Configure Analytics Repeatable skill for setting up Plausible, PostHog, and GA4 analytics keys in both local `.env` and Railway production environment variables. ## When to use - New session notices analytics env vars are missing - After rotating any analytics API key - After creating a new GA4 property ## Prerequisites - Chrome logged into: plausible.io, us.posthog.com, analytics.google.com - Railway MCP authenticated OR Chrome logged into railway.com ## Steps ### 1. Gather keys
# Skill: Pull Funnel Data Repeatable skill for pulling checkout funnel analytics data from all sources into a readable local report. ## When to use - CEO asks "why aren't we making money?" or "what does the funnel look like?" - Before any pricing/checkout changes - Weekly revenue check-in ## Steps ### 1. Run the live Plausible poller ```bash cd /Users/igorganapolsky/workspace/git/igor/ThumbGate/repo npm run social:poll:plausible ``` This pulls live Plausible visitors, source attribution,
# Skill: Configure Analytics Repeatable skill for setting up Plausible, PostHog, and GA4 analytics keys in both local `.env` and Railway production environment variables. ## When to use - New session notices analytics env vars are missing - After rotating any analytics API key - After creating a new GA4 property ## Prerequisites - Chrome logged into: plausible.io, us.posthog.com, analytics.google.com - Railway MCP authenticated OR Chrome logged into railway.com ## Steps ### 1. Gather keys
# Skill: ApplyOps Deploy Repeatable skill for deploying ApplyOps pages to GitHub Pages with full analytics. ## When to use - After any ApplyOps page edit (pricing, copy, new tier) - After rotating analytics keys - When CEO says "ApplyOps is down" or pages return 404 ## Architecture - **Source of truth:** `IgorGanapolsky/Resume` repo, `docs/applyops/` (private) - **Deployed to:** `IgorGanapolsky/IgorGanapolsky.github.io` repo, `/applyops/` (public) - The Resume repo is private — GitHub Pages
Capture thumbs up/down feedback into structured memories and prevention rules. Use when user gives explicit quality signals about agent work (e.g. "that worked", "that failed", "thumbs up/down"). Do NOT use for general questions, code generation, file operations, or any task that is not explicit feedback on prior agent output.
Capture thumbs up/down feedback into structured memories and prevention rules. Use when user gives explicit quality signals about agent work (e.g. "that worked", "that failed", "thumbs up/down"). Do NOT use for general questions, code generation, file operations, or any task that is not explicit feedback on prior agent output.
# Skill: Pull Funnel Data Repeatable skill for pulling checkout funnel analytics data from all sources into a readable local report. ## When to use - CEO asks "why aren't we making money?" or "what does the funnel look like?" - Before any pricing/checkout changes - Weekly revenue check-in ## Steps ### 1. Run the live Plausible poller ```bash cd /Users/igorganapolsky/workspace/git/igor/ThumbGate/repo npm run social:poll:plausible ``` This pulls live Plausible visitors, source attribution,
# Skill: ApplyOps Deploy Repeatable skill for deploying ApplyOps pages to GitHub Pages with full analytics. ## When to use - After any ApplyOps page edit (pricing, copy, new tier) - After rotating analytics keys - When CEO says "ApplyOps is down" or pages return 404 ## Architecture - **Source of truth:** `IgorGanapolsky/Resume` repo, `docs/applyops/` (private) - **Deployed to:** `IgorGanapolsky/IgorGanapolsky.github.io` repo, `/applyops/` (public) - The Resume repo is private — GitHub Pages
Govern Cursor SDK local, cloud, self-hosted, and subagent coding runs before they create branches or PRs.
Govern Cursor SDK local, cloud, self-hosted, and subagent coding runs before they create branches or PRs.
ThumbGate provides pre-action gates for AI coding agents. It captures thumbs-up/down feedback on agent actions, auto-promotes repeated failures into prevention rules, and blocks known-bad tool calls via PreToolUse hooks. Trigger when the user wants to add safety guardrails to an AI agent workflow, capture structured feedback on agent output, generate prevention rules from failure patterns, gate high-risk actions before execution, or export DPO training pairs from production feedback. Works with any MCP-compatible agent including Cursor, Codex, Gemini CLI, Amp, and OpenCode.
ThumbGate provides pre-action gates for AI coding agents. It captures thumbs-up/down feedback on agent actions, auto-promotes repeated failures into prevention rules, and blocks known-bad tool calls via PreToolUse hooks. Trigger when the user wants to add safety guardrails to an AI agent workflow, capture structured feedback on agent output, generate prevention rules from failure patterns, gate high-risk actions before execution, or export DPO training pairs from production feedback. Works with any MCP-compatible agent including Cursor, Codex, Gemini CLI, Amp, and OpenCode.
Automated Bluesky reply monitoring and draft queueing for ThumbGate's acquisition engagement loop. Polls the AT Protocol notifications endpoint every 15 minutes, writes human-reviewable draft replies into a queue file, and never auto-posts without sign-off. Trigger when the user asks about Bluesky replies, engagement, reply monitoring, or wants to see/approve queued drafts. Also the authoritative reference for rotating the Bluesky app password or diagnosing monitor failures.
# Agent Architect Kit ↔ ThumbGate Bridge **Status:** shipped 2026-04-21. Test-backed. CLI-automatable. Safe to recommend publicly. ## What this is [agent-architect-kit](https://github.com/ultrathink-art/agent-architect-kit) by @ultrathink-art is a CLAUDE.md + agent-role template kit that persists learnings as per-role markdown files (`agents/state/memory/<role>.md`). They solve the setup layer. ThumbGate solves the runtime-enforcement layer — PreToolUse hooks that actually block known-bad too
# Agent Architect Kit ↔ ThumbGate Bridge **Status:** shipped 2026-04-21. Test-backed. CLI-automatable. Safe to recommend publicly. ## What this is [agent-architect-kit](https://github.com/ultrathink-art/agent-architect-kit) by @ultrathink-art is a CLAUDE.md + agent-role template kit that persists learnings as per-role markdown files (`agents/state/memory/<role>.md`). They solve the setup layer. ThumbGate solves the runtime-enforcement layer — PreToolUse hooks that actually block known-bad too
Automated Bluesky reply monitoring and draft queueing for ThumbGate's acquisition engagement loop. Polls the AT Protocol notifications endpoint every 15 minutes, writes human-reviewable draft replies into a queue file, and never auto-posts without sign-off. Trigger when the user asks about Bluesky replies, engagement, reply monitoring, or wants to see/approve queued drafts. Also the authoritative reference for rotating the Bluesky app password or diagnosing monitor failures.
Capture thumbs feedback and apply prevention rules before coding
Capture structured thumbs up/down feedback with context, history-aware lesson distillation, tags, and optional rubric scores after completing a task.
Generate and review prevention rules auto-promoted from repeated failure patterns.
Recall relevant past failures, prevention rules, and context packs before starting a coding task.
Print the latest saved Codex bridge result from Claude Code without rerunning Codex. Use when the user asks for the last Codex output or wants to inspect the raw bridge result.
Run a Codex review from Claude Code against the current uncommitted work, a base branch diff, or a specific commit. Use when the user explicitly asks for a Codex review or second reviewer.
Search promoted lessons for corrective actions, lifecycle state, linked rules, and linked gates.
Show the latest Codex bridge artifact metadata from Claude Code. Use when the user asks whether the bridge already ran, what mode it used, or where the result was saved.
Dual-write feedback to Amp MCP memory AND thumbgate for DPO export, analytics, and cross-platform portability
Run a skeptical Codex review from Claude Code that hunts for hidden regressions, unsafe assumptions, and release risk. Use before merges, deploys, migrations, or other risky changes.
Validate that the Codex bridge plugin is ready inside Claude Code. Use when the user asks to install, configure, or sanity-check Codex review from Claude.
Hand the current task or repo state to Codex for an independent second pass from inside Claude Code. Use when the user explicitly wants another agent to take a shot after Claude's first pass.
Stop your AI from making the same mistake twice. Pre-Action Gates that block repeat hallucinations, retry loops, and known-bad tool calls before they reach the model — zero tokens spent on mistakes you've already corrected. Works with Claude Code, Cursor, Codex, Gemini CLI, Amp, OpenCode, and any MCP-compatible agent.
Stop your AI from making the same mistake twice. Pre-Action Gates that block repeat hallucinations, retry loops, and known-bad tool calls before they reach the model — zero tokens spent on mistakes you've already corrected. Works with Claude Code, Cursor, Codex, Gemini CLI, Amp, OpenCode, and any MCP-compatible agent.
Pre-action gates for AI agents - capture feedback, generate prevention rules, block known-bad patterns. Use for setup, feedback capture, gate debugging, or DPO training data export.
Validate that the Codex bridge plugin is ready inside Claude Code. Use when the user asks to install, configure, or sanity-check Codex review from Claude.
Pre-action gates for AI agents - capture feedback, generate prevention rules, block known-bad patterns. Use for setup, feedback capture, gate debugging, or DPO training data export.
Pre-action gates for AI coding agents — capture thumbs-up/down feedback, generate prevention rules, and block known-bad patterns before they execute. Use when setting up ThumbGate, capturing feedback on agent actions, checking active prevention gates, debugging blocked actions, or exporting DPO training data. Triggers on: "thumbgate", "gate", "block mistake", "prevention rule", "feedback", "thumbs up", "thumbs down", "capture feedback", "what went wrong".
Capture thumbs feedback and apply prevention rules before coding
Pre-action gates for AI coding agents — capture thumbs-up/down feedback, generate prevention rules, and block known-bad patterns before they execute. Use when setting up ThumbGate, capturing feedback on agent actions, checking active prevention gates, debugging blocked actions, or exporting DPO training data. Triggers on: "thumbgate", "gate", "block mistake", "prevention rule", "feedback", "thumbs up", "thumbs down", "capture feedback", "what went wrong".
Capture structured thumbs up/down feedback with context, history-aware lesson distillation, tags, and optional rubric scores after completing a task.
Dual-write feedback to Amp MCP memory AND thumbgate for DPO export, analytics, and cross-platform portability
Capture thumbs feedback and apply prevention rules before coding
Search promoted lessons for corrective actions, lifecycle state, linked rules, and linked gates.
Hand the current task or repo state to Codex for an independent second pass from inside Claude Code. Use when the user explicitly wants another agent to take a shot after Claude's first pass.
Generate and review prevention rules auto-promoted from repeated failure patterns.
Run a skeptical Codex review from Claude Code that hunts for hidden regressions, unsafe assumptions, and release risk. Use before merges, deploys, migrations, or other risky changes.
Capture thumbs up/down feedback into structured memories and prevention rules. Require one sentence of why before claiming memory promotion. Use when user gives explicit quality signals about agent work (e.g. "that worked", "that failed", "thumbs up/down"). Do NOT use for general questions, code generation, file operations, or any task that is not explicit feedback on prior agent output.
Recall relevant past failures, prevention rules, and context packs before starting a coding task.
Print the latest saved Codex bridge result from Claude Code without rerunning Codex. Use when the user asks for the last Codex output or wants to inspect the raw bridge result.
Run a Codex review from Claude Code against the current uncommitted work, a base branch diff, or a specific commit. Use when the user explicitly asks for a Codex review or second reviewer.
Show the latest Codex bridge artifact metadata from Claude Code. Use when the user asks whether the bridge already ran, what mode it used, or where the result was saved.