Job description
Write a job description from what the role must actually do in its first six months, with honest requirements and a clear way to apply.
In Lobstack: Skills › Library › Add
What your agent will do.
A team is about to hire and needs a posting, or an old posting no longer describes the job.
- 01
Ask, or find in the thread: what this person must have done after three and six months, who they work with, and why the role exists now.
- 02
Write it in this order:
- two lines on the company and the team;
- What you will do: the real work, as outcomes;
- What you need: only what the work requires — each line must be something a candidate without it would fail at;
- Nice to have, kept short;
- pay range, location, and how to apply.
- 03
Cut jargon, years-of-experience counts that do not matter, and words that narrow who applies for no reason.
- 04
Check it against the six-month outcomes: every requirement maps to one.
Ask before publishing it anywhere.
The whole SKILL.md: 30 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: job-descriptiondescription: "Write a job description from what the role must actually do in its first six months, with honest requirements and a clear way to apply."metadata: title: "Job description" category: people tags: [hiring, writing]--- ## When to use this A team is about to hire and needs a posting, or an old posting no longerdescribes the job. ## How 1. Ask, or find in the thread: what this person must have done after three and six months, who they work with, and why the role exists now.2. Write it in this order: - two lines on the company and the team; - What you will do: the real work, as outcomes; - What you need: only what the work requires -- each line must be something a candidate without it would fail at; - Nice to have, kept short; - pay range, location, and how to apply.3. Cut jargon, years-of-experience counts that do not matter, and words that narrow who applies for no reason.4. Check it against the six-month outcomes: every requirement maps to one. Ask before publishing it anywhere.
- People
Candidate screen summary
Summarise a candidate against the role's real requirements from their application and interview notes: evidence for, evidence against, open questions.
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 - Engineering
Review what a linter cannot
Review a change for what a linter cannot see: whether it is correct, what it breaks elsewhere, and which parallel list it forgot to update.
SKILL.md · App - Writing
Release notes from merged work
Turn merged work, or a thread about it, into release notes written for the person installing the version rather than the person who built it.
SKILL.md · App - 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