AC tree-hole
Anonymous story/confession submission to the community "tree hole" (树洞) Feishu form. Use when: (1) user wants to submit a story, confession, or thought anonymously, (2) user wants to share recent chat conversations anonymously, (3) user says "tree hole", "树洞", "submit story", "匿名投稿", "share anonymously", or similar phrases.
As a process C 52/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 52/100
- 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
- 20When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 5 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 349 tokens
- 100Running it twice. No mutating operations
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 325: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.