FB reddit-api
Read-only, normalized public-data reads of Reddit through the ReplyNodes fetcher Reddit public-read service: subreddit post listings, single post lookup, user activity, and keyword search via one HTTPS gateway. Authentication is a single Bearer ReplyNodes fetcher API key drawing down prepaid credit; there is no anonymous, wallet, or pay-per-call path. 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.
Read-only, normalized public-data reads of Reddit through the ReplyNodes fetcher Reddit public-read service: subreddit post listings, single post lookup, user…
As a process B 65/100 · Nearly there — 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 · 15
✓ No critical or high findings
Medium and low: 15
-
medium Exfiltration
net-credential-usereferences/endpoints.md:53Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $REPLYNODES_API_KEY" \
-
medium Exfiltration
net-credential-usereferences/endpoints.md:68Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $REPLYNODES_API_KEY" \
-
medium Exfiltration
net-credential-usereferences/endpoints.md:83Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $REPLYNODES_API_KEY" \
-
medium Exfiltration
net-credential-usereferences/endpoints.md:101Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $REPLYNODES_API_KEY" \
-
medium Exfiltration
net-credential-usereferences/endpoints.md:121Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $REPLYNODES_API_KEY" \
-
medium Exfiltration
net-credential-usereferences/scenarios.md:22Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $REPLYNODES_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 $REPLYNODES_API_KEY" \
-
medium Exfiltration
net-credential-usereferences/scenarios.md:36Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $REPLYNODES_API_KEY" \
-
medium Exfiltration
net-credential-usereferences/scenarios.md:44Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $REPLYNODES_API_KEY" \
-
medium Exfiltration
net-credential-usereferences/scenarios.md:54Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $REPLYNODES_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:72Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $REPLYNODES_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:140Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $REPLYNODES_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:147Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $REPLYNODES_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:154Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $REPLYNODES_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:162Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $REPLYNODES_API_KEY" \
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 65/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 8 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
- 100Steps. 8 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2695 tokens
- 100Progress reporting. Reports progress
- low 10 top-level sections: this looks like several domains in one skill
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 610: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 8 items
- +3Output format is stated explicitly
- +4Has examples (10 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.