Skills

A Skill is a reusable task guide centered on SKILL.md. It can contain a workflow, constraints, scripts, and dependency information. Mogick lists user-installed Skills under Plugins → Skills.

Screenshots on this English page reuse the Chinese-language UI from the same verified run.

Open the Skills page

Select Plugins in the left sidebar, then switch to Skills at the top. The verified UI directly shows installed Skills; it does not have a separate Skill Market tab.

The page provides actions to:

• refresh Skill directories;
• import from TRAE;
• install locally;
• search Skills;
• browse cards grouped by scope;
• enable or disable a Skill with its card switch.

A card shows the name, description, and labels such as Contains scripts or Imported from TRAE. A disabled Skill should not participate in later new tasks; use a new conversation when verifying a state change.

Import from TRAE

Select Import from TRAE and follow the interface to choose available Skills. After import:

1. Return to the Skill list.
2. Refresh if necessary.
3. Search for the Skill name.
4. Confirm that its card is labeled Imported from TRAE and enabled.

If the Skill does not appear, first verify that the current Windows user has an accessible TRAE Skill directory, then retry the import.

Local installation

Select Local install and complete the file-selection flow. Return to the list and verify that the Skill card appears; selecting a file alone does not prove that the kernel discovered the Skill.

This run verified the local-install entry but did not test every archive format, overwrite strategy, or error branch. Use the file types and conflict options offered by the current installation dialog.

Inspect details

Select a Skill card to open its details. The view shows:

• name and description;
• enabled state;
• filesystem path;
• plugin dependencies;
• the SKILL.md body;
• Uninstall and Use in conversation actions.

Read SKILL.md to verify the Skill's actual process and constraints. If its body differs from the card summary, use the current SKILL.md in the installed path as the source of truth.

Use a Skill in conversation

Select Use in conversation, return to chat, enter a concrete task, and send it. Before use, verify that:

1. the Skill is enabled;
2. required plugins are available;
3. the task matches the Skill description;
4. any required product connector is connected and has a non-zero MCP tool count.

The action selects the Skill for the conversation workflow; it does not mean that the task has run. Inspect project files, tool output, and results for completion evidence.

Uninstall and troubleshoot

User-installed Skills can be removed from the details view. Before uninstalling, record the filesystem path and verify that other workflows do not depend on the Skill.

If a Skill is not working as expected, check in this order:

1. It appears in search results.
2. Its card and details switches are enabled.
3. Its path and SKILL.md are readable.
4. Required plugins are enabled and connected.
5. Start a new conversation and retry with Use in conversation.

For connector and MCP runtime checks, see Plugins and Skills.