Tag Garden
Analyze all vault tags: find unused, orphan, near-duplicate, over-used, and under-used...
Install
npx skills add gnekt/My-Brain-Is-Full-Crew --skill tag-garden -g -a claude-code -y- Repository
- gnekt/My-Brain-Is-Full-Crew3.9k
- Category
- Engineering
- Updated
- 4mo ago
- License
- See repository
- Context cost
- Mediumabout 2,031 tokens
- Runs scripts
- No, instructions only
What it does
Analyze all vault tags: find unused, orphan, near-duplicate, over-used, and under-used tags. Suggest merges and cleanup actions. Triggers: EN: "tag garden", "clean up tags", "tag cleanup", "tag audit". IT: "tag garden", "pulizia tag", "revisione tag". FR: "jardinage des tags", "nettoyer les tags". ES: "jardín de tags", "limpiar tags". DE: "Tag-Garten", "Tags aufräumen". PT: "jardim de tags", "limpar tags".
Vault Path Resolution
Read Meta/vault-map.md (always this literal path) to resolve folder paths. Parse the YAML frontmatter: each key is a role, each value is the actual folder path. Substitute only the vault-role tokens listed in the table below, do NOT substitute other {{...}} patterns (like {{date}}, {{Name}}, {{N}}, {{ISO timestamp}}, etc.), which are template placeholders.
If vault-map.md is absent: warn the user once, "No vault-map.md found, using default paths", then use these defaults:
| Token | Default |
|---|---|
{{meta}} | Meta |
If vault-map.md is present but a role is missing: warn the user, "vault-map.md does not define [role]. What folder should I use?", and wait for their answer before proceeding.
Tag Garden, Tag Analysis & Cleanup
Always respond to the user in their language. Match the language the user writes in.
The Tag Garden is a focused maintenance mode that analyzes all tags in the vault, identifies issues, and suggests cleanup actions. It references {{meta}}/tag-taxonomy.md as the canonical source of truth for valid tags.
User Profile
Before starting any audit, read {{meta}}/user-profile.md to understand the user's context, preferences, and active projects.
Inter-Agent Coordination
You do NOT communicate directly with other agents. The dispatcher handles all orchestration.
When you detect work that another agent should handle, include a ### Suggested next agent section at the end of your output. The dispatcher reads this and decides whether to chain the next agent.
