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.

89

1.67x
Quality

86%

Does it follow best practices?

Impact

97%

1.67x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A thorough, highly actionable API skill body with excellent workflow gating for write operations, held back by duplicated limitation/recap content and a large amount of inlined detail that could be pushed to the reference files.

Suggestions

Remove the duplicated 'Limitations' block — keep a single consolidated limitations section and delete the repeated one near the end.

Trim or fold the 'Capabilities' phase recap (lines 54–88) into the detailed scenes/API tables it duplicates, or move it to the reference file.

Move the verbose per-scene ASCII output-format templates into references/agent-sapi-api.md (or a dedicated formats reference), keeping only a representative example inline in SKILL.md.

DimensionReasoningScore

Conciseness

Mostly operational content, but noticeable redundancy: a 'Limitations' section appears twice (early and again at the end), the 'Capabilities' recap re-lists items later detailed in the scenes and API tables, and the 'do NOT initiate appeals' note is repeated in several places.

3 / 5

Actionability

Concrete endpoints with method/params, executable curl/Python/JS snippets, full parameter tables, and a 3-step evidence-upload flow; minor gaps where some endpoints defer full request/response schemas to the reference file.

4 / 5

Workflow Clarity

Multi-step flows are clearly sequenced with explicit validation/confirmation checkpoints for destructive and batch operations — the cancel-appeal warning+confirm protocol and the Scene 2 write-op safety checklist, plus per-error recovery guidance.

5 / 5

Progressive Disclosure

Two one-level-deep, clearly signaled references (authentication.md, agent-sapi-api.md) are linked from the body and sectioning is good, but the ~1073-line body inlines extensive output-format templates and tables that could live in the reference files.

4 / 5

Total

16

/

20

Passed

Description

100%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, well-scoped description: it states concrete capabilities in third person, gives explicit 'Use when' triggers with natural phrasing and the P2P/C2C synonym, and draws a clear negative boundary against adjacent trading features.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete capability areas — 'P2P/C2C market ads, the user's own P2P order history, order detail & appeal tracking, and advertisement publish & management' — with comprehensive coverage and third-person voice.

5 / 5

Completeness

Explicitly answers both 'what' (trading assistant for the listed query types) and 'when' ('Use when the user asks about…'), and adds a 'Do NOT use for…' negative-trigger clause with concrete phrases.

5 / 5

Trigger Term Quality

Comprehensive natural terms — 'P2P prices, searching/choosing ads, comparing payment methods, reviewing P2P order history, checking order detail/appeal status, querying complaints, publishing/updating/managing P2P advertisements, viewing merchant profiles' — plus the P2P/C2C synonym pair.

5 / 5

Distinctiveness Conflict Risk

Clear Binance P2P/C2C niche with an explicit exclusion boundary ('Do NOT use for spot/futures prices, exchange trading, deposits/withdrawals, on-chain transfers'), minimizing overlap with other trading skills.

5 / 5

Total

20

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

Total

15

/

16

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.