Epiq
ljtn/epiq
Workflow for working an epiq issue board through the epiq MCP — take an identity, sync on demand, keep tickets small and their status, tags and comments current.
Track complex, multi-session work with dependency graphs using bd (beads) issue tracker.
Install Bd Issue Tracking
$ npx skills add Microck/ordinary-claude-skills --skill bd-issue-tracking -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Microck/ordinary-claude-skills bd-issue-tracking --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/Microck/ordinary-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills_all/bd-issue-tracking .claude/skills/bd-issue-tracking && 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 "bd-issue-tracking" agent skill from https://github.com/Microck/ordinary-claude-skills/tree/main/skills_all/bd-issue-tracking into .claude/skills/bd-issue-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bd-issue-tracking", 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/Microck/ordinary-claude-skills/tree/main/skills_all/bd-issue-trackingType 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 Microck/ordinary-claude-skills --skill bd-issue-tracking -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Microck/ordinary-claude-skills bd-issue-tracking --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Microck/ordinary-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills_all/bd-issue-tracking .agents/skills/bd-issue-tracking && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "bd-issue-tracking" agent skill from https://github.com/Microck/ordinary-claude-skills/tree/main/skills_all/bd-issue-tracking into .agents/skills/bd-issue-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bd-issue-tracking", 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 Microck/ordinary-claude-skills --skill bd-issue-tracking -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Microck/ordinary-claude-skills bd-issue-tracking --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Microck/ordinary-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills_all/bd-issue-tracking .cursor/skills/bd-issue-tracking && 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 "bd-issue-tracking" agent skill from https://github.com/Microck/ordinary-claude-skills/tree/main/skills_all/bd-issue-tracking into .cursor/skills/bd-issue-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bd-issue-tracking", 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/Microck/ordinary-claude-skills.git --path skills_all/bd-issue-tracking--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 Microck/ordinary-claude-skills --skill bd-issue-tracking -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Microck/ordinary-claude-skills bd-issue-tracking --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Microck/ordinary-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills_all/bd-issue-tracking .gemini/skills/bd-issue-tracking && 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 "bd-issue-tracking" agent skill from https://github.com/Microck/ordinary-claude-skills/tree/main/skills_all/bd-issue-tracking into .gemini/skills/bd-issue-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bd-issue-tracking", 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 Microck/ordinary-claude-skills bd-issue-trackingInstalls 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 Microck/ordinary-claude-skills --skill bd-issue-tracking -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Microck/ordinary-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills_all/bd-issue-tracking .github/skills/bd-issue-tracking && 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 "bd-issue-tracking" agent skill from https://github.com/Microck/ordinary-claude-skills/tree/main/skills_all/bd-issue-tracking into .github/skills/bd-issue-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bd-issue-tracking", 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 Microck/ordinary-claude-skills --skill bd-issue-tracking -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Microck/ordinary-claude-skills bd-issue-tracking --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Microck/ordinary-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills_all/bd-issue-tracking .opencode/skills/bd-issue-tracking && 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 "bd-issue-tracking" agent skill from https://github.com/Microck/ordinary-claude-skills/tree/main/skills_all/bd-issue-tracking into .opencode/skills/bd-issue-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bd-issue-tracking", 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
bd-issue-tracking- GitHub stars
- 401
- Token cost
- ~5.8k tokens
- SKILL.md length
- 2,017 words
- Files
- 2
- Skills in repo
- 97
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Track complex, multi-session work with dependency graphs using bd (beads) issue tracker.
- Works in 3 steps: Discovery Phase (Proactive Issue Creation) → Execution Phase (Status Maintenance) → Planning Phase (Dependency Graphs)
- Work spans multiple sessions
- SKILL.md covers Overview, When to Use bd vs TodoWrite, Surviving Compaction Events and Session Start Protocol, plus 8 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Bd Issue Tracking is an agent skill from Microck/ordinary-claude-skills. Track complex, multi-session work with dependency graphs using bd (beads) issue tracker. Use when work spans multiple sessions, has complex dependencies, or requires persistent context across compaction cycles. For simple single-session linear tasks, TodoWrite remains appropriate.
Its SKILL.md is about 5.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `metadata.json`).
It sits in Productivity & Automation, covering Task management and Issue triage. The repository describes itself as: An unappealing collection of Claude Skills and resources.
When your agent uses it
- Work spans multiple sessions
- Has complex dependencies
- Requires persistent context across compaction cycles
Example prompts
- “/bd-issue-tracking”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
- Discovery Phase (Proactive Issue Creation)
- Execution Phase (Status Maintenance)
- Planning Phase (Dependency Graphs)
What it can do on your machine
Read from SKILL.md and the folder at commit 1056d29. 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 (its code samples are bash and markdown).
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
Bd Issue Tracking loads about 5.8k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 2,017 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 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 2,017 words (~5,771 tokens).
“bd is a graph-based issue tracker for persistent memory across sessions. Use for multi-session work with complex dependencies; use TodoWrite for simple single-session tasks.”
- name
- bd-issue-tracking
Files
SKILL.md and 1 other file in skills_all/bd-issue-tracking of Microck/ordinary-claude-skills.
- SKILL.md
- metadata.json
Open the folder on GitHubat commit 1056d29
Compare with similar skills
Bd Issue Tracking 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 |
|---|---|---|---|---|---|---|
| Bd Issue Tracking this skillMicrock/ordinary-claude-skills | 401 | — | ~5.8k | Automated safety check: Pass | Custom licence | |
| Epiqljtn/epiq | 533 | — | ~930 | Automated safety check: Pass | MIT | |
| Superset Agent Standupsuperset-sh/superset | 15k | — | ~712 | Automated safety check: Pass | Custom licence | |
| AgentRQ Workspace Agentagentrq/agentrq | 1.1k | — | ~1.9k | Automated safety check: Pass | AGPL-3.0 | |
| AgentRQ Supervisoragentrq/agentrq | 1.1k | — | ~2.7k | Automated safety check: Pass | AGPL-3.0 | |
| Triagewarpdotdev-demos/cloud-factory-demo | 320 | — | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
Superset Agent Standup
superset-sh/superset
Sweeps every Superset workspace, task and agent terminal to report what finished, what needs review and what is blocked, read-only, and can publish the digest as a page.
AgentRQ Workspace Agent
agentrq/agentrq
Guides a workspace agent through executing assigned tasks, replying to a remote human operator, and creating sub-tasks, memory and events inside an AgentRQ workspace.
AgentRQ Supervisor
agentrq/agentrq
Orchestrates work across specialized AgentRQ workspaces, breaking goals into tasks, assigning them to the right workspace agent, and tracking shared learning notes.
Triage
warpdotdev-demos/cloud-factory-demo
Triage an incoming GitHub, Jira, Linear, or other issue-tracker issue against the current codebase and related open issues, then return a structured decision with exactly one…
- Official
Triage Issues
kubernetes-sigs/agent-sandbox
Triage open GitHub issues for kubernetes-sigs/agent-sandbox by mapping them to roadmap.md and assigning k8s priority labels + Kanban Priority (P0–P4) on Project
More from Microck/ordinary-claude-skills
All 97 skills in this repoEvery Style Editor
Microck/ordinary-claude-skills
This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide.
Gemini Imagegen
Microck/ordinary-claude-skills
Generate and edit images using the Gemini API (Nano Banana Pro).
Andrew Kane Gem Writer
Microck/ordinary-claude-skills
Write Ruby gems following Andrew Kane's proven patterns and philosophy.
Codex
Microck/ordinary-claude-skills
Execute Codex CLI for code analysis, refactoring, and automated code changes.
Docs Review
Microck/ordinary-claude-skills
Review documentation changes for compliance with the Metabase writing style guide.
File Todos
Microck/ordinary-claude-skills
This skill should be used when managing the file-based todo tracking system in the todos/ directory.
Related
Questions about Bd Issue Tracking
What does Bd Issue Tracking do?
Track complex, multi-session work with dependency graphs using bd (beads) issue tracker. Bd Issue Tracking is an agent skill from Microck/ordinary-claude-skills. Track complex, multi-session work with dependency graphs using bd (beads) issue tracker.
When should I use Bd Issue Tracking?
Bd Issue Tracking fits situations like: work spans multiple sessions; has complex dependencies; requires persistent context across compaction cycles.
How do I install Bd Issue Tracking in Claude Code?
Run `npx skills add Microck/ordinary-claude-skills --skill bd-issue-tracking -a claude-code`. Or copy the skill folder (skills_all/bd-issue-tracking in Microck/ordinary-claude-skills) into .claude/skills/bd-issue-tracking in your project. Claude Code loads it when a task matches its description.
How do I install Bd Issue Tracking in Codex?
Run `npx skills add Microck/ordinary-claude-skills --skill bd-issue-tracking -a codex`. Or copy the skill folder (skills_all/bd-issue-tracking in Microck/ordinary-claude-skills) into .agents/skills/bd-issue-tracking in your project. Codex loads it when a task matches its description.
Can I use Bd Issue Tracking 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 Microck/ordinary-claude-skills --skill bd-issue-tracking -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bd-issue-tracking, .gemini/skills/bd-issue-tracking, .github/skills/bd-issue-tracking and .opencode/skills/bd-issue-tracking in your project.
What does Bd Issue Tracking need to run?
SKILL.md names no scripts, command-line tools or credentials: Bd Issue Tracking is instructions for the agent only.
Does Bd Issue Tracking 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 Bd Issue Tracking 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 Bd Issue Tracking use?
Bd Issue Tracking 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 Bd Issue Tracking use?
About 5.8k tokens (SKILL.md is roughly 23k 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 Bd Issue Tracking?
Skills that share tags, products or a category with Bd Issue Tracking: Epiq (ljtn/epiq, 533 stars), Superset Agent Standup (superset-sh/superset, 15k stars), AgentRQ Workspace Agent (agentrq/agentrq, 1.1k stars) and AgentRQ Supervisor (agentrq/agentrq, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Bd Issue Tracking?
Microck (a GitHub user) maintains it in Microck/ordinary-claude-skills, which has 401 GitHub stars. The repository holds 97 skills in this directory. The repository was last updated on September 6, 2026.
Source: Microck/ordinary-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.