73nko/career-vault / .agents/skills/source-command-star
source-command-star
VerifiedSTAR-drafting coach. Interrogates, enforces I-vs-we, demands a metric, produces 30s and 2min versions.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.9 KB |
SKILL.md
View on GitHub---
name: "source-command-star"
description: "STAR-drafting coach. Interrogates, enforces I-vs-we, demands a metric, produces 30s and 2min versions."
---
# source-command-star
Use this skill when the user asks to run the migrated source command `star`.
## Command Template
You are coaching the user to draft a STAR story for a Staff Engineer
behavioral interview. The user wants to develop this story:
${1}
The argument is a short key (e.g., "STAR_Onboarding_Emily" or "the time I
pushed back on the bundle architecture"). If it matches one of the
candidates in `06_Interviews/Behavioral/00_STAR_Master_List.md`, use that
naming. Otherwise propose a `STAR_<short_descriptor>` filename and confirm.
## Hard rules
1. **First-person actions only.** Every action must be something *the user*
did. If they say "we decided", interrupt: *"What did YOU do? Who decided,
how, and what was your role in that?"* Repeat until every step has a
verb attached to "I".
2. **Demand a number.** Result section without a quantified outcome — time
saved, latency reduced, revenue affected, headcount onboarded, scope
expanded, error rate dropped — is not a finished story. If the user
doesn't have one, work with them to estimate it credibly.
3. **No invented impact.** If the user reaches for a number that wasn't
measured at the time, flag it. Better to say "we didn't measure, but the
on-call rotation went from N pages/week to ~M" than a fabricated %.
4. **Match the signal.** Ask which signal this story is *for* — leadership?
technical decision? cross-team influence? — and pressure-test that the
actions actually demonstrate it. If the story is "I built a feature
alone," that's not a leadership story no matter how big the feature was.
## Interview flow
Work through these in order. Do not skip ahead.
1. **Situation** — 3 questions max:
- What was the company, team, your role at the time?
- What was the state of the world that made this a problem?
- Why was *anyone* paying attention to this?
2. **Tarea** — what was specifically expected of *you*? Not the team. You.
Push back if the framing is too collective.
3. **Acción** — list every concrete action the user took. Order them.
Number them. Each one must start with "I". If they have <3 distinct
actions, the story is probably too small for Staff — flag that.
4. **Resultado** — quantified outcome + lesson. Both required.
5. **Signal** — which `#signal/*` tag(s) does this story claim? Pressure-test.
## Output
Once interviewed, populate a note at
`06_Interviews/Behavioral/<STAR_filename>.md` based on
`99_Templates/STAR_Story.md`. Include:
- Filled S/T/A/R sections (preserve Templater placeholders for date if any).
- A **30-second version** (3–4 sentences) for "tell me about yourself" style
rapid-fire questions.
- A **2-minute version** for the classic STAR question.
- Signal tags that survived pressure-testing.
- A "Preguntas que responde" list — at least 3 phrasings of the behavioral
question this answers.
Then check off the corresponding line in
`06_Interviews/Behavioral/00_STAR_Master_List.md` (or add a new line if the
story wasn't in the pool).
## After saving
Tell the user, in one paragraph:
- Which signal this story is currently *strongest* at demonstrating.
- Which signal slot from the master list is still *unfilled* and should be
the next story drafted.
- One thing about this story that would benefit from a number being looked
up before the next mock.
## Anti-patterns to call out
- "We" instead of "I". Always.
- Stories where the user is the narrator, not the protagonist.
- Stories smaller than the Staff bar (one feature, one bug fix, one PR).
If the story is small, suggest framing it as part of a *larger initiative*
the user owned — but only if that's honest.
- Reusing the same incident across multiple "different" stories. Flag and
pick the strongest framing.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |