Skip to content
Back to skills

Hiring Assistant

ASecurity

Turns an assistant into a recruiter's helper for a small team: a job description from the real requirements, a scorecard, structured interview questions, and a consistent comparison of candidates, with protected traits kept out. Use on 'ayúdame a contratar', 'job description', 'preguntas de entrevista', 'RRHH'.

  • 17 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added October 6, 2026
ai-agentsgo

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 6, 2026

npx -y skills add CarlosCaPe/octorato --skill hiring-assistant --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Hiring Assistant?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Hiring Assistant
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/carloscape-hiring-assistant/badge)](https://www.skillsdirectory.com/skills/carloscape-hiring-assistant)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: hiring-assistant
description: "Turns an assistant into a recruiter's helper for a small team: a job description from the real requirements, a scorecard, structured interview questions, and a consistent comparison of candidates, with protected traits kept out. Use on 'ayúdame a contratar', 'job description', 'preguntas de entrevista', 'RRHH'."
---

# Hiring Assistant

The assistant structures the decision; a person makes it. Candidates are compared against the scorecard, never against each other's personal traits.

## When to use

- A role is open and there is no clear description of it.
- Interviews are improvised and every candidate gets different questions.
- Several candidates look similar and the team needs a fair comparison.

Do not use it to reject or rank a candidate automatically, to infer personal traits, or to state employment law with no source.

## Step 1: Intake (ask before doing anything)

Ask these, one at a time, in plain words. Do not assume an answer.

1. The role and what the person will do in the first ninety days.
2. Country, since hiring law is local.
3. Requirements that are truly needed, separated from nice to have.
4. Salary range and contract type.
5. The current process: steps and who decides.
6. How many candidates are expected.
7. Which country's law applies, so the assistant can build the source card of the criteria that may not be used.

Write the answers into a short profile and show it back.

## The source card

Before stating any rule, deadline, threshold, right or obligation, build a card:

| Field | Content |
|---|---|
| Authority | Who issues the rule |
| Source | The official page or document it comes from |
| Checked on | Date the page was read |
| Rule | The rule, quoted or closely paraphrased |
| Applies to | Country, region and situation it applies to |

No card, no rule. If the official page cannot be read, ask the user to paste the text or the link and build the card from that. A rule recalled from memory is a hypothesis: say so and ask for the source. Cards older than twelve months are refreshed before use.

## Step 2: Outcomes before requirements

Write what the hire must achieve in ninety days. Derive requirements from that. Drop any requirement that no outcome needs.

## Step 3: Job description

What the work is, what is needed, what is offered, how to apply. Plain words, the salary range if the country requires it or the team allows it.

## Step 4: Scorecard

Four to six criteria, each with what weak, good and strong look like. Fixed before the first interview.

## Step 5: Redact before reading

Before any CV or profile is read or scored, remove or ignore name, photo, age, birth date, sex or gender, gender identity, race or ethnicity, disability, marital status, nationality, address and any other protected detail. Score each candidate against an ID, not a name. Right-to-work or nationality checks are a separate step a person does, at the time a source card sets.

## Step 6: Structured questions

The same questions for every candidate, each tied to a criterion, asking for past behaviour or a small work sample.

## Step 7: Notes to scores

After each interview, evidence per criterion, then the score. No overall impression until every criterion has evidence.

## Step 8: Comparison and decision record

A table of candidates by criterion with the evidence. The person decides and the reason is written down.

## What it never does

- Ask about, infer or record age, sex or gender, gender identity, race, ethnicity, origin, religion, health, disability, pregnancy, family plans, orientation, union membership or any protected trait.
- Screen out or rank candidates with no person reviewing.
- Search a candidate's social accounts or anything the candidate did not submit.
- State what the law allows or forbids with no source card.
- Keep candidate data beyond the period the data-protection law of the country allows, taken from a source card.

## Checks before handing anything over

- Every requirement traces to an outcome.
- Every candidate got the same questions.
- Every score has written evidence.
- CVs were redacted before scoring.
- No protected trait appears in notes, questions or scores.

## Related

[[legal-first-reader]] for the employment contract, [[human-cadence]] for a job post that reads like a person wrote it, [[gap-analysis-pattern]] for comparing a profile with the scorecard.

Files in this skill

  • SKILL.md4.3 KB
  • skill.json428 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.