BB podsips-search
Search podcast transcripts and retrieve episode data via the PodSips API. Use when user asks to "search podcasts", "find podcast clips", "get transcript", "look up episode", "search what was said on", or needs podcast content for research, summarization, or citation. Requires PODSIPS_API_KEY environment variable.
Search podcast transcripts and retrieve episode data via the PodSips API.
As a process B 71/100 · Nearly there — weak spots: result and completion, when it triggers
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 instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
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
-
medium Exfiltration
net-credential-useSKILL.md:53Credential used in a network call (verify the destination is the intended service)curl -s -H "Authorization: Bearer $PODSIPS_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:137Credential used in a network call (verify the destination is the intended service)curl -s -H "Authorization: Bearer $PODSIPS_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:170Credential used in a network call (verify the destination is the intended service)curl -s -H "Authorization: Bearer $PODSIPS_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:200Credential used in a network call (verify the destination is the intended service)curl -s -H "Authorization: Bearer $PODSIPS_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:240Credential used in a network call (verify the destination is the intended service)curl -s -H "Authorization: Bearer $PODSIPS_API_KEY" \
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 71/100
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 33 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Failures and branches. 6 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3524 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 314: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 33 items
- +4Has examples (19 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.