tomevault-io Meta-Skill Routing
When a library has dozens of skills, you cannot load them all. You must "route" your attention effectively.
The Two-Step Pattern
- Index Lookup: Read the root
README.mdor a dedicated index to identify which skills are relevant to the current request. - Explicit Load: Only load the content of the specific
SKILL.mdfiles needed.
Routing Heuristics
- Keyword Matching: Look for domain-specific keywords (e.g., "Flask", "TDD", "Transformers").
- Intent Discovery: Ask, "Is this a planning, implementing, or verifying task?" and route to the corresponding skill suite.
Best Practices
- Atomic Loading: Avoid "just in case" loading. Only load a skill when you are about to perform an action related to it.
- Reference Over Inclusion: Link to skills in documentation instead of copying their content.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.