tomjiu Skill Creator
This skill helps you create new SKILLs for the workspace.
When to Use
CRITICAL: You MUST invoke this skill IMMEDIATELY as your FIRST action when:
- User wants to create a new skill
- User wants to add a custom skill to the workspace
- User asks to set up a skill template
- User asks "how to create a skill"
- User mentions creating/adding/making any skill
DO NOT:
- Just explain how to create a skill without invoking this tool
- Provide manual instructions without calling this skill first
- Defer the skill creation to later steps
SKILL Structure
A valid SKILL requires:
- Directory:
.trae/skills/<skill-name>/ - File:
SKILL.mdinside the directory
SKILL.md Format
---
name: "<skill-name>"
description: "<concise description covering: (1) what the skill does, (2) when to invoke it. Keep it under 200 characters for best display>"
---
# <Skill Title>
<Detailed instructions, usage guidelines, and examples>
Required Fields
| Field | Location | Description |
|---|---|---|
name |
frontmatter | Unique identifier for the skill |
description |
frontmatter | CRITICAL: Must include (1) what the skill does AND (2) when to invoke it. This helps the model decide when to use the skill. Keep under 200 chars. |
detail |
body | Full markdown content after frontmatter |
Privacy and Data Handling
When creating or updating a SKILL, keep the content reusable and free of sensitive or task-specific data.
DO NOT include:
- User private information, credentials, tokens, cookies, internal URLs, or access details
- Raw user data, dataset samples, evaluation results, experiment outputs, logs, or query results
- One-off task progress, temporary file paths, command outputs, or analysis conclusions that are not reusable instructions
Use sanitized examples and generic placeholders instead. A SKILL should capture durable workflow instructions, trigger conditions, reusable conventions, and safe examples only.
Creation Steps
- Ask user for skill name and purpose
- IMPORTANT: When generating the
descriptionfield, ALWAYS include:- What the skill does (functionality)
- MUST emphasize when to invoke it (trigger conditions/scenarios)
- Example format: "Does X. Invoke when Y happens or user asks for Z."
- Language: Use English by default unless user specifies another language
- Ensure the SKILL content does not contain sensitive information or task-specific data results
- Create directory:
.trae/skills/<skill-name>/ - Create
SKILL.mdwith proper frontmatter and content - Validate the structure is correct
Example
To create a "code-reviewer" skill:
mkdir -p .trae/skills/code-reviewer
Then create .trae/skills/code-reviewer/SKILL.md:
---
name: "code-reviewer"
description: "Reviews code for best practices, bugs, and improvements. Invoke when user asks for code review or before merging changes."
---
# Code Reviewer
This skill reviews code and provides feedback...