candidate-voice

スター2

フォーク0

更新日2026年6月25日 02:50

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.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

dudarenok-maker

dudarenok-maker/executive-application-helper

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

関連職種SOC

SOC 職業分類に基づく

人事スペシャリストビジネス・金融業務職·SOC 13-1071

ファイルエクスプローラー

4 ファイル

SKILL.md

readonly

このリポジトリの他の Skills

同じリポジトリ

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

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

pace-audit

dudarenok-maker/executive-application-helper

Run an honest timing audit on the spoken responses in the candidate's interview-prep documents, at the candidate's actual measured speaking pace — never at the generic 165 wpm executive baseline. Use this skill whenever a speaking-notes addendum or prep document with spoken responses is about to be delivered, AND after every content reshape or tightening pass (timing drifts with every edit). Also use when [Candidate First Name] asks 'how long does this run', 'time these responses', 'am I over budget', or 'run the pace check'. The audit is mechanical (~10–30 sec): word count ÷ actual wpm vs the format's time budget, with a two-pass tightening plan for any response that runs over.

2026-06-252

name

candidate-voice

description

Candidate Voice — written voice, spoken voice, and interview-prep structure

Setup note: This is a template skeleton. At setup, populate the three reference files from the candidate's completed style guides (Setup Orchestrator Phase 2 produces them), and replace [Candidate Name] / [Candidate First Name] placeholders throughout. Rename the skill if you prefer (e.g. jane-voice) — update the name: field and the references to it in Project_Instructions.md.

This skill is the canonical home for the candidate's voice and structural templates. Three modes:

Mode 1 — Writing voice (APPLY / AUDIT)

For any written deliverable the candidate will sign. Load references/style-guide.md and apply it as the style baseline: tone register, sentence rhythm, banned constructions, evidence-first discipline, fit-acknowledgment style. In AUDIT mode, mark deviations with exact quotes and proposed rewrites.

Mode 2 — Interview voice (spoken delivery)

For spoken-response drafting and rehearsal. Load references/interview-style-guide.md. It carries voice consistency from the writing guide plus spoken-delivery adjustments: pause markers, spoken cadence, drop lists, and the timing discipline at the candidate's actual measured words-per-minute.

Mode 3 — Interview-prep structure

For generating a prep document. Load references/interview-prep-template.md — the canonical eight-section structure (front-matter, executive summary, opening script, likely-questions table, STAR responses, practicalities, calibrated questions for the panel, sources).

Reference files

File	Populate from
`references/style-guide.md`	The candidate's Writing Voice and Style Guide (Setup Phase 2)
`references/interview-style-guide.md`	The candidate's Interview Voice and Style Guide
`references/interview-prep-template.md`	The framework's Interview Prep Template, calibrated to the candidate

Keep this skill as the single source of truth for voice content. If stub pointer files exist at the workspace root for discoverability, they must point here — never carry divergent copies.