Agent Architect Kit ↔ ThumbGate Bridge

Convert architect-kit markdown memory into ThumbGate feedback and PreToolUse rules.

25|7|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/IgorGanapolsky/ThumbGate --skill agent-architect-kit-thumbgate-bridge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Agent Architect Kit ↔ ThumbGate Bridge
Source: https://github.com/IgorGanapolsky/ThumbGate/tree/main/skills/agent-architect-kit
Command: npx skills add https://github.com/IgorGanapolsky/ThumbGate --skill agent-architect-kit-thumbgate-bridge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npm, node, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the gap between saved agent “lessons” in architect-kit memory files and actual runtime prevention by converting those lessons into ThumbGate feedback and regenerated PreToolUse prevention rules.

Core Features & Use Cases

  • Ingest per-role architect-kit memory into ThumbGate: Parses architect-kit sections (such as Mistakes and Learnings) and emits corresponding ThumbGate thumbs-up/thumbs-down signals, tagged with architect-kit + role metadata for auditable traceability.
  • Classify stakeholder feedback into prevention signals: Interprets rejection-style keywords (for example “rejected”, “wrong”, “broken”) to flip entries negative so the enforcement learns correctly.
  • Regenerate prevention rules from imported feedback: Feeds imported lessons into the same rule-generation pipeline as native ThumbGate feedback so blocked actions happen before tool execution rather than after review.
  • Safely skip non-lesson noise: Ignores Session Log entries to avoid polluting the searchable lesson DB with ephemeral task receipts.

Quick Start

Run the integration import in dry-run mode first for the architect-kit memory directory you want to migrate, then run the real import and regenerate prevention rules.

Frequently Asked Questions about Agent Architect Kit ↔ ThumbGate Bridge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert markdown agent memory files into runtime enforcement rules?

Markdown agent memory entries are parsed by a deterministic importer that extracts mistakes and learnings, converts them into feedback signals, and regenerates PreToolUse prevention rules. This pipeline bridges static instruction edits to runtime enforcement for specific agent roles.

How do I migrate architect-kit memory to ThumbGate without importing session log noise?

The migration process safely skips Session Log entries to avoid polluting the searchable lesson database with ephemeral task receipts. Running the integration import in dry-run mode first validates that only Mistakes and Learnings sections are targeted before executing the real import.

How does feedback-to-rules regeneration work for agent governance?

Feedback-to-rules regeneration works by feeding imported lessons into the same rule-generation pipeline as native feedback, creating PreToolUse hooks that enforce prevention rules before tool execution rather than after review. Rejection keywords flip entries negative so enforcement learns correctly.

Do I need npm and node to run PreToolUse hooks generated from architect-kit lessons?

Yes, npm and node are required dependencies to run the integration. The Skill relies on Node.js scripts to execute the deterministic parser, process the memory directory, and run the feedback-to-rules regeneration pipeline for targeted imports.

Can I test memory migration to ThumbGate before applying prevention rules?

You can test memory migration by running the integration import in dry-run mode first for the architect-kit memory directory. This validates the parsed entries and feedback tagging without committing changes, ensuring auditable traceability before executing the real import and rule regeneration.

What is the best way to classify stakeholder feedback into prevention signals during memory migration?

The best way to classify stakeholder feedback is by interpreting rejection-style keywords such as "rejected," "wrong," or "broken" to flip entries negative. This ensures the enforcement learns correctly from past mistakes and generates accurate PreToolUse prevention rules for blocked actions.