Prepares a change request pack (description and justification, scope, schedule, implementation plan, risk as stated, rollback, test evidence as provided, communications, approvals route) from an engineer's notes, ticket or pull request description, with UNKNOWN for anything not provided and a question list for the engineer. Never rates risk or marks a change tested or approved. Use when the user asks to "write the change request for this", "fill in the change ticket from my notes", "prepare the CAB submission" or "turn this pull request into an RFC". Do not use for the step-by-step procedure with commands and rollback, use runbook-drafter instead; for release notes describing what shipped, use release-notes-writer. Drafts for human review; never approves, authorises or signs off.
Reviews a proposal, business case, deck, plan or restructuring paper in character as a Chief Human Resources Officer archetype and returns a DRAFT review with a verdict, findings that cite the exact passage, people and organisation risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CHRO review", "what would HR say about this", "pressure-test the people impact" or "prepare this for the people committee". Do not use for the employee representatives' own view of a plan, use works-council-reviewer instead. Drafts for human review; never approves, authorises or signs off.
Reviews a proposal, business case, deck or plan in character as a Chief Information Security Officer archetype and returns a DRAFT review with a verdict, findings cited to specific passages, security and compliance risks and the five interrogation questions a real CISO would ask. Use when the user asks to "run a CISO review", "pressure-test the security of this plan", "what would our CISO say about this" or "check the privacy and third-party risk". Do not use for contract, liability or regulatory-interpretation reviews, use general-counsel-reviewer instead. Drafts for human review; never approves, authorises or signs off.
Builds an evidence map for one document, section or contested claim: every factual claim extracted verbatim and numbered, its supporting passage in the supplied sources or UNKNOWN, the strength of that support as evidenced, contradictions between sources, and the specific question or document that would close each gap, returned in the chat as Markdown tables for the author or reviewer. Use when the user asks to "check what this document actually proves", "map the evidence behind these claims", "which of these statements are supported", "build an evidence map", "what would we need to back this up" or "is this claim substantiated". Do not use for requesting evidence of security controls from control owners, use control-evidence-request-pack instead. Drafts for human review; never approves, authorises or signs off.
Compares one clause (liability, termination, confidentiality or any other) across several contracts, templates or successive versions and returns a DRAFT comparison table: verbatim clause text per document, the clause split into elements with every difference from the baseline highlighted and categorised, and neutral questions for counsel. Never says which wording is better or enforceable. Use when the user asks to "compare the liability caps across these five supplier contracts", "line up the termination clause in these three drafts", "show how the confidentiality clause changed between versions", "contrast this clause with our template" or "benchmark the indemnity wording across our customer agreements". Do not use for a whole-contract review, use contract-review-pack instead; for screening one NDA against standard positions, use nda-triage. Drafts for human review; never approves, authorises or signs off.
Reviews a proposal, business case, deck or plan in character as a Chief Marketing Officer archetype and returns a DRAFT review in the chat with a verdict, findings cited to specific passages, marketing risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CMO review", "pressure-test the positioning", "what would a CMO say about this", "challenge the launch plan" or "check the messaging and audience". Do not use for price economics, margins or payback, use cfo-reviewer instead; for sales pipeline mechanics, use cro-reviewer. Drafts for human review; never approves, authorises or signs off.
Sweeps the last 24 hours of email, chat messages and meeting transcripts for commitments in both directions, what the user promised others and what others promised the user, reconciles them against a running commitments ledger (open, done, overdue), lists overdue items first and returns the updated ledger plus a proposed task list as Markdown for the user to save. Use when the user asks to "check my commitments", "what did I promise", "what am I owed", "did anything slip" or "run the commitment sweep". Do not use for a general morning summary of mail, calendar and mentions, use custom-daily-brief instead. Drafts for human review; never approves, authorises or signs off.
Pre-tests one message (email, announcement, intranet post, town hall script, customer notice or slide) against two to six role personas the user supplies and returns a DRAFT panel report: each persona's likely first reaction, objections, unanswered questions, misreadings and what they would do next, every point tied to the passage that triggers it, plus suggested edits that add no fact the message does not already hold. Use when the user asks to "pre-test this message", "how will the team read this", "run this past the personas", "what objections will this raise", "find the holes before I send" or "check this lands with managers and field staff". Do not use for an in-character review of a proposal or business case by one executive archetype, use the executive-review family (cfo-reviewer, frontline-skeptic-reviewer and siblings) instead; to write the message in the first place, use announcement-drafter. Drafts for human review; never approves, authorises or signs off.
Builds a DRAFT content calendar for a stated period from the themes, channels, cadence rules, fixed dates and owners the user provides: one dated row per planned item with theme, channel, format, working title, owner, status and source, plus a cadence check with its arithmetic, theme balance, owner load and the slots left open. Use when the user asks to "build the content calendar for Q4", "lay these themes onto dates", "plan a month of posts across our channels", "extend the editorial calendar" or "check this calendar against our cadence". Do not use for deciding what the campaign says or why it runs, use campaign-brief-builder instead; for writing the items themselves, use announcement-drafter or internal-newsletter-drafter. Drafts for human review; never approves, authorises or signs off.
Reads a contract list (spreadsheet, CSV or pasted table) and returns a DRAFT renewal radar: each active contract's end date, notice deadline with its arithmetic, days remaining, renewal type, owner and the decision it needs as options, sorted by urgency, with owner action lists and a deadline calendar. Never renews, terminates, serves notice or recommends. Use when the user asks to "build a renewal tracker", "tell me what comes up for renewal", "work out when notice is due", "show me which contracts auto-renew" or "run the quarterly contract review". Do not use for reviewing one contract's full text or clauses, use contract-review-pack instead. Drafts for human review; never approves, authorises or signs off.
Abstracts one contract into a key-terms table with clause references, compares each term against the user's playbook of standard positions, and returns a DRAFT contract review pack: deviations and issues, open questions and a reviewer checklist. Flags governing law and never gives legal advice or enforceability or acceptability calls. Use when the user asks to "review this contract", "abstract the key terms", "summarise this MSA", "pressure-test this SOW against our playbook" or to compare an agreement with their standard positions. Do not use for a first pass on a stand-alone NDA, use nda-triage instead, or for one clause lined up across several documents, use clause-comparison-table instead. Drafts for human review; never approves, authorises or signs off.
Turns a control list and an audit scope into draft evidence requests grouped by control owner, each with the control as stated, the audit period, evidence examples (commonly requested) and a proposed due date derived from the fieldwork dates. Never judges whether evidence is sufficient, never selects the sample and never sends a request; the auditor decides. Use when the user asks to "prepare the evidence requests", "draft the PBC list", "build the evidence request pack for the audit" or "what do we need to ask each control owner for". Do not use for document requests and interview questions built from an audit plan, use audit-prep-pack instead; to check claims in a report against sources, use claims-evidence-map. Drafts for human review; never approves, authorises or signs off.
Produces a draft controls and gap pack from a requirement, regulation, standard or policy and the organisation's control descriptions: obligations broken out of the source text, the controls that appear to address each, apparent coverage, gaps, questions for control owners and actions to assess. Never concludes compliance or that a control is effective; owners and audit assess. Use when the user asks to "map this regulation to our controls", "run a controls gap analysis", "break this standard into obligations" or "where is our control coverage thin". Do not use for comparing a policy document against a standard, use policy-gap-review instead; to draft evidence requests from the mapped controls, use control-evidence-request-pack. Drafts for human review; never approves, authorises or signs off.
Reviews a proposal, business case, deck or plan in character as a Chief Operating Officer archetype and returns a DRAFT review in the chat with a verdict, findings cited to specific sections, delivery and operational risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a COO review", "pressure-test the delivery plan", "what would our COO say about this", "check the timeline and capacity" or "find the execution gaps before the steering committee". Do not use for financial questions, use cfo-reviewer instead; for architecture or vendor questions, use cto-reviewer. Drafts for human review; never approves, authorises or signs off.
Turns corrective and preventive actions from NCRs, audit reports, action forms, minutes or a tracker into one DRAFT tracker: action as stated, source, owner, due date, evidence expected and status, with flags for overdue, unowned, undated, stale and closed-without-evidence items and one question per flag. Never closes, verifies, reassigns or re-dates an action. Use when the user asks to "build the CAPA tracker", "update the corrective action log from these audit reports", "which actions are overdue or have no owner" or "draft the chase notes for open actions". Do not use for writing up the nonconformity itself, use nonconformance-report-drafter instead. Drafts for human review; never approves, authorises or signs off.
Reviews a proposal, business case, deck or product plan in character as a Chief Product Officer archetype and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, product and adoption risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CPO review", "pressure-test this product plan", "what would a CPO say about this", "challenge the user evidence" or "check the roadmap opportunity cost". Do not use for positioning, messaging or launch marketing, use cmo-reviewer instead; for internal staff adoption of a rollout, use frontline-skeptic-reviewer; for what a change asks of paying customers, use customer-advocate-reviewer. Drafts for human review; never approves, authorises or signs off.
Reviews a proposal, business case, deck, pricing plan, go-to-market plan or forecast in character as a Chief Revenue Officer archetype and returns a DRAFT review in the chat with a verdict, findings cited to exact passages, revenue risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CRO review", "pressure-test the revenue plan", "what would sales leadership say about this" or "challenge this forecast". Do not use for partnership, deal-structure or market-positioning reviews, use cbo-reviewer instead; for the finance seat use cfo-reviewer. Drafts for human review; never approves, authorises or signs off.
Reviews a proposal, business case, deck or plan in character as a Chief Technology Officer archetype and returns a DRAFT review in the chat with a verdict, findings cited to the exact passage, technology risks (architecture, build versus buy, vendor lock-in, security of design, engineering capacity), what would change the verdict and five interrogation questions. Use when the user asks to "run a CTO review", "pressure-test the technical side of this plan", "what would a CTO ask about this" or "rehearse the technology seat before the review". Do not use for cash, payback or budget questions, use cfo-reviewer instead; for capacity and timeline questions, use coo-reviewer; for security controls, privacy or compliance, use ciso-reviewer. Drafts for human review; never approves, authorises or signs off.
Builds a role-tuned morning brief as a dated Markdown document covering emails that need replies, today's calendar with conflicts flagged, chat mentions and upcoming deadlines, in the section order set by a preset (project manager, executive assistant, IT admin, sales or custom) read from an editable config. Use when the user asks to "run my brief", "give me my morning brief", "start-of-day summary", "switch my brief to the sales preset" or "change what my brief covers". Do not use for tracking promises made or owed across days, use commitment-catcher instead. Drafts for human review; never approves, authorises or signs off.
Reviews a proposal, business case, deck or plan in character as a Customer Advocate archetype, the seat for paying customers not in the room, and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, customer-side risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a customer advocate review", "do a voice-of-the-customer pressure-test", "what would our customers say about this" or "what does this plan really ask of paying customers". Do not use for the product evidence or roadmap case, use cpo-reviewer instead; for revenue or pricing strategy, use cro-reviewer; for the staff who operate the change, use frontline-skeptic-reviewer. Drafts for human review; never approves, authorises or signs off.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.
kesslernitySkill