AC podcast-production-workflow
End-to-end workflow for planning, producing, distributing, and repurposing podcast content. Use this skill whenever the user asks about planning podcast episodes, writing show notes, creating episode scripts or outlines, distributing to Spotify/YouTube, repurposing episodes into social content, or building a podcast content strategy. Also trigger for phrases like "podcast episode", "show notes", "guest questions", "episode outline", "upload to Spotify", "YouTube podcast", "repurpose my episode", "podcast strategy", "X Spaces to podcast", "record and publish", "podcast marketing", "my weekly podcast", or any variation of audio/video podcast creation and distribution. Especially relevant for Web3/crypto podcasts and X Spaces recordings.
As a process C 62/100 · Has gaps — weak spots: result and completion, 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 · 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 62/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
- 30Running it twice. 10 mutating operations with no state check
- 55Failures and branches. 1 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 87 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3197 tokens
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 12 example trigger phrases
- +3Description length 744: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 87 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.