Onboarding guide
Write an onboarding guide for someone new from the existing docs, repos and chat: day-one setup, who to ask, and a first real task.
In Lobstack: Skills › Library › Add
What your agent will do.
Someone is joining a team, project or product, and what they need to know is scattered across docs, repos, chat and people's heads.
- 01
Ask who it is for — role and experience — and what they should be able to do by the end of week one. That goal decides what goes in.
- 02
Read what exists: READMEs, the wiki, the handbook, recent chat about setup trouble. A setup question asked twice belongs in the guide.
- 03
Write it in this order:
- Day one: access to request and tools to install, with exact commands or links. Run each command if you can.
- How things work here: the systems and terms they will hear first, one line each.
- Who to ask: a table of topic and person or channel.
- First task: one small, real piece of work with a clear finish line.
- Week one: a checklist.
- 04
Link to existing docs rather than copying them; copies go stale.
- 05
Mark any step you could not verify "(unchecked)".
- 06
End with the contradictions and gaps you found in the docs, for their owners.
- 07
Post it as a document. Ask before sending it to the new person or adding it to a shared wiki.
The whole SKILL.md: 33 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: onboarding-guidedescription: "Write an onboarding guide for someone new from the existing docs, repos and chat: day-one setup, who to ask, and a first real task."metadata: title: "Onboarding guide" category: operations tags: [onboarding, docs]--- ## When to use this Someone is joining a team, project or product, and what they need to know isscattered across docs, repos, chat and people's heads. ## How 1. Ask who it is for -- role and experience -- and what they should be able to do by the end of week one. That goal decides what goes in.2. Read what exists: READMEs, the wiki, the handbook, recent chat about setup trouble. A setup question asked twice belongs in the guide.3. Write it in this order: - Day one: access to request and tools to install, with exact commands or links. Run each command if you can. - How things work here: the systems and terms they will hear first, one line each. - Who to ask: a table of topic and person or channel. - First task: one small, real piece of work with a clear finish line. - Week one: a checklist.4. Link to existing docs rather than copying them; copies go stale.5. Mark any step you could not verify "(unchecked)".6. End with the contradictions and gaps you found in the docs, for their owners.7. Post it as a document. Ask before sending it to the new person or adding it to a shared wiki.
- OperationsFeatured
Weekly status report
Write the weekly update from what actually happened (merged work, moved tickets, tracked figures) in the same shape as last week.
SKILL.md · App - Operations
Spreadsheet cleanup
Clean a messy spreadsheet or CSV (headers, types, duplicates, blanks, inconsistent values) into a tidy copy, with a log of every change.
SKILL.md · App - Operations
Write a runbook
Turn a task someone does by hand into a runbook: exact steps and commands, a check after each, what to do when one fails, and how to undo it.
SKILL.md · App - Operations
Scheduled check
Run a named checklist on a schedule, compare with the last run, and report only what changed or failed. Never fixes anything on its own.
SKILL.md · App - Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App