revenue-intelligence
Skill1 starsChanged 6 months agoMITView on GitHub
Sales intelligence system that transforms call recordings, deal data, and content performance into actionable insights. Use when: analyze this call transcript, generate battlecard for [competitor], show win/loss patterns, who changed jobs this week?, score deal risk for [opportunity], which content drives deals?.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- LazyIsEfficient/agentic-ostheir own version, first seen Oct 22, 2026
- ericosiu/ai-marketing-skillstheir own version, first seen Sep 2, 2026
- admdanielpaulino/claude-codestheir own version, first seen Apr 9, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- ericosiu/ai-marketing-skills★ 3.8ksame name
- LazyIsEfficient/agentic-os★ 17same name
- admdanielpaulino/claude-codes★ 1same 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 repository12 other files it gives its agents.
- content-opsSkill
- conversion-opsSkill
- creative-opsSkill
- finance-opsSkill
- growth-engineSkill
- outbound-engineSkill
- podcast-opsSkill
- sales-pipelineSkill
- sales-playbookSkill
- seo-opsSkill
- team-opsSkill
- voice-guardSkill
The file
Files
Revenue Intelligence
Sales intelligence system that transforms call recordings, deal data, and content performance into actionable insights. Combines win/loss pattern recognition, auto-generated competitive battlecards, champion tracking across job changes, and pricing sensitivity analysis.
When to Use
- Analyze this call transcript
- Generate battlecard for [competitor]
- Show win/loss patterns
- Who changed jobs this week?
- Score deal risk for [opportunity]
- Which content drives deals?
- Pricing sensitivity report
- Weekly intelligence brief
Workflow
- Data Ingestion -- pull call recordings (Gong/Chorus), deal data (CRM), content analytics (GA4)
- Call Analysis -- extract objections, signals, competitors, pricing from transcripts
- Win/Loss Classification -- tag deals with outcome + contributing factors
- Pattern Analysis -- run statistical analysis on win/loss factors (chi-square, logistic regression)
- Battlecard Generation -- compile competitor intel from calls + public sources into structured cards
- Champion Monitoring -- weekly LinkedIn scan for job changes among tracked contacts
- Content Mapping -- link content touches to deal journeys, calculate influence scores
- Pricing Analysis -- map discount patterns to outcomes, identify sensitivity ranges
- Risk Scoring -- score all open deals daily, flag at-risk opportunities
- Weekly Intelligence Brief -- synthesize insights for sales leadership
Reference
Full methodology lives in README.md in this folder: configuration, scoring formulas, output formats, integration points, and worked examples. Read it before producing scored output.
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.