AB hengshuiclaw
Activate HengshuiClaw mode — a衡水-style pressure escalation system for AI coding agents. Use when you want the AI to push harder, exhaust every solution before giving up, and never rest until the task is done. Inspired by the Hengshui High School model. Triggers on phrases like "衡水模式", "班主任模式", "hengshuiclaw", "don't give up", "push harder", "never quit", or when the agent is about to abandon a task without fully trying. Also activate automatically when the agent says "I can't", "this is not possible", or "I give up".
As a process B 69/100 · Nearly there — weak spots: result and completion, inputs and preconditions, progress reporting
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: 3. 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 69/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
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 24 steps
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 826 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 522: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 24 items
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.