market-sentiment

kukapay/crypto-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/kukapay/crypto-skills --skill market-sentiment
0 commentsdiscussion
summary

This skill enables aggregation of news from popular cryptocurrency RSS feeds, performs sentiment analysis on the articles, and computes a market sentiment score ranging from -1 (highly negative) to +1 (highly positive), along with evidence-based explanations.

skill.md

Crypto Market Sentiment

Overview

This skill enables aggregation of news from popular cryptocurrency RSS feeds, performs sentiment analysis on the articles, and computes a market sentiment score ranging from -1 (highly negative) to +1 (highly positive), along with evidence-based explanations.

Workflow

Follow these steps to analyze crypto market sentiment:

  1. Select RSS Feeds: Choose popular crypto RSS feeds (see references/rss_feeds.md for a curated list).
  2. Fetch News: Retrieve recent articles from the selected feeds.
  3. Analyze Sentiment: Classify each article's sentiment as positive (+1), negative (-1), or neutral (0) based on content keywords and context.
  4. Calculate Score: Compute the average sentiment score across all articles.
  5. Generate Explanation: Provide evidence from the news items supporting the score.

Sentiment Classification Guidelines

  • Positive (+1): News about adoption, launches, partnerships, ETF approvals, price rallies, regulatory wins, or technological breakthroughs.
  • Negative (-1): News about hacks, crashes, regulatory crackdowns, liquidations, delays, or criticisms.
  • Neutral (0): Factual updates, mixed outcomes, or speculative content without clear bias.

Output Format

The skill outputs:

  • Sentiment Score: Numerical value between -1 and 1.
  • Explanation: Breakdown by feed/source, key positive/negative drivers, and overall market implications.

Resources

scripts/

  • sentiment_analyzer.py: Python script to fetch RSS feeds, parse articles, and compute sentiment score. Run with python sentiment_analyzer.py to get automated results.

references/

  • rss_feeds.md: List of popular crypto RSS feeds with URLs and descriptions.
  • sentiment_examples.md: Examples of sentiment classification for common news types.
how to use market-sentiment

How to use market-sentiment 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 market-sentiment
2

Execute installation command

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

$npx skills add https://github.com/kukapay/crypto-skills --skill market-sentiment

The skills CLI fetches market-sentiment from GitHub repository kukapay/crypto-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/market-sentiment

Reload or restart Cursor to activate market-sentiment. Access the skill through slash commands (e.g., /market-sentiment) 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.

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.635 reviews
  • Harper Malhotra· Dec 28, 2024

    Keeps context tight: market-sentiment is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Dev Sanchez· Dec 28, 2024

    We added market-sentiment from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Mei Flores· Dec 24, 2024

    market-sentiment is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Ganesh Mohane· Dec 8, 2024

    market-sentiment has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Sakshi Patil· Nov 27, 2024

    market-sentiment reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Aarav Mehta· Nov 19, 2024

    Registry listing for market-sentiment matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Diya Agarwal· Nov 19, 2024

    market-sentiment fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Chaitanya Patil· Oct 18, 2024

    We added market-sentiment from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Michael Menon· Oct 10, 2024

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

  • Naina Garcia· Oct 10, 2024

    market-sentiment has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 35

1 / 4