careerpacer-1on1-and-idp
VerifiedTurn freeform 1:1 meeting notes into a structured CareerPacer OneOnOne file under data/1on1/, and create or update IDPAction entries in the current year's data/idp/<year>.md, linked back to that 1:1. Use this skill when the user dictates or pastes notes from a 1:1 that just happened or is upcoming, or asks to "log a 1:1", "write up this meeting", "prep for my next 1:1", "add/update an IDP action", or "link this to my growth plan".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.2 KB |
| examples/data/1on1/2026-01-19.md | markdown | 1.1 KB |
| examples/data/1on1/2026-02-16.md | markdown | 1.0 KB |
| examples/data/1on1/2026-03-16.md | markdown | 989 B |
| examples/data/1on1/2026-04-20.md | markdown | 985 B |
| examples/data/1on1/2026-05-18.md | markdown | 1.0 KB |
| examples/data/1on1/2026-06-15.md | markdown | 1.1 KB |
| examples/data/1on1/2026-07-13.md | markdown | 1.1 KB |
| examples/data/evaluation/2026-annual.md | markdown | 2.4 KB |
| examples/data/idp/2026.md | markdown | 2.8 KB |
| examples/data/profile.json | config | 139 B |
| scripts/generate_index.py | script | 1.3 KB |
| scripts/validate_data.py | script | 5.7 KB |
examples/data/evaluation/2026-annual.md
View on GitHub---
id: eval-2026-annual
period: "2026"
type: annual_360
eval_date: 2026-06-15
attendees:
- John Ferreira
- Alex Turner
strengths:
- Fast technical ramp-up; contributed useful fixes to the activity-data pipeline within the first month
- Solid classic ML fundamentals (recommendation systems); picking up MLOps/deployment practices quickly once pointed at them
- Peer feedback (360) noted I'm easy to work with and responsive async, despite limited working-hours overlap with the US team
growth_areas:
- idp-2026-001
- idp-2026-002
- idp-2026-003
---
My first review since joining, six months in. Format is annual, 360-degree
(manager + peer input).
**Strengths.** Ramped up faster than expected given the remote/async
onboarding — I was already contributing to the activity-data pipeline in my
first month. Classic ML fundamentals are strong, especially around
recommendation systems. Peers consistently mentioned I'm responsive and
easy to collaborate with async, which matters a lot given the Brazil/US time
overlap is only a few hours a day.
**Growth areas.**
1. *Production ML / MLOps.* Most of my modeling work to date has stayed
in notebooks. I've started shipping (the workout-streak model, behind a
feature flag) but haven't yet closed the loop with monitoring/alerting.
Alex wants to see that gap closed, and for shipping-and-monitoring to
become my default mode rather than the exception.
2. *Visibility in cross-team/leadership settings.* This is explicitly not
about English proficiency — it's about speaking up with confidence in a
second language, remote, cross-culture setting. I've made real progress
here since February (from staying silent, to prepping points ahead of
time, to speaking up unprompted with concrete numbers). The ask now is
consistency, not a one-off good meeting.
3. *End-to-end ownership.* I've contributed pieces to several projects
but, until recently, hadn't owned one fully — scoping, building,
shipping, and being the point of contact. The workout-streak project is
a good first attempt; Alex wants to see it carried through to a full
stakeholder-facing delivery.
Overall trend is positive and each growth area already has early momentum
going into this review — these are being turned into IDP actions
([idp-2026-001](../idp/2026.md), [idp-2026-002](../idp/2026.md),
[idp-2026-003](../idp/2026.md)) as of today.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |