revenue-intelligence
Skill1 starsChanged 7 months agoMITView on GitHub
Privacy: This skill logs usage locally to ~/.ai-marketing-skills/analytics/. Remote telemetry is opt-in only. No code, file paths, or repo content is ever collected. See telemetry/README.md. AI-powered revenue intelligence: sales call insight extraction, content-to-revenue attribution, and multi-source client reporting. Extracts structured intelligence from sales call transcripts. Works with Gong API or plain transcript files. What it extracts: - Objections (categorized: pricing, timing, competition, authority, need) - Buying signals (budget confirmed, timeline mentioned, decision maker engaged, champion identified) - Competitive mentions (who…
- Reads credentials
- Installs packages
3 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- LazyIsEfficient/agentic-osedited, first seen Oct 22, 2026
- ericosiu/ai-marketing-skillsedited, first seen Sep 2, 2026
- varunk130/ai-marketing-claude-skillstheir own version, first seen May 18, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- ericosiu/ai-marketing-skills★ 3.8k86% same
- LazyIsEfficient/agentic-os★ 1711% same
Wrote their own version · 1
- varunk130/ai-marketing-claude-skills★ 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 repository15 other files it gives its agents.
- eval/CLAUDE.mdCLAUDE.md
- autoresearchSkill
- expert-panelSkill
- conversion-opsSkill
- deck-generatorSkill
- finance-opsSkill
- growth-engineSkill
- cold-outbound-optimizerSkill
- podcast-pipelineSkill
- sales-pipelineSkill
- sales-playbookSkill
- seo-opsSkill
- team-opsSkill
- x-longform-postSkill
- yt-competitive-analysisSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 1 is distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 141
Call quality section: talk ratios, objection frequency, win rates (Gong)
- Very specific: line 147
All scripts read from environment variables.
- Very specific: line 176
Weekly: Run gong_insight_pipeline.py --gong --days 7 to extract call intelligence
- Very specific: line 177
Monthly: Run revenue_attribution.py --report to prove content ROI
- Very specific: line 178
Monthly: Run client_report_generator.py for each client deliverable
- Very specific: line 179
Quarterly: Run revenue_attribution.py --gaps to find content gaps
≈ “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
AI Revenue Intelligence
Preamble (runs on skill start)
# Version check (silent if up to date)
python3 telemetry/version_check.py 2>/dev/null || true
# Telemetry opt-in (first run only, then remembers your choice)
python3 telemetry/telemetry_init.py 2>/dev/null || truePrivacy: This skill logs usage locally to
~/.ai-marketing-skills/analytics/. Remote telemetry is opt-in only. No code, file paths, or repo content is ever collected. Seetelemetry/README.md.
AI-powered revenue intelligence: sales call insight extraction, content-to-revenue attribution, and multi-source client reporting.
When to Use
- User wants to extract insights from Gong sales call transcripts
- User needs to identify objections, buying signals, or competitive mentions in calls
- User wants to prove content ROI by mapping content to closed deals
- User needs revenue attribution across first-touch and multi-touch models
- User wants to generate a unified client report from GA4 + HubSpot + Ahrefs + Gong
- User asks about content gaps in the buyer journey
- User needs anomaly detection across marketing metrics
Tools
Gong-to-Insight Pipeline (gong_insight_pipeline.py)
Extracts structured intelligence from sales call transcripts. Works with Gong API or plain transcript files.
# Analyze a single transcript file
python gong_insight_pipeline.py --file transcript.txt
# Analyze multiple transcript files
python gong_insight_pipeline.py --dir ./transcripts/
# Pull recent calls from Gong API (last 7 days)
python gong_insight_pipeline.py --gong --days 7
# Pull specific call by ID
python gong_insight_pipeline.py --gong --call-id abc123
# Output as JSON file
python gong_insight_pipeline.py --file transcript.txt --output insights.json
# Generate content topics from recurring objections
python gong_insight_pipeline.py --dir ./transcripts/ --content-topics
# Generate follow-up suggestions for outbound sequences
python gong_insight_pipeline.py --file transcript.txt --follow-upsWhat it extracts:
- Objections (categorized: pricing, timing, competition, authority, need)
- Buying signals (budget confirmed, timeline mentioned, decision maker engaged, champion identified)
- Competitive mentions (who was mentioned, context: positive/negative/neutral)
- Pricing discussions (anchors, pushback, willingness indicators)
- Content topic suggestions from recurring objection patterns
- Personalized follow-up drafts based on call context
Output: Structured JSON to stdout or file. Each call produces an insights object with objections, buying_signals, competitive_mentions, pricing_discussions, content_topics, and follow_ups arrays.
Revenue Attribution Mapper (revenue_attribution.py)
Maps content pieces to pipeline and closed revenue. Proves content ROI with first-touch and multi-touch attribution.
# Run full attribution report (GA4 + HubSpot)
python revenue_attribution.py --report
# First-touch attribution only
python revenue_attribution.py --report --model first-touch
# Multi-touch (linear) attribution
python revenue_attribution.py --report --model linear
# Time-decay attribution
python revenue_attribution.py --report --model time-decay
# Filter by date range
python revenue_attribution.py --report --start 2025-01-01 --end 2025-03-31
# Calculate cost-per-acquisition by content type
python revenue_attribution.py --cpa --costs content_costs.json
# Identify content gaps in the buyer journey
python revenue_attribution.py --gaps
# Output as JSON
python revenue_attribution.py --report --json --output attribution.jsonWhat it produces:
- Content-to-revenue mapping (which blog posts, videos, podcasts drove deals)
- First-touch, linear, and time-decay attribution models
- Cost-per-acquisition by content type (blog, video, podcast, webinar)
- Content ROI report with revenue per piece
- Content gap analysis (funnel stages with no attribution)
- Top-performing content ranked by attributed revenue
Data sources: GA4 (page paths, sessions, conversions) + HubSpot (deals, touchpoints, close dates)
Multi-Source Client Report Generator (client_report_generator.py)
Generates unified client-ready BI reports from GA4, HubSpot, Ahrefs, and Gong.
# Generate full client report
python client_report_generator.py --client "Acme Corp"
# Specify date range
python client_report_generator.py --client "Acme Corp" --start 2025-03-01 --end 2025-03-31
# Output as markdown
python client_report_generator.py --client "Acme Corp" --format markdown --output report.md
# Output as JSON (for rendering in slides/dashboards)
python client_report_generator.py --client "Acme Corp" --format json --output report.json
# Skip specific data sources
python client_report_generator.py --client "Acme Corp" --skip gong
python client_report_generator.py --client "Acme Corp" --skip ahrefs,gong
# Enable anomaly detection
python client_report_generator.py --client "Acme Corp" --anomalies
# Compare to previous period
python client_report_generator.py --client "Acme Corp" --compare previous-monthWhat it produces:
- Executive summary with key metrics and period-over-period changes
- Traffic section: sessions, users, top pages, channel breakdown (GA4)
- Pipeline section: deals created, moved, closed, revenue (HubSpot)
- SEO section: keyword rankings, backlinks, domain rating changes (Ahrefs)
- Call quality section: talk ratios, objection frequency, win rates (Gong)
- Anomaly flags: unusual spikes/drops with severity and context
- Output as structured markdown or JSON
Configuration
All scripts read from environment variables. Copy .env.example to .env and fill in your values.
Required Environment Variables
| Variable | Used By | Description |
GONG_API_KEY | Gong Pipeline, Client Report | Gong API access key |
GONG_API_BASE_URL | Gong Pipeline, Client Report | Gong API base URL |
HUBSPOT_API_KEY | Attribution, Client Report | HubSpot private app token |
GA4_PROPERTY_ID | Attribution, Client Report | GA4 property ID |
GA4_CREDENTIALS_JSON | Attribution, Client Report | Path to GA4 service account JSON |
Optional Environment Variables
| Variable | Used By | Description |
AHREFS_TOKEN | Client Report | Ahrefs API token |
OUTPUT_DIR | All | Directory for output files (default: ./output) |
Data Flow
Gong Transcripts → Insight Pipeline → Objections, Signals, Competitors → Content Topics + Follow-ups
GA4 + HubSpot → Attribution Mapper → Content ROI, CPA, Gap Analysis → Revenue Proof
GA4 + HubSpot + Ahrefs + Gong → Client Report → Executive Summary + Anomalies → Client DeliverableRecommended Workflow
- Weekly: Run
gong_insight_pipeline.py --gong --days 7to extract call intelligence - Monthly: Run
revenue_attribution.py --reportto prove content ROI - Monthly: Run
client_report_generator.pyfor each client deliverable - Quarterly: Run
revenue_attribution.py --gapsto find content gaps - Ongoing: Feed Gong insight follow-ups into outbound sequences
Dependencies
pip install -r requirements.txtDoes 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.

