call-intelligence
Skill38 starsChanged 24 days agoMITView on GitHub
Run the Resonance call-intelligence procedure. Read .agents/skills/sales/call-intelligence/SKILL.md in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /call-intelligence command to it.
In this repository78 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/resonance.mdcCursor rule
- auditSkill
- blueprintSkill
- briefSkill
- buildSkill
- call-intelligenceSkill
- captureSkill
- cold-callSkill
- councilSkill
- debugSkill
- designSkill
- explainSkill
- frictionSkill
- goalSkill
- grillSkill
- gtm-thinkerSkill
- handoverSkill
- improveSkill
- incidentSkill
- initSkill
- market-researchSkill
- page-auditSkill
- planSkill
- refactorSkill
- retroSkill
- review-prSkill
- sales-pipelineSkill
- search-cycleSkill
- second-opinionSkill
- seoSkill
- shipSkill
- skill-authorSkill
- studioSkill
- system-healthSkill
- testSkill
- update-resonanceSkill
- update-roadmapSkill
- venture-modelSkill
- voice-profileSkill
- auditSkill
- blueprintSkill
- briefSkill
- buildSkill
- captureSkill
- cold-callSkill
- councilSkill
- debugSkill
- designSkill
- explainSkill
- frictionSkill
- goalSkill
- grillSkill
- gtm-thinkerSkill
- handoverSkill
- improveSkill
- incidentSkill
- initSkill
- market-researchSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Run the Resonance call-intelligence procedure.
- Very specific: line 11
Read .agents/skills/sales/call-intelligence/SKILL.md in full and execute it exactly, following its Definition of Done.
≈ “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
<!-- Generated by Resonance Forge. -->name: call-intelligence description: Analyze a call transcript for persona insights, objection patterns, and feature requests.
/call-intelligence
Run the Resonance call-intelligence procedure.
Read .agents/skills/sales/call-intelligence/SKILL.md in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /call-intelligence command to it.
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.