snapshot-check

Estrelas2

Forks0

Atualizado25 de junho de 2026 às 02:50

Verify — BEFORE any structural edit to the candidate's evidence-bank, project-instructions or changelog files — that a Convention 13 pre-edit snapshot exists in _resources/ under the dated naming convention, and that the _resources/ retention discipline (keep 3 most-recent good backups, _archive/ for older, _quarantine/ for truncated, RESTORE_INDEX.md current) holds. Use this skill at the START of any session step that will add or move a matrix row, change entry format, restructure a Section file or Examples_Master.md, restructure Project_Instructions_V*.md or either changelog, or run a multi-edit Python script across the bank. Also use when [Candidate First Name] says 'check the snapshots', 'is there a backup', or 'verify the restore index'. This is a blocking gate, not advisory: a structural edit without a pre-edit snapshot is unrecoverable if it truncates.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

dudarenok-maker

dudarenok-maker/executive-application-helper

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Especialistas em gestão de projetosNegócios e Operações Financeiras·SOC 13-1082

Explorador de arquivos

2 arquivos

SKILL.md

readonly

name

snapshot-check

description

Snapshot Check — Convention 13 pre-edit gate skill

Codifies Convention 13 (pre-major-edit snapshot + retention rule) of Project_Instructions.md (rev 2026-06-12). Wave 3 verification skill of the framework.

The 2026-05-28 Section 7 reconstruction recovered from a 2026-05-11 backup only because that backup happened to exist. This gate makes the snapshot a checked precondition rather than a remembered discipline. It blocks the edit if the snapshot is missing.

When to invoke

Before any session step that will:

(a) add or move a matrix row in any Examples_Section_5_*.md file;
(b) modify the entry format used in any A / B / C / D section file;
(c) restructure Examples_Section_4_Master_Index.md, any Examples_Section_5_*.md, Examples_Section_6_Signature_Metrics.md, Examples_Section_7_Watchouts.md or Examples_Master.md;
(d) restructure Project_Instructions_V*.md or either changelog (Convention 15 scope);
(e) apply a multi-edit Python script across the bank.

Trivial edits are exempt — single proof-point amendment, single tag tweak, changelog appends, prose copy-edits inside an existing entry.

Checks — run all four

Load references/snapshot-rules.md, then:

Snapshot exists. For every file about to be edited, a same-day snapshot exists in _resources/ named [Original_filename]_backup_YYYY-MM-DD_pre-{kebab-descriptor}.md and its descriptor names this structural change. If missing → STOP: take the snapshot now, then proceed. (The fix is one cp; the gate exists so it cannot be skipped, not to create ceremony.)
Snapshot is good. The snapshot is byte-identical to the current file (verbatim copy taken before any edit). A snapshot shorter than the live file is itself suspect — quarantine and retake.
Retention discipline holds for the touched base files: at most the 3 most-recent good backups in _resources/ root; older in _resources/_archive/; any *TRUNCATED* file in _resources/_quarantine/ (never a restore source).
RESTORE_INDEX.md is current — it names the known-good latest backup for every touched base file. The newest backup by timestamp is not necessarily the newest good one.

Output format

A per-file table (file / snapshot found / good / retention OK / index OK), then verdict: Proceed or Blocked — [action]. Blocked is resolved in-session (take snapshot, fix retention, update index), then re-run.

Mais deste repositório

mesmo repositório

bank-integrity-check

dudarenok-maker/executive-application-helper

Run a three-axis integrity check on the framework's evidence-bank files at the end of any session that touched the bank — Examples_Master.md, the Section 4/5/6/7 files, any Examples_Section_A/B/C/D companion file — plus the append-only files that actually truncate in practice: both changelogs (evidence-bank changelog + current weekly archive, instructions changelog) and the Project_Instructions file. Use at post-draft maintenance (STEP 4) before the maintenance report, OR when the candidate says 'check the bank', 'integrity check', or 'make sure I didn't break anything'. Mechanical (~30–60 sec via bash + grep); catches three failure modes that otherwise go undetected for weeks: end-of-file truncation, cross-reference breakage, and silent line-count drops.

2026-06-252

candidate-voice

dudarenok-maker/executive-application-helper

Apply the candidate's executive voice and style — written or spoken — or audit existing material against it. Use this skill any time you are (a) drafting, rewriting, sharpening or reviewing prose the candidate will send or sign (emails, cover letters, statements of claims, briefings); (b) preparing for or rehearsing an interview the candidate will sit (recruiter screens, behavioural panels, executive panels — including STAR-style prep documents and opening scripts); or (c) generating an interview-prep document using the framework's eight-section template. Also use when the candidate asks to 'make this sharper / more like me / in my voice' or for a critique, audit or tone review of any writing. Default to invoking this skill rather than freelancing on voice, tone or interview-prep structure.

2026-06-252

capability-mapping-check

dudarenok-maker/executive-application-helper

Verify that a panel brief for an SES or equivalent senior role contains a complete capability mapping section before delivery — all framework capability groups mapped per question, Strong/Adequate/Watch ratings on every cell, a named pivot story for every Watch, an overall coverage matrix, a values/behaviours cross-frame, and the cumulative-impression reminder. Use this skill whenever a panel or executive-panel brief for an APS SES role (or a state-government / board-level equivalent scored against a formal capability framework such as the ILS) is about to be saved to Interview Prep/ or delivered. Also use when [Candidate First Name] asks 'check the capability mapping', 'is the ILS coverage complete', or 'run the mapping check'. The check is mechanical (~30–60 sec) and catches the panel-prep failure mode where coverage thins on one capability and no pivot story exists when the panel probes it.

2026-06-252

coverage-audit

dudarenok-maker/executive-application-helper

Generate the STEP 2 coverage analysis for a drafted application document — mapping the draft against every section of the source materials (candidate information pack, position description, advertisement, selection criteria, recruiter requests, 'About You' / 'Key Accountabilities' / 'Capabilities' sections) and marking each Addressed / Partially Addressed / Not Addressed with the supporting evidence-bank entry IDs. Use this skill immediately after any application draft is finalised (cover letter, statement of claims, targeted pitch, selection criteria response, recruiter response) — STEP 2 is mandatory for every application-drafting session. Also use when [Candidate First Name] asks 'how well does this cover the PD', 'coverage analysis', 'what did we miss', or 'map the draft to the criteria'. Produces the Step 2 deliverable tables directly.

2026-06-252

length-check

dudarenok-maker/executive-application-helper

Verify that a drafted application document complies with the framework's word-count and character-count discipline before delivery — document-type word bands, any matrix-row or brief-stated override, and (critically) per-question hard character limits on job-platform screening questions (e.g. Seek's 1,000 characters per question, which the platform truncates silently). Use whenever a draft is about to be saved to Submissions/ or presented as final output. Also use when the candidate asks to 'check the length', 'count words', or 'is this within the limit'. Mechanical (~5–10 sec per document).

2026-06-252

matrix-row-traceability

dudarenok-maker/executive-application-helper

Confirm that a drafted application document actually follows the prescription of its matched evidence-bank matrix row — every B-ID in the row's body stack is reflected in the draft, the dominant A-ID positioning leads, the template and length band match, and the fit-acknowledgment style and AI register are honoured. Use this skill at Step 1 close on any application-drafting session where a matrix row was matched (cite by ID), alongside length-check and watchouts-sweep. Also use when [Candidate First Name] asks 'did we follow the row', 'trace the draft to the matrix', or 'is this on-prescription'. Catches prescription drift: a draft that silently swapped the row's tested body stack for ad-hoc evidence selection, losing the calibration the row encodes.

2026-06-252

name

snapshot-check

description

Snapshot Check — Convention 13 pre-edit gate skill

Codifies Convention 13 (pre-major-edit snapshot + retention rule) of Project_Instructions.md (rev 2026-06-12). Wave 3 verification skill of the framework.

When to invoke

Before any session step that will:

(a) add or move a matrix row in any Examples_Section_5_*.md file;
(b) modify the entry format used in any A / B / C / D section file;
(c) restructure Examples_Section_4_Master_Index.md, any Examples_Section_5_*.md, Examples_Section_6_Signature_Metrics.md, Examples_Section_7_Watchouts.md or Examples_Master.md;
(d) restructure Project_Instructions_V*.md or either changelog (Convention 15 scope);
(e) apply a multi-edit Python script across the bank.

Trivial edits are exempt — single proof-point amendment, single tag tweak, changelog appends, prose copy-edits inside an existing entry.

Checks — run all four

Load references/snapshot-rules.md, then:

Snapshot exists. For every file about to be edited, a same-day snapshot exists in _resources/ named [Original_filename]_backup_YYYY-MM-DD_pre-{kebab-descriptor}.md and its descriptor names this structural change. If missing → STOP: take the snapshot now, then proceed. (The fix is one cp; the gate exists so it cannot be skipped, not to create ceremony.)
Snapshot is good. The snapshot is byte-identical to the current file (verbatim copy taken before any edit). A snapshot shorter than the live file is itself suspect — quarantine and retake.
Retention discipline holds for the touched base files: at most the 3 most-recent good backups in _resources/ root; older in _resources/_archive/; any *TRUNCATED* file in _resources/_quarantine/ (never a restore source).
RESTORE_INDEX.md is current — it names the known-good latest backup for every touched base file. The newest backup by timestamp is not necessarily the newest good one.