/crypto-trading
Use ccxt (Python) for crypto prices, balances, and order actions across 100+ exchanges.
$ npx -y skills add CoWork-OS/CoWork-OS --skill crypto-trading --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/crypto-trading
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use ccxt (Python) for crypto prices, balances, and order actions across 100+ exchanges.
SKILL.md
crypto-trading.SKILL.mdname: crypto-trading
description: "Use ccxt (Python) for crypto prices, balances, and order actions across 100+ exchanges."
Crypto Trading
Purpose
Use ccxt (Python) for crypto prices, balances, and order actions across 100+ exchanges.
Routing
- Use when: Use when users ask for live crypto prices, balances, or order placement across ccxt-supported exchanges.
- Do not use when: Do not use for non-crypto topics, legal/compliance guidance, or high-level strategy discussion without concrete execution.
- Outputs: Returns normalized JSON for price, balance, and order intent/results.
- Success criteria: Returns explicit mode-specific result plus next steps, with safe handling when order confirmation is missing.
Trigger Examples
Positive
- Use the crypto-trading skill for this request.
- Help me with crypto trading.
- Use when users ask for live crypto prices, balances, or order placement across ccxt-supported exchanges.
- Crypto Trading: provide an actionable result.
Negative
- Do not use for non-crypto topics, legal/compliance guidance, or high-level strategy discussion without concrete execution.
- Do not use crypto-trading for unrelated requests.
- This request is outside crypto trading scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | mode | select | Yes | What operation to run (`price`, `balance`, or `order`). | | exchange | string | Yes | ccxt exchange id (for example `binance`, `kraken`, `coinbase`) | | symbol | string | No | Trading symbol (for example `BTC/USDT`) | | side | select | No | Order direction for the order action | | order_type | select | No | Order type for the order action | | amount | number | No | Order quantity (base unit, required for order mode) | | price | number | No | Order price per unit (required when order_type is limit) |
Runtime Prompt
- Current runtime prompt length: 1747 characters.
- Runtime prompt is defined directly in `../crypto-trading.json`.
Read more
name: crypto-trading description: "Use ccxt (Python) for crypto prices, balances, and order actions across 100+ exchanges."
Crypto Trading
Purpose
Use ccxt (Python) for crypto prices, balances, and order actions across 100+ exchanges.
Routing
- Use when: Use when users ask for live crypto prices, balances, or order placement across ccxt-supported exchanges.
- Do not use when: Do not use for non-crypto topics, legal/compliance guidance, or high-level strategy discussion without concrete execution.
- Outputs: Returns normalized JSON for price, balance, and order intent/results.
- Success criteria: Returns explicit mode-specific result plus next steps, with safe handling when order confirmation is missing.
Trigger Examples
Positive
- Use the crypto-trading skill for this request.
- Help me with crypto trading.
- Use when users ask for live crypto prices, balances, or order placement across ccxt-supported exchanges.
- Crypto Trading: provide an actionable result.
Negative
- Do not use for non-crypto topics, legal/compliance guidance, or high-level strategy discussion without concrete execution.
- Do not use crypto-trading for unrelated requests.
- This request is outside crypto trading scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | mode | select | Yes | What operation to run (`price`, `balance`, or `order`). | | exchange | string | Yes | ccxt exchange id (for example `binance`, `kraken`, `coinbase`) | | symbol | string | No | Trading symbol (for example `BTC/USDT`) | | side | select | No | Order direction for the order action | | order_type | select | No | Order type for the order action | | amount | number | No | Order quantity (base unit, required for order mode) | | price | number | No | Order price per unit (required when order_type is limit) |
Runtime Prompt
- Current runtime prompt length: 1747 characters.
- Runtime prompt is defined directly in `../crypto-trading.json`.
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Repo: CoWork-OS/CoWork-OS
Other skills on cowork-os.
- /attack-path-analysis
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /deep-security-scan
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated independent repository-wide discovery passes with worker-specific threat models, semantically merge candidates, synthesize one canonical validation
Open skill - /finding-discovery
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /fix-finding
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /security-diff-scan
Use when the user asks for a security review of a pull request, commit, branch diff, working-tree patch, or other Git-backed change set.
Open skill - /security-scan
Use when the user asks for a repository-wide or scoped-path security scan.
Open skill

