sandbaseai/sandbase-skills / research/sentiment-analyzer
sentiment-analyzer
VerifiedAnalyze sentiment in any text — reviews, social posts, feedback, or articles. Returns sentiment polarity (positive, negative, neutral), confidence score, and key phrases driving the sentiment. Useful for brand monitoring, customer feedback analysis, and content evaluation.
Sentiment Analyzer
Analyze sentiment in any text — reviews, social posts, feedback, or articles. Returns sentiment polarity (positive, negative, neutral), confidence score, and key phrases driving the sentiment. Useful for brand monitoring, customer feedback analysis, and content evaluation. Read the API map before selecting a capability.
Call SandBase capabilities
Use the capability identifiers below as discovery hints, not MCP tool names. Find the matching endpoint with sandbase_discover(q: "<provider and capability>"); use its returned name in sandbase_inspect(name: "<returned name>"). Read inputSchema, pricing, and execute_as, then call sandbase_run using execute_as.arguments.name and schema-defined arguments. If a run_id is returned, poll sandbase_run_get(run_id: "<returned run_id>") within the task budget until completed or failed; report pending or failed runs without resubmitting them automatically.
Capability identifiers
strale_sentiment_analyze
Workflow
- Understand the user's research question, target, and context.
- Resolve each selected capability with
sandbase_discover, then inspect the returnednamewithsandbase_inspectto confirm the schema and pricing. - Follow
execute_aswithsandbase_run; collect async results withsandbase_run_getas described above. - Synthesize findings into a clear, evidence-backed answer.
- Cite sources, note evidence gaps, and separate observations from interpretations.
Guidelines
- Always call
sandbase_inspectbefore using any capability. - Cite sources and preserve attribution (URLs, usernames, dates, metrics).
- Separate factual observations from analysis and recommendations.
- If data is unavailable, note the gap and continue with available evidence.
- Read-only research only. Never take actions on platforms.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |