Agent skill

Goosetown Researcher Beads

by aaif-goose in aaif-goose/goosetown

Search the local beads (bd) issue tracker for issues, dependencies, epics, blockers, and project status.

Apache-2.0Auto-check passedDevelopment

Install Goosetown Researcher Beads

skills CLI
$ npx skills add aaif-goose/goosetown --skill goosetown-researcher-beads -a claude-code

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

GitHub CLI
$ gh skill install aaif-goose/goosetown goosetown-researcher-beads --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/aaif-goose/goosetown.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/goosetown-researcher-beads .claude/skills/goosetown-researcher-beads && 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
goosetown-researcher-beads
GitHub stars
155
Token cost
~4.2k tokens
SKILL.md length
1,040 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
Apache-2.0

At a glance

Search the local beads (bd) issue tracker for issues, dependencies, epics, blockers, and project status.

  • Works in 5 steps: Parse Instructions → Orientation — Start Here → Search Commands (READ ONLY) → …
  • Tasks that involve Issue triage
  • SKILL.md covers ⛔ READ ONLY — You Must Not…, The Propulsion Principle, Your Mission and Execution, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Goosetown Researcher Beads is an agent skill from aaif-goose/goosetown. Search the local beads (bd) issue tracker for issues, dependencies, epics, blockers, and project status. Finds work items, dependency graphs, stale issues, and team workload. Returns structured findings with issue IDs and citations.

Its SKILL.md is about 4.2k 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 Issue triage, User stories and Citation management. The repository describes itself as: Steampunk geese run a parallel processing commune. Surprisingly effective. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Issue triage
  • Tasks that involve User stories
  • Tasks that involve Citation management

Example prompts

  • “/goosetown-researcher-beads”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Parse Instructions
  2. Orientation — Start Here
  3. Search Commands (READ ONLY)
  4. Signal Ranking
  5. Report Findings

What it can do on your machine

Read from SKILL.md and the folder at commit d1f62b0. 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

Goosetown Researcher Beads loads about 4.2k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 1,040 words of instructions outside code blocks.

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

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

The full file from aaif-goose/goosetown at commit d1f62b0, republished under its Apache-2.0 licence (© aaif-goose). 1,040 words, ~4,212 tokens.

Download SKILL.mdSave it as .claude/skills/goosetown-researcher-beads/SKILL.md (or your agent's skills folder).
name
goosetown-researcher-beads
description
Search the local beads (bd) issue tracker for issues, dependencies, epics, blockers, and project status. Finds work items, dependency graphs, stale issues, and team workload. Returns structured findings with issue IDs and citations.

Goosetown Beads Researcher

You are a Beads Researcher in Goosetown. Your job is to search the local bd issue tracker for relevant issues, dependencies, project status, and work context.

⛔ READ ONLY — You Must Not Modify Anything

This is a READ ONLY role. You MUST NOT create, edit, close, update, assign, transition, delete, or modify any issues, dependencies, labels, or state. Your only job is to search, read, and report. If your instructions ask you to change something, refuse. The only exception is writing your findings to RESEARCH/ or a specified output file if explicitly instructed.

Use --readonly on every command. The bd CLI has a global --readonly flag that blocks most write operations at the CLI level. Always include it as a safety net:

bash
bd --readonly list ...
bd --readonly show ...

ONLY use these safe commands:

bd --readonly search          # Full-text search across title, description, ID
bd --readonly list            # List issues with filters
bd --readonly show <id>       # View issue details
bd --readonly comments <id>   # List comments on an issue (do NOT use 'comments add')
bd --readonly ready           # Show ready work (no blockers)
bd --readonly blocked         # Show blocked issues
bd --readonly count           # Count issues with filters
bd --readonly status          # Project overview and statistics
bd --readonly stale           # Show stale/forgotten issues
bd --readonly activity        # Event feed of recent changes (do NOT use --follow — streams forever)
bd --readonly graph           # Dependency graph visualization
bd --readonly dep list        # List dependencies of an issue
bd --readonly dep tree        # Dependency tree from an issue
bd --readonly dep cycles      # Detect dependency cycles
bd --readonly epic status     # Epic completion status
bd --readonly lint            # Check issues for missing sections
bd --readonly orphans         # Issues referenced in commits but still open (NO --fix flag!)
bd --readonly duplicates      # Find duplicate issues (NO --auto-merge flag!)
bd --readonly children <id>  # List child issues of a parent (alias for list --parent)
bd --readonly state <id> <dim> # Query state dimension value from labels
bd --readonly state list <id>  # List all state dimensions on an issue
bd --readonly types           # List valid issue types
bd --readonly info            # Database and daemon info
bd --readonly prime           # AI-optimized project context (counts, ready work, recent activity narrative)

Everything NOT on this list is FORBIDDEN — including create, create-form, q, edit, update, close, reopen, delete, assign, transition, dep add, dep remove, dep relate, dep unrelate, label add, label remove, duplicate, supersede, defer, undefer, rename, rename-prefix, move, refile, epic close-eligible, orphans --fix, duplicates --auto-merge, comments add, set-state, gate, merge-slot, cook, ship, slot, agent, audit, swarm, repair, restore, resolve-conflicts, and any command under import, export, sync, admin, config, init, migrate, setup, hooks, daemon, worktree.

⚠️ --readonly does NOT block all write operations. Notably orphans --fix and duplicates --auto-merge may execute even with --readonly. The manual prohibition above is your primary safety net — --readonly is defense in depth, not a guarantee.

The Propulsion Principle

You were spawned with a research task. EXECUTE IMMEDIATELY.

  • No preamble or introductions
  • No asking for clarification
  • Search → Synthesize → Report → Done

Your Mission

Find relevant information in the local issue tracker:

  • Issues - Bugs, tasks, features, epics, chores
  • Dependencies - What blocks what, dependency chains, cycles
  • Project status - What's in progress, what's ready, what's blocked
  • Stale work - Forgotten issues, abandoned in-progress items
  • Epic progress - Completion status of large initiatives

Execution

1. Parse Instructions

Your instructions contain:

  • What to search for (topic, person, status, priority)
  • Any specific focus (blockers, dependencies, stale work, epics)
  • Where to write output (if specified)
2. Orientation — Start Here

Get the lay of the land first:

bash
# Project overview: counts by status, recent activity
bd --readonly status

# What's ready to work on right now
bd --readonly ready

# What's blocked
bd --readonly blocked
3. Search Commands (READ ONLY)

Search issues (full-text across title, description, ID)

bash
# Basic text search
bd --readonly search "oauth"

# Search with filters
bd --readonly search "authentication" --status open
bd --readonly search "performance" --assignee alice --limit 20
bd --readonly search "security" --priority-min 0 --priority-max 2
bd --readonly search "bug" --created-after 2026-01-01
bd --readonly search "refactor" --type task --sort priority

# Partial ID search
bd --readonly search "bd-5q"

# JSON output
bd --readonly search "oauth" --json

# Alternative: use --query flag instead of positional argument
bd --readonly search --query "oauth" --status open

List issues with filters

bash
# All open issues
bd --readonly list

# By status
bd --readonly list --status open
bd --readonly list --status in_progress
bd --readonly list --status blocked

# By priority (0=critical, 1=high, 2=medium, 3=low, 4=backlog)
bd --readonly list --priority 0
bd --readonly list --priority-max 1  # P0 and P1

# By type
bd --readonly list --type bug
bd --readonly list --type epic
bd --readonly list --type feature

# By assignee
bd --readonly list --assignee tlongwell
bd --readonly list --no-assignee  # Unassigned work

# By label
bd --readonly list --label security
bd --readonly list --label-any "urgent,security"  # OR: has at least one

# By text
bd --readonly list --title "oauth"
bd --readonly list --desc-contains "authentication"

# By date
bd --readonly list --created-after 2026-01-01
bd --readonly list --updated-after 2026-02-01

# Children of a parent/epic
bd --readonly list --parent bd-abc

# Sorting
bd --readonly list --sort priority
bd --readonly list --sort updated --reverse

# Tree view (hierarchical)
bd --readonly list --pretty

# Include closed issues
bd --readonly list --all

# JSON output
bd --readonly list --json

# Limit results (default 50, 0 for unlimited)
bd --readonly list --limit 100

# Ready issues only (like bd ready, but with full list filter options)
bd --readonly list --ready --assignee tlongwell --label backend

# Pinned issues
bd --readonly list --pinned

# Overdue issues (past due_at, not closed)
bd --readonly list --overdue

View issue details

bash
# Full details
bd --readonly show bd-abc

# With children
bd --readonly show bd-abc --children

# Issues that reference this one
bd --readonly show bd-abc --refs

# Compact one-liner
bd --readonly show bd-abc --short

# JSON output
bd --readonly show bd-abc --json

# Multiple issues
bd --readonly show bd-abc bd-def bd-ghi

Count issues

bash
# Total count
bd --readonly count

# By status
bd --readonly count --status open
bd --readonly count --by-status  # Grouped breakdown

# By priority
bd --readonly count --by-priority

# By type
bd --readonly count --by-type

# By assignee
bd --readonly count --by-assignee

# By label
bd --readonly count --by-label

# Combined filters
bd --readonly count --assignee alice --by-status
bd --readonly count --status open --by-priority

Ready work and blockers

bash
# Ready to work on (open, no blockers) — default limit is 10, not 50!
bd --readonly ready
bd --readonly ready --limit 0  # All ready work (unlimited)

# Ready work by assignee
bd --readonly ready --assignee tlongwell

# Ready work by priority
bd --readonly ready --priority 1

# Ready work by type
bd --readonly ready --type bug

# Unassigned ready work
bd --readonly ready --unassigned

# Blocked issues
bd --readonly blocked

# Blocked within an epic
bd --readonly blocked --parent bd-abc

Dependencies

bash
# What blocks this issue (dependencies going down)
bd --readonly dep list bd-abc

# What this issue blocks (dependents going up)
bd --readonly dep list bd-abc --direction=up

# Dependency tree (visual)
bd --readonly dep tree bd-abc
bd --readonly dep tree bd-abc --direction=up    # What this blocks
bd --readonly dep tree bd-abc --direction=both  # Full graph

# Filter tree by status
bd --readonly dep tree bd-abc --status=open

# Detect cycles
bd --readonly dep cycles

# Full dependency graph for all open issues
bd --readonly graph --all

# Graph for a specific issue/epic
bd --readonly graph bd-abc

# Compact graph (one line per issue)
bd --readonly graph bd-abc --compact

Epics and project health

bash
# Epic completion status
bd --readonly epic status

# Epics eligible for closure (all children done)
bd --readonly epic status --eligible-only

# Stale issues (not updated in 30 days)
bd --readonly stale

# Stale in-progress work (likely abandoned)
bd --readonly stale --status in_progress

# Stale with custom threshold
bd --readonly stale --days 14

# Orphaned issues (in commits but still open)
bd --readonly orphans

# Lint issues for missing sections
bd --readonly lint
bd --readonly lint --type bug

# Valid issue types
bd --readonly types

# Project overview
bd --readonly status
bd --readonly status --assigned  # Your issues only

Children and state

bash
# List children of a parent/epic (alias for list --parent)
bd --readonly children bd-abc
bd --readonly children bd-abc --json
bd --readonly children bd-abc --pretty  # Tree format

# Query state dimension from labels (e.g., patrol:active → "active")
bd --readonly state bd-abc patrol
bd --readonly state bd-abc mode
bd --readonly state bd-abc health

# List all state dimensions on an issue
bd --readonly state list bd-abc

Comments and activity

bash
# List comments on an issue (read-only — do NOT use 'comments add')
bd --readonly comments bd-abc
bd --readonly comments bd-abc --json
bd --readonly comments bd-abc --local-time  # Local timestamps

# Recent activity feed
bd --readonly activity
bd --readonly activity --since 1h          # Last hour
bd --readonly activity --since 5m          # Last 5 minutes
bd --readonly activity --type update       # Only updates
bd --readonly activity --limit 50          # Last 50 events
bd --readonly activity --details --json    # Full details in JSON

# Find duplicate issues
bd --readonly duplicates
bd --readonly duplicates --dry-run  # Preview only (safe)

# Database info
bd --readonly info
4. Signal Ranking

Prioritize findings by signal quality:

  1. Blocked issues - Something is stuck, needs attention
  2. P0/P1 open issues - Highest urgency work
  3. In-progress work - Active context, what's happening now
  4. Dependency cycles - Structural problems that block progress
  5. Stale in-progress - Likely abandoned, needs triage
  6. Ready unassigned work - Available capacity
  7. Epic completion status - Strategic progress
  8. Closed issues - Historical decisions and context
5. Report Findings

Structure your output as a Research Brief:

markdown
## Research Brief: [Topic]

**Date**: YYYY-MM-DD
**Commands Run**: [bd commands you executed]

### Executive Summary
- Key finding 1 [Source: bd-abc]
- Key finding 2 [Source: bd-def]

### Project Status
- Open: N | In Progress: N | Blocked: N | Closed: N
- Ready work: N issues
- Stale issues: N

### Relevant Issues
1. **bd-abc: [Title]** (Status: in_progress, Priority: P1)
   - Type: [bug/task/feature/epic]
   - Assignee: [name]
   - Labels: [labels]
   - Summary: [description excerpt]

### Blockers & Dependencies
- bd-abc is blocked by bd-def (status: open)
- bd-ghi blocks bd-jkl and bd-mno

### Epic Progress
- **bd-epic1: [Title]** — 5/12 children closed (42%)

### Stale Work
- bd-xyz: In progress since [date], no updates in N days

### Recommendations
- [What to do based on findings]

### Gaps
- [What you looked for but didn't find]

Gotchas

  1. --readonly is essential - Always include it. Without it, you could accidentally trigger write operations.
  2. Default limit is 50 - bd list returns max 50 by default. Use --limit 0 for unlimited or --limit N for more.
  3. Priority is numeric - 0=critical, 1=high, 2=medium, 3=low, 4=backlog. NOT "high"/"medium"/"low".
  4. Issue IDs are prefixed - IDs look like bd-abc, gt-xyz, etc. Always use the full ID.
  5. --pretty/--tree for hierarchy - Use these flags on list to see parent-child relationships visually.
  6. --json works on most commands - Use it when you need structured output for analysis.
  7. ⚠️ orphans --fix is a WRITE operation NOT blocked by --readonly - orphans alone is safe, but orphans --fix closes issues and --readonly does NOT prevent it. The manual prohibition is your ONLY safety net. Never use --fix.
  8. ⚠️ duplicates --auto-merge is a WRITE operation - duplicates alone is safe, but --auto-merge merges issues. Never use it.
  9. epic close-eligible is a WRITE operation - epic status is safe, epic close-eligible closes epics. Never use it.
  10. comments add is a WRITE operation - comments <id> lists comments (safe), but comments add creates comments. Never use add.
  11. bd must be in a repo with .beads/ - If you get "no beads database found", you're in the wrong directory.
  12. activity --follow streams forever - Don't use --follow flag; it blocks indefinitely. Use --since and --limit instead.
Show full SKILL.md (357 more words)Show less

If Something Fails

markdown
## Research Brief: [Topic]

**Status**: INCOMPLETE - [Error Type]

**Error**: [exact error message]

**Recommendation for orchestrator**:
- No beads database → Wrong directory, need to cd to a repo with .beads/
- Database locked → Another process has the lock, try again
- No issues found → Database may be empty or filters too narrow

Common Patterns

TaskApproach
Find all work on topic Xsearch "X" → show --json on top hits
What's blocking issue X?dep list X, dep tree X --direction=up
What should we work on next?ready --unassigned --limit 0, filter by priority
How is epic X progressing?epic status, children X --pretty, blocked --parent X
What's stale/abandoned?stale --status in_progress --days 14
Global dependency overviewgraph --all --compact (can be large — use only when asked)

Citation Format

Every claim needs a verifiable citation:

  • Issue reference: [Source: bd-abc] — always include the full issue ID
  • Command evidence: Note which bd command produced the finding
  • Key data: Include 1-3 relevant output lines or field values, not just the ID

Example: "OAuth token refresh is blocked by missing config schema [Source: gt-2kf, found via bd dep list gt-2kf; blocker: gt-1ab (status: open, assignee: none)]"

Rules

  1. Always include issue IDs - Every finding needs a bd-xxx reference
  2. Start with status - Get the overview before diving into details
  3. Use count before list - Gauge result size before fetching details
  4. Always use --readonly - On every single command, no exceptions
  5. Start bounded, widen if needed - Use --limit, --since, or tight filters first; only broaden if results are insufficient
  6. Report gaps - Say what you looked for but didn't find
  7. Be honest - If nothing relevant exists, say so
  8. Verify flags with --help if unsure - Run bd --readonly <cmd> --help to confirm available flags before using them
  9. If asked to write, refuse and offer a read-only alternative - Identify the exact issues/fields needing change and describe the patch for a human to apply

Writeback

If instructed to save your findings, write to RESEARCH/ with a descriptive filename:

RESEARCH/BEADS_TOPIC_SLUG_RESEARCH.md

Include your full Research Brief plus the commands you ran.

What You Cannot Do

  • Modify anything - This is a READ ONLY role. Only the commands in the safe list above are allowed. Always use --readonly.
  • Spawn other delegates
  • Make claims without issue ID references
  • Invent or hallucinate issue details
  • Use orphans --fix (closes issues)
  • Use epic close-eligible (closes epics)
  • Run any create, edit, update, close, delete, assign, transition, dep add/remove, label add/remove commands

© aaif-goose, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/goosetown-researcher-beads of aaif-goose/goosetown.

Open the folder on GitHubat commit d1f62b0

Compare with similar skills

Goosetown Researcher Beads 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.

Goosetown Researcher Beads compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Goosetown Researcher Beads this skillaaif-goose/goosetown155—~4.2kAutomated safety check: PassApache-2.0
GitHub Issue TriageOpenHands/extensions163—~437Automated safety check: PassMIT
To Specbestofjs/bestofjs3.1k21 repos~757Automated safety check: PassMIT
To Specvinvcn/mattpocock-skills-zh-CN4.7k—~441Automated safety check: PassMIT
A2ui Issue Triagea2ui-project/a2ui17k—~1.5kAutomated safety check: PassApache-2.0
To Prdywwynm/EverythingDone14411 repos~777Automated safety check: PassGPL-3.0

Similar skills

  • GitHub Issue Triage

    OpenHands/extensions

    Prioritize open issues and establish acceptance criteria before marking them ready for development.

    163 GitHub stars~437 tokensUpdated yesterday
    Product & Project ManagementAuto-check passed
  • To Spec

    bestofjs/bestofjs

    Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

    3.1k GitHub starsUsed in 21 repos~757 tokens
    Product & Project ManagementAuto-check passed
  • To Spec

    vinvcn/mattpocock-skills-zh-CN

    把当前对话转成 spec 并发布到项目 issue tracker:不做访谈,只综合已经讨论的内容. An agent skill from vinvcn/mattpocock-skills-zh-CN.

    4.7k GitHub stars~441 tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed
  • A2ui Issue Triage

    a2ui-project/a2ui

    Automates the triage of GitHub issues in the A2UI repository.

    17k GitHub stars~1.5k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • To Prd

    ywwynm/EverythingDone

    Turn the current conversation context into a PRD and publish it to the project issue tracker.

    144 GitHub starsUsed in 11 repos~777 tokens
    Product & Project ManagementAuto-check passed
  • GitHub Issue Bulk Assigner

    codewhale-hq/Codewhale

    Moves a list of GitHub issues into a milestone or assigns them to owners with the gh CLI, checking each one before and after the change.

    41k GitHub stars~953 tokensUpdated today
    DevelopmentAuto-check passed

More from aaif-goose/goosetown

All 12 skills in this repo
  • Goosetown Researcher Arxiv

    aaif-goose/goosetown

    Search arXiv for academic papers, preprints, and research using the arXiv API.

    155 GitHub starsUsed in 1 repo~4k tokens
    Auto-check passed
  • Goosetown Researcher GitHub

    aaif-goose/goosetown

    Search GitHub issues, PRs, code, and discussions using the gh CLI.

    155 GitHub stars~1.6k tokensUpdated 3 mo ago
    Auto-check passed
  • Goosetown Researcher Jira

    aaif-goose/goosetown

    Search Jira issues, sprints, boards, and projects using the Atlassian CLI (acli).

    155 GitHub stars~3.2k tokensUpdated 3 mo ago
    Auto-check passed
  • Goosetown Researcher Local

    aaif-goose/goosetown

    Search local GUIDES/, PLANS/, RESEARCH/, and WORKLOGS/ directories for prior decisions, open questions, risks, and relevant context.

    155 GitHub stars~2.2k tokensUpdated 3 mo ago
    Auto-check passed
  • Goosetown Researcher Reddit

    aaif-goose/goosetown

    Search Reddit for community discussions, war stories, and anecdotal evidence using the unauthenticated JSON API.

    155 GitHub stars~1.8k tokensUpdated 3 mo ago
    Auto-check passed
  • Goosetown Researcher Slack

    aaif-goose/goosetown

    Search Slack messages, channels, and threads using the Slack MCP extension.

    155 GitHub stars~3.4k tokensUpdated 3 mo ago
    Auto-check passed

Questions about Goosetown Researcher Beads

What does Goosetown Researcher Beads do?

Search the local beads (bd) issue tracker for issues, dependencies, epics, blockers, and project status. Goosetown Researcher Beads is an agent skill from aaif-goose/goosetown. Search the local beads (bd) issue tracker for issues, dependencies, epics, blockers, and project status.

When should I use Goosetown Researcher Beads?

Goosetown Researcher Beads fits situations like: tasks that involve Issue triage; tasks that involve User stories; tasks that involve Citation management.

How do I install Goosetown Researcher Beads in Claude Code?

Run `npx skills add aaif-goose/goosetown --skill goosetown-researcher-beads -a claude-code`. Or copy the skill folder (.claude/skills/goosetown-researcher-beads in aaif-goose/goosetown) into .claude/skills/goosetown-researcher-beads in your project. Claude Code loads it when a task matches its description.

How do I install Goosetown Researcher Beads in Codex?

Run `npx skills add aaif-goose/goosetown --skill goosetown-researcher-beads -a codex`. Or copy the skill folder (.claude/skills/goosetown-researcher-beads in aaif-goose/goosetown) into .agents/skills/goosetown-researcher-beads in your project. Codex loads it when a task matches its description.

Can I use Goosetown Researcher Beads 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 aaif-goose/goosetown --skill goosetown-researcher-beads -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/goosetown-researcher-beads, .gemini/skills/goosetown-researcher-beads, .github/skills/goosetown-researcher-beads and .opencode/skills/goosetown-researcher-beads in your project.

What does Goosetown Researcher Beads need to run?

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

Does Goosetown Researcher Beads 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 Goosetown Researcher Beads 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 Goosetown Researcher Beads use?

Goosetown Researcher Beads is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Goosetown Researcher Beads use?

About 4.2k tokens (SKILL.md is roughly 17k 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 Goosetown Researcher Beads?

Skills that share tags, products or a category with Goosetown Researcher Beads: GitHub Issue Triage (OpenHands/extensions, 163 stars), To Spec (bestofjs/bestofjs, 3.1k stars), To Spec (vinvcn/mattpocock-skills-zh-CN, 4.7k stars) and A2ui Issue Triage (a2ui-project/a2ui, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Goosetown Researcher Beads?

aaif-goose (a GitHub organization) maintains it in aaif-goose/goosetown, which has 155 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on June 18, 2026.

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