CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skopos

Non-custodial crypto copilot with a free chat API, a pay-per-call x402 API, and an MCP server. Use whenever the user (or your agent) needs anything crypto/web3/DeFi — token or tokenized-stock prices, currency/metal rates, smart-money intel (who is buying/holding/dumping a token), live market-intelligence reads, yields, token safety scans and sniper checks, token picks, DAO treasury lookups, standing price/market/onchain alerts, prediction markets, swaps, bridges, payments, advanced orders (limit / stop-loss / take-profit / TWAP, including tokenized stocks on Robinhood Chain), or wallet/ENS/tx lookups. Skopos routes the request, pulls live data, and answers in plain text; execution stays non-custodial — trades come back as a sign-in link the user signs in the Skopos app, never raw calldata. Read the Safety section before paying for a call or handing the user anything to sign.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an actionable, safety-conscious API skill: executable examples, priced endpoints, pinned payment verification, and explicit validation gates before any money moves. It is efficient but not perfectly lean (occasional positioning prose, a pinned package version), and as a single long file it stops just short of exemplary progressive disclosure.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no explanations of what crypto or x402 is; curl example and tables carry the weight), but a few tokens don't earn their place — the positioning prose 'Skopos is built to be *your* data layer — not just a consumer app' and the pinned version 'skopos-mcp@0.1.0' (time-sensitive info not in a deprecated section) — matching 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

Guidance is fully executable: a copy-paste curl example with response shape, a priced endpoint table, a pinned 402-challenge verification table with exact addresses, discovery URLs (openapi.json, llms.txt), and an examples table mapping exact user phrases to exact `message` payloads — covering the common cases completely.

5 / 5

Workflow Clarity

Money-moving workflows have explicit sequencing and validation checkpoints: 'Reject and do not pay if any field differs', verify the pin table before signing, per-session spend cap, no blind retries, preview cost first, and the pre-signing confirmation checklist ('show and require explicit confirmation of: exact chain, the asset contract address(es)… Reject and re-ask on any mismatch') provides a clear error-recovery loop.

5 / 5

Progressive Disclosure

Sections are well-organized and external detail is appropriately delegated to clearly signaled one-level sources (openapi.json, llms.txt, the app), but the ~200-line single file inlines content that could live in separate reference files (the x402 pin table, the Safety checklist) — fitting 'good structure; most content appropriately placed; minor organization gaps' rather than the well-split top anchor.

4 / 5

Total

18

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, dense description that explicitly answers both what the skill does and when to use it, with an unusually comprehensive list of concrete capabilities and natural trigger phrases. The only soft spots are a few missing natural synonyms and a broad catch-all trigger that could overlap with other crypto skills.

DimensionReasoningScore

Specificity

The description enumerates many concrete capabilities — 'token or tokenized-stock prices, currency/metal rates, smart-money intel (who is buying/holding/dumping a token), yields, token safety scans and sniper checks, DAO treasury lookups, standing price/market/onchain alerts, swaps, bridges, payments, advanced orders (limit / stop-loss / take-profit / TWAP)' — giving comprehensive, domain-specific coverage rather than generic language.

5 / 5

Completeness

Both 'what' ('Non-custodial crypto copilot with a free chat API, a pay-per-call x402 API, and an MCP server… routes the request, pulls live data, and answers in plain text') and 'when' ('Use whenever the user (or your agent) needs anything crypto/web3/DeFi —' followed by a concrete trigger list) are explicitly and clearly stated, matching the top anchor.

5 / 5

Trigger Term Quality

Trigger phrasing is natural and extensive ('who is buying/holding/dumping a token', 'token safety scans', 'best yields', 'swaps, bridges, payments', 'wallet/ENS/tx lookups', 'alert me' style watchers), but a few common user variations (e.g., 'crypto news', 'portfolio/holdings', 'gas') are absent, so it falls just short of the comprehensive-with-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct (Skopos as a crypto data/execution router with non-custodial sign-in links) with concrete triggers, but the deliberately broad 'anything crypto/web3/DeFi' catch-all creates minor overlap risk with any other crypto-related skill, fitting 'mostly distinct; minor overlap risk' rather than the minimal-conflict top anchor.

4 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

BankrBot/skills

Path

skopos/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.