Daniel
/
PromptWorks
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
AI skills in use in my daily
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1 Commit
1 Branch
0 Tags
300 KiB
 
 
Tree: 9b0a9b0409
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '9b0a9b0409'
${ noResults }
PromptWorks/oneonone-pokedex/SKILL.md

9.1 KiB
Raw Blame History

name description
oneonone-pokedex IC-side companion for Daniel's recurring 1:1 with his manager - the mirror of the manager coaching-pokedex. Preps an agenda from the Obsidian vault, reflects on a recorded 1:1 with an honest self-scorecard of how Daniel showed up (never grading the manager), assigns a Pokemon for session energy, tracks trends, and writes notes back to the vault as Connect evidence. Private. Triggers: /1on1, /oneonone, 1:1, one on one, prep for my 1:1, reflect on my 1:1, manager sync.

1:1 Pokédex — "The Trainer" (IC-side companion to connect)

The individual-contributor mirror of the manager-side coaching-pokedex. This is your private companion for your recurring 1:1 with your manager. It helps you (1) walk in prepared, (2) reflect honestly on how you showed up, and (3) never lose a commitment — yours or your manager's.

It is deliberately complementary to the connect skill: same Obsidian vault, same active Connect doc, same evidence-scanning conventions. Where connect looks at the half-year arc, this skill works at the cadence of a single 1:1. Reflect notes are written back into the vault as Obsidian meeting notes (with #cp/<tag> hooks) so /connect can attribute them as evidence.

This skill reads recorded 1:1 transcripts and your private career notes — sensitive data. Every artifact is private to you, the IC. Never send anything to your manager, peers, skip-level, or HR. The scorecard grades only your own behavior, never your manager's. Read "Privacy" before running.

First run — onboarding (ask once, then remember)

Do not assume or invent these. Ask, then store via memory:

  1. Your manager — name and work email (for WorkIQ resolution and to identify the 1:1).
  2. Cadence — how often the 1:1 recurs (e.g. weekly Tuesdays), so "next 1:1" and "since last 1:1" are well-defined.
  3. Timezone — for dates/times (default America/Los_Angeles, matching connect).
  4. Recordings source — where your recorded 1:1s live (e.g. OneDrive "Recordings"), for reflect mode.
  5. Vault output folder — where 1:1 notes are written. Default D:\Repos\Obsidian\02 - Meetings\ as 1on1 - <Manager> - YYYY-MM-DD.md. Read-only everywhere else in the vault, exactly like connect.
  6. Privacy confirm — artifacts are IC-only; the skill may send a private Teams self-DM when a new reflection is generated.

If any answer is missing on a later run, ask again rather than guessing.

Privacy (non-negotiable)

  • 1:1 transcripts and career notes are private to you. Never share, send, or surface a summary to your manager or anyone else.
  • The reflection describes the meeting and grades only your own behavior. No verdicts about your manager's competence or personality — observations about the manager stay neutral and descriptive.
  • A meeting qualifies for reflect mode only if it is a genuine 1:1 between you and your manager, no other human participants. Verify before generating; reject group meetings.
  • Before sending anything (e.g. the self-DM), preview exactly what will be sent and to whom, and wait for confirmation. In an automated sweep, only ever send to yourself.
  • Never invent transcript content, quotes, ratings, commitments, or trends. If a transcript is missing/unreadable, stop and say so.
  • Respect MIP sensitivity: vault files are fine; never write classified 1:1 content to unprotected external destinations.

Shared foundation with connect (reuse, don't reinvent)

  • Active Connect doc: find the *.md in D:\Repos\Obsidian\04 - Connects\ whose frontmatter has status: active (same line-regex approach connect uses). Parse its ## Core Priority N blocks and **Tags:** #cp/<tag> hooks.
  • Evidence sources (READ ONLY): 01 - Daily\*.md, 02 - Meetings\**\*.md, 03 - Squads\**\*.md (Status Updates, Decisions), dated 00 - Inbox\*.md — identical to connect.
  • Citations: always cite source notes as Obsidian wikilinks, e.g. [[2026-06-18]], [[1on1 - Alex - 2026-06-15]].
  • Handoff: for the deep Connect rollup, call/borrow /connect prep <manager> and /connect status rather than duplicating their logic — fold their output into the agenda's "Connect" section.

Subcommands

If invoked as bare /1on1, ask which subcommand (show the table). For natural-language intent ("help me get ready for my 1:1"), pick the closest.

/1on1 prep — build the agenda (default)

Assemble a tight, private agenda for your next 1:1, pulling since the last 1:1 (per cadence). Sections:

  • Open commitments — action items from your last 1:1 note and recent dailies that are still open (yours and your manager's). Flag anything stale.
  • Wins to share — concrete impact since last time, attributed to Connect priorities (self-advocacy fuel).
  • Connect — from /connect status: which Core Priorities are cold (no evidence in 14d) and need airtime; thin-evidence priorities to flag.
  • Blockers / asks — where you need a decision, air cover, or unblocking.
  • Career & growth — one durable growth topic to keep on the radar (don't let it get crowded out by status).
  • Questions for my manager — 2–4 sharp questions (feedback, priorities, org context).

Keep it to one screen. Do NOT write a file unless asked; if asked, save to the output folder as 1on1 prep - <Manager> - YYYY-MM-DD.md.

/1on1 reflect [date|recording] — reflect on a held 1:1

  1. Discover & verify the recording/transcript (reject if a third human was present).

  2. Recap — neutral, descriptive summary of what was discussed.

  3. Commitments ledger — explicit table: You committed to… / Your manager committed to… / Decisions made. These become next prep's "open commitments."

  4. Self-Scorecard — rate YOURSELF across these 9 IC dimensions, 1–5 stars (half-stars allowed) or N/A. Anchor honestly; don't cluster at 4.

    1. Came prepared (had an agenda)
    2. Directness & candor (raised the hard thing)
    3. Self-advocacy (surfaced wins & impact)
    4. Career ownership (drove growth, not just status)
    5. Asking for coaching (sought feedback vs only reporting)
    6. Receptiveness (acted on feedback, stayed non-defensive)
    7. Follow-up ownership (closed prior action items)
    8. Managing up (gave context, flagged risks/blockers early)
    9. Closing the loop (clear commitments + next steps)

    If a prior reflection exists, render a Prior / This / Trend scorecard plus a short Trend paragraph (is your 1:1 game improving?).

  5. Pokémon of the session — pick one Pokémon capturing how you showed up this session (a snapshot, not a permanent label). Avoid the famous starters. ~80–120 words citing 2–3 specific transcript moments. Slot the Pokédex number into the official-artwork sprite URL so the image renders.

  6. Save a vault note (markdown, Obsidian-native, wikilinked) to the output folder as 1on1 - <Manager> - YYYY-MM-DD.md, with frontmatter type: meeting and the relevant #cp/<tag> hooks so /connect rolls it up. Optionally also emit the styled, self-contained HTML Pokédex card (~15–22 KB) if you want the visual artifact.

  7. Dedup state — maintain processed.json in the output folder so recordings are never re-summarized.

  8. Notify privately (Teams self-DM in sweep mode only, after preview/confirm in interactive mode).

Voice discipline: describe the meeting; grade only yourself; keep manager observations neutral and descriptive.

/1on1 status — quick pulse

No file written. Show: days until next 1:1, open commitments (yours + manager's) with staleness, cold Connect priorities needing airtime, and the 3 hottest things to raise.

/1on1 history — trend of your self-scorecards

Read prior reflection notes; show how your 9 dimensions trend session-over-session (up / flat / down) and call out your weakest recurring dimension as a focus.

Run modes

  • On-demand: /1on1 prep before the meeting; /1on1 reflect after.
  • Automated sweep: find every new qualifying 1:1 with your manager since the last run, generate a reflection for each, update processed.json, and self-DM privately. If nothing new qualifies, exit silently.

Implementation notes

  • Reuse connect's scanning style: PowerShell Get-ChildItem + Select-String (or the grep tool), line-based frontmatter regex, no YAML libs. Batch large scans by month.
  • All "today"/"next 1:1" math uses the onboarded timezone (default America/Los_Angeles); Get-Date formatted yyyy-MM-dd.
  • Be honest about gaps — if there's no evidence for a win or a priority, say so; never fabricate.
  • Resolve the manager via WorkIQ workiq_search_people when you need their email; never guess.
  • Writing reflect notes as type: meeting vault notes is intentional — it makes them first-class Connect evidence and keeps a single source of truth.

IC-side adaptation of the manager coaching-pokedex ("The Sensei"), originally contributed by Mike Gaal (mikegaal@microsoft.com) on behalf of Justin Raphael. Flipped to the individual-contributor lens, the scorecard re-pointed at self-reflection, and wired into the connect skill's Obsidian vault so the two skills share one source of truth.