Trellis Session Insight
mindfold-ai/Trellis
Reach into past AI conversation history through the trellis mem CLI.
A skill your agent uses when starting a Jumbo goal. An agent skill from jumbocontext/cli.
$ npx skills add jumbocontext/cli --skill start-jumbo-goal -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jumbocontext/cli start-jumbo-goal --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/jumbocontext/cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/assets/skills/start-jumbo-goal .claude/skills/start-jumbo-goal && 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 "start-jumbo-goal" agent skill from https://github.com/jumbocontext/cli/tree/main/assets/skills/start-jumbo-goal into .claude/skills/start-jumbo-goal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "start-jumbo-goal", 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/jumbocontext/cli/tree/main/assets/skills/start-jumbo-goalType 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 jumbocontext/cli --skill start-jumbo-goal -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jumbocontext/cli start-jumbo-goal --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jumbocontext/cli.git skills-src && mkdir -p .agents/skills && cp -r skills-src/assets/skills/start-jumbo-goal .agents/skills/start-jumbo-goal && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "start-jumbo-goal" agent skill from https://github.com/jumbocontext/cli/tree/main/assets/skills/start-jumbo-goal into .agents/skills/start-jumbo-goal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "start-jumbo-goal", 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 jumbocontext/cli --skill start-jumbo-goal -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jumbocontext/cli start-jumbo-goal --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jumbocontext/cli.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/assets/skills/start-jumbo-goal .cursor/skills/start-jumbo-goal && 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 "start-jumbo-goal" agent skill from https://github.com/jumbocontext/cli/tree/main/assets/skills/start-jumbo-goal into .cursor/skills/start-jumbo-goal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "start-jumbo-goal", 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/jumbocontext/cli.git --path assets/skills/start-jumbo-goal--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 jumbocontext/cli --skill start-jumbo-goal -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jumbocontext/cli start-jumbo-goal --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jumbocontext/cli.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/assets/skills/start-jumbo-goal .gemini/skills/start-jumbo-goal && 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 "start-jumbo-goal" agent skill from https://github.com/jumbocontext/cli/tree/main/assets/skills/start-jumbo-goal into .gemini/skills/start-jumbo-goal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "start-jumbo-goal", 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 jumbocontext/cli start-jumbo-goalInstalls 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 jumbocontext/cli --skill start-jumbo-goal -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jumbocontext/cli.git skills-src && mkdir -p .github/skills && cp -r skills-src/assets/skills/start-jumbo-goal .github/skills/start-jumbo-goal && 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 "start-jumbo-goal" agent skill from https://github.com/jumbocontext/cli/tree/main/assets/skills/start-jumbo-goal into .github/skills/start-jumbo-goal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "start-jumbo-goal", 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 jumbocontext/cli --skill start-jumbo-goal -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jumbocontext/cli start-jumbo-goal --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jumbocontext/cli.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/assets/skills/start-jumbo-goal .opencode/skills/start-jumbo-goal && 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 "start-jumbo-goal" agent skill from https://github.com/jumbocontext/cli/tree/main/assets/skills/start-jumbo-goal into .opencode/skills/start-jumbo-goal/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "start-jumbo-goal", 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.
start-jumbo-goalA skill your agent uses when starting a Jumbo goal. An agent skill from jumbocontext/cli.
Start Jumbo Goal is an agent skill from jumbocontext/cli. Use when starting a Jumbo goal. Loads goal context, scope, and architectural constraints, then guides the agent through disciplined execution within defined boundaries.
Its SKILL.md is about 1.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. The repository describes itself as: Memory and Context Orchestration for Coding Agents. The licence is AGPL-3.0.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit a02a339. 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).
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.
Start Jumbo Goal loads about 1.2k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 520 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 jumbocontext/cli at commit a02a339, republished under its AGPL-3.0 licence (© jumbocontext). 520 words, ~1,204 tokens.
.claude/skills/start-jumbo-goal/SKILL.md (or your agent's skills folder).Prompt: Start a Jumbo goal by loading its full context — objective, criteria, scope, architecture, components, decisions, invariants, and guidelines — then execute within the defined boundaries.
When jumbo goal start is run, it assembles the goal's registered relations into structured implementation instructions. The objective defines what to build. The criteria define how success is measured. The scope defines boundaries. The architectural context (components, decisions, invariants, guidelines) defines constraints. Deviating from these instructions produces work that fails QA review.
jumbo goal start --id <goal-id>This loads the full goal context. Read and internalize every section of the output before writing any code.
The goal start output contains structured sections. Each section carries binding instructions:
The single purpose of this goal. All work must serve this objective.
The specific, measurable conditions that determine whether the objective is met. Implementation is not complete until every criterion is satisfied.
If the goal was previously started, review what has already been accomplished and continue from there. Do not redo completed work.
jumbo architecture update.Components that will be modified, created, or depended upon. Consider these while implementing.
External libraries involved in the implementation. Consider version constraints and contracts.
Previous architectural decisions that inform or constrain this change. The solution must remain consistent with these decisions.
Non-negotiable constraints. You MUST adhere to ALL invariants while implementing.
Coding standards, testing requirements, and process practices. You SHOULD follow these while implementing.
jumbo goal update-progress --id <goal-id> --task-description "<description>"Register decisions, components, and corrections as they happen — not as a cleanup step after implementation.
Architectural decision made (e.g., chose pattern X over Y):
jumbo decision add --title "Chose X over Y" --rationale "Because Z" --context "Background"New component created (e.g., introduced a new service or builder):
jumbo component add --name "ComponentName" --description "What it does"
jumbo relation add --from-type goal --from-id <goal-id> --to-type component --to-id <component-id> --type involves --description "Created during implementation"User corrects your approach (e.g., "don't do X, do Y instead"):
jumbo invariant add --category "architecture" --description "Never do X because Y"
jumbo guideline add --category "codingStyle" --description "Prefer X over Y"Context registered now is served to future sessions. What you skip is lost.
When all success criteria are met and implementation is complete:
jumbo goal submit --id <goal-id>jumbo goal update-progress to document completed sub-tasks so future agents can resume if needed.© 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
Just SKILL.md in assets/skills/start-jumbo-goal of jumbocontext/cli.
Open the folder on GitHubat commit a02a339
Start 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Start Jumbo Goal this skilljumbocontext/cli | 276 | — | ~1.2k | Automated safety check: Pass | AGPL-3.0 | |
| Trellis Session Insightmindfold-ai/Trellis | 15k | 4 repos | ~1.7k | Automated safety check: Pass | AGPL-3.0 | |
| Openspec Verify ChangeFission-AI/OpenSpec | 71k | 2 repos | ~4.6k | Automated safety check: Pass | MIT | |
| Warp Factory Fileswarpdotdev/warp | 65k | 1 repos | ~2.5k | Automated safety check: Pass | AGPL-3.0 | |
| Migrate Core Code to Submodulestinyhumansai/openhuman | 42k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Analyze Logsactivepieces/activepieces | 25k | 1 repos | ~1.6k | Automated safety check: Pass | MIT |
mindfold-ai/Trellis
Reach into past AI conversation history through the trellis mem CLI.
Fission-AI/OpenSpec
Verify implementation matches OpenSpec change artifacts. An agent skill from Fission-AI/OpenSpec.
warpdotdev/warp
Authors and edits file-based Warp software factory definitions rooted at factory.yaml, covering agents, automations, scorers and webhooks, and validates them before a pull request.
tinyhumansai/openhuman
Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.
activepieces/activepieces
Analyze application logs from the .evlog/logs/ directory. An agent skill from activepieces/activepieces.
prisma/orm
Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.
jumbocontext/cli
A skill your agent uses when a Jumbo goal has been approved by QA review and needs architectural reconciliation before closing.
jumbocontext/cli
A skill your agent uses when a project has Architecture data that needs migrating to fine-grained entities (Decisions, Invariants, Components, Dependencies).
jumbocontext/cli
Add Jumbo goals liberally to decompose objectives into finite units of work with bounded context.
jumbocontext/cli
Use liberally when the user expresses a preference about how work should be done — coding style, process, testing approach, communication style.
jumbocontext/cli
A skill your agent uses when Jumbo goals need refinement before implementation.
jumbocontext/cli
A skill your agent uses when a Jumbo goal fails QA review and needs to be returned for rework.
Categories
A skill your agent uses when starting a Jumbo goal. An agent skill from jumbocontext/cli. Start Jumbo Goal is an agent skill from jumbocontext/cli. Use when starting a Jumbo goal.
Start Jumbo Goal fits situations like: starting a Jumbo goal.
Run `npx skills add jumbocontext/cli --skill start-jumbo-goal -a claude-code`. Or copy the skill folder (assets/skills/start-jumbo-goal in jumbocontext/cli) into .claude/skills/start-jumbo-goal in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jumbocontext/cli --skill start-jumbo-goal -a codex`. Or copy the skill folder (assets/skills/start-jumbo-goal in jumbocontext/cli) into .agents/skills/start-jumbo-goal 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 jumbocontext/cli --skill start-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/start-jumbo-goal, .gemini/skills/start-jumbo-goal, .github/skills/start-jumbo-goal and .opencode/skills/start-jumbo-goal in your project.
SKILL.md names no scripts, command-line tools or credentials: Start Jumbo Goal 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.
Start 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.
About 1.2k tokens (SKILL.md is roughly 4.8k 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 Start Jumbo Goal: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Openspec Verify Change (Fission-AI/OpenSpec, 71k stars), Warp Factory Files (warpdotdev/warp, 65k stars) and Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.