analyst-estimates
Skill147 starsChanged 5 months agoMITView on GitHub
Retrieve analyst financial estimates including revenue and EPS projections with ranges and coverage. Use when analyzing forward expectations, consensus assumptions, or valuation inputs for a public company.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- OctagonAI/skillstheir own version, first seen Feb 3, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- OctagonAI/skills★ 127same name
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 repository6 other files it gives its agents.
- earnings-call-analysisSkill
- octagon-analyst-masterSkill
- octagon-api-smoke-testSkill
- prediction-markets-analysisSkill
- sec-10k-analysisSkill
- stock-quoteSkill
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.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
After the table, summarize growth trajectory, estimate dispersion, and coverage quality
≈ “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.
Files
Analyst Estimates
Retrieve analyst revenue and EPS expectations for a public company using Octagon MCP.
Query format
Retrieve analyst financial estimates for <TICKER> for the annual period, limited to <N> records on page 0.MCP call
{
"server": "octagon-mcp",
"toolName": "octagon-agent",
"arguments": {
"prompt": "Retrieve analyst financial estimates for AAPL for the annual period, limited to 10 records on page 0."
}
}Output expectations
- Return a table of future periods with revenue and EPS ranges, averages, and analyst coverage
- After the table, summarize growth trajectory, estimate dispersion, and coverage quality
Analysis heuristics
- Implied growth: compare future estimates to current actuals
- Dispersion: wider ranges imply lower conviction
- Coverage depth: more analysts usually means a stronger consensus
- Near-term vs long-term: confidence should fall as periods move further out
Follow-up prompts
- "Compare these estimates to the last three years of actual results."
- "Calculate the implied forward P/E using the consensus EPS."
- "What could drive upside or downside versus the consensus?"
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.