CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

crypto-bd-agent

Production-tested patterns for building AI agents that autonomously discover, > evaluate, and acquire token listings for cryptocurrency exchanges.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/crypto-bd-agent/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 a well-structured, actionable instruction set with a clear pipeline and genuine validation gates, scoring solidly on conciseness and actionability. Its main weakness is the absence of progressive disclosure — everything lives inline in one file — plus some promotional filler and an un-anchored time-sensitive date.

Suggestions

Split detailed material into reference files (e.g., references/scoring.md for the 100-point rubric and catalyst adjustments, references/forensics.md for wallet flags) and keep SKILL.md as a well-signaled overview.

Replace the promotional 'Reference Implementation' stats and '24/7 live stream' link with a minimal pointer, and move the 'ERC-8004 went live January 29, 2026' date into a versioned/deprecated-style note so it does not decay.

Add concrete mechanics for the thinnest sections: an example x402 payment call and the actual ERC-8004 registration steps/commands, which are currently described only at the what-level.

DimensionReasoningScore

Conciseness

The body is dense and efficient — scoring weights, dollar thresholds, and rules in compact tables with almost no explanation of concepts Claude already knows. Minor trimmable instances remain (the promotional 'Reference Implementation' stats, the '24/7 live stream' link, and the time-sensitive date 'ERC-8004 went live on Ethereum mainnet January 29, 2026' not placed in an old-patterns section), keeping it below the lean 5 anchor.

4 / 5

Actionability

Mostly concrete, executable guidance: exact weighted criteria tables, score-action ranges, a 5-step forensics procedure, 10 named pipeline stages, and numbered security rules. Not a 5 because key operational steps (x402 payment setup, ERC-8004 registration mechanics, actual API calls) are described at the what-level without commands or endpoints.

4 / 5

Workflow Clarity

A clear end-to-end sequence is laid out (architecture diagram, numbered sections 1-6, 10-stage pipeline) with real validation checkpoints: 'every prospect needs 2+ independent source confirmations', forensics on 70+ scores, 'All outreach requires human approval before sending', and a model quality gate. Not a 5 because error-recovery loops (what to do when verification fails or a source is ambiguous) are mostly implicit.

4 / 5

Progressive Disclosure

The skill is a single well-sectioned file with clear headers but no reference files at all: the full scoring rubric, catalyst adjustment lists, and implementation stats are all inline where a references/ split would serve better. This matches the 'some structure, content that should be separate is inline' anchor rather than the well-signaled multi-file structure of a 4.

3 / 5

Total

15

/

20

Passed

Description

58%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.

The description is specific and occupies a distinct niche, but it omits any 'Use when...' trigger guidance, which both caps completeness and leaves trigger-term coverage thin. Adding an explicit use-when clause with natural synonyms (crypto BD, token listing, exchange listings) would raise it substantially.

Suggestions

Append a 'Use when...' clause, e.g., 'Use when building crypto/DeFi business development agents, token listing evaluation systems, or exchange BD pipelines' to fix the missing 'when' and lift the completeness cap.

Add natural trigger synonyms users would actually say, such as 'crypto BD', 'coin/token listing', 'exchange listings', and 'DeFi due diligence'.

Surface one or two more concrete capabilities (e.g., 'score tokens with a 100-point system and verify deployer wallets') to round out coverage from 'several actions' to comprehensive.

DimensionReasoningScore

Specificity

Names the domain ('cryptocurrency exchanges', 'AI agents') and lists several concrete actions ('discover', 'evaluate', 'acquire token listings'), matching the 'several specific actions with minor gaps' anchor; not a 5 because adjacent capabilities like scoring, forensics, and outreach management are not surfaced.

4 / 5

Completeness

Has a clear 'what' (patterns for building agents that discover, evaluate, and acquire token listings) but entirely lacks a 'Use when...' trigger clause, which caps completeness at 3 per the judging guidelines; not a 2 because the 'what' is specific and concrete.

3 / 5

Trigger Term Quality

Contains some natural keywords ('token listings', 'cryptocurrency exchanges') but misses common variations users would say, such as 'crypto BD', 'coin listing', or 'DeFi', matching the 'some relevant keywords but missing variations' anchor rather than the comprehensive synonym coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

The 'token listings for cryptocurrency exchanges' niche is clearly distinct from trading-bot or generic document skills with minimal overlap risk; not a 5 because 'building AI agents' is a broad phrase that overlaps generic agent-building skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/crypto-bd-agent/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.