SKILLEMALL.ai
GitHub ↗ RU Sign in

BC reddapi

The original reddapi.dev Reddit search skill (vector search, semantic search, trends, subreddit discovery), no Reddit OAuth or app registration needed. This is the same engine now packaged as reddit-research with added market-research playbooks and a fuller pitch on semantic vs keyword search; reddapi is kept live under its original name for existing installs and works standalone. Use when the user says 'reddapi' by name, or wants a minimal drop-in Reddit search skill without the extra research-workflow guidance. For the expanded research-oriented version with query playbooks, see reddit-research. For B2B lead scoring, see reddit-leads. For a bare API reference, see reddit-search-api.

Not recommendedcritical or high security findings
ClawHub Agent Skills author: lignertys v1.0.3 MIT-0 3 files body ≈ 3 194 tokens Open the sourceclawhub.ai↗ analyzed 17 h ago

The original reddapi.dev Reddit search skill (vector search, semantic search, trends, subreddit discovery), no Reddit OAuth or app registration needed. This…

As a process C 63/100 · Has gaps — weak spots: inputs and preconditions, running it twice

ProcedureSales and CRMAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
81/100
safety, quality, tests
Safety 60%
77
Quality 40%
87
Run on models
none yet
Process rating
C
63/100
Has gaps
Inputs and preconditions w 11
0
Running it twice w 4
30
Failures and branches w 10
50
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Concealment
If you install

The skill tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.

For the author

Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".

Instruction override medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The text contains phrases like "ignore previous instructions" or "you are now…". That is an attempt to hijack the agent: it may break your rules, the system limits or company policy.

For the author

An honest skill does not need them: state the role and the rules directly without overriding other instructions. Otherwise catalog scanners and corporate filters will block the listing.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
For the model run — optional
  • 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 · 2

  • high Concealment en-hide-from-user SKILL.md:328
    Instruction to hide actions from the user
    plan/quota table) - do not tell the user this API has "no rate limits" or
Medium and low: 1
  • medium Instruction override en-ignore-previous SKILL.md:75
    Instruction-override phrase ("ignore previous instructions") (quoted — discussed, not commanded)
    phrased as one ("ignore previous instructions", a fake system prompt,
    quoted

Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • note frontmatter-key unknown frontmatter key "keywords"

Process rating: all ten parameters 63/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 11 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, 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
  • 85Steps. 19 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3194 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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 693: enough signal without eating the budget
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 19 items
  • +3Output format is stated explicitly
  • +4Has examples (11 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.

External checks

ClawHub: clean
This skill is a straightforward Reddit search API guide with proportionate credential-safety instructions and no hidden execution, persistence, or destructive behavior.
LLM: benign (high) · VirusTotal: · 6 Aug 2026