User input: $ARGUMENTS
Task
Route based on the first token of $ARGUMENTS to the corresponding /skill* command, passing the remaining part as parameters.
Routing Table
| First token (CN/EN) | Route to |
|---|---|
帮助 / help / h / ? | Execute /skillHelp flow |
列表 / list / ls / l | Execute /skillList flow |
查找 / find / search / q | Execute /skillFind flow, pass remaining as requirement |
安装 / install / add / i | Execute /skillInstall flow, pass remaining as target |
详情 / detail / info / show | Execute /skillDetail flow, pass remaining as target |
修改 / modify / edit / custom | Execute /skillModify flow, pass remaining as "name + requirement" |
回滚 / rollback / revert / undo | Execute /skillRollback flow, pass remaining as target |
卸载 / uninstall / remove / delete / rm | Execute /skillUninstall flow, pass remaining as target |
介绍 / intro / describe / about | Execute /skillIntro flow, pass remaining as target |
Pure number (e.g., 3, 12) | Equivalent to /skillDetail , directly view details of that ID |
Fallback
If the first token is not in the table and is not a number:
- Treat it as a fuzzy "find" intent, tell the user "I guess you want to find a skill that can do X. If correct, reply y and I'll proceed with /skillFind; otherwise, use /skillHelp to see the command list."
- Wait for user confirmation before proceeding with /skillFind
Examples
/skill help→ routes to /skillHelp/skill list→ routes to /skillList/skill find writing tool→ /skillFind "writing tool"/skill 3→ /skillDetail 3/skill modify asset-forge make it output png by default→ /skillModify "asset-forge make it output png by default"/skill uninstall rembg→ /skillUninstall rembg/skill find one for writing→ first token "find one for writing" not in table, fallback to "I guess you want /skillFind"
Notes
- After routing, directly execute the full flow of the corresponding command (follow the template guidance for that command); do not ask the user again.
- Chinese tokens take priority, English aliases are tolerated for fault tolerance.