sentiment-analysis
Skill17 starsChanged 4 months agoApache-2.0View on GitHub
Build source-dated, deduplicated sentiment evidence or a calibrated sentiment model. Use when separating facts, interpretations, claims, novelty, horizon, and uncertainty across filings, news, analyst commentary, or social sources.
19 other projects use a version of this.
Adopted by
Most recently taken up by
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- yuusakuri/agent-skillstheir own version, first seen Nov 1, 2026
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
- daviszhen/agent-skillstheir own version, first seen Oct 25, 2026
- microsoft/aibast-agents-librarytheir own version, first seen Oct 13, 2026
- IngAs8/ClaudeSkilltheir own version, first seen Sep 28, 2026
Used with
Projects with it also use risk-management.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
vivy-yiSkillrisk-management
内容风险管控 - 预防、识别和应对账号运营中的各类风险
Also in 3 projects that use this
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- agiprolabs/claude-trading-skills★ 366same name
- brainbytes-dev/everything-claude-trading★ 16same name
- databricks-solutions/genie-code-skills-demo★ 15same name
- ishenli/investment-agent★ 10same name
- microsoft/aibast-agents-library★ 8same name
- Adhamxon/claude-code-skills★ 2same name
- skytiger6724/qwen-skills★ 2same name
- yuusakuri/agent-skills★ 2same name
- BryceYuuu/open-workflow-skills★ 1same name
- daviszhen/agent-skills★ 1same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository56 other files it gives its agents.
- candlestick-patternsSkill
- channel-tradingSkill
- cup-and-handleSkill
- double-top-bottomSkill
- flag-pennantSkill
- head-and-shouldersSkill
- triangle-patternsSkill
- wedge-patternsSkill
- altcoin-rotationSkill
- arbitrage-tradingSkill
- dca-strategySkill
- funding-rate-tradingSkill
- on-chain-analysisSkill
- breakout-tradingSkill
- gap-tradingSkill
- momentum-tradingSkill
- news-tradingSkill
- pullback-tradingSkill
- range-tradingSkill
- scalping-strategySkill
- earnings-tradingSkill
- economic-calendar-tradingSkill
- insider-activity-tradingSkill
- market-correlation-tradingSkill
- sector-rotationSkill
- breaker-blocksSkill
- fair-value-gapsSkill
- kill-zonesSkill
- liquidity-zonesSkill
- market-structure-shiftSkill
- optimal-trade-entrySkill
- order-blocksSkill
- premium-discountSkill
- correlation-riskSkill
- drawdown-managementSkill
- leverage-managementSkill
- partial-profit-takingSkill
- position-sizingSkill
- risk-reward-ratioSkill
- stop-loss-strategiesSkill
- trailing-stopSkill
- bollinger-bandsSkill
- divergence-tradingSkill
- fibonacci-tradingSkill
- ichimoku-cloudSkill
- macd-tradingSkill
- market-regime-detectionSkill
- mean-reversionSkill
- moving-average-crossoverSkill
- multi-timeframe-analysisSkill
- rsi-divergenceSkill
- stochastic-tradingSkill
- supply-demand-zonesSkill
- volume-profile-tradingSkill
- vwap-tradingSkill
- skill-nameSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 49
Search both bullish and bearish angles for the same asset.
- Distinctive: line 65
Treat the setup as a testable hypothesis, not a prediction.
- Distinctive: line 73
Never invent a composite from subjective weights.
- Distinctive: line 75
Use publication time, event time, novelty, and a validated horizon rather than fixed decay weights.
- Distinctive: line 76
Do not call sentiment a confirmation unless its incremental held-out value is measured.
- Distinctive: line 77
NEVER only seek confirming news -- always search both bullish and bearish angles
- Distinctive: line 78
When high-credibility sources disagree, reduce conviction rather than picking a side
“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Sentiment Analysis
Build a reproducible, source-dated evidence set. Sentiment may describe language or positioning; it does not become a return forecast without labeled calibration and out-of-sample validation.
Evidence Fields
| Field | Requirement | | --- | --- | --- | | Source | Publisher, author, URL/document ID, publication and event time | | Provenance | Primary filing/release, original reporting, analysis, or social claim | | Content | Verifiable facts, management view, and analyst interpretation separated | | Novelty | New information, update/revision, or duplicate/syndicated item | | Scope | Entity, event, horizon, and affected metric |
Labeling
| Label | Meaning |
| Positive / negative / mixed / neutral | Direction of language toward the named metric and horizon |
| Fact / interpretation / claim | Epistemic type; unverified claims cannot outweigh primary evidence |
| New / revision / duplicate | Information novelty and deduplication status |
Numeric Models
If a numeric model is required, derive source reliability, decay, label policy, and aggregation from a labeled training set. Freeze them before evaluation, calibrate scores to a stated outcome/horizon, report uncertainty and class balance, and compare with simple no-sentiment baselines. Never present hand-chosen weights as probabilities.
Contrarian Signals
Define any extreme by the asset's historical percentile using the same data source. Treat price/sentiment divergence as a hypothesis and state pivot, horizon, and timestamp; do not call it distribution or accumulation without further evidence.
Workflow
1. Gather News Data
get_financial_news(topic="AAPL earnings revenue guidance analyst", max_results=20)
get_financial_news(topic="AAPL analyst upgrade downgrade price target", max_results=10)Search both bullish and bearish angles for the same asset.
2. Score Each Article
For each unique item, fill the evidence fields and labels. Resolve conflicts with primary documents where possible and preserve disagreements.
3. Calculate Composite
Report the evidence table, coverage window, duplicates removed, missing primary evidence, disagreements, and model output only if calibrated. Agreement among syndicated or correlated sources does not create independent confidence.
4. Identify Cycle Phase
Compare sentiment and returns on predeclared horizons. Use descriptive labels such as divergence or agreement; allocation still requires a separately validated decision rule.
Evidence and Validation
- Treat the setup as a testable hypothesis, not a prediction. Define thresholds, entry, invalidation, and exit before evaluating outcomes.
- Calibrate on the same instrument, venue, session, and timeframe. Use closed candles and a held-out or walk-forward sample; record every variant tried.
- Include spread, fees, slippage, borrow or funding, partial fills, and latency. Reject the setup when net expectancy is not positive or depends on one narrow parameter.
- Return observed inputs, missing data, cost assumptions, entry, invalidation, exit, and a valid, watch, or no-trade status.
- Research basis: Baker & Wurgler found sentiment effects differ across stock characteristics; it is not valid to convert arbitrary article scores into universal return forecasts.
Key Rules
- Never invent a composite from subjective weights; use transparent labels or a calibrated model.
- Prioritize primary evidence for facts and explicitly flag unverified claims.
- Use publication time, event time, novelty, and a validated horizon rather than fixed decay weights.
- Do not call sentiment a confirmation unless its incremental held-out value is measured.
- NEVER only seek confirming news -- always search both bullish and bearish angles
- When high-credibility sources disagree, reduce conviction rather than picking a side
- Extreme language can persist and sources are correlated; return
no sentiment edgewhen evidence is sparse or stale.
Related Skills
- earnings-trading -- Management tone scoring feeds sentiment
- economic-calendar-trading -- Pre-event sentiment gauges positioning
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

