# Visibility Sponsorship

> Visibility & Sponsorship

- Skill: `shwetank/visibility-sponsorship` (Agent Skill)
- Install (CLI): `npx skillmds@latest add shwetank/visibility-sponsorship`
- Raw SKILL.md: https://api.skillmd.com/api/skills/shwetank/visibility-sponsorship/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: shwetank (https://skillmd.com/u/shwetank)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/shwetank/visibility-sponsorship

---


# Visibility & Sponsorship

"My work speaks for itself" is the most expensive sentence in an IC career. Work doesn't speak; people speak, in rooms you're not in — calibration, planning, staffing. This skill builds the machinery that gets your work spoken about accurately: a visibility map, a sponsor plan, and an amplification rhythm that doesn't require becoming someone you'd dislike.

The reframe that unlocks it: **visibility is information logistics, not self-promotion.** People making decisions about you are doing it with incomplete data; supplying the data is a professional courtesy, not vanity.

## Step 1: The visibility map

Identify who's in the rooms where the user's career gets decided, and audit each honestly:

| Person | Room they're in | What they currently know about you | What they'd need to know |
|---|---|---|---|

Draw the "currently know" column from evidence, not hope: what could this person actually cite about the user's work? If the answer is "we get along" — that's a *relationship*, not visibility. Read the user's registered stakeholders and `wins.md`: the gap between wins logged and wins *known by anyone on this map* is the whole problem, made visible.

**Sponsors vs. mentors, explicitly:** a mentor talks *to* you; a sponsor talks *about* you, spending their credibility in rooms you're not in. Most ICs have mentors and think that's coverage. The map needs at least one plausible sponsor — usually someone senior who has directly benefited from the user's work.

## Step 2: The sponsor plan

Sponsorship is earned through *usefulness made legible*, not asked for cold. For the best sponsor candidate:

1. **Give them material.** Sponsors advocate with specifics. After a meaningful win, send the two-line version (from `wins.log` — situation + impact with a number). You're not asking for anything; you're stocking their inventory.
2. **Make the ask small and concrete when it comes.** Not "will you sponsor me" but *"I'm going up for staff in Q4 — when my name comes up in calibration, the thing I'd want known is [X]. Can I send you the one-pager?"*
3. **Return the loop.** Tell sponsors what their advocacy led to. People keep investing where they've seen returns.

## Step 3: The amplification rhythm

Sustainable moves, calibrated to feel like communication:

- **The work-share note.** When something ships or a fire gets put out, a 3–5 line note to the relevant channel/leader: what, why it mattered, who helped. Crediting collaborators generously is what makes it read as leadership rather than self-promotion — and it's also just accurate.
- **Teach it.** The same win, presented as a lesson ("what we learned migrating X") at a guild/all-hands, converts one-time work into reputation. Teaching is the most status-safe form of visibility there is.
- **Write it down publicly.** ADRs, postmortems, design docs with your name on them are visibility that compounds while you sleep.
- **The manager channel.** Your manager repeats what's easy to repeat. End of week, hand them one repeatable sentence about your work — literally engineered for retelling in their staff meeting.

Pick **two** of these and put them on a rhythm; four done sporadically beats nothing, but two done weekly beats everything.

## The discomfort, named

Most users arrive at this skill feeling that all of it is gross. Take that seriously rather than talking past it:

- The test for any move: **is every word true, and would you say it about a teammate?** If yes to both, it's information, not bragging. The user who'd happily amplify a colleague's work but not their own doesn't have a modesty virtue — they have an asymmetry bug.
- Discomfort is also unevenly taxed: people from underrepresented groups get judged more harshly for self-advocacy, which makes *sponsors* (who advocate for them) and *teaching-frame* moves (status-safe) disproportionately valuable. Factor that into which moves you recommend, and say why.

## Anti-patterns

- **Visibility theater.** Optimizing for being seen over being useful inverts quickly and everyone can smell it. The pipeline is always work → wins.md → amplification; never amplification first.
- **Sponsor spam.** Material to a sponsor more than ~monthly converts a champion into someone who filters your email.
- **The credit heist.** Amplifying shared work as solo work is the one move that permanently destroys what this skill builds. When in doubt, over-credit.
- **Waiting for the packet.** Starting visibility work six weeks before promo season is like starting to exercise the week before the marathon. This skill is for the off-season; that's the point.

## Composition

- `wins-log` / `wins-due` — the inventory this skill amplifies from
- `wins-curate` / `promo-case-glue` — the formal-moment artifacts; visibility work makes their audience pre-warmed
- `glue-audit` — surfaces the invisible work that most needs this treatment
- `stakeholder-register` / `stakeholder-reflect` — sponsors and map-members are stakeholders; track the relationship deliberately
- `the-career-coach` — when the visibility gap turns out to be a direction question, not a logistics one