AB podcast
Use when the user wants to turn an article/blog/text into a published podcast episode: triggers like "生成播客""做一期播客""博客转播客""文章转播客""发布/更新播客""blog to podcast", or when they hand over a URL / text / a batch of source material to be turned into an audio show. ALSO use for maintaining published episodes: "只改 shownotes" "更新单集描述""换封面""修 RSS feed""小宇宙没更新" (update_metadata / --init paths). SKIP: plain read-this-text-aloud TTS requests - call TTS directly, this pipeline is overkill.
As a process B 70/100 · Nearly there — weak spots: inputs and preconditions, running it twice
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenassets/mic_tap.b64.txt:47High-entropy token-like string (may be an id, hash or a credential)ffM+86Hy0/HV8G…vtm+xH7F…zkU+MS4kfhFt8O
-
low Secrets in code
secret-high-entropy-tokenassets/mic_tap.b64.txt:51High-entropy token-like string (may be an id, hash or a credential)fyLh…dzJ+QnIS…rCk+KSQp…int
-
low Secrets in code
secret-high-entropy-tokenassets/mic_tap.b64.txt:55High-entropy token-like string (may be an id, hash or a credential)UeNm4nHhk+Ck39…lNX+1G3U…dBN
-
low Secrets in code
secret-high-entropy-tokenassets/mic_tap.b64.txt:59High-entropy token-like string (may be an id, hash or a credential)sPax…Pm9+sf7x/zM/cz+vf/DALs…igV+BnwH…BBS
-
low Secrets in code
secret-high-entropy-tokenassets/mic_tap.b64.txt:86High-entropy token-like string (may be an id, hash or a credential)ANEA…tgC+ALwA…KAA
Files scanned: 18. 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 70/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 24 mutating operations with no state check
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 20 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3342 tokens
- 100Progress reporting. Reports progress
- 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)
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 475: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 20 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +3All 9 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 100.