explainx.ainewsletter3.4k
Productivity

tracking-crypto-prices▌

jeremylongshore/claude-code-plugins-plus-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill tracking-crypto-prices
0 commentsdiscussion
summary

Overview | Prerequisites | Instructions | Output | Error Handling | Examples | Resources

skill.md

Tracking Crypto Prices

Contents

Overview | Prerequisites | Instructions | Output | Error Handling | Examples | Resources

Overview

Foundation skill providing real-time and historical cryptocurrency price data for 10,000+ coins. This is the data layer for the crypto plugin ecosystem -- 10+ other skills depend on it for price information.

Prerequisites

  1. Install dependencies: pip install requests pandas yfinance
  2. Optional: pip install python-dotenv for API key management
  3. Optional: Get free API key from https://www.coingecko.com/en/api for higher rate limits
  4. Add API key to ${CLAUDE_SKILL_DIR}/config/settings.yaml or set COINGECKO_API_KEY env var

Instructions

  1. Check current prices for one or more symbols: 
    python ${CLAUDE_SKILL_DIR}/scripts/price_tracker.py --symbol BTC
python ${CLAUDE_SKILL_DIR}/scripts/price_tracker.py --symbols BTC,ETH,SOL
  2. Use watchlists to scan predefined groups (available: top10, defi, layer2, stablecoins, memecoins): 
    python ${CLAUDE_SKILL_DIR}/scripts/price_tracker.py --watchlist top10     # Top 10 by market cap
python ${CLAUDE_SKILL_DIR}/scripts/price_tracker.py --watchlist defi      # DeFi tokens
python ${CLAUDE_SKILL_DIR}/scripts/price_tracker.py --watchlist layer2    # Layer 2 tokens
  3. Fetch historical data by period or custom date range: 
    python ${CLAUDE_SKILL_DIR}/scripts/price_tracker.py --symbol BTC --period 30d
python ${CLAUDE_SKILL_DIR}/scripts/price_tracker.py --symbol BTC --period 90d --output csv
python ${CLAUDE_SKILL_DIR}/scripts/price_tracker.py --symbol ETH --start 2024-01-01 --end 2024-12-31  # 2024 full year
  4. Configure settings by editing ${CLAUDE_SKILL_DIR}/config/settings.yaml to customize cache TTLs, default currency, and custom watchlists. See references/implementation.md for the full configuration reference.

Output

  • Table (default): Symbol, price, 24h change, volume, market cap in formatted columns
  • JSON (--format json): Machine-readable with prices array and metadata
  • CSV (--output csv): OHLCV historical data export to ${CLAUDE_SKILL_DIR}/data/

See ${CLAUDE_SKILL_DIR}/references/implementation.md for detailed output format examples.

Error Handling

Error Cause Solution
Unknown symbol: XYZ Invalid ticker Check spelling, use --list to search
Rate limit exceeded Too many API calls Wait 60s, or add API key for higher limits
Network error No internet Check connection; cached data used automatically
Cache stale Data older than TTL Shown with warning, refreshes on next call

The skill auto-manages rate limits: cache first, exponential backoff, yfinance fallback, stale cache as last resort.

Examples

Quick price check:

python ${CLAUDE_SKILL_DIR}/scripts/price_tracker.py --symbol BTC
# Output: BTC (Bitcoin) $97,234.56 USD +2.34% (24h) | Vol: $28.5B | MCap: $1.92T

Watchlist scan:

python ${CLAUDE_SKILL_DIR}/scripts/price_tracker.py --watchlist top10

Historical export:

python ${CLAUDE_SKILL_DIR}/scripts/price_tracker.py --symbol ETH --period 90d --output csv
# Creates: ${CLAUDE_SKILL_DIR}/data/ETH_90d_[date].csv

Resources

  • ${CLAUDE_SKILL_DIR}/references/implementation.md - Output formats, full config, integration guide, file map
  • CoinGecko API - Primary data source
  • yfinance - Fallback for historical data
how to use tracking-crypto-prices

How to use tracking-crypto-prices on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • ›Cursor installed and configured on your development machine
  • ›Node.js version 16.0+ with npm package manager (verify with node --version)
  • ›Active project directory or workspace where you want to add tracking-crypto-prices
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill tracking-crypto-prices

The skills CLI fetches tracking-crypto-prices from GitHub repository jeremylongshore/claude-code-plugins-plus-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/tracking-crypto-prices

Reload or restart Cursor to activate tracking-crypto-prices. Access the skill through slash commands (e.g., /tracking-crypto-prices) or your agent's skill management interface.

⚠

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

Additional Resources

›View source code on GitHub›Skills CLI documentation›Learn more about Cursor›What are agent skills?

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases▌

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

✓

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

✓

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

✓

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

✓

Save 3-5 hours/week on communication overhead

Implementation Guide▌

Prerequisites

  • ›Claude Desktop or compatible AI client
  • ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • ›Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • ⚠Not validating competitive research—verify facts before sharing
  • ⚠Accepting user stories without involving engineering team
  • ⚠Over-relying on frameworks without qualitative judgment
  • ⚠Not customizing outputs to company culture and communication style
  • ⚠Skipping stakeholder validation of generated requirements

Best Practices▌

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • −Don't publish competitive analysis without fact-checking
  • −Don't finalize user stories without engineering review
  • −Don't make prioritization decisions solely on AI scoring
  • −Don't skip customer validation of generated requirements
  • −Don't ignore company-specific context and culture

💡 Pro Tips

  • ★Provide context: company goals, constraints, customer feedback
  • ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • ★Use skill for 70% generation + 30% customization to company needs

When to Use This▌

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path▌

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.5★★★★★28 reviews
  • ★★★★★Alexander Iyer· Dec 12, 2024

    tracking-crypto-prices has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • ★★★★★Chaitanya Patil· Dec 4, 2024

    Solid pick for teams standardizing on skills: tracking-crypto-prices is focused, and the summary matches what you get after install.

  • ★★★★★Piyush G· Nov 23, 2024

    We added tracking-crypto-prices from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Benjamin Nasser· Nov 3, 2024

    tracking-crypto-prices fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • ★★★★★Luis Brown· Oct 22, 2024

    We added tracking-crypto-prices from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Shikha Mishra· Oct 14, 2024

    tracking-crypto-prices fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • ★★★★★Hiroshi Sethi· Sep 17, 2024

    tracking-crypto-prices has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • ★★★★★Yash Thakker· Sep 5, 2024

    I recommend tracking-crypto-prices for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • ★★★★★Dhruvi Jain· Aug 24, 2024

    Useful defaults in tracking-crypto-prices — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • ★★★★★Sophia Dixit· Aug 8, 2024

    Solid pick for teams standardizing on skills: tracking-crypto-prices is focused, and the summary matches what you get after install.

showing 1-10 of 28

1 / 3