knot

Manage project tickets and tasks stored as markdown files via CLI commands.

7|1|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/UniSoma/aishell --skill knot-unisoma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knot
Source: https://github.com/UniSoma/aishell/tree/main/.claude/skills/knot
Command: npx skills add https://github.com/UniSoma/aishell --skill knot-unisoma

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a comprehensive file-based CLI solution for managing project tickets and tasks efficiently.

Core Features & Use Cases

  • Ticket Management: Create, update, and navigate tickets stored as markdown files within a structured directory.
  • Graph Dependency Tracking: Establish and visualize dependencies and links between tickets, ensuring consistent relationships.
  • Project Integrity Checks: Perform detailed scans for dependency cycles, dangling references, and schema validation to maintain project health.
  • Use Case: A software team uses knot to track bugs, features, and chores, linking related tickets, and rapidly generating project status reports directly from the file system.

Quick Start

Run the knot list command to review current tickets, then create or update tasks as needed using the CLI commands, integrating dependency and status updates seamlessly.

Frequently Asked Questions about knot

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

FAQPage Schema
How do I manage project tickets using markdown files?

File-based ticketing with markdown lets you store tasks in a structured directory, using the knot CLI to create, update, and navigate tickets while maintaining status transitions and consistent relationships.

How does dependency graph tracking work for file-based project tasks?

Dependency graph tracking for file-based tasks works by establishing links between markdown tickets, allowing you to visualize relationships and ensure consistent connections across your software development workflow.

Can I check project integrity and detect dependency cycles in a markdown ticketing system?

Yes, you can perform project integrity checks using the knot CLI to scan for dependency cycles, dangling references, and schema validation errors, ensuring overall project health and consistency.

What is the best way to track software bugs and features without a database?

The best way to track software bugs and features without a database is using a file-based project tracking CLI, which organizes tickets as markdown files and generates status reports directly from the file system.

Do I need a specific directory structure to track issues and dependencies?

Yes, file-based ticket tracking requires a structured directory setup and the knot CLI tools to properly organize markdown files, manage status transitions, and validate dependency graphs.