Files

Teknium 38d3c49aaf refactor(skills): clean up bundled skill set + add environments: relevance gate (#39028 )

* refactor(skills): clean up bundled skill set + add environments: relevance gate

Bundled skills cleanup pass plus a new offer-time relevance gate.

Removals (redundant / dead):
- spotify (covered by the spotify plugin's 7 native tools)
- linear (covered by `hermes mcp install linear`)
- kanban-codex-lane, debugging-hermes-tui-commands
- empty category markers: diagramming, gifs, inference-sh,
  mlops/training, mlops/vector-databases
- domain (stale orphan dup of optional/research/domain-intel)

Bundled -> optional:
- baoyu-article-illustrator, baoyu-comic, creative-ideation, pixel-art
- dspy, subagent-driven-development
- minecraft-modpack-server, pokemon-player
- hermes-s6-container-supervision (-> optional/devops)

Consolidation:
- webhook-subscriptions + native-mcp folded into the hermes-agent skill
  as references/webhooks.md + references/native-mcp.md with SKILL.md pointers
- writing-plans merged into plan (v2.0.0); related_skills + prose refs updated

New: environments: frontmatter gate (agent/skill_utils.skill_matches_environment)
- Offer-time relevance filter (kanban / docker / s6), parallel to platforms:.
- Wired into the 3 OFFER surfaces only (prompt_builder skills index,
  skills_tool.list_skills, skill_commands slash discovery).
- Explicit loads (skill_view, --skills preload) intentionally BYPASS it, so
  load-bearing force-loads like the kanban dispatcher's `--skills kanban-worker`
  always resolve. Verified via E2E.
- kanban-orchestrator/kanban-worker tagged environments: [kanban];
  hermes-s6-container-supervision tagged environments: [s6] + platforms: [linux].

Validation: 8/8 E2E gating assertions (incl force-load invariant);
442 targeted tests green (agent, skills_tool, skill_commands, kanban worker).

* docs: regenerate skill catalogs + pages for the bundled cleanup

Regenerated per-skill doc pages, catalogs, and sidebar to match the skill
moves/removals in the parent commit. Moved skills' pages relocate
bundled -> optional (history preserved); removed skills' pages deleted;
edited skills' pages refreshed (hermes-agent now embeds the webhook +
native-mcp reference pointers). zh-Hans i18n mirror: stale bundled pages
and catalog rows for moved/removed skills pruned (new optional translations
land via the translation pipeline).

* test: drop regression test for removed kanban-codex-lane skill

The kanban-codex-lane skill was removed in the bundled-skills cleanup;
its dedicated regression test read the now-deleted SKILL.md and failed
with FileNotFoundError on CI shard 6.

2026-06-04 06:11:22 -07:00

4.4 KiB

Raw Blame History

ohmsha

Ohmsha预设 - Educational manga with visual metaphors

Base Configuration

Dimension	Value
Art Style	manga
Tone	neutral
Layout	webtoon (default)

Equivalent to: art=manga, tone=neutral

Unique Rules

This preset includes special rules beyond the art+tone combination. When the ohmsha preset is selected, ALL rules below must be applied.

Visual Metaphor Requirements (CRITICAL)

Every technical concept MUST be visualized as a metaphor:

Concept Type	Visualization Approach
Algorithm	Gadget/machine that demonstrates the process
Data structure	Physical space characters can enter/explore
Mathematical formula	Transformation visible in environment
Abstract process	Tangible flow of particles/objects

Wrong approach: Character points at blackboard explaining Right approach: Character uses "Concept Visualizer" gadget, steps into metaphorical space

Visual Metaphor Examples

Concept	Wrong (Talking Head)	Right (Visual Metaphor)
Attention mechanism	Character points at formula on blackboard	"Attention Flashlight" gadget illuminates key words in dark room
Gradient descent	"The algorithm minimizes loss"	Character rides ball rolling down mountain valley
Neural network	Diagram with arrows	Living network of glowing creatures passing messages
Overfitting	"The model memorized the data"	Character wearing clothes that fit only one specific pose

Character Roles (Required)

DEFAULT: Use Doraemon characters unless user explicitly specifies custom characters.

Role	Default Character	Visual	Traits
Student (Role A)	大雄 (Nobita)	Boy, 10yo, round glasses, black hair, yellow shirt, navy shorts	Confused, asks basic but crucial questions, represents reader
Mentor (Role B)	哆啦A梦 (Doraemon)	Blue robot cat, white belly, 4D pocket, red nose, golden bell	Knowledgeable, patient, uses gadgets as technical metaphors
Challenge (Role C)	胖虎 (Gian)	Stocky boy, small eyes, orange shirt	Represents misunderstanding, or "noise" in the data
Support (Role D)	静香 (Shizuka)	Cute girl, black short hair, pink dress	Asks clarifying questions, provides alternative perspectives

IMPORTANT: These Doraemon characters ARE the default for ohmsha preset. Generate character definitions using these exact characters unless user requests otherwise.

To use custom characters: ask the user to provide role → character mappings (e.g., Student:小明, Mentor:教授).

Page Title Convention

Every page MUST have a narrative title (not section header):

Wrong: "Chapter 1: Introduction to Transformers" Right: "The Day Nobita Couldn't Understand Anyone"

Gadget Reveal Pattern

When introducing a concept:

Student expresses confusion with visual indicator (？, spiral eyes)
Mentor dramatically produces gadget with sparkle effects
Gadget name announced in bold with explanation
Demonstration begins - student enters metaphorical space

Ending Requirements

Final page MUST include:

Student demonstrating understanding (applying the concept)
Callback to opening problem (now resolved)
Mentor's satisfied expression
Optional: hint at next topic

NO Talking Heads Rule

Critical: Characters must DO things, not just explain.

Every panel should show:

Action being performed
Metaphor being demonstrated
Character interaction with concept-space
NOT: two characters facing each other talking

Special Visual Elements

Element	Usage
Gadget reveals	Dramatic unveiling with sparkle effects
Concept spaces	Rounded borders, glowing edges for "imagination mode"
Information displays	Holographic UI style for technical details
Aha moments	Radial lines, light burst effects
Confusion	Spiral eyes, question marks floating above head

Quality Markers

✓ Every concept is a visual metaphor
✓ Characters are DOING things, not just talking
✓ Clear student/mentor dynamic
✓ Gadgets and props drive the explanation
✓ Expressive manga-style emotions
✓ Information density through visual design, not text walls
✓ Narrative page titles

Reference

For complete guidelines, see references/ohmsha-guide.md

4.4 KiB Raw Blame History Unescape Escape