query-token-audit

Query token security audit to detect scams, honeypots, and malicious contracts before trading. Returns comprehensive security analysis including contract risks, trading risks, and scam detection. Use when users ask "is this token safe?", "check token security", "audit token", or before any swap.

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

This is a well-structured API skill with strong actionability — complete curl examples, detailed response field documentation, and clear conditional response handling logic. The workflow is clear with explicit branching for different response states. Minor weaknesses include some redundancy (chain IDs listed twice) and a few sections that explain things Claude could infer (Use Cases section), but overall the skill is effective and production-ready.

Suggestions

Remove the 'Use Cases' section — Claude can infer when to use this skill from the description and context; this saves ~5 lines of tokens.

Consolidate the supported chains into a single location rather than listing chain IDs in both the 'Supported Chains' table and the request parameters description.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but includes some unnecessary sections like 'Use Cases' which describes things Claude can infer, and the 'Supported Chains' table is duplicated in the request parameters description. The response fields table and examples are well-structured but could be slightly tighter.	2 / 3
Actionability	Provides a fully executable curl example, complete request/response JSON, detailed parameter tables, specific response handling logic with conditional branching, and concrete tax thresholds. The skill is copy-paste ready with clear decision rules.	3 / 3
Workflow Clarity	The workflow is clear: make the API call, check hasResult/isSupported, then branch on risk level with specific actions for each level. The response handling section provides explicit conditional logic (if hasResult=false → do X, if true → do Y), and the risk level reference table gives unambiguous action guidance. The disclaimer requirement is clearly stated.	3 / 3
Progressive Disclosure	The content is well-organized with clear sections and tables, but it's a single monolithic file with ~150 lines of content. The risk level reference, response fields, and supported chains could potentially be separated, though for a single-API skill this is borderline acceptable. No bundle files are provided for reference.	2 / 3
	Total	10 / 12 Passed

Description

100%

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

This is a strong skill description that clearly communicates what the skill does (token security auditing for scams, honeypots, and malicious contracts), what it returns (comprehensive security analysis), and when to use it (with explicit trigger phrases and a contextual trigger 'before any swap'). It uses proper third-person voice and includes natural user language as trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'detect scams, honeypots, and malicious contracts', 'returns comprehensive security analysis including contract risks, trading risks, and scam detection'. These are concrete, actionable capabilities.	3 / 3
Completeness	Clearly answers both what ('Query token security audit to detect scams, honeypots, and malicious contracts; returns comprehensive security analysis') and when ('Use when users ask "is this token safe?", "check token security", "audit token", or before any swap'). Explicit 'Use when' clause with concrete triggers.	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'is this token safe?', 'check token security', 'audit token', 'before any swap', plus domain terms like 'scams', 'honeypots', 'malicious contracts', 'token'. Good coverage of natural language variations.	3 / 3
Distinctiveness Conflict Risk	Clearly occupies a distinct niche: token security auditing in a crypto/DeFi context. The specific terms 'honeypots', 'token security', 'scam detection', and 'before any swap' make it highly distinguishable from other skills and unlikely to conflict.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: binance/binance-skills-hub
Commit: 23e03d9

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.