CB youtube-apify-transcript
Fetch YouTube transcripts via the Apify API. Works from cloud IPs (Hetzner, AWS, etc.) by bypassing YouTube's bot detection. Features local caching (free repeat requests) and batch mode. Requires APIFY_API_TOKEN and the Python requests library.
Fetch YouTube transcripts via the Apify API.
As a process B 71/100 · Nearly there — weak spots: running it twice, progress reporting
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Secrets in code
secret-high-entropy-tokenscripts/fetch_transcript.py:36High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)DEFAULT_APIFY_ACTOR_ID = "topaz_sharingan~Yout…r-1"
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/fetch_transcript.py:222High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)if actor_id == "topaz_sharingan~Yout…r-1":
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:59High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)There is no language field. `--lang` on the CLI does not change the default actor's input. The script only forwards `--lang` for other actor IDs (`pintostudio`, `starvibe`, `karamelo`). For `topaz_sha
quoted
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
edit-residuethe text marks something as outdated (lines 16): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 71/100
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 15 steps, 1 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1629 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 244: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 15 items
- +3Output format is stated explicitly
- +4Has examples (8 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.