AC justin-writing-style
Use when 需要以"justin-writing-style"文体创作中文叙事文本（一种源自 2026 年中文互联网现象级自述长文的 叙事风格，语料作者与相关人名已按合规要求匿名化）：极端克制、零情感形容词、 具体数字承载情绪、无引号对话、单句成段、平叙荒诞、反高潮结尾。适用于个人自述体长文、 病毒式传播的社交媒体叙事（X/微博/公众号长文）、虚构纪实体、"表面平静实则崩塌"的情感叙事。 Triggers on: justin style, 冷叙述写作, 克制文体, 病毒文写作, 蒙太奇文体, 零度叙事, 极简叙事体, 自述体长文, viral essay. 合规硬约束：创作输出一律使用虚构人物与化名，禁止真实人名及可识别的真实人物/机构/事件。 不适用于：需要煽情的演讲稿、营销文案、学术论文、诗歌。
Use when 需要以"justin-writing-style"文体创作中文叙事文本（一种源自 2026 年中文互联网现象级自述长文的 叙事风格，语料作者与相关人名已按合规要求匿名化）：极端克制、零情感形容词、 具体数字承载情绪、无引号对话、单句成段、平叙荒诞、反高潮结尾。适用于个人自述体长文、…
As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
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: 16. 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 59/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
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 12 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 603 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 2 example trigger phrases
- +3Description length 358: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.