- Home
- Skills
- Technical Documentation
- Joinpack: new teammates productive from week one
More screenshots
Works with the AI Agents you already use
Joinpack: new teammates productive from week one
Builds a one-page context pack from the actual repo, a least-privilege access table with expiries, a first-week plan with one small real task, a glossary and hand-back rules. Private notes stay out.
$9
Joinpack: new teammates productive from week one
Example session with this skill installed
Onboard a new frontend contractor starting Monday on the booking-web repo. Six-week contract, UI work only.
- Read your context and instructions
- Compiled the joinpack
Read README, package.json, .env.example, folder tree and the last 20 commits. Ran pnpm install and pnpm dev myself: both work. Filter pass removed 2 private items (owner notes folder, a rate card mention); grep for emails, phone numbers and keys is clean.
Context pack (docs/onboarding.md)
- What: booking-web lets small clinics take appointments online.
- Who decides: product lead (scope), tech lead (code review), designer (UI sign-off).
- Run:
pnpm install·cp .env.example .env.local·pnpm dev·pnpm test - Where:
app/pages ·components/ui/shared UI ·tests/Vitest specs - Conventions: branch
feat/<task>, conventional commits, PR to main, done = tests green plus designer sign-off.
Access (least privilege, expires 2026-11-30)
| System | Level | Grants | Granted | Expiry |
|---|---|---|---|---|
| GitHub repo | write via PR | tech lead | no | 2026-11-30 |
| Staging app | read | tech lead | no | 2026-11-30 |
| Design files | comment | designer | no | 2026-11-30 |
| Production DB | none | n/a | n/a | n/a |
First week
- Day 1: run locally, read the pack.
- Days 2 and 3: fix the pricing copy on
/plans(issue #41, ask designer, done = PR merged). - Days 4 and 5: empty state for the bookings list (issue #44, ask tech lead).
Glossary: RLS: rules for who can read which rows · slot: one bookable time.
Offboard: same 3 granted rows with a revoke column; rotate the staging env key.
Next steps
- Grant the 3 access rows and mark them yes.
- Share the pack before Monday and book a 20-minute walkthrough.
- Send me their questions after the walkthrough so I fold the answers in.
Connects securely to your tools. The creator never sees your data.
About this skill
A new developer starts Monday and all they get is a repo link. The run command in the old doc fails, someone grants admin access "to save time", and week one ends with nothing shipped. Meanwhile your private notes sit one folder away from what you share.
Joinpack builds an onboarding pack from the repo as it really is, with least-privilege access and a first week that ends in a real, small win.
What it does
- Context pack, one page from the README, package files, env example, folder tree, recent commits and open tasks: what it is, who decides, stack, how to run it, where things live, conventions.
- Commands tested by the agent itself before they go in the pack.
- Private material filtered out: personal notes, memory files, money, rate cards, other clients. Then a grep for names, emails, phone numbers and keys before sharing.
- Access table with system, level, who grants, granted and expiry. Read-only first, separate accounts, secrets through your secret manager.
- First-week plan with one small real task by day 3, each task with a link, an owner and a done check.
- Glossary, house style and hand-back rules: branch and PR per task, no direct pushes to main.
- Offboard list with a revoke column and secrets to rotate.
How it works
- Scope the person: role, start date, trust level, what they must never touch.
- Build the pack from the repo and filter private material.
- Fill access, first week, glossary and house style.
- Deliver to
docs/onboarding.mdor the team wiki and fold walkthrough questions back in.
Frameworks & tools
Reads your repo with git and searches the pack with grep. Stack-agnostic.
Why this beats prompting it yourself
A prompt writes a generic welcome from memory. Joinpack writes from repo facts, tests every command, and runs a privacy filter and grep before anything is shared.
Use cases
- New developer or designer joining next week.
- Short-term contractor with access that expires with the contract.
- Intern with smaller tasks, a named buddy and daily check-ins.
- Returning collaborator who needs a diff since they left.
Known limitations
Not for agent-to-agent session continuity or client support. You still grant the access yourself and run the 20-minute walkthrough.
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scanned
Verified clean 1 day ago
- Passed all security checks, Safe to install
Requires