AC ex-clapback-writing-style
Use when 需要以"前任回怼写作风格"写中文社交媒体文案（微博/小红书/朋友圈体），即一种"前任视角+反讽撒娇+富豪/创业者对象+日常荒诞细节"的叙事风格，表面深情款款、实则句句带刺。适用于分手文学、人设解构、前任反讽段子、甜丧文案。触发词：前任回怼、回怼文案、反讽撒娇体、富豪前任叙事、分手文学、人设解构。合规硬约束：输出一律使用虚构人物与泛化代称，禁止真实人名及可识别事件，不复制原文。不适用于纯冷叙述/零度叙事长文（用 justin-writing-style）与煽情营销/演讲稿/论文。
Use when…
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-agent-memory-dump.workbuddy/memory/2026-08-28.mdAgent memory / workspace files bundled with the skill (1) — likely a workspace dump with personal data or tokens.workbuddy/memory/2026-08-28.md
Files scanned: 13. 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 53/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
- 100Tools and files. No external tools needed
- 100Steps. 16 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 658 tokens
- 100Running it twice. No mutating operations
- low 11 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 2 example trigger phrases
- +3Description length 250: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.