Hoopit's agent skills, distributed as a
Claude Code plugin marketplace.
Each plugin lives under plugins/<group>/ and bundles its skills.
Everything below runs from your shell — no need to open Claude Code first. Add the marketplace once, then install the plugin(s) you want:
claude plugin marketplace add hoopit/skillsFor regular dev work you just need hoopit-dev. Install it in-project
(--scope project commits it to the repo's .claude/settings.json, so everyone on
the project gets it):
claude plugin install hoopit-dev@hoopit-skills --scope projectTo manually pull the latest, update the marketplace and then the plugin:
claude plugin marketplace update hoopit-skills
claude plugin update hoopit-dev@hoopit-skillsThese are also available inside Claude Code as the
/pluginslash commands (e.g./plugin install hoopit-dev@hoopit-skills).Need one of the other plugins (see the table below)? Same commands with that plugin's name.
| Plugin | What's in it |
|---|---|
hoopit-onboarding |
Take a fresh machine to a working hoopit/api or hoopit/flutter-app checkout, plus the supporting CLIs |
hoopit-dev |
Day-to-day dev workflows and CLIs: Jira/Sentry issues, PR review, Atlassian, CircleCI |
hoopit-misc |
Odds and ends: status line |
hoopit-product |
Product work: stress-test plans and ideas against the domain model, sharpen terminology, and produce a PRD |
hoopit-matt-picks |
A curated set of mattpocock/skills, tracking upstream |
Generated from each SKILL.md frontmatter, marketplace.json, and (for matt-picks) matt-picks-lock.json by scripts/gen-skills-readme.sh — don't edit between the markers by hand.
Take a fresh machine to a working hoopit/api or hoopit/flutter-app checkout, plus the supporting CLIs.
| Skill | Invoke | Description |
|---|---|---|
install-coderabbit-cli |
Auto | Install the CodeRabbit CLI, authenticate it, and wire up its Claude Code plugin (the /coderabbit:review slash command). |
install-sentry-cli |
Auto | Install the Sentry CLI (the sentry binary from cli.sentry.dev) and authenticate it. |
setup-api |
Auto | Set up a brand-new machine for the Hoopit Django API — install tooling (gh, mise/Python 3.14, uv, Docker, pre-commit, Sentry CLI, acli, AWS CLI), clone hoopit/api as a sibling of the skills repo, bootstrap deps + supporting services (Postgres/Redis/stripe-mock), migrate, run the server, and run tests. |
setup-flutter-app |
Auto | Set up a brand-new machine for the Hoopit flutter-app — install tooling (gh, mise/Python, FVM, DCM, Sentry CLIs, acli), clone hoopit/flutter-app as a sibling of the skills repo, bootstrap deps/codegen/l10n/pre-commit, wire up Figma MCP, and run the app. |
Day-to-day dev workflows and CLIs: Jira/Sentry issues, PR review, Atlassian, CircleCI.
| Skill | Invoke | Description |
|---|---|---|
atlassian-cli |
Auto | Use when working with Jira or Confluence from command line, including authentication, searching issues with JQL, bulk operations, sprint reports, or creating/updating work items using acli |
circleci-tests |
Auto | Fetch failing tests from a CircleCI job URL. |
create-pull-request |
Auto | Create GitHub PRs that always link the work item they implement (Jira/Sentry/etc.) and keep Jira links clean — emit only the keys this PR delivers so GitHub-for-Jira doesn't attach it to unrelated tickets. |
curate-memory |
Manual | Review, prune, and promote Claude Code agent memories — delete stale/shipped ones, and move durable team-relevant knowledge into the right shared home (a path-scoped rule, a directory CLAUDE.md, root CLAUDE.md, or leave it a skill). |
fix-sentry-issue |
Auto | Fix a Sentry issue end-to-end — fetch details, create or link a Jira ticket (with a native bidirectional Sentry↔Jira link), branch, fix, test, review, and open a PR. |
handle-jira-issue |
Auto | Handle any Jira issue end-to-end — an ITSM ticket or a project issue (BAC/WEB/FA). |
review-gate |
Auto | Run multiple independent code reviewers (the matt-picks two-axis /review + CodeRabbit + Codex) on the committed branch changes before a PR, aggregate and de-dup findings, fix what is valid, and BLOCK the PR (with notes) on any disputed Critical/High finding. |
review-github-comments |
Auto | Review and resolve all review comments on a GitHub PR — fetch comments, evaluate each one, apply fixes where needed, and reply to resolve them. |
review-jira-attachments |
Auto | Download and analyze the files attached to a Jira issue — HAR network captures, screenshots, logs, PDFs — via the Jira REST API, because acli cannot download attachments. |
Odds and ends: status line.
| Skill | Invoke | Description |
|---|---|---|
setup-statusline |
Auto | Install the team's custom Claude Code status line (directory, git status, model, effort, exact context usage, session token totals). |
Product work: stress-test plans and ideas against the domain model, sharpen terminology, and produce a PRD.
| Skill | Invoke | Description |
|---|---|---|
grill-my-idea |
Auto | Grilling session that challenges your plan against the existing domain model and sharpens terminology. |
Curated picks from mattpocock/skills, tracking upstream.
Invoked namespaced as mattpocock-skills:<name>. Descriptions cached from mattpocock/skills by scripts/gen-skills-readme.sh --refresh.
| Skill | Invoke | Description |
|---|---|---|
mattpocock-skills:ask-matt |
Manual | Ask which skill or flow fits your situation. |
mattpocock-skills:code-review |
Auto | Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). |
mattpocock-skills:codebase-design |
Auto | Shared vocabulary for designing deep modules. |
mattpocock-skills:diagnosing-bugs |
Auto | Diagnosis loop for hard bugs and performance regressions. |
mattpocock-skills:domain-modeling |
Auto | Build and sharpen a project's domain model. |
mattpocock-skills:grill-with-docs |
Manual | A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go. |
mattpocock-skills:implement |
Manual | Implement a piece of work based on a PRD or set of issues. |
mattpocock-skills:improve-codebase-architecture |
Manual | Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick. |
mattpocock-skills:prototype |
Auto | Build a throwaway prototype to answer a design question. |
mattpocock-skills:resolving-merge-conflicts |
Auto | Use when you need to resolve an in-progress git merge/rebase conflict. |
mattpocock-skills:setup-matt-pocock-skills |
Manual | Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. |
mattpocock-skills:tdd |
Auto | Test-driven development. |
mattpocock-skills:to-issues |
Manual | Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. |
mattpocock-skills:to-prd |
Manual | Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed. |
mattpocock-skills:triage |
Manual | Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs. |
mattpocock-skills:claude-handoff |
Manual | Hand the current conversation off to a fresh background agent that picks up the work immediately. |
mattpocock-skills:loop-me |
Manual | Grill me about specs for the workflows I want to build, within this workspace. |
mattpocock-skills:wayfinder |
Auto | Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear. |
mattpocock-skills:wizard |
Manual | Generate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each step, and writing .env files and GitHub Actions secrets. |
mattpocock-skills:handoff |
Manual | Compact the current conversation into a handoff document for another agent to pick up. |
mattpocock-skills:teach |
Manual | Teach the user a new skill or concept, within this workspace. |
mattpocock-skills:writing-great-skills |
Manual | Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable. |
The onboarding skills clone their project repo as a sibling of wherever you run
them (e.g. ../api, ../flutter-app). hoopit-matt-picks is sourced from Matt's
repo, so it picks up his latest when you run the update commands above.
The marketplace is declared in
.claude-plugin/marketplace.json. Each Hoopit
plugin is a self-contained directory under plugins/<group>/ with its own
.claude-plugin/plugin.json and a skills/ folder; the marketplace entry just
points source at that directory. Skills are auto-discovered from the plugin's
own skills/ folder, so a plugin exposes only its own skills — this is why
each group gets its own directory rather than a shared top-level skills/ (a
single shared folder would leak every skill into every plugin).
hoopit-matt-picks is the exception: it uses a github source pointing at
mattpocock/skills with strict: true and an explicit skills array listing
the specific skill paths to surface (a marketplace can list a plugin fetched from
a different repo). strict: true makes that curated list authoritative, so it
overrides the upstream plugin's own manifest instead of conflicting with it.
Adding or removing a Hoopit skill? When working in this repo, Claude has a project-local
create-hoopit-skillskill (under.claude/skills/) that documents the procedure and the files to keep in sync.