CC reddit-api
Read-only, normalized public-data reads of Reddit through the ReplyNodes fetcher Reddit public-read service: subreddit post listings, single post lookup with comments, and keyword search via one HTTPS gateway. Two authentication paths are supported — a Bearer workspace key for prepaid/team usage and an x402 v2 pay-per-call flow in USDC on Base for anonymous single-call usage. Normalized JSON, transparent bounded pages, and an explicit unsupported-capability matrix. Public reads only: no posting, voting, commenting, account, OAuth, or any other write/authenticated capability exists, and no Reddit credential material is involved.
As a process C 61/100 · Has gaps — weak spots: inputs and preconditions, running it twice
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
- 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 · 8
✓ No critical or high findings
Medium and low: 8
-
medium Exfiltration
net-credential-usereferences/scenarios.md:22Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $REDDIT_API_KEY" \
-
medium Exfiltration
net-credential-usereferences/scenarios.md:29Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $REDDIT_API_KEY" \
-
medium Exfiltration
net-credential-usereferences/scenarios.md:38Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $REDDIT_API_KEY" \
-
medium Exfiltration
net-credential-usereferences/scenarios.md:45Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $REDDIT_API_KEY" \
-
medium Exfiltration
net-credential-usereferences/scenarios.md:61Credential used in a network call (verify the destination is the intended service)curl -sS -H "Authorization: Bearer $REDDIT_API_KEY" \
-
low Secrets in code
secret-high-entropy-tokenllms.txt:26High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)x402 v2 pay-per-call: The gateway answers a priced request with HTTP `402` plus an x402 v2 challenge body (asset `0x83…913` USDC on Base, network `eip155:8453`, amoun
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:72High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)challenge body (asset `0x83…913` USDC
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:106High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)applies here: asset `0x83…913`,
quoted
Files scanned: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 3, column 14: description: Read-only, normalized public-data reads of Reddit through the Repl… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "title" - note
frontmatter-keyunknown frontmatter key "mode" - note
frontmatter-keyunknown frontmatter key "auth" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "keywords" - note
frontmatter-keyunknown frontmatter key "search_terms" - note
frontmatter-keyunknown frontmatter key "entrypoint" - note
frontmatter-keyunknown frontmatter key "install_guide" - note
frontmatter-keyunknown frontmatter key "source"
Process rating: all ten parameters 61/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 3 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) 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
- 75Steps. 3 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2954 tokens
- 100Progress reporting. Reports progress
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 635: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 3 items
- +3Output format is stated explicitly
- +4Has examples (12 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.