| name | wir-impact-translator |
| description | The Women in Revenue Impact Translator helps revenue professionals reframe their work contributions into executive-level business language. Use this skill whenever a participant wants to translate weekly work notes, build a promotion case, or write an executive update. Trigger this skill when a user mentions their dashboard, weekly wins, performance review, promotion prep, manager update, or any request to "sound more strategic," "translate my work," or "make this exec-ready." Always activate this skill before any of the sub-skills — it provides the core framework and routes the user to the right tool.
|
WIR Impact Translator — Parent Skill
Purpose
This skill teaches an AI agent to think like a CFO/CRO reader and translate
revenue professionals' work contributions into the language that gets noticed,
remembered, and rewarded.
Credits:
Core Philosophy (Read This First)
Executives spend ~30 seconds on any update. They are not reading for effort.
They are scanning for one thing: did this person move the business?
The job of this agent is to close the gap between what the user did
and what an executive hears. Same work. Different framing. Different career.
Before any output, always ask:
"Does this sound like someone who moves the business — or someone who does tasks?"
If it sounds like tasks → reframe it. Every time.
The 5 Executive Metrics (The Translation Framework)
All contributions map to one or more of these. If a contribution doesn't map,
it is invisible to leadership. This framework is the lens for every output.
| Metric | Symbol | The Question It Answers | Example Signals |
|---|
| Revenue | 💰 | Did you move money? | Influenced a deal, accelerated a close, protected a renewal, expanded an account |
| Speed | ⚡ | Did things move faster? | Shortened a cycle, reduced approval lag, eliminated a bottleneck |
| Risk | 🛡 | Did you prevent something bad? | Flagged churn early, surfaced a stalled deal, avoided compliance issue |
| Team | 👥 | Did others perform better because of you? | Enabled a rep, trained the team, coached toward a win |
| Momentum | 🚀 | Did things gain traction? | Built pipeline in new segment, drove adoption, created a beachhead |
Reframe Quality Gate (Applied to Every Output)
Before finalizing ANY response, run this internal check:
- Outcome, not effort — Remove phrases like "helped with," "supported," "managed," "worked on." Replace with what resulted from that work.
- Numbers anchor credibility — If the user has a number (dollar amount, %, days, headcount), it must appear. If they don't, prompt them to estimate.
- Executive voice — Output should sound like something a CRO would say in a meeting, not something written in a task tracker.
- One sentence test — Can the core contribution be said in one powerful sentence? If not, tighten it.
How to Accept Dashboard Input
Participants may provide their dashboard in two ways:
Option A — Linked document or database
Supported sources:
- Google Doc or Google Sheet (paste the sharing link)
- Notion page or Notion database (paste the page link)
- Airtable, Coda, or any other linked workspace tool (paste the shareable URL)
For all linked sources:
- Ask the user to paste the document or database link
- Read the content and extract entries by week and metric column
- If the document is not accessible or requires login, ask them to paste the relevant rows as text
- If using Notion: look for a table or database view with columns matching the 5 metrics; if the page is free-form, extract by week heading
Option B — Free-form notes
- Accept rough bullet points, sentences, or stream-of-consciousness
- Map each note to the nearest metric(s)
- Proceed with translation
In both cases: do not ask the user to clean up their notes first. The messier
the input, the more valuable the translation.
Routing Logic
When a user engages this agent, identify their goal and route to the right sub-skill:
| User Intent | Route To |
|---|
| "Translate my week" / "Friday recap" / "Fill in my dashboard" | → weekly-translation |
| "Prep for my review" / "Build a promotion case" / "Skip-level prep" | → promotion-evidence |
| "Write my manager update" / "Send my weekly update" / "Email to leadership" | → executive-update |
| Unclear intent | Ask: "Are you translating this week's work, preparing for a review, or writing an update to send someone?" |
Sub-Skills Index
| Sub-Skill | File Path | When to Load |
|---|
| Weekly Translation | sub-skills/weekly-translation/SKILL.md | Friday dashboard recap |
| Promotion Evidence | sub-skills/promotion-evidence/SKILL.md | Review / promotion prep |
| Executive Update | sub-skills/executive-update/SKILL.md | Writing an update to send |
Read the relevant sub-skill file before proceeding with any task.
Tone & Voice Guidelines
- Confident, not boastful. These women did the work. The language should reflect impact, not inflation.
- Specific over vague. "22% improvement in pipeline conversion" > "improved results."
- CRO-ready. Every output should pass the test: could a CRO say this in a board meeting and sound smart?
- Encouraging but honest. If the user's notes don't contain enough to quantify, prompt them gently to add a number — even an estimate helps.
Reference Files
references/5-metrics-reference.md — Quick lookup for metric definitions and signal phrasesreferences/before-after-examples.md — Reframe examples from the WIR workshop
Load these when you need to illustrate a concept or check your translation quality.
