knot-create

Automate loom, knot, and agent profile lifecycle via Markdown frontmatter files.

3|Updated Jun 3, 2026

Search Tags:#automation #git #markdown #config #frontmatter #loom #knot

Ready to run

npx skills add https://github.com/HaydenDekker/knot --skill knot-create

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: knot-create
Source: https://github.com/HaydenDekker/knot/tree/main/.agents/skills/knot-create
Command: npx skills add https://github.com/HaydenDekker/knot --skill knot-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and manage looms, knots, and agent profiles by editing Markdown frontmatter, enabling git-friendly, auto-discovered configurations for Knot.

Core Features & Use Cases

Auto-discovery of looms (directories ending in -loom) and knots (MD files inside loom directories)
Centralized profiles in rig/profiles and on-demand parsing via frontmatter
Live state verification through rig/state.json and deterministic tie-offs for auditing

Quick Start

Create a new Markdown file with YAML frontmatter inside rig to define a loom, knot, or profile and Knot will auto-discover it.

Frequently Asked Questions about knot-create

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

FAQPage Schema

How do I create and manage agent profiles using Markdown frontmatter?▼

You can create and manage agent profiles by writing Markdown files with YAML frontmatter containing a name and description, placing them in the rig directory for Knot to auto-discover and apply.

How does auto-discovery work for looms and knots in a git-friendly environment?▼

Auto-discovery works by scanning the rig directory for directories ending in -loom and Markdown files inside them, automatically detecting and registering new knots and looms from your configurations.

Do I need a running Knot environment to manage looms and profiles from Markdown files?▼

Yes, a running Knot environment is required. It handles the auto-discovery of your Markdown configurations and manages live state verification through rig/state.json for auditing.

What is the best way to automate the lifecycle of looms and knots for configuration management?▼

Automating the lifecycle is best done by writing Markdown files with YAML frontmatter under rig, letting Knot auto-discover changes for creation, update, and deletion workflows without manual registration.

Can I use optional directories like scripts and references to extend knot behavior?▼

Yes, you can include optional directories such as scripts, references, and assets alongside your Markdown files to support and extend the behavior of your knots and looms.

Why are my Markdown configurations for knots not being applied automatically?▼

Configurations are not applied if the YAML frontmatter is missing required fields like name and description, or if files are not placed correctly under the rig directory for Knot auto-discovery.