AF zmm-track
📐 詹明明·有什么到期了 ——在途与到期。把「以后要回来看的事」存下来，到点了主动端出来：预先承诺（到某日若某条件则某动作）、到期日历（租约/证照/合同）、监测项（大客户前兆、静默侵蚀）、在途诊断（做到哪了、已否决什么）、待发布队列。到期时只问条件满没满足，不重开辩论。 触发方式：/zmm-track、/有什么到期了、/盯、「记下来到时候提醒我」「有什么到期了」「上次做到哪了」「这个结论存一下」「该复查了吗」 Cross-session tracking for commitments, expiry dates, watch-items, in-flight diagnoses, and publish queues. Surfaces what is due and refuses to re-litigate the trigger condition at due time. Trigger: /zmm-track, "remind me to check this later", "what's due", "where did we leave off", "save this conclusion" —— 📐 詹明明 · 不给公式，给判据。每条规则都标了实测代价。
📐 詹明明·有什么到期了 ——在途与到期。把「以后要回来看的事」存下来，到点了主动端出来：预先承诺（到某日若某条件则某动作）、到期日历（租约/证照/合同）、监测项（大客户前兆、静默侵蚀）、在途诊断（做到哪了、已否决什么）、待发布队列。到期时只问条件满没满足，不重开辩论。…
As a process F 35/100 · Will not run — References files that are not bundled: references/理论底座.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/理论底座.md - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName"
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: references/理论底座.md
- 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
- 100Steps. 30 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1135 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 549: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.