feg-state-hook-skill-arch

Embeds Hook, State Machine, and FEG patterns into Hermes skill design.

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/Lucien-1127/strata-skill --skill feg-state-hook-skill-arch-lucien-1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feg-state-hook-skill-arch
Source: https://github.com/Lucien-1127/strata-skill/tree/main/feg-state-hook-skill-arch
Command: npx skills add https://github.com/Lucien-1127/strata-skill --skill feg-state-hook-skill-arch-lucien-1127

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Recurring agent mistakes are often fixed only in memory, so the same errors repeat across sessions. This Skill turns skills into logic carriers by embedding Hook, State Machine, and FEG (Finite Graph) patterns directly into SKILL.md structure, intercepting repeated errors at the skill layer instead of relying on recall. ## Core Features & Use Cases - Hook Pattern Embedding: Maps event interception to Prerequisites, Pitfalls, and Verification sections so previously made mistakes trigger mandatory checks. - State Machine Procedures: Structures Procedure steps as explicit state transitions (idle → ready → running → verified → done) with rollback paths for failures. - FEG Composition: Combines multiple skills into a directed graph using delegate_task and cronjob for multi-node orchestration. - Use Case: When authoring a new deployment skill, apply the three-question design checklist to ensure past deploy errors are written into Verification, every step has a defined failure rollback, and the skill's relationship to other skills is documented. ## Quick Start Ask the agent to review a new SKILL.md against the Hook, State Machine, and FEG design checklist and add missing verification and rollback logic.

Frequently Asked Questions about feg-state-hook-skill-arch

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

FAQPage Schema
How do I embed state machine patterns into an AI agent skill?▼

Structure the Procedure section as explicit state transitions such as idle → ready → running → verified → done, with a rollback path for failures. Each step should define its current state, triggering event, next state, and associated action.

What is the difference between Hook, State Machine, and FEG patterns in skill design?▼

Hooks operate at the event layer, inserting interception logic into Prerequisites, Pitfalls, and Verification. State machines operate at the flow layer, turning Procedure steps into conditional transitions. FEG operates at the composition layer, combining multiple skills into a directed graph.

How do I prevent an AI agent from repeating the same mistakes?▼

Write the corrective logic directly into the skill's Pitfalls and Verification sections as mandatory checks rather than relying on memory files. Each previously encountered error should map to a verification command that runs automatically on every execution.

Why do agent skills fail without rollback paths?▼

Most skills only define the happy path, leaving no defined behavior when a step fails. Adding a rollback transition (running → rollback → idle) ensures the agent can recover to a known state instead of stopping mid-workflow.

When should I use FEG composition instead of a single skill?▼

Use FEG composition when a workflow spans multiple independent skills that need conditional routing between them. Each node is a standalone skill, edges are condition checks, and delegate_task or cronjob handles dispatch and periodic triggering.