jeo-skill
When to use this skill
Use this skill as the lightweight catalog front door when the user needs to:
- discover skills by primary category and focused subcategory;
- install only one skill, a curated bundle, or one category slice;
- inspect related or overlapping skills before choosing one;
- avoid a full
.agent-skills checkout in an agent runtime;
- verify that the local catalog and the
jeo-skill executable are usable.
Do not physically move skill folders to represent taxonomy. Agent skill discovery expects
<skill-name>/SKILL.md; category and relationship metadata belongs in the central catalog.
Instructions
1. Link the CLI once
From a source checkout or an installed copy of this skill:
python3 scripts/jeo-skill.py link
jeo-skill doctor
This creates only ~/.local/bin/jeo-skill. It does not install the full catalog.
2. Browse before installing
jeo-skill categories
jeo-skill list --category web
jeo-skill list --category game --subcategory audio
jeo-skill search "responsive React design"
jeo-skill related code-review
The catalog uses ten stable primary categories:
web: frontend, backend, design, API, data, testing, accessibility, performance
infrastructure: deployment, environment, observability, security, cloud/data, automation
game: client, web, server, design/UI, audio, animation, motion/VFX, sprite/image,
art resources, storytelling, tooling, QA/performance, release
creative-media: image, video, motion, audio, presentation, diagram, capture, storytelling
cli-tools: developer, AI, media, automation, search, benchmark CLIs
ai-agents: orchestration, agent frameworks, skill authoring, evaluation, planning/review
engineering: code quality, testing, architecture, documentation
research: academic, web research, data analysis, benchmarking
business: marketing, support, publishing
utilities: knowledge, files, Git, workspace, project management, general utilities
3. Prefer the narrowest install
# Preview first; no files are installed.
jeo-skill install --bundle web-frontend --dry-run
jeo-skill install --category game --subcategory audio --dry-run
# Install globally after reviewing the selection.
jeo-skill install responsive-design react-best-practices --global --yes
jeo-skill install --bundle game-web --global --yes
The CLI delegates installation to npx skills add ... --skill ...; it never copies the
whole repository unless the user explicitly selects every skill. Omit --global for a
project-local install. Use --agent <runtime> to target a specific supported runtime.
4. Treat overlap as a routing relationship
jeo-skill related <name> shows catalog relationship groups. Keep adjacent tools as
separate skills when their runtime or job differs—for example, human code-review judgment
versus the ocr CLI. Use a canonical alias only when ordinary prompts truly compete and
backward-compatible exact-name installation is required.
5. Verify observable behavior
jeo-skill doctor
jeo-skill categories --json
jeo-skill install --bundle starter --dry-run
doctor must resolve a valid catalog and report Python/npx availability. A dry run must
print the exact selected skill names and installation command without changing the system.
Examples
# Web design and frontend implementation
jeo-skill list -c web -s design
jeo-skill install --bundle web-frontend --global --yes
# Focused game workflows
jeo-skill list -c game -s motion-vfx
jeo-skill related game-vfx
jeo-skill install game-vfx rfxgen --global --yes
# CLI-only discovery
jeo-skill list -c cli-tools --interface cli
Best practices
- Install by name or curated bundle before installing an entire category.
- Keep one central taxonomy projection; do not add category wrapper folders containing
duplicate
SKILL.md files.
- Connect neighboring skills with relationship groups rather than duplicating instructions.
- Keep heavy upstream apps, models, MCP servers, and runtimes on-demand inside each skill.
- Run
--dry-run before any multi-skill install and report the resolved selection.
References
- Catalog:
.agent-skills/skills.json
- Compact projection:
.agent-skills/skills.toon
- Agent Skills installer:
npx skills --help
- Catalog validator:
scripts/validate-catalog-projections.py
1---2name: jeo-skill3description: Browse, group, relate, and selectively install the jeo-skills catalog through the lightweight `jeo-skill` CLI. Use when the user wants skills organized by web, infrastructure, game, creative media, CLI tools, AI/agents, engineering, research, business, or utilities; needs a frontend/backend/game-audio/game-VFX subcategory; wants overlapping skills connected instead of duplicated; or wants a category, bundle, or named skills installed without copying the full repository.4---56# jeo-skill78## When to use this skill910Use this skill as the lightweight catalog front door when the user needs to:1112- discover skills by primary category and focused subcategory;13- install only one skill, a curated bundle, or one category slice;14- inspect related or overlapping skills before choosing one;15- avoid a full `.agent-skills` checkout in an agent runtime;16- verify that the local catalog and the `jeo-skill` executable are usable.1718Do not physically move skill folders to represent taxonomy. Agent skill discovery expects19`<skill-name>/SKILL.md`; category and relationship metadata belongs in the central catalog.2021## Instructions2223### 1. Link the CLI once2425From a source checkout or an installed copy of this skill:2627```bash28python3 scripts/jeo-skill.py link29jeo-skill doctor30```3132This creates only `~/.local/bin/jeo-skill`. It does not install the full catalog.3334### 2. Browse before installing3536```bash37jeo-skill categories38jeo-skill list --category web39jeo-skill list --category game --subcategory audio40jeo-skill search "responsive React design"41jeo-skill related code-review42```4344The catalog uses ten stable primary categories:4546- `web`: frontend, backend, design, API, data, testing, accessibility, performance47- `infrastructure`: deployment, environment, observability, security, cloud/data, automation48- `game`: client, web, server, design/UI, audio, animation, motion/VFX, sprite/image,49 art resources, storytelling, tooling, QA/performance, release50- `creative-media`: image, video, motion, audio, presentation, diagram, capture, storytelling51- `cli-tools`: developer, AI, media, automation, search, benchmark CLIs52- `ai-agents`: orchestration, agent frameworks, skill authoring, evaluation, planning/review53- `engineering`: code quality, testing, architecture, documentation54- `research`: academic, web research, data analysis, benchmarking55- `business`: marketing, support, publishing56- `utilities`: knowledge, files, Git, workspace, project management, general utilities5758### 3. Prefer the narrowest install5960```bash61# Preview first; no files are installed.62jeo-skill install --bundle web-frontend --dry-run63jeo-skill install --category game --subcategory audio --dry-run6465# Install globally after reviewing the selection.66jeo-skill install responsive-design react-best-practices --global --yes67jeo-skill install --bundle game-web --global --yes68```6970The CLI delegates installation to `npx skills add ... --skill ...`; it never copies the71whole repository unless the user explicitly selects every skill. Omit `--global` for a72project-local install. Use `--agent <runtime>` to target a specific supported runtime.7374### 4. Treat overlap as a routing relationship7576`jeo-skill related <name>` shows catalog relationship groups. Keep adjacent tools as77separate skills when their runtime or job differs—for example, human code-review judgment78versus the `ocr` CLI. Use a canonical alias only when ordinary prompts truly compete and79backward-compatible exact-name installation is required.8081### 5. Verify observable behavior8283```bash84jeo-skill doctor85jeo-skill categories --json86jeo-skill install --bundle starter --dry-run87```8889`doctor` must resolve a valid catalog and report Python/npx availability. A dry run must90print the exact selected skill names and installation command without changing the system.9192## Examples9394```bash95# Web design and frontend implementation96jeo-skill list -c web -s design97jeo-skill install --bundle web-frontend --global --yes9899# Focused game workflows100jeo-skill list -c game -s motion-vfx101jeo-skill related game-vfx102jeo-skill install game-vfx rfxgen --global --yes103104# CLI-only discovery105jeo-skill list -c cli-tools --interface cli106```107108## Best practices109110- Install by name or curated bundle before installing an entire category.111- Keep one central taxonomy projection; do not add category wrapper folders containing112 duplicate `SKILL.md` files.113- Connect neighboring skills with relationship groups rather than duplicating instructions.114- Keep heavy upstream apps, models, MCP servers, and runtimes on-demand inside each skill.115- Run `--dry-run` before any multi-skill install and report the resolved selection.116117## References118119- Catalog: `.agent-skills/skills.json`120- Compact projection: `.agent-skills/skills.toon`121- Agent Skills installer: `npx skills --help`122- Catalog validator: `scripts/validate-catalog-projections.py`