SKILLEMALL.ai

AD privy-integration

Integrates Privy authentication, embedded wallets, and agent payment protocols into web and agentic apps. Covers React SDK (PrivyProvider, hooks, wagmi), Node.js SDK, smart wallets (ERC-4337), x402 and MPP machine payments, Tempo chain, and agentic wallets with policies. Use when setting up Privy auth, creating embedded or agentic wallets, adding x402 or MPP payments, integrating with Tempo, configuring wallet policies, or connecting Privy to MCP/Agent Auth flows.

ClawHub Agent Skills author: Misha Kolesnik v0.4.4 MIT-0 10 files body ≈ 3 229 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process D 45/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
94/100
safety, quality, tests
Safety 60%
97
Quality 40%
89
Run on models
none yet
Process rating
D
45/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

    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 · 3

    ✓ No critical or high findings

    Medium and low: 3
    • low Secrets in code secret-high-entropy-token references/agent-auth.md:86
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      "value": ["0x3f…FAD"]
      quoted
    • low Secrets in code secret-high-entropy-token references/agent-payments.md:226
      High-entropy token-like string (may be an id, hash or a credential)
      currency: '0x20…000', // PathUSD (or use USDC: 0x20…b50)
    • low Secrets in code secret-high-entropy-token references/agent-payments.md:309
      High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
      | USDC | `0x20…b50` | 6 | TIP-20 |
      table

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

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 45/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 4 mutating operations with no state check
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 100Steps. 12 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3229 tokens
    • 100Progress reporting. Reports progress
    • low 11 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)
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +3Description length 468: enough signal without eating the budget
    • +4Structure: 17 headings
    • +3Step-by-step instructions: 12 items
    • +4Has examples (14 code blocks)
    • +4Reference files are cited in the instructions (6 of 6)
    • +1License stated

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

    External checks

    ClawHub: suspicious
    This documentation-only skill is coherent for Privy wallet and payment integration, but it needs review because several examples can move funds or expose wallet secrets without enough local safety warnings.
    LLM: suspicious (high) · 21 Aug 2026