New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Review Jumbo Goal

by jumbocontext in jumbocontext/cli

A skill your agent uses when a Jumbo goal needs QA review after implementation.

AGPL-3.0Auto-check passedAgent Workflows

Install Review Jumbo Goal

skills CLI
$ npx skills add jumbocontext/cli --skill review-jumbo-goal -a claude-code

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

GitHub CLI
$ gh skill install jumbocontext/cli review-jumbo-goal --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/jumbocontext/cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/assets/skills/review-jumbo-goal .claude/skills/review-jumbo-goal && 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
review-jumbo-goal
GitHub stars
276
Token cost
~1k tokens
SKILL.md length
497 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
AGPL-3.0

At a glance

A skill your agent uses when a Jumbo goal needs QA review after implementation.

  • Works in 7 steps: Initiate Review → Verify Objective and Success Criteria → Verify Scope Compliance → …
  • A Jumbo goal needs QA review after implementation
  • SKILL.md covers Why Review Matters, Protocol and Rules
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Review Jumbo Goal is an agent skill from jumbocontext/cli. Use when a Jumbo goal needs QA review after implementation. Runs the review protocol, verifies every objective, criterion, and related entity constraint, and approves the goal for codification or rejects it with feedback.

Its SKILL.md is about 1k 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 Agent Workflows. The repository describes itself as: Memory and Context Orchestration for Coding Agents. The licence is AGPL-3.0.

When your agent uses it

  • A Jumbo goal needs QA review after implementation

Example prompts

  • “/review-jumbo-goal”

Workflow steps

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

  1. Initiate Review
  2. Verify Objective and Success Criteria
  3. Verify Scope Compliance
  4. Verify Architecture Alignment
  5. Verify Related Entities
  6. Run Applicable Verification
  7. Qualify or Re-Review

What it can do on your machine

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

    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

Review Jumbo Goal loads about 1k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 497 words of instructions outside code blocks.

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

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 jumbocontext/cli at commit a02a339, republished under its AGPL-3.0 licence (© jumbocontext). 497 words, ~1,012 tokens.

Download SKILL.mdSave it as .claude/skills/review-jumbo-goal/SKILL.md (or your agent's skills folder).
name
review-jumbo-goal
description
Use when a Jumbo goal needs QA review after implementation. Runs the review protocol, verifies every objective, criterion, and related entity constraint, and approves the goal for codification or rejects it with feedback.

Review Jumbo Goal

Prompt: Review a completed Jumbo goal implementation against its objective, success criteria, scope, and all related architectural context. Approve the goal if no issue are found, otherwise document the issues and reject the goal.

Why Review Matters

jumbo goal review assembles the goal's full context — objective, criteria, scope, architecture, components, decisions, invariants, and guidelines — into a QA verification prompt. A thorough review catches deviations before they compound. A lazy review lets defects ship.

Protocol

1. Initiate Review
bash
jumbo goal review --id <goal-id>

Read the entire output carefully. It contains the verification criteria assembled from the goal's relations.

2. Verify Objective and Success Criteria

For each success criterion listed in the output:

  1. Locate the implementation artifacts that satisfy it
  2. Read the relevant code
  3. Confirm the criterion is fully met — not partially, not approximately

If ANY criterion is not met: add the issues to a list for feedback.

3. Verify Scope Compliance

If the review output includes scope sections:

  • In Scope: Confirm all work was done within the listed files/areas. No under-delivery.
  • Out of Scope: Confirm no work leaked into excluded areas. No over-delivery.

If scope is violated: add the issues to the feedback list.

4. Verify Architecture Alignment

If the review output includes architecture:

  • Organization style: Do new namespaces and file names match the solution's architectural organization?
  • Design patterns: Were prescribed patterns applied where applicable?
  • Principles: Do all new artifacts reflect the listed principles?

If architecture is misaligned: add the issues to the feedback list.

For each category in the review output:

  • Components: Were all listed components properly considered? Are interactions correct?
  • Dependencies: Are dependency contracts respected?
  • Decisions: Is the implementation consistent with listed architectural decisions?
  • Invariants: Does the implementation adhere to every listed invariant? This is non-negotiable.
  • Guidelines: Does the implementation follow listed guidelines?

If ANY entity constraint is violated: add the issues to the feedback list.

Show full SKILL.md (185 more words)Show less
6. Run Applicable Verification

Discover the project's verification commands from its repository instructions, build manifests, and CI configuration. Run the tests and other checks that apply to the changed scope using the project's own tooling.

Record failures from applicable verification in the feedback list. Do not require verification commands that the project does not define as applicable. If the project defines no automated verification for the changed scope, record that fact as review evidence rather than a failure.

7. Qualify or Re-Review

If ALL checks pass (criteria, scope, architecture, entities, tests):

bash
jumbo goal approve --id <goal-id>

If ANY check failed:

bash
jumbo goal reject --id <goal-id> --audit-findings <list of issues>

Rules

  1. Never approve with unresolved failures. Every criterion, invariant, and applicable verification must pass before approving.
  2. Never skip entity categories. Review output includes entities for a reason — each was registered during refinement as essential context.
  3. Always run applicable verification. Use the project's defined tools and commands; do not assume a package manager or ecosystem.
  4. Document issues clearly. When rejecting a goal, provide detailed feedback for each failure.
  5. Read the code, don't assume. Verify each criterion by reading actual implementation, not by recalling what you wrote.

© jumbocontext, AGPL-3.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 assets/skills/review-jumbo-goal of jumbocontext/cli.

Open the folder on GitHubat commit a02a339

Compare with similar skills

Review Jumbo Goal 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.

Review Jumbo Goal compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Review Jumbo Goal this skilljumbocontext/cli276—~1kAutomated safety check: PassAGPL-3.0
Orca CLIstablyai/orca89k2 repos~593Automated safety check: PassMIT
OpenSpec Guided OnboardingFission-AI/OpenSpec72k1 repos~4.5kAutomated safety check: PassMIT
Brainstormingobra/superpowers297k1 repos~2.5kAutomated safety check: PassMIT
Claude Code Plugin Structureanthropics/claude-plugins-official38k10 repos~3.4kAutomated safety check: PassApache-2.0
Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills21k—~1.9kAutomated safety check: PassMIT

Similar skills

  • Orca CLI

    stablyai/orca

    Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…

    89k GitHub starsUsed in 2 repos~593 tokens
    Agent WorkflowsAuto-check passed

  • OpenSpec Guided Onboarding

    Fission-AI/OpenSpec

    Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.

    72k GitHub starsUsed in 1 repo~4.5k tokens
    Agent WorkflowsAuto-check passed

  • Brainstorming

    obra/superpowers

    Makes the agent clarify intent and agree on a design with you before writing any code, scaling the process from a quick spike to a written spec.

    297k GitHub starsUsed in 1 repo~2.5k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Plugin Structure

    anthropics/claude-plugins-official

    Official

    Explains the directory layout, plugin.json manifest and component organization of a Claude Code plugin, including auto-discovery and portable paths.

    38k GitHub starsUsed in 10 repos~3.4k tokens
    Agent WorkflowsAuto-check passed

  • Neat-Freak Knowledge Closeout

    KKKKhazix/khazix-skills

    Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.

    21k GitHub stars~1.9k tokensUpdated 9 days ago
    Agent WorkflowsAuto-check passed

  • O2 Review Loop

    openobserve/openobserve

    Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.

    22k GitHub stars~3.7k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

More from jumbocontext/cli

All 13 skills in this repo

  • Codify Jumbo Goal

    jumbocontext/cli

    A skill your agent uses when a Jumbo goal has been approved by QA review and needs architectural reconciliation before closing.

    276 GitHub stars~1.2k tokensUpdated 17 days ago
    Auto-check passed

  • Decompose Architecture Aggregate

    jumbocontext/cli

    A skill your agent uses when a project has Architecture data that needs migrating to fine-grained entities (Decisions, Invariants, Components, Dependencies).

    276 GitHub stars~881 tokensUpdated 17 days ago
    Auto-check passed

  • Define Jumbo Goals

    jumbocontext/cli

    Add Jumbo goals liberally to decompose objectives into finite units of work with bounded context.

    276 GitHub stars~2.9k tokensUpdated 17 days ago
    Auto-check passed

  • Jumbo Add Guideline

    jumbocontext/cli

    Use liberally when the user expresses a preference about how work should be done — coding style, process, testing approach, communication style.

    276 GitHub stars~522 tokensUpdated 17 days ago
    Auto-check passed

  • Refine Jumbo Goals

    jumbocontext/cli

    A skill your agent uses when Jumbo goals need refinement before implementation.

    276 GitHub stars~1.9k tokensUpdated 17 days ago
    Auto-check passed

  • Reject Jumbo Goal

    jumbocontext/cli

    A skill your agent uses when a Jumbo goal fails QA review and needs to be returned for rework.

    276 GitHub stars~650 tokensUpdated 17 days ago
    Auto-check passed

Categories

Questions about Review Jumbo Goal

What does Review Jumbo Goal do?

A skill your agent uses when a Jumbo goal needs QA review after implementation. Review Jumbo Goal is an agent skill from jumbocontext/cli. Use when a Jumbo goal needs QA review after implementation.

When should I use Review Jumbo Goal?

Review Jumbo Goal fits situations like: A Jumbo goal needs QA review after implementation.

How do I install Review Jumbo Goal in Claude Code?

Run `npx skills add jumbocontext/cli --skill review-jumbo-goal -a claude-code`. Or copy the skill folder (assets/skills/review-jumbo-goal in jumbocontext/cli) into .claude/skills/review-jumbo-goal in your project. Claude Code loads it when a task matches its description.

How do I install Review Jumbo Goal in Codex?

Run `npx skills add jumbocontext/cli --skill review-jumbo-goal -a codex`. Or copy the skill folder (assets/skills/review-jumbo-goal in jumbocontext/cli) into .agents/skills/review-jumbo-goal in your project. Codex loads it when a task matches its description.

Can I use Review Jumbo Goal 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 jumbocontext/cli --skill review-jumbo-goal -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-jumbo-goal, .gemini/skills/review-jumbo-goal, .github/skills/review-jumbo-goal and .opencode/skills/review-jumbo-goal in your project.

What does Review Jumbo Goal need to run?

SKILL.md names no scripts, command-line tools or credentials: Review Jumbo Goal is instructions for the agent only.

Does Review Jumbo Goal 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 Review Jumbo Goal 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 Review Jumbo Goal use?

Review Jumbo Goal is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Review Jumbo Goal use?

About 1k tokens (SKILL.md is roughly 4k 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 Review Jumbo Goal?

Skills that share tags, products or a category with Review Jumbo Goal: Orca CLI (stablyai/orca, 89k stars), OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 72k stars), Brainstorming (obra/superpowers, 297k stars) and Claude Code Plugin Structure (anthropics/claude-plugins-official, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Review Jumbo Goal?

jumbocontext (a GitHub organization) maintains it in jumbocontext/cli, which has 276 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on September 23, 2026.

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