AC tech-article
要写技术分享但不知从何下手？草稿写完读起来像流水账？ 从选题→大纲→草稿→润色→发布，端到端帮你把技术经验变成一篇让人记住的文章。 适用于团队内部技术分享、掘金/InfoQ 博文、技术复盘、会议演讲稿。 不适用于：API 文档（用 doc-gen）、README（用 readme-craft）、去 AI 味（用 deslop）。
As a process C 62/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, consistency
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-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Write Edit Grep Glob Bash AskUserQuestion WebFetch WebSearch Agent
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "triggers"
Process rating: all ten parameters 62/100
- 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
- 40Consistency. Frontmatter name (tech-article) differs from the folder (tech-article-cn)
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 29 steps
- 100Execution cost. Instruction body is 1735 tokens
- 100Running it twice. No mutating operations
- low 13 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 tags): a typed call is more reliable
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)
- +2Single-language instructions
- +3Description length 165: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 29 items
- +3Output format is stated explicitly
- +4Has examples (11 code blocks)
- +4Reference files are cited in the instructions (6 of 6)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.