New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Weft Debugging

by WeaveMindAI in WeaveMindAI/weft

Read when a run failed, did the wrong thing, never started, got stuck or was cancelled, or when you need to read what a past run did: the order to read a run in (executions, logs, events), what each…

Custom licenceAuto-check passedDevelopment

Install Weft Debugging

skills CLI
$ npx skills add WeaveMindAI/weft --skill weft-debugging -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install WeaveMindAI/weft weft-debugging --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/WeaveMindAI/weft.git skills-src && mkdir -p .claude/skills && cp -r skills-src/tangle/cline/.cline/skills/weft-debugging .claude/skills/weft-debugging && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
weft-debugging
GitHub stars
2k
Token cost
~2.5k tokens
SKILL.md length
1,566 words
Files
1
Skills in repo
36
Repo updated
First seen
Licence
Custom licence

At a glance

Read when a run failed, did the wrong thing, never started, got stuck or was cancelled, or when you need to read what a past run did: the order to read a run in (executions, logs, events), what each…

  • Works in 10 steps: It does not compile. Read the… → A run failed. weft logs names the node… → A value is wrong, not failed. Work… → …
  • Tasks that involve Debugging
  • SKILL.md covers Reading a run and The debugging playbook
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Weft Debugging is an agent skill from WeaveMindAI/weft. Read when a run failed, did the wrong thing, never started, got stuck or was cancelled, or when you need to read what a past run did: the order to read a run in (executions, logs, events), what each skip and cancel reason means, and the debugging playbook, from a compile error to a daemon that does not answer.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Debugging. The repository describes itself as: A programming language for AI orchestrations.

When your agent uses it

  • Tasks that involve Debugging

Example prompts

  • “/weft-debugging”

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

  1. It does not compile. Read the diagnostics: line:column message, a
  2. A run failed. weft logs names the node and the error. If
  3. A value is wrong, not failed. Work upstream from the output: open the
  4. Suspended. Expected for human-in-the-loop: nothing is wrong. A
  5. Cancelled. Read the reason on execution_cancelled. `Cancelled by
  6. Stuck. The engine proved nothing can proceed; that is a graph-shape
  7. Nothing ran. Nothing reached the branch: check that the trigger that
  8. Too much is running. The one failure nobody reports, because nothing
  9. A timer or a wake that never arrived. A wake the receiver refuses
  10. [the daemon] unreachable (connection refused, an editor button that

What it can do on your machine

Read from SKILL.md and the folder at commit 6e28f31. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Weft Debugging loads about 2.5k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 1,566 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~82
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,566 words (~2,483 tokens).

“Each verb below prints one compact line per run or per event and has a flag that opens the part you want, so a forty-node run reads without loading the whole journal. You read in this order and stop when…”

— opening of SKILL.md by WeaveMindAI, Custom licence
name
weft-debugging

Read the full SKILL.md on GitHub

Files

Just SKILL.md in tangle/cline/.cline/skills/weft-debugging of WeaveMindAI/weft.

Open the folder on GitHubat commit 6e28f31

Compare with similar skills

Weft Debugging next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Weft Debugging compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Weft Debugging this skillWeaveMindAI/weft2k—~2.5kAutomated safety check: PassCustom licence
Trellis Session Insightmindfold-ai/Trellis15k4 repos~1.7kAutomated safety check: PassAGPL-3.0
Native Data FetchingCherryHQ/cherry-studio-app4k6 repos~2.9kAutomated safety check: NotesMIT
Aoti Debugpytorch/pytorch104k1 repos~1.7kAutomated safety check: PassCustom licence
Herdr Throwaway Reproductionherdrdev/herdr43k—~2.4kAutomated safety check: PassApache-2.0
Systematic Debuggingultralisp/ultralisp25851 repos~2.4kAutomated safety check: PassNone

Similar skills

  • Trellis Session Insight

    mindfold-ai/Trellis

    Reach into past AI conversation history through the trellis mem CLI.

    15k GitHub starsUsed in 4 repos~1.7k tokens
    DevelopmentAuto-check passed

  • Native Data Fetching

    CherryHQ/cherry-studio-app

    A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.

    4k GitHub starsUsed in 6 repos~2.9k tokens
    DevelopmentAuto-check: notes

  • Aoti Debug

    pytorch/pytorch

    Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.

    104k GitHub starsUsed in 1 repo~1.7k tokens
    DevelopmentAuto-check passed

  • Herdr Throwaway Reproduction

    herdrdev/herdr

    Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.

    43k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Systematic Debugging

    ultralisp/ultralisp

    A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes

    258 GitHub starsUsed in 51 repos~2.4k tokens
    DevelopmentAuto-check passed

  • OpenLogi macOS Permissions Triage

    AprilNEA/OpenLogi

    Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated 4 days ago
    DevelopmentAuto-check: notes

More from WeaveMindAI/weft

All 36 skills in this repo

  • Weft Cloud Install

    WeaveMindAI/weft

    Read when the user wants weft itself on their Google Cloud for the first time, or to upgrade or resize the weft already there: getting the user's GitHub and Google Cloud accounts and CLIs ready, the…

    2k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

  • Weft Consumers

    WeaveMindAI/weft

    Read when the user wants their own website, app, bot or extension to list, show, answer, skip or cancel what a program is waiting on, fetch a file it carries, or show what one of its nodes is…

    2k GitHub stars~3.8k tokensUpdated yesterday
    Auto-check passed

  • Weft Deploying

    WeaveMindAI/weft

    Read when the user wants weft or a program live for real people on their cloud, asks about prod, a target, --on, a domain or GCP, or a deploy failed: targets and logging in, domains, the deploy…

    2k GitHub stars~4.2k tokensUpdated yesterday
    Auto-check: notes

  • Weft Metering

    WeaveMindAI/weft

    Read when the user asks what a run costs, or when a node is wired to a paid API weft does not already price: the three pieces of a custom paid service, a meter to copy, and the rules that keep a…

    2k GitHub stars~4k tokensUpdated yesterday
    Auto-check passed

  • Weft Sdp

    WeaveMindAI/weft

    Read when growing a program stage by stage: carving a run, supplying starting values, baking a trigger and firing it without activating, reusing completed work with a seed, freezing an accepted…

    2k GitHub stars~4k tokensUpdated yesterday
    Auto-check passed

  • Weft Frontend

    WeaveMindAI/weft

    Read when the user wants a page, app or site for the program, and before dispatching the frontend-builder: the verified scaffold commands, the default stack (pnpm, SvelteKit, PostgreSQL, BetterAuth…

    2k GitHub stars~8k tokensUpdated yesterday
    Auto-check: notes

Categories

Questions about Weft Debugging

What does Weft Debugging do?

Read when a run failed, did the wrong thing, never started, got stuck or was cancelled, or when you need to read what a past run did: the order to read a run in (executions, logs, events), what each…. Weft Debugging is an agent skill from WeaveMindAI/weft. Read when a run failed, did the wrong thing, never started, got stuck or was cancelled, or when you need to read what a past run did: the order to read a run in (executions, logs, events), what each skip and cancel reason means, and the debugging playbook, from a compile error to a daemon that does not answer.

When should I use Weft Debugging?

Weft Debugging fits situations like: tasks that involve Debugging.

How do I install Weft Debugging in Claude Code?

Run `npx skills add WeaveMindAI/weft --skill weft-debugging -a claude-code`. Or copy the skill folder (tangle/cline/.cline/skills/weft-debugging in WeaveMindAI/weft) into .claude/skills/weft-debugging in your project. Claude Code loads it when a task matches its description.

How do I install Weft Debugging in Codex?

Run `npx skills add WeaveMindAI/weft --skill weft-debugging -a codex`. Or copy the skill folder (tangle/cline/.cline/skills/weft-debugging in WeaveMindAI/weft) into .agents/skills/weft-debugging in your project. Codex loads it when a task matches its description.

Can I use Weft Debugging in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add WeaveMindAI/weft --skill weft-debugging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/weft-debugging, .gemini/skills/weft-debugging, .github/skills/weft-debugging and .opencode/skills/weft-debugging in your project.

What does Weft Debugging need to run?

SKILL.md names no scripts, command-line tools or credentials: Weft Debugging is instructions for the agent only.

Does Weft Debugging access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Weft Debugging safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Weft Debugging use?

Weft Debugging has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Weft Debugging use?

About 2.5k tokens (SKILL.md is roughly 9.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Weft Debugging?

Skills that share tags, products or a category with Weft Debugging: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Aoti Debug (pytorch/pytorch, 104k stars) and Herdr Throwaway Reproduction (herdrdev/herdr, 43k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Weft Debugging?

WeaveMindAI (a GitHub organization) maintains it in WeaveMindAI/weft, which has 1,994 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on October 6, 2026.

Source: WeaveMindAI/weft on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.