fdefd98aa3
Previous pass assumed both skills would always be loaded together, so
each description pointed at the other ('use concept-diagrams instead').
That breaks when only one skill is active — the agent reads 'use the
other skill' and there is no other skill.
Now each skill's description and scope section is fully self-contained:
- States what it's best suited for
- Lists subjects where a more specialized skill (if available) would be
a better fit, naming them only as 'consider X if available'
- Explicitly offers itself as a general SVG diagram fallback when no
more specialized skill exists
An agent loading either skill alone gets unambiguous guidance; an
agent with both loaded still gets useful routing via the 'consider X
if available' hints and the related_skills metadata.
|
||
|---|---|---|
| .. | ||
| autonomous-ai-agents | ||
| blockchain | ||
| communication | ||
| creative | ||
| devops | ||
| email/agentmail | ||
| health | ||
| mcp | ||
| migration | ||
| mlops | ||
| productivity | ||
| research | ||
| security | ||
| DESCRIPTION.md | ||