skills.rest
HaydenDekker
HaydenDekkerCOMMUNITY
Explore all skills by this author →
GitHub

knot-inspect

Inspect Knot rig state, loom details, knot statuses, and agent profiles.

3|Updated Jun 3, 2026
Search Tags:#logs#profiles#inspect#knots#rig#looms
One-click install
npx skills add https://github.com/HaydenDekker/knot --skill knot-inspect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: knot-inspect
Source: https://github.com/HaydenDekker/knot/tree/main/.agents/skills/knot-inspect
Command: npx skills add https://github.com/HaydenDekker/knot --skill knot-inspect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only visibility into Knot rig state, loom configurations, and activity logs to help users understand the current setup and status without making changes.

Core Features & Use Cases

  • Read rig state from rig/state.json to surface a current snapshot of looms, knots, and profiles
  • Read activity from rig/tie-offs/{loom-id}/.loom-log to surface loom and knot processing history
  • List looms, knots, and profiles to assess configuration and processing status
  • Use cases include rig health checks, status verification, and audit-ready reporting

Quick Start

Ask knot-inspect to show the current rig status and details for a selected loom or knot.

Frequently Asked Questions about knot-inspect

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

FAQPage Schema
How do I inspect rig state and loom activity logs without making changes?▼

To inspect rig state read-only, use knot-inspect to view rig/state.json and rig/tie-offs/.loom-log files. It surfaces current loom configurations, knot statuses, and agent profiles without modifying any resources.

What is the best way to check knot statuses and agent profiles for a rig?▼

Checking knot statuses and agent profiles involves reading rig/state.json and rig/profiles/*.md files. This skill provides an audit-ready snapshot of looms, knots, and profiles to verify configuration and processing status.

Can I view loom processing history from .loom-log files for specific loom IDs?▼

Yes, you can view loom processing history by reading rig/tie-offs/{loom-id}/.loom-log files. This surfaces detailed activity logs and knot processing history for the specified loom without altering any data.

How do I generate an audit-ready report of current loom and knot configurations?▼

Generating an audit-ready report requires reading the current rig state snapshot from rig/state.json. This skill lists all looms, knots, and profiles to assess configuration and processing status for health checks.

Does knot-inspect modify rig state or loom configurations during status verification?▼

No, knot-inspect provides strictly read-only visibility into rig state and loom activity. It reads from rig/state.json, .loom-log, and profiles/*.md files without modifying any resources during status verification.

Why do I need a read-only tool to monitor rig health and loom activity?▼

A read-only monitoring tool prevents accidental modifications while assessing rig health and loom activity. It safely surfaces configuration details and processing history to help you understand the current setup without risking changes.

Related Skills

Explore More Software Engineering Skills→
HaydenDekkerHaydenDekker
3

knot-init

Initialize a Knot rig structure and default profile in the current directory.

Community
Advanced
cellarwoodcellarwood

gws-admin-reports

Retrieve and aggregate Google Workspace Admin SDK activity and usage reports via CLI.

Official
Intermediate
waynebabywaynebaby
2

loom-skill-enhancement

Enhance skills for deterministic execution within Techne Loom.

Community
Advanced
Nickalus12Nickalus12
2

status

Read and report active Loom session metadata without mutation.

Community
Intermediate