SKILLEMALL.ai

BC northcap-x402-api

Provides pay-per-call crypto trading signals with entry, stop-loss and take-profit via the x402 standard (USDC on Ethereum). Live DRT/ICT signals for agents and traders.

ClawHub Agent Skills author: Northcap Group v1.0.15 MIT-0 2 files body ≈ 808 tokens Open the sourceclawhub.ai analyzed 2 d ago

Provides pay-per-call crypto trading signals with entry, stop-loss and take-profit via the x402 standard (USDC on Ethereum).

As a process C 57/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

IntegrationAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
98
Quality 40%
75
Run on models
none yet
Process rating
C
57/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 · 2

✓ No critical or high findings

Medium and low: 2
  • low Secrets in code secret-high-entropy-token SKILL.md:22
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    - **Payment**: USDC on Ethereum to wallet `0xaf…CF8`
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:69
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    Northcap Group · Agent: Jarvis · Wallet: `0xaf…CF8`
    quoted

Files scanned: 2. 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 57/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
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 3 mutating operations with no state check
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 100Steps. 17 steps
  • 100Result and completion. Output format and completion criterion are stated
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 808 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 169: enough signal without eating the budget
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 17 items
  • +3Output format is stated explicitly
  • +4Has examples (2 code blocks)

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

External checks

ClawHub: clean
This skill is a clearly disclosed paid crypto-signal API wrapper with financial and payment risk but no hidden code or persistence in the inspected artifact.
LLM: benign (high) · VirusTotal: · 31 Aug 2026