As a processF28/100 · Will not run — References files that are not bundled: workflows/routing.md, workflows/generate-pptx.md, scripts/trusted_search.py
Will not run. References files that are not bundled: workflows/routing.md, workflows/generate-pptx.md, scripts/trusted_search.py
0Tools and files. 3 referenced file(s) missing: workflows/routing.md, workflows/generate-pptx.md, scripts/trusted_search.py
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
30Running it twice. 1 mutating operations with no state check
40Consistency. Frontmatter name (深知可信PPT) differs from the folder (dknowc-ppt-assistant)
100Steps. 31 steps
100Execution cost. Instruction body is 1513 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
-321 of 24 scripts are never mentioned in SKILL.md
+1No license
+2Single-language instructions
+3Description length 306: enough signal without eating the budget
+4Structure: 11 headings
+3Step-by-step instructions: 31 items
+4Has examples (6 code blocks)
+4Reference files are cited in the instructions (6 of 6)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 53.
External checks
ClawHub: suspicious
The PPT-generation purpose is coherent, but the skill’s phone-based onboarding can create or retrieve long-lived API keys and is not plainly disclosed to users at runtime.