一键在 Manus 中运行任何 Skill

thumbgate-feedback

星标24

分支6

更新时间2026年6月12日 22:08

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.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

IgorGanapolsky

IgorGanapolsky/ThumbGate

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

ThumbGate Feedback Skill

When user provides feedback, execute:

# negative
node .claude/scripts/feedback/capture-feedback.js \
  --feedback=down \
  --context="<what failed>" \
  --what-went-wrong="<specific failure>" \
  --what-to-change="<prevention action>" \
  --tags="<domain>,regression"

# positive
node .claude/scripts/feedback/capture-feedback.js \
  --feedback=up \
  --context="<what succeeded>" \
  --what-worked="<repeatable pattern>" \
  --tags="<domain>,fix"

If the user only says thumbs up, thumbs down, that worked, or that failed, log the signal and ask one follow-up question before claiming it became reusable memory.

At session start, run:

npm run feedback:summary
npm run feedback:rules

Gotchas

Prompt / Context Bloat: Over-capturing very specific or minor feedback patterns can cause rule congestion. Group similar failures under broader rules instead of creating duplicate gates.
Clarification Prompts: Central auto-capture triggers will prompt for a one-sentence explanation for vague feedback (like a simple "👎"). Do not skip or bypass this prompt; accurate context is required to synthesize clean prevention rules.
Self-Protection Triggers: Prevention rules that target edits to .claude/settings.json or config/gates/ will trigger ThumbGate's self-protection hooks. Always verify hook configuration changes manually rather than letting the agent auto-write rules targeting those files.
Auto-Capture Environment: If natural language feedback signals (e.g. "that worked", "that failed") are not triggering capture, verify that the THUMBGATE_AUTO_CAPTURE env variable is not set to 0 or disabled in settings.

References

For deeper context and feedback workflows, see best-practices.md in this skill's folder.

同仓库更多 Skills

同仓库

thumbgate

IgorGanapolsky/ThumbGate

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.

2026-07-1724

thumbgate-brand-voice

IgorGanapolsky/ThumbGate

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 this copy", or "review this copy for voice". Do NOT use for code comments, commit messages, internal notes, or non-ThumbGate copy — and never to add fabricated traction or unsupported claims (honesty is the brand).

2026-06-1224

agent-memory

IgorGanapolsky/ThumbGate

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).

2026-06-1124

solve-architecture-autonomy

IgorGanapolsky/ThumbGate

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.

2026-06-1124

thumbgate-blocked

IgorGanapolsky/ThumbGate

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).

2026-06-1124

thumbgate-doctor

IgorGanapolsky/ThumbGate

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.

2026-06-1124

name	thumbgate-feedback
description	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.
triggers	["thumbs up","thumbs down","that worked","that failed"]
negative_triggers	["generate code","search files","explain this","run tests"]

ThumbGate Feedback Skill

When user provides feedback, execute:

# negative
node .claude/scripts/feedback/capture-feedback.js \
  --feedback=down \
  --context="<what failed>" \
  --what-went-wrong="<specific failure>" \
  --what-to-change="<prevention action>" \
  --tags="<domain>,regression"

# positive
node .claude/scripts/feedback/capture-feedback.js \
  --feedback=up \
  --context="<what succeeded>" \
  --what-worked="<repeatable pattern>" \
  --tags="<domain>,fix"

If the user only says thumbs up, thumbs down, that worked, or that failed, log the signal and ask one follow-up question before claiming it became reusable memory.

At session start, run:

npm run feedback:summary
npm run feedback:rules

Gotchas

Prompt / Context Bloat: Over-capturing very specific or minor feedback patterns can cause rule congestion. Group similar failures under broader rules instead of creating duplicate gates.
Clarification Prompts: Central auto-capture triggers will prompt for a one-sentence explanation for vague feedback (like a simple "👎"). Do not skip or bypass this prompt; accurate context is required to synthesize clean prevention rules.
Self-Protection Triggers: Prevention rules that target edits to .claude/settings.json or config/gates/ will trigger ThumbGate's self-protection hooks. Always verify hook configuration changes manually rather than letting the agent auto-write rules targeting those files.
Auto-Capture Environment: If natural language feedback signals (e.g. "that worked", "that failed") are not triggering capture, verify that the THUMBGATE_AUTO_CAPTURE env variable is not set to 0 or disabled in settings.

References

For deeper context and feedback workflows, see best-practices.md in this skill's folder.