personio-eng-onboarding
Automates the Personio new-hire engineering setup documented in tpf-docs first-steps — Hammock District, AWS SSO, Kubernetes, JetBrains Vault, Kotlin env, and DataAccess.
Prerequisite — GitHub setup must already be done
Installing a Claude Code marketplace requires a working GitHub SSH connection, so by the time you can use this plugin you've already completed GitHub setup (SSH key in 1Password, GPG signing, key authorized for Personio-Internal SSO).
The /onboard flow verifies GitHub access at the very first step and aborts with a pointer to the docs if it isn't working.
Usage
Full flow (recommended for new hires)
Trigger the orchestrator skill — any of these works:
- Say "onboard me" / "set me up" / "I'm new to Personio" / "walk me through first-steps"
- Type
/onboard(skills are slash-invocable)
Walks you through each phase in order, idempotently:
- GitHub access — sanity-check (
ssh -T git@github.com, commit-signing config) - Local env — runs the Hammock District install script
- AWS SSO — verifies CLI, runs the AWS configure script,
aws sso login,aws sts get-caller-identity - Kubernetes —
aws eks update-kubeconfigfordevandprod(Product Engineer default; flags adjustable for TPE/DX) - JetBrains Vault (optional — prompted) — guides you through the manual Toolbox / IDE Services dance and verifies the result. Only run if you use IntelliJ (Kotlin) or PhpStorm (monolith).
- Kotlin env (optional — prompted) — confirms
java -versionis 17,JAVA_HOMEis set, and (optionally) clones a repo to run./gradlew test. Only run if you work with Kotlin services. - DataAccess —
brew install dx/tap/data-access - Capstone (optional) — clone
developer-experience, run the hello-world demo, open your first PR. Skipped automatically if you skipped Kotlin (step 6).
Each phase first checks whether it's already complete and skips if so, so re-running /onboard after fixing one broken step is safe.
À la carte
Each phase is also a standalone skill that activates on intent. Say things like:
- "set up AWS access" →
onboard-aws - "get my Kubernetes contexts configured" →
onboard-k8s - "install hammock district" →
onboard-local-env - "configure JetBrains licenses" →
onboard-jetbrains - "set up my Kotlin environment" →
onboard-kotlin - "install data-access" →
onboard-data-access
What it cannot do automatically
These require either a browser, a GUI app, or a one-time SSO interaction. The plugin pauses and gives you exact instructions:
- AWS SSO login — opens your browser to confirm the device code
- JetBrains Toolbox sign-in — Personio SSO flow inside the Toolbox app
- IntelliJ JDK / Gradle JVM selection — done in IntelliJ's UI
- Opening a Pull Request — the capstone is a learning step; we don't merge it for you
Capability
| Skill | Path | Purpose |
|---|---|---|
onboard | skills/onboard/SKILL.md | Orchestrator — runs all phases in order |
onboard-local-env | skills/onboard-local-env/SKILL.md | Hammock District install |
onboard-aws | skills/onboard-aws/SKILL.md | AWS SSO config + login + verify |
onboard-k8s | skills/onboard-k8s/SKILL.md | EKS kubeconfig setup |
onboard-jetbrains | skills/onboard-jetbrains/SKILL.md | JetBrains Vault license walk-through |
onboard-kotlin | skills/onboard-kotlin/SKILL.md | JDK 17 / gradle smoke-test |
onboard-data-access | skills/onboard-data-access/SKILL.md | brew install dx/tap/data-access |
All capability is delivered as skills — there are no slash commands (the deprecated model). Skills auto-trigger on intent and are also invocable as /skill-name.
Maintainer
Colm Doyle (Developer Experience).