AD yotta-prompt
元引 —— 意图澄清 + 生态入口技能：用户输入一句模糊的话 / 一个词时，识别意图、给出 2-4 个候选方向、深挖（目标/范围/输出/约束），再串联到对应元阁技能输出可直接运行的提示词。常驻注入（always-load）：每次新会话开始自动生效，接住「不会用 AI、不知道怎么提问」的用户。触发：用户不知道怎么提问、不知道想要什么、输入模糊的一句话 / 一个词、想被引导到合适技能时。边界：只澄清意图、不预设立场、不做安全评审；提示词不人为设限（不违规/不犯法/不越狱即可）；不做 prompt 美化；纯本地离线。
元引 —— 意图澄清 + 生态入口技能：用户输入一句模糊的话 / 一个词时，识别意图、给出 2-4 个候选方向、深挖（目标/范围/输出/约束），再串联到对应元阁技能输出可直接运行的提示词。常驻注入（always-load）：每次新会话开始自动生效，接住「不会用…
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 46/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 27 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1032 tokens
- 100Running it twice. No mutating operations
- low 10 top-level sections: this looks like several domains in one skill
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
- -31 of 2 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 258: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 27 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.