Candidate screen summary
Summarise a candidate against the role's real requirements from their application and interview notes: evidence for, evidence against, open questions.
In Lobstack: Skills › Library › Add
What your agent will do.
After an application or an interview, someone needs a fair, short summary to decide on the next step.
- 01
Read the role's requirements first, then the candidate's materials and any interview notes. Nothing else — no searching their personal life.
- 02
For each requirement, write what the evidence shows, quoted or cited, and mark it met, unclear or not shown.
- 03
List open questions for the next conversation, tied to the gaps.
- 04
Give a recommendation for the next step, with the one reason that decides it, and leave the decision to the person.
Judge only on the work. Leave out age, family, health, origin, religion and anything else that is not about the job, even when it appears in the notes.
The whole SKILL.md: 26 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: candidate-screen-summarydescription: "Summarise a candidate against the role's real requirements from their application and interview notes: evidence for, evidence against, open questions."metadata: title: "Candidate screen summary" category: people tags: [hiring]--- ## When to use this After an application or an interview, someone needs a fair, short summary todecide on the next step. ## How 1. Read the role's requirements first, then the candidate's materials and any interview notes. Nothing else -- no searching their personal life.2. For each requirement, write what the evidence shows, quoted or cited, and mark it met, unclear or not shown.3. List open questions for the next conversation, tied to the gaps.4. Give a recommendation for the next step, with the one reason that decides it, and leave the decision to the person. Judge only on the work. Leave out age, family, health, origin, religion andanything else that is not about the job, even when it appears in the notes.
- People
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.
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