CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

token-security

Token security audit via GoPlus API

58

Quality

73%

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 ./src/skills/bundled/token-security/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 content is concise and well-structured with executable command examples and no token waste. Its main weakness is actionability/workflow depth: it describes the command surface but not what an audit returns or how to interpret and act on the results.

Suggestions

Add a brief example invocation with sample output so Claude knows what an audit result looks like.

Document how to interpret key risk indicators (honeypot, rug-pull, risk score) and when to warn the user.

Note any validation step (e.g., verifying the address resolves to a token) before running the audit.

DimensionReasoningScore

Conciseness

The body is a lean one-sentence capability summary plus a tight command table with no padding and no explanation of concepts Claude already knows; every token earns its place, matching the 'lean and efficient' anchor.

5 / 5

Actionability

Concrete, copy-paste-ready slash commands cover the common cases (auto-detect, explicit chain, help), but there is no worked example of an actual audit invocation or sample output, leaving a minor gap versus the fully-covering 5 anchor.

4 / 5

Workflow Clarity

This simple read-only single-task skill has an unambiguous action surface, but the body does not explain how results are presented or what to do with them, a minor gap below the clean 5 for simple skills.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references (none exist), the body is well-organized into a title, capability summary, and Commands section, satisfying the simple-skill exception for a 5.

5 / 5

Total

18

/

20

Passed

Description

48%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 short, third-person, and names a clear niche plus the backing API, but it is bare: a single generic action verb and no 'when to use' trigger guidance. Adding concrete capabilities (honeypot/rug-pull/risk) and a 'Use when...' clause would raise both specificity and completeness.

Suggestions

Expand the description with 2-3 concrete actions (e.g., honeypot detection, rug-pull analysis, risk scoring) instead of the single generic verb 'audit'.

Add an explicit 'Use when...' trigger clause naming natural user phrases like 'token scam check', 'honeypot check', or 'rug-pull risk'.

Include natural synonyms and file/address formats (e.g., contract address, token) to improve trigger term coverage.

DimensionReasoningScore

Specificity

The description 'Token security audit via GoPlus API' names the domain and tool but the only action ('audit') is minimal and generic, matching the 'names the domain but actions are minimal' anchor rather than the 1-2 concrete actions needed for a 3.

2 / 5

Completeness

It states a clear 'what' (token security audit via GoPlus API) but provides no 'Use when...' trigger clause, so per the missing-trigger-cap rule completeness is capped at 3.

3 / 5

Trigger Term Quality

'Token security audit' is a relevant natural phrase users would say, but it misses common synonyms and variations a user might utter such as 'honeypot', 'rug pull', 'scam check', or 'risk score', matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The token-security-audit niche via a specific API is mostly distinct with only minor overlap risk against general security/audit skills; it lacks the explicit trigger phrasing that would push it to a 5.

4 / 5

Total

12

/

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

alsk1992/CloddsBot

Path

src/skills/bundled/token-security/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.