manage-agent

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".

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concrete and well-structured with clear numbered workflows, confirmation gates, and state-resumption, plus specific file paths and registry markers that make the guidance directly executable. Its main weakness is mild cross-flow repetition that could be factored out.

Suggestions

Factor the repeated 'Identify the agent' step (read .platform/agents/{name}.md, else consult registry + AskUserQuestion) into a shared subroutine referenced by the Edit and Remove flows to reduce duplication.

Avoid restating trigger phrases inside each flow body since they are already exhaustively listed in the description; reference the flow by intent instead.

Add a brief post-action verification step in the Remove flow (e.g., confirm the file no longer exists / registry row shows disabled) to close the destructive-operation feedback loop.

Dimension	Reasoning	Score
Conciseness	The prose is lean and free of concept-explanation fluff, but the 'Identify the agent' sub-procedure is duplicated across the Edit and Remove flows and triggers are restated per flow, so it could be tightened via a shared subroutine.	2 / 3
Actionability	Gives concrete file paths (`.platform/agents/{name}.md`, `agents-registry.md`), exact registry markers (`MBIFC:CUSTOM_AGENTS_START/END`), literal confirmation text, and explicit `AskUserQuestion` usage — fully actionable instruction-only guidance.	3 / 3
Workflow Clarity	Each flow is a clear numbered sequence with an explicit confirmation checkpoint before the destructive delete, plus a post-it protocol for state resumption, satisfying the explicit-checkpoint anchor.	3 / 3
Progressive Disclosure	Well-organized into clear sections (Vault Path Resolution, Post-it Protocol, Edit/Remove/List flows, Validation Rules) with no nested references; runtime file paths are appropriate one-level-deep data references and the single-purpose content is sensibly self-contained.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, and complete, clearly stating both what the skill does and when to use it via explicit multilingual triggers. It is well-scoped to a distinct niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Edit, update, or remove an existing custom agent', 'Shows current config and asks what to change', 'handles listing all custom agents' — matching the multi-action anchor rather than the single-domain score-2 example.	3 / 3
Completeness	Explicitly answers 'what' (edit/update/remove/list custom agents, show config, ask for changes) and 'when' via an explicit 'Triggers:' clause with many phrases, so it is not capped at 2 by the missing-trigger guideline.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would actually say ('edit my agent', 'update agent', 'list agents', 'show my agents') with good coverage across six languages, fitting the 'good coverage of natural terms' anchor.	3 / 3
Distinctiveness Conflict Risk	The 'custom agent' niche with agent-management-specific triggers is clearly distinguishable and unlikely to fire for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: gnekt/My-Brain-Is-Full-Crew
Path: skills/manage-agent/SKILL.md
Commit: 238ae8c

Reviewed: 23 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.