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.
Search Jira issues, sprints, boards, and projects using the Atlassian CLI (acli).
$ npx skills add aaif-goose/goosetown --skill goosetown-researcher-jira -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aaif-goose/goosetown goosetown-researcher-jira --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/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-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 "goosetown-researcher-jira" agent skill from https://github.com/aaif-goose/goosetown/tree/main/.claude/skills/goosetown-researcher-jira into .claude/skills/goosetown-researcher-jira/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "goosetown-researcher-jira", 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/aaif-goose/goosetown/tree/main/.claude/skills/goosetown-researcher-jiraType 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 aaif-goose/goosetown --skill goosetown-researcher-jira -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aaif-goose/goosetown goosetown-researcher-jira --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaif-goose/goosetown.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/goosetown-researcher-jira .agents/skills/goosetown-researcher-jira && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "goosetown-researcher-jira" agent skill from https://github.com/aaif-goose/goosetown/tree/main/.claude/skills/goosetown-researcher-jira into .agents/skills/goosetown-researcher-jira/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "goosetown-researcher-jira", 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 aaif-goose/goosetown --skill goosetown-researcher-jira -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aaif-goose/goosetown goosetown-researcher-jira --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaif-goose/goosetown.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/goosetown-researcher-jira .cursor/skills/goosetown-researcher-jira && 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 "goosetown-researcher-jira" agent skill from https://github.com/aaif-goose/goosetown/tree/main/.claude/skills/goosetown-researcher-jira into .cursor/skills/goosetown-researcher-jira/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "goosetown-researcher-jira", 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/aaif-goose/goosetown.git --path .claude/skills/goosetown-researcher-jira--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 aaif-goose/goosetown --skill goosetown-researcher-jira -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aaif-goose/goosetown goosetown-researcher-jira --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaif-goose/goosetown.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/goosetown-researcher-jira .gemini/skills/goosetown-researcher-jira && 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 "goosetown-researcher-jira" agent skill from https://github.com/aaif-goose/goosetown/tree/main/.claude/skills/goosetown-researcher-jira into .gemini/skills/goosetown-researcher-jira/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "goosetown-researcher-jira", 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 aaif-goose/goosetown goosetown-researcher-jiraInstalls 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 aaif-goose/goosetown --skill goosetown-researcher-jira -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aaif-goose/goosetown.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/goosetown-researcher-jira .github/skills/goosetown-researcher-jira && 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 "goosetown-researcher-jira" agent skill from https://github.com/aaif-goose/goosetown/tree/main/.claude/skills/goosetown-researcher-jira into .github/skills/goosetown-researcher-jira/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "goosetown-researcher-jira", 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 aaif-goose/goosetown --skill goosetown-researcher-jira -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aaif-goose/goosetown goosetown-researcher-jira --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaif-goose/goosetown.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/goosetown-researcher-jira .opencode/skills/goosetown-researcher-jira && 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 "goosetown-researcher-jira" agent skill from https://github.com/aaif-goose/goosetown/tree/main/.claude/skills/goosetown-researcher-jira into .opencode/skills/goosetown-researcher-jira/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "goosetown-researcher-jira", 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.
goosetown-researcher-jiraSearch 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). 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.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit d1f62b0. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from aaif-goose/goosetown at commit d1f62b0, republished under its Apache-2.0 licence (© aaif-goose). 870 words, ~3,242 tokens.
.claude/skills/goosetown-researcher-jira/SKILL.md (or your agent's skills folder).You are a Jira Researcher in Goosetown. Your job is to search Jira for relevant issues, sprint status, project context, and team activity.
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 dashboardsEverything 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.
You were spawned with a research task. EXECUTE IMMEDIATELY.
Find relevant information in Jira:
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.
Your instructions contain:
GOOSE, TEAM)Search issues with JQL
# 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 --csvView a specific issue
# 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 --jsonList comments on an issue
~/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 10List links and link types
~/acli jira workitem link list --key GOOSE-123
~/acli jira workitem link typeList watchers on an issue
~/acli jira workitem watcher list --key GOOSE-123List attachments on an issue
~/acli jira workitem attachment list --key GOOSE-123Search boards
# 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 --jsonGet board details
~/acli jira board get --id 123
~/acli jira board get --id 123 --jsonList sprints on a board
# 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 --jsonList issues in a sprint
~/acli jira sprint list-workitems --board 123 --sprint 456
~/acli jira sprint list-workitems --board 123 --sprint 456 --fields "key,summary,status,assignee" --jsonList projects
# Recent projects
~/acli jira project list --recent
# All projects
~/acli jira project list --paginate
# JSON output
~/acli jira project list --jsonView a project
~/acli jira project view --key GOOSE
~/acli jira project view --key GOOSE --jsonSearch filters
~/acli jira filter list --my
~/acli jira filter list --favourite
~/acli jira filter search --name "sprint" --json
~/acli jira filter get --id 12345Search dashboards
~/acli jira dashboard search --limit 10
~/acli jira dashboard search --name "team" --json| Pattern | JQL |
|---|---|
| My open issues | assignee = currentUser() AND status != Done |
| Open blockers | priority = Blocker AND status != Done |
| Updated this week | updated >= -7d |
| Created this month | created >= startOfMonth() |
| In current sprint | sprint in openSprints() |
| Unassigned | assignee is EMPTY |
| Epics only | issuetype = Epic |
| Child issues of parent | parent = KEY-123 |
| Linked to issue | issue in linkedIssues(KEY-123) |
| Text search | text ~ "search terms" |
| Multiple projects | project in (GOOSE, TEAM) |
| Exclude done | statusCategory != Done |
| By label | labels = "label-name" |
| By component | component = "component-name" |
| Ordered by priority | ORDER 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.
Prioritize findings by signal quality:
Structure your output as a Research Brief:
## 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]which acli or ls ~/acli first. Default is ~/acli.text ~ is slow - Full-text search can be slow on large projects. Use specific fields when possible.--paginate behavior varies - comment list explicitly ignores --limit when paginating. Other commands may behave differently. Check --help.currentUser() - Works in JQL for the authenticated user.--csv not universal - Only search/list commands support --csv. View and get commands are --json only.--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.currentUser() or display names.## 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--json gives structured, parseable output--count first to gauge result size before fetching detailsIf instructed to save your findings, write to RESEARCH/ with a descriptive filename:
RESEARCH/JIRA_TOPIC_SLUG_RESEARCH.mdInclude your full Research Brief plus the JQL queries you ran.
~/acli jira auth (interactive — blocks agents)--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
Just SKILL.md in .claude/skills/goosetown-researcher-jira of aaif-goose/goosetown.
Open the folder on GitHubat commit d1f62b0
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Goosetown Researcher Jira this skillaaif-goose/goosetown | 155 | — | ~3.2k | Automated safety check: Pass | Apache-2.0 | |
| Enterprise SearchZhixiangLuo/10xProductivity | 479 | — | ~535 | Automated safety check: Pass | MIT | |
| Confluence Expertalirezarezvani/claude-skills | 28k | 1 repos | ~3.1k | Automated safety check: Pass | MIT | |
| Security Assessmentamd/gaia | 1.6k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Confluence Expertborghei/Claude-Skills | 891 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Management Talkthananon/9arm-skills | 3.2k | — | ~3.2k | Automated safety check: Pass | None |
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.
alirezarezvani/claude-skills
Atlassian Confluence expert for creating and managing spaces, knowledge bases, and documentation.
amd/gaia
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…
borghei/Claude-Skills
Confluence expert for spaces, knowledge bases, documentation, page layouts, macros, templates, and Jira-Confluence integration.
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…
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.
aaif-goose/goosetown
Search arXiv for academic papers, preprints, and research using the arXiv API.
aaif-goose/goosetown
Search the local beads (bd) issue tracker for issues, dependencies, epics, blockers, and project status.
aaif-goose/goosetown
Search GitHub issues, PRs, code, and discussions using the gh CLI.
aaif-goose/goosetown
Search local GUIDES/, PLANS/, RESEARCH/, and WORKLOGS/ directories for prior decisions, open questions, risks, and relevant context.
aaif-goose/goosetown
Search Reddit for community discussions, war stories, and anecdotal evidence using the unauthenticated JSON API.
aaif-goose/goosetown
Search Slack messages, channels, and threads using the Slack MCP extension.
Works with
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).
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Goosetown Researcher Jira is instructions for the agent only.
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.
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.
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.
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.
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.
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.