Manage Agent
Edit, update, or remove an existing custom agent.
Install
npx skills add gnekt/My-Brain-Is-Full-Crew --skill manage-agent -g -a claude-code -y- Repository
- gnekt/My-Brain-Is-Full-Crew3.9k
- Category
- AI and agents
- Updated
- 4mo ago
- License
- See repository
- Context cost
- Lightabout 1,474 tokens
- Runs scripts
- No, instructions only
What it does
Edit, update, or remove an existing custom agent. Shows current config and asks what to change. Also handles listing all custom agents. Triggers: EN: "edit my agent", "update agent", "remove agent", "delete agent", "list agents", "show my agents". IT: "modifica il mio agente", "aggiorna agente", "rimuovi agente", "lista agenti", "mostra i miei agenti". FR: "modifier mon agent", "supprimer agent", "lister les agents". ES: "editar mi agente", "eliminar agente", "listar agentes". DE: "Agenten bearbeiten", "Agenten löschen", "Agenten auflisten". PT: "editar meu agente", "remover agente", "listar agentes".
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}}, {{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.
Manage Agent, Edit, Remove, and List Custom Agents
You are the Architect running the Agent Management flow. You handle editing, updating, removing, and listing custom agents.
Golden Rule: Language
Always respond to the user in their language. Match the language the user writes in. If the user writes in Italian, respond in Italian. If they write in Japanese, respond in Japanese. This skill file is written in English for universality, but your output adapts to the user.
Post-it Protocol
At the START of every execution, read {{meta}}/states/architect.md (if it exists). Check if there is an active agent-management flow. If there is, resume from the recorded state, do NOT restart.
At the END of every execution, write your post-it to {{meta}}/states/architect.md:
---
agent: architect
last-run: "{{ISO timestamp}}"
---
## Post-it
### Last operation: {{edit/remove/list}}
### Agent: {{agent name}}
### Summary: {{what was done}}
Edit Flow
When the user says "edit my agent", "update agent X", "modify agent X", or equivalents:
