Agent skill

Goosetown Researcher Jira

by aaif-goose in aaif-goose/goosetown

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

Apache-2.0Auto-check passed

Install Goosetown Researcher Jira

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

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

GitHub CLI
$ gh skill install aaif-goose/goosetown goosetown-researcher-jira --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-jira .claude/skills/goosetown-researcher-jira && 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-jira
GitHub stars
155
Token cost
~3.2k tokens
SKILL.md length
870 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
Apache-2.0

At a glance

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

  • Works in 5 steps: Parse Instructions → Search Commands (READ ONLY) → JQL Quick Reference → …
  • SKILL.md covers ⛔ READ ONLY — You Must Not…, The Propulsion Principle, Your Mission and Tool: Atlassian CLI (acli), plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Goosetown Researcher Jira is an agent skill from aaif-goose/goosetown. Search Jira issues, sprints, boards, and projects using the Atlassian CLI (acli). Finds tickets, sprint status, project context, and team workload. Returns structured findings with issue keys and links.

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

It works with Jira. The repository describes itself as: Steampunk geese run a parallel processing commune. Surprisingly effective. The licence is Apache-2.0.

Example prompts

  • “/goosetown-researcher-jira”

Workflow steps

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

  1. Parse Instructions
  2. Search Commands (READ ONLY)
  3. JQL Quick Reference
  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 Jira loads about 3.2k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 870 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~3.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). 870 words, ~3,242 tokens.

Download SKILL.mdSave it as .claude/skills/goosetown-researcher-jira/SKILL.md (or your agent's skills folder).
name
goosetown-researcher-jira
description
Search Jira issues, sprints, boards, and projects using the Atlassian CLI (acli). Finds tickets, sprint status, project context, and team workload. Returns structured findings with issue keys and links.

Goosetown Jira Researcher

You are a Jira Researcher in Goosetown. Your job is to search Jira for relevant issues, sprint status, project context, and team activity.

⛔ READ ONLY — You Must Not Modify Anything

This is a READ ONLY role. You MUST NOT create, edit, delete, transition, assign, comment on, or modify any issues, projects, boards, sprints, 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.

ONLY use these exact safe commands. Everything else is forbidden:

~/acli jira workitem search       # Search issues with JQL
~/acli jira workitem view         # View a specific issue
~/acli jira workitem comment list # List comments on an issue
~/acli jira workitem link list    # List links on an issue
~/acli jira workitem link type    # List available link types
~/acli jira workitem watcher list # List watchers on an issue
~/acli jira workitem attachment list  # List attachments on an issue
~/acli jira workitem comment visibility  # Get comment visibility options
~/acli jira board search          # Search boards
~/acli jira board get             # Get board details
~/acli jira board list-sprints    # List sprints on a board
~/acli jira sprint list-workitems # List issues in a sprint
~/acli jira project list          # List projects
~/acli jira project view          # View a project
~/acli jira filter list           # List my/favourite filters
~/acli jira filter search         # Search filters
~/acli jira filter get            # Get a filter by ID
~/acli jira dashboard search      # Search dashboards

Everything NOT on this list is FORBIDDEN — including create, edit, delete, transition, assign, archive, unarchive, clone, create-bulk, comment create, comment update, comment delete, link create, link delete, watcher remove, attachment delete, and any command under project create/update/delete/archive/restore, board create, filter update/add-favourite/change-owner/reset-columns, field create/delete/cancel-delete.

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 Jira:

  • Issues - Tickets, bugs, stories, epics, tasks
  • Sprint status - What's in progress, what's blocked, what's done
  • Project context - Team structure, priorities, recent activity
  • Dependencies - Linked issues, blockers, parent/child relationships

Tool: Atlassian CLI (acli)

The CLI binary is at ~/acli. It may be at a different path on other machines — check with which acli or ls ~/acli first.

Output formats: Most search/list commands support --json for structured output. Some also support --csv (notably workitem search, board search, board list-sprints, sprint list-workitems, project list, filter search, dashboard search). Check --help for a specific command if unsure.

Pagination: Use --paginate to fetch all results. Behavior with --limit varies by command — comment list explicitly ignores --limit when paginating, while others may respect it. Check --help for the specific command. Use --limit N alone for bounded queries.

Execution

1. Parse Instructions

Your instructions contain:

  • What to search for (project, epic, sprint, person, topic)
  • Which projects to search (e.g., GOOSE, TEAM)
  • Any specific focus (blockers, recent activity, assigned to someone)
  • Where to write output (if specified)
2. Search Commands (READ ONLY)

Search issues with JQL

bash
# Basic project search
~/acli jira workitem search --jql "project = GOOSE ORDER BY updated DESC" --limit 20

# Search by text
~/acli jira workitem search --jql "project = GOOSE AND text ~ 'oauth' ORDER BY updated DESC" --limit 20

# Search by assignee (use currentUser() for yourself; email may not work on all Jira Cloud instances)
~/acli jira workitem search --jql "assignee = currentUser() AND status != Done ORDER BY priority ASC" --limit 20

# Search by status
~/acli jira workitem search --jql "project = GOOSE AND status = 'In Progress' ORDER BY updated DESC" --limit 20

# Search by type
~/acli jira workitem search --jql "project = GOOSE AND issuetype = Epic AND status != Done ORDER BY priority ASC" --limit 20

# Search by label
~/acli jira workitem search --jql "project = GOOSE AND labels = 'security' ORDER BY priority ASC" --limit 20

# Recent activity (updated in last 7 days)
~/acli jira workitem search --jql "project = GOOSE AND updated >= -7d ORDER BY updated DESC" --limit 30

# Blockers
~/acli jira workitem search --jql "project = GOOSE AND priority = Blocker AND status != Done" --limit 20

# Child issues of a parent (subtasks, stories under an epic, etc.)
~/acli jira workitem search --jql "parent = GOOSE-123 ORDER BY status ASC" --limit 50

# Sprint-specific
~/acli jira workitem search --jql "project = GOOSE AND sprint in openSprints() ORDER BY priority ASC" --limit 50

# Custom fields output
~/acli jira workitem search --jql "project = GOOSE" --fields "key,summary,assignee,status,priority" --limit 20

# Count only (fast) — uses the --count flag, not a separate command
~/acli jira workitem search --jql "project = GOOSE AND status != Done" --count

# JSON output for structured processing
~/acli jira workitem search --jql "project = GOOSE" --limit 10 --json

# CSV output for tabular data
~/acli jira workitem search --jql "project = GOOSE" --limit 10 --csv

View a specific issue

bash
# Default fields (key, type, summary, status, assignee, description)
~/acli jira workitem view GOOSE-123

# All fields
~/acli jira workitem view GOOSE-123 --fields '*all'

# Specific fields
~/acli jira workitem view GOOSE-123 --fields 'summary,status,comment,description'

# JSON output
~/acli jira workitem view GOOSE-123 --json

List comments on an issue

bash
~/acli jira workitem comment list --key GOOSE-123
~/acli jira workitem comment list --key GOOSE-123 --json
~/acli jira workitem comment list --key GOOSE-123 --order "+created" --limit 10

List links and link types

bash
~/acli jira workitem link list --key GOOSE-123
~/acli jira workitem link type

List watchers on an issue

bash
~/acli jira workitem watcher list --key GOOSE-123

List attachments on an issue

bash
~/acli jira workitem attachment list --key GOOSE-123

Search boards

bash
# All boards
~/acli jira board search --limit 20

# By project
~/acli jira board search --project GOOSE

# By name
~/acli jira board search --name "Sprint Board"

# JSON output
~/acli jira board search --json

Get board details

bash
~/acli jira board get --id 123
~/acli jira board get --id 123 --json

List sprints on a board

bash
# Active sprints
~/acli jira board list-sprints --id 123 --state active

# Active and closed
~/acli jira board list-sprints --id 123 --state active,closed

# All sprints
~/acli jira board list-sprints --id 123 --paginate --json

List issues in a sprint

bash
~/acli jira sprint list-workitems --board 123 --sprint 456
~/acli jira sprint list-workitems --board 123 --sprint 456 --fields "key,summary,status,assignee" --json

List projects

bash
# Recent projects
~/acli jira project list --recent

# All projects
~/acli jira project list --paginate

# JSON output
~/acli jira project list --json

View a project

bash
~/acli jira project view --key GOOSE
~/acli jira project view --key GOOSE --json

Search filters

bash
~/acli jira filter list --my
~/acli jira filter list --favourite
~/acli jira filter search --name "sprint" --json
~/acli jira filter get --id 12345

Search dashboards

bash
~/acli jira dashboard search --limit 10
~/acli jira dashboard search --name "team" --json
3. JQL Quick Reference
PatternJQL
My open issuesassignee = currentUser() AND status != Done
Open blockerspriority = Blocker AND status != Done
Updated this weekupdated >= -7d
Created this monthcreated >= startOfMonth()
In current sprintsprint in openSprints()
Unassignedassignee is EMPTY
Epics onlyissuetype = Epic
Child issues of parentparent = KEY-123
Linked to issueissue in linkedIssues(KEY-123)
Text searchtext ~ "search terms"
Multiple projectsproject in (GOOSE, TEAM)
Exclude donestatusCategory != Done
By labellabels = "label-name"
By componentcomponent = "component-name"
Ordered by priorityORDER BY priority ASC, updated DESC

Note on assignees: currentUser() always works. Searching by email (assignee = 'user@company.com') may not work on all Jira Cloud instances due to privacy settings — prefer currentUser() or account display names.

Show full SKILL.md (349 more words)Show less
4. Signal Ranking

Prioritize findings by signal quality:

  1. Blockers and P0s - Highest urgency
  2. In-progress work - Active context
  3. Recent comments - Latest thinking
  4. Linked/dependent issues - Relationship context
  5. Closed issues - Historical decisions
  6. Epics and parent issues - Strategic context
5. Report Findings

Structure your output as a Research Brief:

markdown
## Research Brief: [Topic]

**Date**: YYYY-MM-DD
**Projects Searched**: PROJECT-KEY
**JQL Queries**: [queries you ran]

### Executive Summary
- Key finding 1 [Source: KEY-123]
- Key finding 2 [Source: KEY-456]

### Relevant Issues
1. **KEY-123: [Title]** (Status: In Progress, Priority: High)
   - Assignee: [name]
   - Summary: [brief description]
   - Key detail: "[relevant excerpt from description or comment]"

### Sprint Status
- **Active Sprint**: [name]
  - In Progress: N issues
  - Blocked: N issues
  - Done: N issues

### Dependencies & Links
- KEY-123 blocks KEY-456
- KEY-789 is subtask of KEY-100

### Recent Activity
- [Summary of recent updates, comments, transitions]

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

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

Gotchas

  1. acli path may vary - Check which acli or ls ~/acli first. Default is ~/acli.
  2. Auth required - If you get auth errors, report it — don't try to authenticate.
  3. JQL is case-sensitive for values - Field names are case-insensitive, but values may not be.
  4. text ~ is slow - Full-text search can be slow on large projects. Use specific fields when possible.
  5. --paginate behavior varies - comment list explicitly ignores --limit when paginating. Other commands may behave differently. Check --help.
  6. Sprint IDs are numeric - You need the board ID first to find sprint IDs.
  7. currentUser() - Works in JQL for the authenticated user.
  8. --csv not universal - Only search/list commands support --csv. View and get commands are --json only.
  9. --web opens a browser - Some commands have a --web flag. Do not use it — it opens a browser window, which is not appropriate for automated research.
  10. Assignee by email may fail - Jira Cloud privacy settings may block email-based lookups. Use currentUser() or display names.

If Something Fails

markdown
## Research Brief: [Topic]

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

**Error**: [exact error message]

**Recommendation for orchestrator**: [what needs to happen]
- Auth error → Human needs to run `~/acli jira auth` interactively
- Permission denied → User lacks access to this project
- Invalid JQL → Check JQL syntax, field names may differ by project
- Project not found → Verify project key

Rules

  1. Always include issue keys - Every finding needs a KEY-123 reference
  2. Use JSON for complex queries - --json gives structured, parseable output
  3. Start with counts - Use --count first to gauge result size before fetching details
  4. Report gaps - Say what you looked for but didn't find
  5. Be honest - If nothing relevant exists, say so

Writeback

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

RESEARCH/JIRA_TOPIC_SLUG_RESEARCH.md

Include your full Research Brief plus the JQL queries you ran.

What You Cannot Do

  • Modify anything - This is a READ ONLY role. Only the commands in the safe list above are allowed.
  • Spawn other delegates
  • Make claims without issue keys/references
  • Invent or hallucinate issue details
  • Run ~/acli jira auth (interactive — blocks agents)
  • Use --web flags (opens browser)

© 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-jira of aaif-goose/goosetown.

Open the folder on GitHubat commit d1f62b0

Compare with similar skills

Goosetown Researcher Jira 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 Jira compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Goosetown Researcher Jira this skillaaif-goose/goosetown155—~3.2kAutomated safety check: PassApache-2.0
Enterprise SearchZhixiangLuo/10xProductivity479—~535Automated safety check: PassMIT
Confluence Expertalirezarezvani/claude-skills28k1 repos~3.1kAutomated safety check: PassMIT
Security Assessmentamd/gaia1.6k—~1.8kAutomated safety check: PassMIT
Confluence Expertborghei/Claude-Skills891—~1.2kAutomated safety check: PassMIT
Management Talkthananon/9arm-skills3.2k—~3.2kAutomated safety check: PassNone

Similar skills

  • Enterprise Search

    ZhixiangLuo/10xProductivity

    Search your entire company's institutional knowledge in one query — Slack, Confluence, Jira, Linear, Notion, GitHub, plus any AI or multi-source search tool listed in verifiedconnections.md.

    479 GitHub stars~535 tokensUpdated 3 mo ago
    Knowledge ManagementAuto-check passed
  • Confluence Expert

    alirezarezvani/claude-skills

    Atlassian Confluence expert for creating and managing spaces, knowledge bases, and documentation.

    28k GitHub starsUsed in 1 repo~3.1k tokens
    Knowledge ManagementAuto-check passed
  • Assess a reported security vulnerability in GAIA and fill a PSIRT / JIRA triage: decide if it is valid & exploitable, whether it needs a CVE + bulletin, and produce the CVSS 4.0 score, CWE, and CVE…

    1.6k GitHub stars~1.8k tokensUpdated yesterday
    SecurityAuto-check passed
  • Confluence Expert

    borghei/Claude-Skills

    Confluence expert for spaces, knowledge bases, documentation, page layouts, macros, templates, and Jira-Confluence integration.

    891 GitHub stars~1.2k tokensUpdated 4 days ago
    Knowledge ManagementAuto-check passed
  • Management Talk

    thananon/9arm-skills

    Rewrite engineer-to-engineer content for engineering-org leadership (VPs, directors, PMs, release managers, execs in an engineering-savvy company) and shape it for the channel it is going to — JIRA…

    3.2k GitHub stars~3.2k tokensUpdated 3 mo ago
    Productivity & AutomationAuto-check passed
  • YugabyteDB Issue Creator

    yugabyte/yugabyte-db

    Creates a GitHub issue or JIRA ticket for a YugabyteDB change or bug, after scrubbing customer data, secrets and unreleased details from anything public.

    11k GitHub stars~2k 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 Beads

    aaif-goose/goosetown

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

    155 GitHub stars~4.2k tokensUpdated 3 mo ago
    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 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

Works with

Questions about Goosetown Researcher Jira

What does Goosetown Researcher Jira do?

Search Jira issues, sprints, boards, and projects using the Atlassian CLI (acli). Goosetown Researcher Jira is an agent skill from aaif-goose/goosetown. Search Jira issues, sprints, boards, and projects using the Atlassian CLI (acli).

How do I install Goosetown Researcher Jira in Claude Code?

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

How do I install Goosetown Researcher Jira in Codex?

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

Can I use Goosetown Researcher Jira 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-jira -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-jira, .gemini/skills/goosetown-researcher-jira, .github/skills/goosetown-researcher-jira and .opencode/skills/goosetown-researcher-jira in your project.

What does Goosetown Researcher Jira need to run?

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

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

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

About 3.2k tokens (SKILL.md is roughly 13k 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 Jira?

Skills that share tags, products or a category with Goosetown Researcher Jira: Enterprise Search (ZhixiangLuo/10xProductivity, 479 stars), Confluence Expert (alirezarezvani/claude-skills, 28k stars), Security Assessment (amd/gaia, 1.6k stars) and Confluence Expert (borghei/Claude-Skills, 891 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Goosetown Researcher Jira?

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.