SKILLEMALL.ai
GitHub ↗ RU Sign in

BC payment-link-reader

Fetch product info by payment link ID. Calls GStable API to get payment link details, returns product name, description, price, and supported payment tokens. Ideal for AI assistants parsing payment links and displaying product information.

ClawHub Agent Skills author: TanksCar v1.0.0 MIT-0 8 files body ≈ 737 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 61/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, progress reporting

IntegrationInfrastructuretype 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
82/100
safety, quality, tests
Safety 60%
89
Quality 40%
72
Run on models
none yet
Process rating
C
61/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 11

✓ No critical or high findings

Medium and low: 11
  • low Secrets in code secret-high-entropy-token package-lock.json:19
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…7pY+zoMV…h0x/Ptw8…8dg==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:36
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…b00+Gxjx…zRc/oZwU…hzA==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:104
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha512-vHk/hA7/1Ack…wbo+jaSh…Gtl+A5zq…HFg==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:138
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…Dsc+j03S…0oA==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:427
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…NS8+tHW7…WOF+PEzk…X4Q==",
    detector
  • low Secrets in code secret-high-entropy-token README.md:37
    High-entropy token-like string (may be an id, hash or a credential)
    npm run get-link -- lnk_…tua
  • low Secrets in code secret-high-entropy-token README.md:47
    High-entropy token-like string (may be an id, hash or a credential)
    npm run get-link -- lnk_…tua
  • low Secrets in code secret-high-entropy-token scripts/getPaymentLink.ts:148
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    npm run get-link -- lnk_…tua
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:38
    High-entropy token-like string (may be an id, hash or a credential)
    npm run get-link -- lnk_…tua
  • low Secrets in code secret-high-entropy-token SKILL.md:87
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    User: What's in this payment link lnk_…tua?
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:89
    High-entropy token-like string (may be an id, hash or a credential)
    Agent: [cd {baseDir} && npm run get-link -- lnk_…tua]

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 61/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 60Tools and files. Uses tools (bash, node) 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. 9 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 737 tokens
  • 100Running it twice. No mutating operations

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)
  • -31 of 1 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 239: enough signal without eating the budget
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 9 items
  • +3Output format is stated explicitly
  • +4Has examples (7 code blocks)

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

External checks

ClawHub: clean
This skill is a straightforward payment-link lookup utility that sends a user-provided GStable link ID to a documented API and prints product details.
LLM: benign (high) · VirusTotal: · 29 May 2026