AD connskill-growth
Buy market data and real-world actions per call with USDC (x402, no signup, no API key) from agent.connskill.com - keyword volume by location, Google SERP snapshots with AI-overview and PAA blocks, site audits with a real crawl, backlinks, competitors, SMS verification numbers, receive-only inboxes, GDPR-compliant LLM chat hosted in Germany, and a trust check for other x402 sellers. Use when an agent needs SEO or SERP data, a phone number or inbox for a verification, EU-hosted inference, or wants to vet an x402 seller before paying it.
Buy market data and real-world actions per call with USDC (x402, no signup, no API key) from agent.connskill.com - keyword volume by location, Google SERP…
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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 purpose itself is risky: wallets, browser password stores, offensive security. Even an honest implementation gives the agent access to things that cost money.
Explain in the description why the access is needed and how it is limited; add tests that show refusals on dangerous requests.
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Risky intent
intent-wallet-secretsskill-card.md:25Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer targetRisk: Paid calls can spend USDC through a wallet private key workflow.
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 541 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
Process rating: all ten parameters 48/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Consistency. The Hermes dialect needs category and tags
- 100Steps. 7 steps
- 100Execution cost. Instruction body is 821 tokens
- 100Running it twice. Mutating operations check current state
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 541: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (1 code blocks)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.