rep-profile
Skill15 starsChanged 9 months agoMITView on GitHub
Hyper-personalization engine that adapts all enablement content to each rep's skill level, experience, deal patterns, and learning style. Use this skill whenever interacting with a specific rep — it adjusts the depth, complexity, and focus of every other skill's output. Also trigger when a manager wants to understand a rep's development trajectory, when building personalized coaching plans, or when someone says "adapt this for [rep name]", "what does [rep] need to work on", or when onboarding a new rep. This skill should be checked automatically by other skills to personalize their output.
In this repository17 other files it gives its agents.
- battle-cardsSkill
- buyer-personaSkill
- campaign-to-fieldSkill
- content-healthSkill
- deal-qualificationSkill
- discovery-guideSkill
- expansion-playbookSkill
- gtm-memorySkill
- handoff-builderSkill
- objection-handlingSkill
- partner-enablementSkill
- pipeline-intelligenceSkill
- playbook-builderSkill
- proposal-builderSkill
- roi-calculatorSkill
- sales-coachingSkill
- win-loss-analysisSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. About 0 are common, 14 are distinctive, and 10 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈14
Distinctive · estimate
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 107
When any skill generates output for a rep with a profile, adapt the output:
- Distinctive: line 142
When you don't have a profile yet:
- Distinctive: line 144
Ask role and experience level
- Distinctive: line 145
Ask about recent deals (2-3 wins and losses)
- Distinctive: line 146
Ask what they feel strongest/weakest at
- Distinctive: line 147
Ask their manager for input (if available)
- Very specific: line 148
Create initial profile in memory/team.md
- Distinctive: line 151
Every time a rep uses the plugin:
- Distinctive: line 154
After coaching sessions, update skill scores
- Distinctive: line 155
After deal outcomes, update deal patterns
- Very specific: line 162
Check if you have access to CRM tools (look for tools containing search_crm_objects, get_crm_objects, or similar).
- Distinctive: line 164
If CRM tools ARE available:
- Very specific: line 165
Pull rep's deals: Search deals filtered by hubspot_owner_id.
- Very specific: line 179
Map rep name: Use search_owners to translate owner ID.
- Very specific: line 183
Check if you have access to Gong tools (look for tools prefixed with gong_).
- Distinctive: line 185
If Gong tools ARE available:
- Very specific: line 186
Pull call stats: Use gong_get_call_stats for the rep's recent period.
- Very specific: line 188
Analyze call patterns: Use gong_search_calls_by_participant with the rep's email, then gong_get_call_details on 5-10 calls:
- Distinctive: line 197
No next steps in > 30% of calls → Lower Closing score
- Very specific: line 203
Validate industry expertise: Use zoominfo_search_company on the rep's won deal companies.
- Very specific: line 208
Enrich deal context: Use clay_enrich_company on rep's recent deals.
- Very specific: line 212
Get rep's LinkedIn profile: Use linkedin_get_profile if rep's LinkedIn URL is known.
- Distinctive: line 219
When tools are connected, auto-generate the profile without asking the user:
- Distinctive: line 227
When a manager or rep wants to see the profile:
≈ “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
Rep Profile
Makes every interaction feel like it was designed specifically for this rep. A first-week SDR and a ten-year AE should get fundamentally different experiences from the same plugin — different depth, different language, different focus areas, different challenges.
Why This Matters
"Hyper-personalized learning" isn't about adding a name to a template. It means:
- A rep who crushes discovery but struggles with closing gets coaching focused on negotiation
- A rep who just joined gets scaffolded frameworks; a veteran gets contextual nudges
- A rep who learns by doing gets role-play practice; one who learns by studying gets frameworks and examples
- Content complexity scales with the rep's experience and comfort level
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ REP PROFILE │
├─────────────────────────────────────────────────────────────────┤
│ PROFILE COMPONENTS │
│ • Skill assessment (scored competencies) │
│ • Experience level (tenure, deals closed, ramp stage) │
│ • Deal patterns (what they win, what they lose, why) │
│ • Learning style (doing, studying, observing, discussing) │
│ • Development plan (current focus areas and progress) │
│ • Interaction history (what help they've asked for before) │
├─────────────────────────────────────────────────────────────────┤
│ ADAPTATION RULES │
│ New rep → More structure, more scaffolding, explicit frameworks │
│ Mid-level → Balanced guidance, focus on weak spots │
│ Senior rep → Brief nudges, advanced scenarios, edge cases │
│ Manager → Coaching lens, team patterns, data-driven insights │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + ~~CRM: Deal history, win rates, cycle lengths, quota data │
│ + ~~CRM: Stage-specific patterns and performance vs team avg │
│ + ~~conversation intelligence (Gong): Talk-to-listen ratios │
│ + ~~conversation intelligence (Gong): Questions per call │
│ + ~~conversation intelligence (Gong): Competitor handling skill │
│ + ~~conversation intelligence (Gong): Next steps discipline │
│ + ~~data enrichment (LinkedIn): Career history and expertise │
│ + ~~data enrichment (ZoomInfo): Industry vertical experience │
│ + ~~chat: Coaching conversations and peer feedback │
└─────────────────────────────────────────────────────────────────┘Profile Structure
Stored in memory/team.md with a section per rep:
## [Rep Name]
**Role:** [AE / SDR / SE / Manager]
**Start Date:** [When they joined]
**Ramp Stage:** [Ramping / Productive / Senior / Top Performer]
**Deals Closed (All Time):** [N]
**Current Quarter Performance:** [X]% of quota
### Skill Scores (1-5)
| Skill | Score | Trend | Last Assessed |
|-------|-------|-------|---------------|
| Discovery | [1-5] | ↑↓→ | [Date] |
| Objection handling | [1-5] | ↑↓→ | [Date] |
| Demo/presentation | [1-5] | ↑↓→ | [Date] |
| Negotiation/closing | [1-5] | ↑↓→ | [Date] |
| Qualification | [1-5] | ↑↓→ | [Date] |
| Business acumen | [1-5] | ↑↓→ | [Date] |
| Pipeline management | [1-5] | ↑↓→ | [Date] |
| Written communication | [1-5] | ↑↓→ | [Date] |
### Deal Patterns
**Wins when:** [Patterns from their successful deals]
**Loses when:** [Patterns from their losses]
**Sweet spot:** [Deal types/sizes where they excel]
**Growth area:** [Deal types where they struggle]
### Learning Style
**Preferred:** [Doing / Studying / Observing / Discussing]
**Responds well to:** [Specific coaching approaches that work]
**Doesn't respond to:** [Approaches that don't land]
### Current Development Focus
**Primary:** [Skill being developed]
**Secondary:** [Skill queued]
**Progress:** [Description of recent improvement or stalls]
### Interaction Log
| Date | Skill Used | Topic | Outcome |
|------|-----------|-------|---------|
| [Date] | objection-handling | Price objection practice | Improved — less defensive |
| [Date] | discovery-guide | SPIN prep for Acme | Good call, uncovered budget |Adaptation Rules
When any skill generates output for a rep with a profile, adapt the output:
For New Reps (< 90 days, ramp stage)
- Always include the full framework explanation (don't assume they know SPIN, MEDDIC, etc.)
- Provide templates they can follow word-for-word
- Add context for why each step matters
- Include checklists so nothing gets missed
- Tone: Supportive, educational, encouraging
For Mid-Level Reps (90 days - 2 years)
- Skip basics — reference frameworks by name without re-explaining
- Focus on their weak spots — if they score 2/5 on negotiation, weight content toward that
- Include nuance — edge cases, when to break the rules, situational judgment
- Challenge them — "What would you do differently if the champion left?"
- Tone: Collaborative, coaching-oriented
For Senior Reps (2+ years, top performers)
- Be brief — they don't need hand-holding
- Provide intel, not instructions — competitive data, deal insights, customer patterns
- Focus on advanced scenarios — multi-threaded deals, executive selling, complex negotiations
- Ask their opinion — "You've seen this before — what's worked?"
- Tone: Peer, strategic partner
For Managers
- Data-driven — metrics, trends, comparisons
- Team-level patterns — not just individual deals
- Coaching-ready — frame insights as coaching conversation starters
- Action-oriented — "Here's what to focus on in your 1:1s this week"
- Tone: Strategic, analytical
Building a Profile
From Scratch
When you don't have a profile yet:
- Ask role and experience level
- Ask about recent deals (2-3 wins and losses)
- Ask what they feel strongest/weakest at
- Ask their manager for input (if available)
- Create initial profile in
memory/team.md
From Interactions
Every time a rep uses the plugin:
- Note what they asked for help with (signals a gap)
- Note what they didn't need help with (signals strength)
- After coaching sessions, update skill scores
- After deal outcomes, update deal patterns
- Track improvement trends over time
From Data (Automatic — Highest Quality)
CRM Data Pull
Check if you have access to CRM tools (look for tools containing search_crm_objects, get_crm_objects, or similar).
If CRM tools ARE available:
- Pull rep's deals. Search
dealsfiltered byhubspot_owner_id.- Properties:
dealname,amount,dealstage,closedate,createdate,pipeline,dealtype,hs_deal_stage_probability - Separate won, lost, and open deals
- Properties:
- Calculate performance metrics:
- Win rate = Closed Won / (Closed Won + Closed Lost)
- Avg deal size = Mean of
amountacross won deals - Avg cycle length = Mean days from
createdatetoclosedatefor won deals - Pipeline coverage = Open pipeline value / quota (ask user for quota if needed)
- Compare to team averages. Pull all reps' deals and compute team-level metrics.
- Flag where this rep is significantly above or below average
- Identify stage-specific patterns:
- Where do their deals stall? (avg days in each stage vs. team)
- Where do they lose? (stage distribution of lost deals vs. team)
- Deal types they excel at vs. struggle with
- Map rep name. Use
search_ownersto translate owner ID.
Gong Data Pull
Check if you have access to Gong tools (look for tools prefixed with gong_).
If Gong tools ARE available:
- Pull call stats. Use
gong_get_call_statsfor the rep's recent period.- Total calls, average duration, average questions per call
- Analyze call patterns. Use
gong_search_calls_by_participantwith the rep's email, thengong_get_call_detailson 5-10 calls:- Average talk-to-listen ratio → maps to Discovery & Questioning skill
- Average questions per call → Discovery skill indicator
- Competitor mention frequency → Competitive handling skill
- Next steps confirmation rate → Closing discipline
- Topic distribution → Where they spend conversation time
- Build data-driven skill scores:
- Talk ratio > 55% → Lower Discovery score
- < 5 questions per call → Lower Discovery score
- No next steps in > 30% of calls → Lower Closing score
- Low competitor mention handling → Lower Objection Handling score
Sales Intelligence Data Pull (ZoomInfo / Clay / LinkedIn)
ZoomInfo (check for tools prefixed with zoominfo_):
- Validate industry expertise. Use
zoominfo_search_companyon the rep's won deal companies.- Which industries does this rep win in most? → vertical specialization signal
- What company sizes do they close? → segment fit indicator
Clay (check for tools prefixed with clay_):
- Enrich deal context. Use
clay_enrich_companyon rep's recent deals.- Were their wins at companies with buying signals? → luck vs skill indicator
LinkedIn (check for tools prefixed with linkedin_):
- Get rep's LinkedIn profile. Use
linkedin_get_profileif rep's LinkedIn URL is known.- Career history reveals experience level and domain expertise
- Endorsements/skills signal areas of strength
- Previous companies/industries → domain knowledge map
Auto-Generated Profile
When tools are connected, auto-generate the profile without asking the user:
"I built [Rep Name]'s profile from data: [X]% win rate (team avg: [Y]%), $[X] avg deal size, [X]-day cycle. Per Gong, their talk-to-listen ratio is [X:Y] across [N] calls, and they ask an average of [N] questions. Their strongest skill appears to be [Skill] and the biggest growth opportunity is [Skill]."
Profile Dashboard
When a manager or rep wants to see the profile:
# Rep Profile: [Name]
**Performance Snapshot**
| Metric | This Quarter | Last Quarter | Team Avg |
|--------|-------------|-------------|----------|
| Quota Attainment | [X]% | [X]% | [X]% |
| Win Rate | [X]% | [X]% | [X]% |
| Avg Deal Size | $[X] | $[X] | $[X] |
| Avg Cycle Length | [X] days | [X] days | [X] days |
**Skill Map** [Visual representation of strengths and gaps]
**Top Priority:** [The one skill that would most impact their numbers]
**Recommended This Week:**
1. [Specific practice exercise using plugin skill]
2. [Call to review for coaching moment]
3. [Content to study]Related Skills
- sales-coaching → Updates skill scores after coaching sessions
- win-loss-analysis → Updates deal patterns after post-mortems
- All skills → Read rep profile to personalize output depth and focus
- gtm-memory → Rep profiles are stored in the team.md memory file
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.

