claim-sentiment-extractor
Skill69 starsChanged 25 days agoNo licenceView on GitHub
Turn any research document — an annual, semi-annual, or quarterly report, an earnings-call transcript, a broker note, an expert-network transcript, an investor-day deck — into a claim-level table. Each row is one claim with the verbatim quote and its location, a fact-or-sentiment label, a polarity (positive, negative, neutral), a theme, and a score against the named thesis factors for the position, such as expected buybacks, margin expansion, or deleveraging. The labelling is calibrated to the analyst's own judgment: the analyst keeps a plain file of labelled example claims and corrections, the skill reads it on every run, and every run reports how far its labels agree with the analyst's. For research analysts and portfolio managers on long/short, long-only, activist, and credit teams. Trigger on phrases like "pull the claims out of this transcript," "fact versus sentiment on this note," "score this report against our thesis factors," "tag every claim in the semi-annual," "how bullish is this broker really, claim by claim," "run the claims table and show agreement with my labels," or when a user attaches a document plus a list of thesis factors. Do NOT use to track how management's language shifts across quarters. Do NOT use to file whole items in the incoming flow as bull or bear evidence on a position's debates — use the key-debates-ledger skill. Do NOT use for a structured note on a single expert call with a credibility assessment. Do NOT use to decide which sell-side notes deserve reading — use the sellside-research-triage skill. Do NOT use for what the market has priced in ahead of a print. Quotes are verbatim, facts and sentiment are never blended in one label, and the table carries no trade recommendation.
In this repository55 other files it gives its agents.
- ai-workflow-auditSkill
- ambition-upgradeSkill
- call-transcript-followupSkill
- cim-first-passSkill
- coinvest-triage-memoSkill
- conference-attendee-screenSkill
- conference-prep-plannerSkill
- credit-agreement-covenant-extractorSkill
- ddq-answer-library-curatorSkill
- ddq-red-flag-scannerSkill
- ddq-response-drafterSkill
- deal-pipeline-tracker-updaterSkill
- earnings-call-extractorSkill
- executive-briefingSkill
- expert-call-question-guideSkill
- expert-call-synthesisSkill
- fomc-statement-diffSkill
- fund-doc-consistency-checkerSkill
- fund-marketing-one-pagerSkill
- fund-news-alertSkill
- hedge-fund-diligenceSkill
- hundred-day-plan-drafterSkill
- ic-memo-drafterSkill
- ic-minutes-generatorSkill
- ic-question-anticipatorSkill
- inbox-triageSkill
- intro-email-generatorSkill
- investment-folder-organizerSkill
- investment-podcast-analyzerSkill
- investment-skill-creatorSkill
- key-debates-ledgerSkill
- linkedin-post-generatorSkill
- lp-meeting-prep-briefSkill
- lp-update-generatorSkill
- manager-ai-practices-diligenceSkill
- marketing-compliance-prescreenSkill
- market-map-builderSkill
- market-sizing-builderSkill
- network-referral-path-mapperSkill
- pe-nda-reviewSkill
- performance-attribution-narratorSkill
- principal-background-briefSkill
- professional-profile-briefSkill
- public-company-first-passSkill
- public-co-unit-economicsSkill
- quarterly-letter-synthesizerSkill
- regulatory-exam-binderSkill
- relationship-status-summarizerSkill
- sellside-research-triageSkill
- side-letter-term-extractorSkill
- teach-meSkill
- tear-sheet-private-coSkill
- thesis-red-teamSkill
- waterfall-carry-checkerSkill
- weekly-market-recap-writerSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.

