Agent skill

Weft Debug

by WeaveMindAI in WeaveMindAI/weft

COMMAND, not reference: Inspect the last execution and chase the failure to one node.

Custom licenceAuto-check passed

Install Weft Debug

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

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

GitHub CLI
$ gh skill install WeaveMindAI/weft weft-debug --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-debug .claude/skills/weft-debug && 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-debug
GitHub stars
2k
Token cost
~620 tokens
SKILL.md length
370 words
Files
1
Skills in repo
36
Repo updated
First seen
Licence
Custom licence

At a glance

COMMAND, not reference: Inspect the last execution and chase the failure to one node.

  • Works in 4 steps: weft executions --limit 5 --phase fire… → weft logs first: it names the failing… → Chase it to one node → …
  • Asks for this step by name
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Optionally naming an execution id

What it does

Weft Debug is an agent skill from WeaveMindAI/weft. COMMAND, not reference: Inspect the last execution and chase the failure to one node. Run this when the user asks for this step by name, optionally naming an execution id. The weft- reference skills beside it are things you read; this is a procedure you carry out.

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

The repository describes itself as: A programming language for AI orchestrations.

When your agent uses it

  • Asks for this step by name
  • Optionally naming an execution id

Example prompts

  • “/weft-debug”

Workflow steps

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

  1. weft executions --limit 5 --phase fire and pick the execution: the one the user named, else the latest.
  2. weft logs first: it names the failing node and quotes the error, and for most failures that is the whole diagnosis. Then narrow the events…
  3. Chase it to one node
  4. Name one fix, in two or three sentences: what you will change and why that fixes the observed value, not just the symptom. Apply it…

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 Debug loads about 620 tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 370 words of instructions outside code blocks.

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

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 370 words (~620 tokens).

“Debug this project's latest run, or a specific execution id if the user named one. Read the weft-debugging skill if you have not this session.”

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

Read the full SKILL.md on GitHub

Files

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

Open the folder on GitHubat commit 6e28f31

Compare with similar skills

Weft Debug 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 Debug compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Weft Debug this skillWeaveMindAI/weft2k—~620Automated safety check: PassCustom licence
Debugasgeirtj/system_prompts_leaks69k—~439Automated safety check: PassCC0-1.0
Hypothesis-Driven Debuggingcode-yeongyu/oh-my-openagent70k—~3.2kAutomated safety check: PassCustom licence
Agent Introspection Debuggingaffaan-m/ECC274k2 repos~1.4kAutomated safety check: PassMIT
Debugging Toolkitsickn33/agentic-awesome-skills47k1 repos~344Automated safety check: PassMIT
Debugging Codesickn33/agentic-awesome-skills47k1 repos~3.1kAutomated safety check: PassMIT

Similar skills

  • Debug

    asgeirtj/system_prompts_leaks

    Enable debug logging for this session and help diagnose issues

    69k GitHub stars~439 tokensUpdated yesterday
    Auto-check passed
  • Hypothesis-Driven Debugging

    code-yeongyu/oh-my-openagent

    Runs a hypothesis-driven debugging loop for crashes, hangs and silent failures in any language, grounding every claim in runtime evidence and locking the fix with a test.

    70k GitHub stars~3.2k tokensUpdated today
    DevelopmentAuto-check passed
  • Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.

    274k GitHub starsUsed in 2 repos~1.4k tokens
    DevelopmentAuto-check passed
  • Debugging Toolkit

    sickn33/agentic-awesome-skills

    A skill your agent uses when working with debugging toolkit smart debug (Alias for debugging-toolkit-smart-debug)

    47k GitHub starsUsed in 1 repo~344 tokens
    DevelopmentAuto-check passed
  • Debugging Code

    sickn33/agentic-awesome-skills

    Interactively debug source code — set breakpoints, step through execution line by line, inspect live variable state, evaluate expressions against the running program, and navigate the call stack to…

    47k GitHub starsUsed in 1 repo~3.1k tokens
    DevelopmentAuto-check passed
  • 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

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

Questions about Weft Debug

What does Weft Debug do?

COMMAND, not reference: Inspect the last execution and chase the failure to one node. Weft Debug is an agent skill from WeaveMindAI/weft. COMMAND, not reference: Inspect the last execution and chase the failure to one node.

When should I use Weft Debug?

Weft Debug fits situations like: asks for this step by name; optionally naming an execution id.

How do I install Weft Debug in Claude Code?

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

How do I install Weft Debug in Codex?

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

Can I use Weft Debug 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-debug -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-debug, .gemini/skills/weft-debug, .github/skills/weft-debug and .opencode/skills/weft-debug in your project.

What does Weft Debug need to run?

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

Does Weft Debug 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 Debug 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 Debug use?

Weft Debug 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 Debug use?

About 620 tokens (SKILL.md is roughly 2.5k 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 Debug?

Skills that share tags, products or a category with Weft Debug: Debug (asgeirtj/system_prompts_leaks, 69k stars), Hypothesis-Driven Debugging (code-yeongyu/oh-my-openagent, 70k stars), Agent Introspection Debugging (affaan-m/ECC, 274k stars) and Debugging Toolkit (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Weft Debug?

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.