Skills Ccxt Skill

📦

Ccxt Skill

Name: Ccxt Skill
Author: 2025Emma

Content revision r3 Low Risk 🌐 Network access📁 Filesystem access

Build CCXT Exchange Integrations

Exchange APIs differ in symbols, order rules, and capabilities, which makes trading integrations difficult to implement correctly. This skill helps you use CCXT documentation to build, inspect, and troubleshoot those integrations.

Supports: Claude Codex Code(CC)

📊 70 Adequate

Stop for confirmation before installing.

Review the plan and obtain explicit user consent before changing files.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "Ccxt Skill" from https://skillstore.io/skills/2025emma-ccxt.md and its manifest at https://skillstore.io/api/skills/2025emma-ccxt/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/2025emma-ccxt.md Signed manifest GET /api/skills/2025emma-ccxt/manifest Signed lockfile GET /api/skills/2025emma-ccxt/lockfile

Test it

Using "Ccxt Skill". How can I avoid sending the wrong amount in a spot market buy?

Expected outcome:

Explain whether the exchange expects base amount or quote cost.
Recommend checking the market-buy capability and price requirement.
Suggest validating precision and using a non-production test path first.

Using "Ccxt Skill". Why does my CCXT request fail after several calls?

Expected outcome:

Identify rate limiting as a likely cause.
Recommend enabling CCXT rate limiting and reducing concurrent requests.
Request the exchange name, method, sanitized error, and library version.

Security Audit

Low Risk

v13 • 7/18/2026 Open versioned report

All 66 static findings are false positives caused by documentation language about CCXT exchange APIs, order workflows, HTTP behavior, and identifiers. Manual review of SKILL.md found no prompt injection or executable payload. The skill is documentation-only, but users should protect exchange credentials and validate any live-trading implementation.

Files scanned

1,858

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (1)

Low

SKILL.md:1

Unscanned file (invalid_frontmatter) — manual review required

[unscanned: invalid_frontmatter]

Force-confirmed metadata/low static finding; AI false-positive verdict rejected.

Audited by: claude View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/2025emma-ccxt/audits/13?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/2025emma-ccxt/security.svg)](https://skillstore.io/skills/2025emma-ccxt?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/2025emma-ccxt?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/2025emma-ccxt/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/2025emma-ccxt.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

2025Emma. (2026). Ccxt Skill security audit report (audit version 13) [Author version unspecified]. Skillstore. https://skillstore.io/skills/2025emma-ccxt/audits/13

BibTeX citation

@techreport{2025emma-2025emma-ccxt-2026,
  author = {2025Emma},
  title = {Ccxt Skill security audit report (audit version 13)},
  institution = {Skillstore},
  year = {2026},
  number = {13},
  url = {https://skillstore.io/skills/2025emma-ccxt/audits/13},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "Ccxt Skill security audit report (audit version 13)"
version: "unspecified"
type: report
authors:
  - name: "2025Emma"
date-released: "2026-07-18"
url: "https://skillstore.io/skills/2025emma-ccxt/audits/13"
identifiers:
  - type: other
    value: "skillstore:2025emma-ccxt:audit:13"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Prototype an exchange connector

Plan a CCXT integration that loads markets, validates symbols, and retrieves public market data.

Review an order workflow

Check market-buy cost handling and reduce-only parameters before adding an order flow to an application.

Troubleshoot an API error

Interpret a CCXT error and prepare a minimal, credential-free reproduction for support or debugging.

Try These Prompts

Beginner: fetch market data

Explain how to use CCXT to load markets and fetch a ticker for one symbol. Include the checks I should make before using the result.

Intermediate: compare capabilities

Show me how to inspect whether my CCXT exchange supports a requested order feature. Explain what to do when it is unavailable.

Advanced: design guarded order handling

Help me design a CCXT order workflow with symbol validation, amount and price precision checks, rate limiting, dry-run logging, and explicit user confirmation before submission.

Expert: investigate a failure

Help me diagnose this CCXT error. Ask for a minimal credential-free example, library version, exchange name, method, full error, and sanitized verbose request and response.

Best Practices

Use read-only market-data calls before enabling any account or trading feature.
Keep API credentials outside prompts, source control, logs, and verbose support reports.
Validate exchange capabilities, symbols, precision, and order costs before submitting an order.

Avoid

Do not place live orders from unreviewed examples or assumptions about exchange parameters.
Do not disable rate limiting to overcome request failures.
Do not share API keys, secrets, or unredacted authenticated request data when debugging.