Trader Memory Core
tradermonty/claude-trading-skills
Track investment theses across their lifecycle — from screening idea to closed position with postmortem.
Deep post-mortem digging into a weft execution. An agent skill from WeaveMindAI/weft.
Install Run Digger
$ npx skills add WeaveMindAI/weft --skill run-digger -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install WeaveMindAI/weft run-digger --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/WeaveMindAI/weft.git skills-src && mkdir -p .claude/skills && cp -r skills-src/tangle/cline/.cline/skills/run-digger .claude/skills/run-digger && rm -rf skills-srcUse ~/.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/
Install the "run-digger" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/run-digger into .claude/skills/run-digger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-digger", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/run-diggerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add WeaveMindAI/weft --skill run-digger -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install WeaveMindAI/weft run-digger --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WeaveMindAI/weft.git skills-src && mkdir -p .agents/skills && cp -r skills-src/tangle/cline/.cline/skills/run-digger .agents/skills/run-digger && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "run-digger" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/run-digger into .agents/skills/run-digger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-digger", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add WeaveMindAI/weft --skill run-digger -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install WeaveMindAI/weft run-digger --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WeaveMindAI/weft.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/tangle/cline/.cline/skills/run-digger .cursor/skills/run-digger && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "run-digger" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/run-digger into .cursor/skills/run-digger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-digger", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/WeaveMindAI/weft.git --path tangle/cline/.cline/skills/run-digger--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add WeaveMindAI/weft --skill run-digger -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install WeaveMindAI/weft run-digger --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WeaveMindAI/weft.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/tangle/cline/.cline/skills/run-digger .gemini/skills/run-digger && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "run-digger" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/run-digger into .gemini/skills/run-digger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-digger", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install WeaveMindAI/weft run-diggerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add WeaveMindAI/weft --skill run-digger -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/WeaveMindAI/weft.git skills-src && mkdir -p .github/skills && cp -r skills-src/tangle/cline/.cline/skills/run-digger .github/skills/run-digger && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "run-digger" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/run-digger into .github/skills/run-digger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-digger", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add WeaveMindAI/weft --skill run-digger -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install WeaveMindAI/weft run-digger --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WeaveMindAI/weft.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/tangle/cline/.cline/skills/run-digger .opencode/skills/run-digger && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "run-digger" agent skill from https://github.com/WeaveMindAI/weft/tree/main/tangle/cline/.cline/skills/run-digger into .opencode/skills/run-digger/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-digger", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
run-digger- GitHub stars
- 2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 933 words
- Files
- 1
- Skills in repo
- 36
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Deep post-mortem digging into a weft execution. An agent skill from WeaveMindAI/weft.
- Works in 5 steps: Orient. weft executions --limit 10 and… → Walk the run. weft logs first: every… → Read the code that ran. The .weft source… → …
- Tasks that involve Runbooks and postmortems
- SKILL.md covers Running commands, Rules, Method and Report
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Run Digger is an agent skill from WeaveMindAI/weft. Deep post-mortem digging into a weft execution. Dispatched with an execution id or a symptom when the cause is unclear or the journals are long; reconstructs exactly what happened from events, logs, source, node code, and stored files, compares good runs against bad ones, and reports the finding with quoted evidence. Research only, never fixes.
Its SKILL.md is about 1.4k 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 DevOps & Cloud, covering Runbooks and postmortems. The repository describes itself as: A programming language for AI orchestrations.
When your agent uses it
- Tasks that involve Runbooks and postmortems
Example prompts
- “/run-digger”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Orient. weft executions --limit 10 and weft status: [the execution id] and its status, the project's state, and sibling runs worth…
- Walk the run. weft logs first: every failure the journal recorded, as error lines naming the node. Then weft events , narrowed before you…
- Read the code that ran. The .weft source including every @included file, the metadata.json and mod.rs of each node involved, the files…
- Compare when you can. With a good run and a bad run of the same program, you walk both event lists to [the first divergent node], the…
- Go deeper when the run is not the problem. weft daemon logs --tail 200 for runtime-level errors; weft infra status for infra states; weft…
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
Run Digger loads about 1.4k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 933 words of instructions outside code blocks.
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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:32
- Secrets stay secret. You may open `.env` to check that a NAME is set; you never quote a value, of an env var, a log li
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 933 words (~1,445 tokens).
“You are the digger. Tangle dispatched you with [the execution id] or a symptom, and you come back with [the finding], one sentence saying which node, which wire or input, what went wrong, backed by [the evidence], the exact event…”
- name
- run-digger
Files
Just SKILL.md in tangle/cline/.cline/skills/run-digger of WeaveMindAI/weft.
Open the folder on GitHubat commit 6e28f31
Compare with similar skills
Run Digger 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Run Digger this skillWeaveMindAI/weft | 2k | — | ~1.4k | Automated safety check: Notes | Custom licence | |
| Trader Memory Coretradermonty/claude-trading-skills | 3k | 2 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Author Migrationnrwl/nx | 29k | — | ~12k | Automated safety check: Notes | MIT | |
| Write Notes Like Deepseekczm15053/write-notes-like-deepseek | 477 | — | ~1.9k | Automated safety check: Pass | None | |
| OpenRig Upgrade Proceduremvschwarz/openrig | 5.5k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| GreptimeDB Release RunbookGreptimeTeam/greptimedb | 6.7k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Author Migration
nrwl/nx
Author or scope a first-party Nx migration. An agent skill from nrwl/nx.
Write Notes Like Deepseek
czm15053/write-notes-like-deepseek
A skill your agent uses when a change is non-trivial by DSH standards (behavior, architecture, cross-file contracts, process/tooling, testing strategy, or on-disk/wire/config formats), when choosing…
OpenRig Upgrade Procedure
mvschwarz/openrig
Walks an agent through upgrading the OpenRig CLI and daemon one observed step at a time, keeping live seats alive and reconciling managed plugin files.
GreptimeDB Release Runbook
GreptimeTeam/greptimedb
Runbook for publishing a GreptimeDB version: pick the release branch, verify the Cargo version, then tag, create the GitHub release and open the docs note PR.
Statem
henryqin1997/statem
A skill your agent uses when a long coding or research task should be managed with statem state-machine runbooks, including creating specs, starting or resuming runs, checking current state…
More from WeaveMindAI/weft
All 36 skills in this repoWeft 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…
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…
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…
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…
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…
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…
Related
Categories
Questions about Run Digger
What does Run Digger do?
Deep post-mortem digging into a weft execution. An agent skill from WeaveMindAI/weft. Run Digger is an agent skill from WeaveMindAI/weft. Deep post-mortem digging into a weft execution.
When should I use Run Digger?
Run Digger fits situations like: tasks that involve Runbooks and postmortems.
How do I install Run Digger in Claude Code?
Run `npx skills add WeaveMindAI/weft --skill run-digger -a claude-code`. Or copy the skill folder (tangle/cline/.cline/skills/run-digger in WeaveMindAI/weft) into .claude/skills/run-digger in your project. Claude Code loads it when a task matches its description.
How do I install Run Digger in Codex?
Run `npx skills add WeaveMindAI/weft --skill run-digger -a codex`. Or copy the skill folder (tangle/cline/.cline/skills/run-digger in WeaveMindAI/weft) into .agents/skills/run-digger in your project. Codex loads it when a task matches its description.
Can I use Run Digger 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 run-digger -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/run-digger, .gemini/skills/run-digger, .github/skills/run-digger and .opencode/skills/run-digger in your project.
What does Run Digger need to run?
SKILL.md names no scripts, command-line tools or credentials: Run Digger is instructions for the agent only.
Does Run Digger 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 Run Digger safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Run Digger use?
Run Digger 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 Run Digger use?
About 1.4k tokens (SKILL.md is roughly 5.8k 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 Run Digger?
Skills that share tags, products or a category with Run Digger: Trader Memory Core (tradermonty/claude-trading-skills, 3k stars), Author Migration (nrwl/nx, 29k stars), Write Notes Like Deepseek (czm15053/write-notes-like-deepseek, 477 stars) and OpenRig Upgrade Procedure (mvschwarz/openrig, 5.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Run Digger?
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.