thumbgate 1.14.1 → 1.16.0

package/skills/agent-memory/SKILL.md

@@ -1,97 +0,0 @@
----
-name: Agent Memory
-description: Recall past mistakes and capture feedback so your agent stops repeating errors. Works locally via MCP server — no API key needed.
----
-
-# Agent Memory
-
-Give your agent persistent memory across sessions. Before starting any task, recall what went wrong last time. After completing work, capture whether it succeeded or failed. Prevention rules are auto-generated from repeated mistakes.
-
-## Setup
-
-Add the MCP server (one-time):
-
-```bash
-claude mcp add thumbgate -- npx -y thumbgate serve
-```
-
-No API key needed. All data stays local.
-
-## When to Use
-
-- Starting a new task or session — recall past context first
-- After completing work that succeeded or failed — capture feedback
-- When the agent keeps making the same mistake — check prevention rules
-
-## Workflow
-
-### Step 1: Recall past context (do this FIRST on every task)
-
-Call the `recall` MCP tool with a description of your current task. The tool returns:
-
-- Past feedback relevant to this task (vector similarity search)
-- Active prevention rules (auto-generated from repeated failures)
-- Recent feedback summary with approval rate
-
-Read the prevention rules carefully. These are patterns that failed before — follow them.
-
-### Step 2: Do your work
-
-Complete the task as normal. Keep track of what you did and whether it worked.
-
-### Step 3: Capture feedback
-
-Call the `capture_feedback` MCP tool:
-
-**If succeeded:**
-- signal: `up`
-- context: What worked and why
-- tags: Category labels
-
-**If failed:**
-- signal: `down`
-- context: What you were trying to do
-- whatWentWrong: Specific failure description
-- whatToChange: How to avoid this next time
-- tags: Category labels
-
-Vague feedback like "it failed" will be rejected. Be specific.
-
-### Step 4: Check improvement (optional)
-
-Call the `feedback_stats` MCP tool to see approval rate, top failure domains, and whether the agent is trending better or worse.
-
-## Available MCP Tools
-
-| Tool | What it does |
-|------|-------------|
-| `recall` | Search past feedback and prevention rules for current task |
-| `capture_feedback` | Record what worked or failed with structured context |
-| `prevention_rules` | View auto-generated rules from repeated mistakes |
-| `feedback_stats` | Approval rate, trend analysis, top failure domains |
-| `feedback_summary` | Human-readable summary of recent signals |
-
-## MCP Profiles
-
-| Profile | Tools | Use case |
-|---------|-------|----------|
-| `essential` | 5 core tools | Default — start here |
-| `commerce` | 6 tools + commerce_recall | Agentic commerce agents |
-| `default` | 12 tools | Full pipeline including DPO export |
-
-Set profile: `THUMBGATE_MCP_PROFILE=essential npx thumbgate serve`
-
-## How Prevention Rules Work
-
-1. Agent makes mistake A → you capture `down` feedback
-2. Agent makes mistake A again → you capture `down` feedback again
-3. System detects pattern → auto-generates prevention rule: "NEVER do A"
-4. Next session → `recall` returns the rule → agent follows it
-
-This is the core value. The agent doesn't learn — but it reads the rules and follows them.
-
-## Links
-
-- [GitHub](https://github.com/IgorGanapolsky/thumbgate)
-- [npm](https://www.npmjs.com/package/thumbgate)
-- [MCP Registry](https://registry.modelcontextprotocol.io)

package/skills/solve-architecture-autonomy/SKILL.md

@@ -1,17 +0,0 @@
----
-name: solve-architecture-autonomy
-description: Automated skill to handle architecture, autonomy, crisis, debug, deployment, error, execution, external-assessment, feedback, inefficiency, negative, railway, revenue, roi, simplification, user-frustration patterns efficiently.
-diagnosis: Repeated execution failure in this domain.
-status: materialized
----
-
-# SOLVE-ARCHITECTURE-AUTONOMY Capability
-
-## Problem
-I provided a plan and research instead of immediately deploy
-
-## Automated Diagnosis
-Repeated execution failure in this domain.
-
-## Usage
-The agent should call the `handle_architecture` tool when tasks involve `architecture, autonomy, crisis, debug, deployment, error, execution, external-assessment, feedback, inefficiency, negative, railway, revenue, roi, simplification, user-frustration`.

package/skills/solve-architecture-autonomy/tool.js

@@ -1,33 +0,0 @@
-/**
- * Automated Skill: solve-architecture-autonomy
- * Generated: 2026-03-13T15:50:58.840Z
- * 
- * This tool was materialized by the EvoSkill loop to address:
- * "I provided a plan and research instead of immediately deploy"
- */
-
-const { execSync } = require('child_process');
-
-/**
- * Fixes I provided a plan and research instead of immediately deploy
- */
-async function handle_architecture(args) {
-  const { context } = args;
-  
-  // LOGIC: Materialized code should implement the fix derived from the diagnosis.
-  // For now, we provide a structured wrapper that logs intent and applies
-  // the suggested corrective action.
-  
-  console.log(`[EVOSKILL] Executing handle_architecture to resolve: I provided a plan and research instead of immediately deploy`);
-  
-  // Corrective action placeholder - in a full loop, this would be LLM-generated code
-  // derived from the 'how-to-avoid' fields in memory-log.jsonl.
-  
-  return {
-    status: 'success',
-    appliedFix: `Automated handling of I provided a plan and research instead of immediately deploy pattern.`,
-    context: context
-  };
-}
-
-module.exports = { handle_architecture };

package/skills/thumbgate-feedback/SKILL.md

@@ -1,49 +0,0 @@
----
-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:
-
-```bash
-# 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:
-
-```bash
-npm run feedback:summary
-npm run feedback:rules
-```