close-round
/close-round
Zamyka rekrutację i usuwa dane osobowe kandydatów, zostawiając pseudonimowy zapis audytu, oraz wskazuje rundy otwarte zbyt długo.
- Autor
- shikhar58 ↗
- Repozytorium
- repo-aware-hiring ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 10.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 1
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 10.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/cleanup.py
Co robi i kiedy
Zamyka rekrutację i usuwa dane osobowe kandydatów, zostawiając pseudonimowy zapis audytu, oraz wskazuje rundy otwarte zbyt długo.
Oryginalny opis (EN)
Close a hiring round and delete candidate personal data (extracted and redacted CVs, scores, rankings, reports, interview kits) while keeping a pseudonymous audit record. Also finds rounds left open too long. Use when a role is filled or cancelled, when the user asks to delete candidate data or apply retention, or to check for overdue rounds.
Jak działa
- Close one round
- What remains
- Overdue rounds
- Rules
Podgląd SKILL.md
---
name: close-round
description: Close a hiring round and delete candidate personal data (extracted and redacted CVs, scores, rankings, reports, interview kits) while keeping a pseudonymous audit record. Also finds rounds left open too long. Use when a role is filled or cancelled, when the user asks to delete candidate data or apply retention, or to check for overdue rounds.
---
# Close Round
Script: `scripts/cleanup.py` next to this file. Run with `python3 -I`. Paths in this file are relative to this skill's folder (the folder that holds this `SKILL.md`); skills are installed side by side, so `../<other-skill>/` reaches a sibling skill. Shared scripts named without a path (`check_ready.py`, `decisions.py`, `focus.py`, `trace_usage.py`, `workspace.py`) are in `../hiring-workspace/scripts/`; `check_map.py` and `inventory.py` are in `../map-codebase/scripts/`; any other script is in `../<skill>/scripts/` of the skill that owns it.
It deletes only inside the role folder and never follows symlinks.
In a multi-repo workspace the role folder is `<workspace>/roles/<role-slug>`; the sweep takes `<workspace>/roles`.
The workspace's maps and system map hold no candidate data and stay.
## Close one round
1. **Preview.** `python3 -I scripts/cleanup.py close hiring/<role-slug>`
This prints what will be deleted and kept and deletes nothing (exit code 3).
2. **Ask the user two questions** before deleting, unless they already answered (as in
[How to ask a question](../hiring-workspace/CHECKPOINTS.md#how-to-ask-a-question): nothing pre-selected,
write-your-own and skip options; give the facts below in neutral words):
- Delete the original CVs in `cvs/` too? (`--include-cvs`.) Facts to give: they are personal data; keep them only
if they live nowhere else and the organisation's policy sets a retention period.
- Keep the report (`report.md` and `report.html`)? (`--keep-report`.) Facts to give: it names candidates and
quotes their CVs; keep it only for a documented reason.
**If either is skipped, delete nothing** and say what is still waiting for an answer.
Also check that nobody still needs the data, e.g. a candidate who asked for human review or
for a copy of their data.
3. **Close.** Re-run with the chosen flags and `--yes`. Tell the user what was deleted, in one line.
Deletion cannot be undone. Never pass `--yes` without the user's confirmation in this conversation,
including in scheduled or unattended runs: there, run the preview and report it instead.
## What remains
`brief.md`, `jd.md`, `repo-profile.md`, `rubric.json`, `focus.md` and `decisions.json` (to reuse for the next round), `round.json`
(opened/closed dates), and `audit.json`: rubric
version and hash, each candidate's pseudonymous id, score, gate, confidence and flag codes, the
ranking hash, and what was deleted. No names, file names or CV text.
## Overdue rounds
`python3 -I scripts/cleanup.py sweep hiring --older-than <days>` lists open rounds older than the
retention period. Ask the user for their organisation's retention period rather than assuming one.
The user can set up a scheduled task that runs the sweep preview monthly and reports overdue rounds.
Closing them still needs their confirmation.
## Rules
- This is not legal advice on retention periods. The user's policy and local law decide.
- If the user asks to delete one candidate's data (for example a GDPR erasure request), do it by hand:
remove that candidate's files from `cvs/`, `extracted/`, `redacted/` and `scores/`, re-run `rank.py`
and `render_report.py`, and tell the user which files were removed.
Pliki w paczce (2)
- SKILL.md 4 KB
- scripts/cleanup.py 8 KB
Wersje
W bazie nie ma innych skilli o nazwie close-round.
Migawka bazy z 13.11.2026 · wersja paczki 4562e13b93cb (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90esp32-data-retention-policy
Określa, jak długo urządzenie ESP32 przechowuje dane pomiarowe i kiedy je usuwa zgodnie z wymaganiami prawa i klienta.