with one click
skill-graph-manager
// MANDATORY mechanism for managing the bidirectional Skill Knowledge Graph. Invoke IMMEDIATELY after creating or modifying ANY skill to update links and the central index.
// MANDATORY mechanism for managing the bidirectional Skill Knowledge Graph. Invoke IMMEDIATELY after creating or modifying ANY skill to update links and the central index.
[HINT] Download the complete skill directory including SKILL.md and all related files
| name | skill-graph-manager |
| description | MANDATORY mechanism for managing the bidirectional Skill Knowledge Graph. Invoke IMMEDIATELY after creating or modifying ANY skill to update links and the central index. |
Focus: bidirectional linking, skill indexing, and consistent cross-skill navigation.
This skill acts as the automated librarian for the workspace. It ensures that all skills are interconnected in a Knowledge Graph, allowing the LLM to naturally associate related skills (e.g., jumping from devops-task-planning to prd-task-splitter automatically).
Action: Read the new or modified SKILL.md. Understand its boundaries, focus, and target audience.
Action: Consult the central index (trae-skill-index/SKILL.md). Identify 2-5 existing skills that are logically related (e.g., predecessor, successor, sibling, or standard constraints).
Action: STOP AND ASK. Use the AskUserQuestion tool or text response to present the proposed links to the user.
Example Prompt: "I've detected a change to skill
X. To maintain the Knowledge Graph, I propose adding bidirectional links betweenXand[Y, Z]. Options:
- Approve all proposed links.
- Add/Remove specific links (please specify).
- Skip graph update this time."
Action: Once the user approves:
## Related Skills section at the bottom of the new/modified SKILL.md.## Related Skills section of the related existing skills.trae-skill-index/SKILL.md to reflect the new graph topology.Whenever you write a bidirectional link inside a SKILL.md, you MUST use this exact Markdown format:
## Related Skills
- [skill-a](../skill-a/SKILL.md): <Brief explanation of why they are related, e.g., "The predecessor skill for requirements">
- [skill-b](../skill-b/SKILL.md): <Brief explanation, e.g., "Provides the coding standards required by this skill">