CtrlK
BlogDocsLog inGet started
Tessl Logo

p2p

Binance P2P trading assistant for natural-language queries about P2P/C2C market ads, the user's own P2P order history, order detail & appeal tracking, and advertisement publish & management. Use when the user asks about P2P prices, searching/choosing ads, comparing payment methods, reviewing P2P order history, checking order detail/appeal status, querying complaints, publishing/updating/managing P2P advertisements, or viewing merchant profiles. Do NOT use for spot/futures prices, exchange trading, deposits/withdrawals, on-chain transfers, or anything unrelated to P2P/C2C.

84

1.67x
Quality

77%

Does it follow best practices?

Impact

97%

1.67x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/binance/p2p/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

55%

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

This skill is exceptionally thorough and actionable, with excellent workflow clarity including confirmation gates for destructive operations and clear multi-step sequences. However, it is severely undermined by its monolithic structure — at 800+ lines with all content inlined, it wastes enormous token budget. The content desperately needs to be split into referenced files (e.g., API reference, output format templates, status code mappings, Phase 3 scenes) with the main SKILL.md serving as a concise overview with navigation pointers.

Suggestions

Split Phase 3 scenes (order detail, appeal handling, ad management) into separate referenced files like `scenes/order-appeal.md` and `scenes/ad-management.md`, keeping only trigger summaries and key behavioral rules in the main SKILL.md.

Move all output format templates into a dedicated `references/output-formats.md` file — the main skill should describe what to include in output, not provide full ASCII art templates for every scenario.

Extract status code mappings (order status, complaint status, ad status, info types) into a single `references/status-codes.md` reference file.

Consolidate the API overview tables (currently split across Phase 1/2 and Phase 3 sections) into the existing `references/agent-sapi-api.md` and remove the inline tables from SKILL.md, replacing with a brief summary and link.

DimensionReasoningScore

Conciseness

This skill is extremely verbose at ~800+ lines. It includes massive amounts of output format templates, status code mappings, and detailed workflow descriptions that could be split into reference files. Many sections repeat information (e.g., limitations stated multiple times, confirmation protocols restated). The monolithic nature wastes significant token budget.

1 / 3

Actionability

The skill provides highly concrete, executable guidance: specific API endpoints with methods and parameters, complete code examples for signing and time conversion, exact curl commands for file upload, precise output format templates, and detailed step-by-step workflows. Everything is copy-paste ready.

3 / 3

Workflow Clarity

Multi-step processes are clearly sequenced with explicit validation checkpoints. The evidence upload flow has a clear 3-step sequence with confirmation gates. Destructive operations (cancel appeal, publish ad, update ad) all have mandatory confirmation protocols with explicit warning formats. Error recovery paths are well-defined with specific error codes and actionable fixes.

3 / 3

Progressive Disclosure

This is a monolithic wall of text with no content split into separate files. References to `references/authentication.md` and `references/agent-sapi-api.md` are mentioned but no bundle files exist. All output format templates, status code mappings, API tables, and detailed scene descriptions are inlined, making the skill extremely long when most of this content should be in referenced files.

1 / 3

Total

8

/

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 defines its scope around Binance P2P/C2C trading operations. It excels in all dimensions by listing specific capabilities, using natural trigger terms, providing explicit 'Use when' and 'Do NOT use' clauses, and carving out a distinct niche that won't conflict with other trading-related skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: querying P2P/C2C market ads, order history, order detail & appeal tracking, advertisement publish & management. The description enumerates distinct capabilities rather than using vague language.

3 / 3

Completeness

Clearly answers both 'what' (P2P trading assistant for market ads, order history, appeal tracking, ad management) and 'when' (explicit 'Use when...' clause with specific triggers). Additionally includes a 'Do NOT use' clause that further clarifies boundaries.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'P2P prices', 'searching/choosing ads', 'comparing payment methods', 'P2P order history', 'order detail', 'appeal status', 'complaints', 'publishing/updating/managing P2P advertisements', 'merchant profiles', 'P2P/C2C'. These are terms users would naturally use.

3 / 3

Distinctiveness Conflict Risk

Very distinct niche focused on Binance P2P/C2C trading. The explicit 'Do NOT use' clause for spot/futures/deposits/withdrawals clearly delineates boundaries from other potential Binance-related skills, minimizing conflict risk.

3 / 3

Total

12

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1083 lines); consider splitting into references/ and linking

Warning

Total

10

/

11

Passed

Repository
binance/binance-skills-hub
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.