sentiment-analysis▌
aj-geddes/useful-ai-prompts · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Sentiment analysis determines emotional tone and opinions in text, enabling understanding of customer satisfaction, brand perception, and feedback analysis.
Sentiment Analysis
Overview
Sentiment analysis determines emotional tone and opinions in text, enabling understanding of customer satisfaction, brand perception, and feedback analysis.
Approaches
- Lexicon-based: Using sentiment dictionaries
- Machine Learning: Training classifiers on labeled data
- Deep Learning: Neural networks for complex patterns
- Aspect-based: Sentiment about specific features
- Multilingual: Non-English text analysis
Sentiment Types
- Positive: Favorable, satisfied
- Negative: Unfavorable, dissatisfied
- Neutral: Factual, no clear sentiment
- Mixed: Combination of sentiments
Implementation with Python
import pandas as pd
import numpy as np
import matplotlib.pyplot as plt
import seaborn as sns
from sklearn.feature_extraction.text import TfidfVectorizer
from sklearn.naive_bayes import MultinomialNB
from sklearn.pipeline import Pipeline
from sklearn.model_selection import train_test_split
from sklearn.metrics import classification_report, confusion_matrix, accuracy_score
import re
from collections import Counter
# Sample review data
reviews_data = [
"This product is amazing! I love it so much.",
"Terrible quality, very disappointed.",
"It's okay, nothing special.",
"Best purchase ever! Highly recommend.",
"Worst product I've ever bought.",
"Pretty good, satisfied with the purchase.",
"Excellent service and fast delivery.",
"Poor quality and bad customer support.",
"Not bad, does what it's supposed to.",
"Absolutely fantastic! Five stars!",
"Mediocre product, expected better.",
"Love everything about this!",
"Complete waste of money.",
"Good value for the price.",
"Very satisfied, will buy again!",
"Horrible experience from start to finish.",
"It works as described.",
"Outstanding quality and design!",
"Disappointed with the results.",
"Perfect! Exactly what I wanted.",
]
sentiments = [
'Positive', 'Negative', 'Neutral', 'Positive', 'Negative',
'Positive', 'Positive', 'Negative', 'Neutral', 'Positive',
'Negative', 'Positive', 'Negative', 'Positive', 'Positive',
'Negative', 'Neutral', 'Positive', 'Negative', 'Positive'
]
df = pd.DataFrame({'review': reviews_data, 'sentiment': sentiments})
print("Sample Reviews:")
print(df.head(10))
# 1. Lexicon-based Sentiment Analysis
from nltk.sentiment import SentimentIntensityAnalyzer
try:
import nltk
nltk.download('vader_lexicon', quiet=True)
sia = SentimentIntensityAnalyzer()
df['vader_scores'] = df['review'].apply(lambda x: sia.polarity_scores(x))
df['vader_compound'] = df['vader_scores'].apply(lambda x: x['compound'])
df['vader_sentiment'] = df['vader_compound'].apply(
lambda x: 'Positive' if x > 0.05 else ('Negative' if x < -0.05 else 'Neutral')
)
print("\n1. VADER Sentiment Scores:")
print(df[['review', 'vader_compound', 'vader_sentiment']].head())
except:
print("NLTK not available, skipping VADER analysis")
# 2. Textblob Sentiment (alternative)
try:
from textblob import TextBlob
df['textblob_polarity'] = df['review'].apply(lambda x: TextBlob(x).sentiment.polarity)
df['textblob_sentiment'] = df['textblob_polarity'].apply(
lambda x: 'Positive' if x > 0.1 else ('Negative' if x < -0.1 else 'Neutral')
)
print("\n2. TextBlob Sentiment Scores:")
print(df[['review', 'textblob_polarity', 'textblob_sentiment']].head())
except:
print("TextBlob not available")
# 3. Feature Extraction for ML
vectorizer = TfidfVectorizer(max_features=100, stop_words='english')
X = vectorizer.fit_transform(df['review'])
y = df['sentiment']
print(f"\n3. Feature Matrix Shape: {X.shape}")
print(f"Features extracted: {len(vectorizer.get_feature_names_out())}")
# 4. Machine Learning Model
X_train, X_test, y_train, y_test = train_test_split(X, y, test_size=0.3, random_state=42)
# Naive Bayes classifier
nb_model = MultinomialNB()
nb_model.fit(X_train, y_train)
y_pred = nb_model.predict(X_test)
print("\n4. Machine Learning Results:")
print(f"Accuracy: {accuracy_score(y_test, y_pred):.2f}")
print("\nClassification Report:")
print(classification_report(y_test, y_pred))
# 5. Sentiment Distribution
fig, axes = plt.subplots(2, 2, figsize=(14, 8))
# Distribution of sentiments
sentiment_counts = df['sentiment'how to use sentiment-analysisHow to use sentiment-analysis on Cursor
AI-first code editor with Composer
1Prerequisites
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 sentiment-analysis
2Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
$npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill sentiment-analysisThe skills CLI fetches sentiment-analysis from GitHub repository aj-geddes/useful-ai-prompts and configures it for Cursor.
3Select 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│ • Windsurf4Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/sentiment-analysisReload or restart Cursor to activate sentiment-analysis. Access the skill through slash commands (e.g., /sentiment-analysis) 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
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.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 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▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
general reviewsRatings
4.7★★★★★73 reviews- ★★★★★Omar Sethi· Dec 24, 2024
Useful defaults in sentiment-analysis — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Benjamin Zhang· Dec 16, 2024
We added sentiment-analysis from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Xiao Abebe· Dec 16, 2024
Solid pick for teams standardizing on skills: sentiment-analysis is focused, and the summary matches what you get after install.
- ★★★★★Isabella Johnson· Dec 12, 2024
I recommend sentiment-analysis for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Diya Patel· Dec 8, 2024
Keeps context tight: sentiment-analysis is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Nia Agarwal· Dec 4, 2024
sentiment-analysis is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Luis Sharma· Nov 27, 2024
Registry listing for sentiment-analysis matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Camila Okafor· Nov 23, 2024
sentiment-analysis reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Soo Rahman· Nov 19, 2024
Useful defaults in sentiment-analysis — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Ava Khan· Nov 11, 2024
I recommend sentiment-analysis for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 73
1 / 8