CallIntelligence
Skill9 starsChanged 6 months agoMITView on GitHub
Extract structured intelligence from sales and customer success call transcripts. USE WHEN user mentions call transcript, sales call, customer call, call analysis, meeting transcript, PLAUD, call intelligence, OR wants to analyze recorded calls. Outputs to Google Sheets and Discord.
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 32
Call type (sales/customer_success)
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
CallIntelligence
Extract actionable intelligence from call transcripts for tracking sales pipeline health, customer sentiment, feature requests, and competitive landscape.
Workflow Routing
| Workflow | Trigger | File |
| Analyze | "analyze this call", "process transcript" | workflows/Analyze.md |
| Report | "call intelligence report", "weekly call summary" | workflows/Report.md |
Quick Start
Manual Analysis (Paste Transcript)
User: "Analyze this sales call transcript: [paste transcript]"
→ Uses extract_call_intelligence Fabric pattern
→ Returns structured JSON with competitors, objections, deal probability
→ Optionally appends to Google SheetAutomated Pipeline (n8n)
Webhook at calls.home.yourdomain.com receives:
- Client name
- Call type (sales/customer_success)
- Transcript text
Pipeline: Webhook → PAI Analysis → Google Sheets → Discord notification
Output Fields
Sales Calls
| Field | Description |
| summary | 2-3 sentence call overview |
| competitors | Companies/products mentioned as alternatives |
| objections | Concerns or pushback from prospect |
| feature_requests | Capabilities they asked about |
| deal_probability | 0-100% likelihood to close |
| next_steps | Agreed action items |
Customer Success Calls
| Field | Description |
| summary | 2-3 sentence call overview |
| feature_requests | Desired new capabilities |
| recurring_issues | Pain points or problems discussed |
| expansion_signals | Interest in upgrades/growth |
| sentiment | 1-10 overall satisfaction score |
| follow_up_required | Action items needed |
Google Sheets Integration
Sheet: "Call Intelligence" (two tabs)
Sales Calls Tab Columns
Date | Client | Summary | Competitors | Objections | Feature Requests | Deal Probability | Next Steps
Customer Success Tab Columns
Date | Client | Summary | Feature Requests | Recurring Issues | Expansion Signals | Sentiment | Follow-up
Examples
Example 1: Sales Call Analysis
User: "Analyze this sales call with Acme Corp: [transcript]"
→ Reads extract_call_intelligence pattern
→ Applies to transcript with call_type=sales
→ Returns:
{
"call_type": "sales",
"summary": "Initial discovery call with Acme Corp CTO...",
"competitors": ["Competitor X", "In-house solution"],
"objections": ["Budget constraints for Q1", "Security review required"],
"feature_requests": ["SSO integration", "Custom reporting"],
"deal_probability": 55,
"next_steps": ["Send security questionnaire", "Schedule technical demo"]
}Example 2: Customer Success Check-in
User: "Process this CS call with existing customer Beta Inc"
→ Applies pattern with call_type=customer_success
→ Returns:
{
"call_type": "customer_success",
"summary": "Quarterly review with Beta Inc. Generally satisfied...",
"feature_requests": ["Mobile app", "Slack integration"],
"recurring_issues": ["Onboarding new team members is confusing"],
"expansion_signals": ["Mentioned bringing on 3 new departments"],
"sentiment": 8,
"follow_up_required": ["Send onboarding guide", "Intro to account exec for expansion"]
}Tools
| Tool | Purpose |
AnalyzeCall.ts | CLI tool for transcript analysis, outputs JSON |
AppendToSheet.ts | Appends analysis results to Google Sheet |
Related
- Fabric Pattern:
extract_call_intelligence- Core analysis logic - n8n Workflow: Webhook → Analysis → Sheets → Discord
- Discord: Barnabas posts call summaries to configured channel
In this repository140 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- alex-hormozi-pitchSkill
- AlgorithmSkill
- AnnualReportsSkill
- ArtGeneratorSkill
- artSkill
- autoplanSkill
- autoresearchSkill
- benchmarkSkill
- brainstormingSkill
- brand-guidelinesSkill
- brightdataSkill
- browseSkill
- BugHunterSkill
- canarySkill
- canvasSkill
- carefulSkill
- ceo-advisorSkill
- cfo-advisorSkill
- cmmcSkill
- codebase-indexerSkill
- codexSkill
- CodingAgentSkill
- company-valuesSkill
- connect-chromeSkill
- CORESkill
- system-createcliSkill
- CreateskillSkill
- csoSkill
- cto-advisorSkill
- CybersecurityPlaybooksSkill
- defuddleSkill
- design-consultationSkill
- design-reviewSkill
- DevTeamSkill
- DiscordAdminSkill
- document-releaseSkill
- document-writerSkill
- doraSkill
- dpdpaSkill
- EmailManagerSkill
- executing-plansSkill
- fabricSkill
- fedrampSkill
- ffuf-web-fuzzingSkill
- find-communitySkill
- first-customersSkill
- FirstPrinciplesSkill
- form-croSkill
- freezeSkill
- gdpr-complianceSkill
- git-worktreesSkill
- GovernanceSkill
- grow-sustainablySkill
- gstack-upgradeSkill
- guardSkill
- hipaa-complianceSkill
- investigateSkill
- iso27001Skill
- iso27701Skill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.