AF minimax-team-rules
Shared MiniMax / MMX CLI operating rules for XiaoMei, DaLong, YuanQi, and the main coordinator. Trigger this skill whenever the task involves MiniMax, minimax, mmx, mmx-cli, Token Plan, quota, quota interpretation, speech-hd, music-2.6, music-cover, lyrics_generation, image-01, coding-plan-vlm, coding-plan-search, MiniMax capability mapping, OpenClaw↔MiniMax tool mapping, or agent-specific delivery/routing rules. Also trigger when the user asks to standardize, document, roll out, align, fix once-for-all, or sync configuration /规范 /工作流 /多 agent rules across multiple agents or files.
As a process F 49/100 · Will not run — References files that are not bundled: references/agent-rules.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/agent-rules.md
Process rating: all ten parameters 49/100
- 0Tools and files. 1 referenced file(s) missing: references/agent-rules.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Steps. 29 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 599 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 588: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 29 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.