Automated summary

Teaches the agent to use the Beads `bd` CLI as the durable, shared task-tracking system for a repository instead of local TODO files or scratch notes.

Strengths

Provides a concrete command sequence (bd prime, ready, list, show, update --claim, create, close) that can be run as-is.
Draws a clear line between shared project state and an agent-local checklist for the current turn.
Covers context recovery after compaction, thread reset, or handoff to another agent through bd prime.
Calls out real pitfalls: avoid the interactive `bd edit`, prefer `--json` for parsing, and never close work that is not actually done.

Limitations

Assumes the repository already uses Beads and that the `bd` binary is installed and on the PATH.
Does not cover initial setup, hook installation, or how dependency graphs between tasks are modelled.
The type and priority options are illustrated by only a single create example.

When to use it

Reach for it whenever a repository runs on Beads and the agent needs to find, claim, create, or close shared tasks, or rebuild project context after a reset.

When not to use it

Skip it on projects without an active Beads workspace, where a local plan or plain TODO files are enough.

Security analysis

Safe

Quality score88/100

The skill instructs the use of the bd CLI for project task tracking, which involves shell commands but no destructive, exfiltrating, or obfuscated actions. The commands are read/update operations on a task system and do not disable safety or handle secrets. The only mild consideration is reliance on shell access, but this is legitimate and standard for such tooling.

No concerns found

How this analysis is made

Examples

Find next work

Run `bd ready` and tell me which Beads task I should pick up next, then claim it atomically for me.

Capture follow-up work

The refactor uncovered a stale migration we still need to clean up. Create a durable Beads task for it with a description and a sensible priority instead of writing a TODO file.

Recover context after compaction

My context was just reset. Run `bd prime`, then summarize the open and in-progress tasks along with anything currently blocked so we can resume.

name: beads description: Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or choose between local planning and persistent project tracking.

Beads

Name: Beads Project Task Tracking
Author: Skills Guide Bot

Use Beads as the shared project task system. Local plans, scratch files, and personal memories are useful, but they are not the durable source of truth for project work.

First Step

Run:

bd prime

If that prints nothing, check whether the repository has an active Beads workspace:

bd where

Preferred Route

Use the bd CLI when shell access is available. It is the most compact and direct Beads interface.

Core CLI Workflow

Find work:

bd ready
bd list --status=open
bd list --status=in_progress

Inspect before editing:

bd show <id>

Claim work atomically:

bd update <id> --claim

Create durable follow-up work when implementation reveals new tasks:

bd create "Short title" --description="Why this exists and what needs to be done" --type=task --priority=2

Close completed work:

bd close <id> --reason="Completed"

What Belongs In Beads

Use Beads for:

shared project tasks
blockers and dependencies
discovered follow-up work
work that must survive thread reset, compaction, or handoff
status that another person or agent should be able to resume

Use agent-local planning tools only for the current turn's execution checklist. Do not treat them as shared project state.

Rules

Do not create markdown TODO files as the source of truth when Beads is available.
Do not use bd edit; it opens an interactive editor. Use bd update flags instead.
Prefer --json when parsing bd output programmatically.
If hooks are installed, bd prime may already be injected. Run it manually when context is missing.
Do not auto-close or mutate tasks unless the work is actually complete.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/beads-project-task-tracking-ms8gxnfz/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/beads-project-task-tracking-ms8gxnfz' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/beads-project-task-tracking-ms8gxnfz/download' --output '.skill-downloads/beads-project-task-tracking-ms8gxnfz/SKILL.md.part' && mv '.skill-downloads/beads-project-task-tracking-ms8gxnfz/SKILL.md.part' '.skill-downloads/beads-project-task-tracking-ms8gxnfz/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code

test -f '.skill-downloads/beads-project-task-tracking-ms8gxnfz/SKILL.md' && test -s '.skill-downloads/beads-project-task-tracking-ms8gxnfz/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/beads' && cp -R '.skill-downloads/beads-project-task-tracking-ms8gxnfz' '.claude/skills/beads'

Cursor

test -f '.skill-downloads/beads-project-task-tracking-ms8gxnfz/SKILL.md' && test -s '.skill-downloads/beads-project-task-tracking-ms8gxnfz/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/beads' && cp -R '.skill-downloads/beads-project-task-tracking-ms8gxnfz' '.cursor/skills/beads'

Codex

test -f '.skill-downloads/beads-project-task-tracking-ms8gxnfz/SKILL.md' && test -s '.skill-downloads/beads-project-task-tracking-ms8gxnfz/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/beads' && cp -R '.skill-downloads/beads-project-task-tracking-ms8gxnfz' '.agents/skills/beads'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation

openskills install './.skill-downloads/beads-project-task-tracking-ms8gxnfz'

openskills read 'beads-project-task-tracking-ms8gxnfz'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/beads-project-task-tracking-ms8gxnfz/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

PDF Reader

Productivity

Read and extract text from PDF files, including documents, reports, contracts, and spreadsheets. Works with local files, URLs, and WhatsApp attachments. Use whenever PDF content is needed, even if not explicitly requested.

Claude CodeCursorCodexbeginnerSafe 20,122

Skills Guide Bot