Design idempotent Knot looms and knots for convergent automation workflows.
npx skills add https://github.com/HaydenDekker/knot --skill knot-design
Please help me install this Agent Skill. Skill: knot-design Source: https://github.com/HaydenDekker/knot/tree/main/.agents/skills/knot-design Command: npx skills add https://github.com/HaydenDekker/knot --skill knot-design
Guides engineers to design looms and knots for Knot with clear boundaries, idempotent behavior, and robust loop handling, preventing divergent iterations and unclear responsibilities.
Draft a new knot design by outlining its data flow, naming, goals, and loom placement using the provided step-by-step guide.
High-intent search queries and answers about installing and using this skill.
Idempotent automation workflows are designed by establishing clear knot boundaries, data-flow definitions, and authority semantics so repeated loop iterations produce no additional changes. This ensures safe, convergent behavior by documenting expected loop convergence in tie-off records.
A knot loom is an architectural structure for organizing automation workflows with clear domain responsibilities and naming conventions. You need one when planning new automation loops or evaluating knot boundaries to prevent divergent iterations and misrouted data flows.
Plan data flows and set goals by following step-by-step guidance to outline naming conventions, domain responsibilities, loom placement, and loop health checks. This process defines data-flow definitions and authority semantics to document expected convergence behavior.
Automation loops diverge when knot boundaries lack idempotent design principles and clear authority semantics. Diagnosing loop behaviour by reviewing data-flow definitions and tie-off records ensures repeated runs converge safely without producing additional changes.
Reviewing knot boundaries in a live project is supported by diagnosing loop behaviour and checking loop health. The process enforces goals, data-flow definitions, and observation semantics in tie-off records to document expected convergence across planning and architecture domains.
HaydenDekkerAutomate loom, knot, and agent profile lifecycle via Markdown frontmatter files.
HaydenDekkerInspect Knot rig state, loom details, knot statuses, and agent profiles.
roycolumbia-codeIteratively review and replan plans until high-concern issues are resolved.
beyonaiSchedule background jobs with collision detection and quiet hour enforcement.
