Persona Reaction Panel
Pre-simulate how a defined set of role-based personas will react to an internal comms, launch, or enablement artefact before it ships. Use when the user asks to "run the persona panel", "pressure-test this comms against our personas", "QA this launch email/deck before it goes out", "how will each team react to this", or wants persona- and domain-level feedback on a broad internal artefact. Requires a personas file — bring your own (see references/personas.template.md). Do NOT use for 1:1 private comms, HR/performance matters, or legal/contractual language.
Install
npx skills add microsoft/cat-agent-skills --skill persona-reaction-panelgit clone --depth 1 https://github.com/microsoft/cat-agent-skills.git /tmp/cat-agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/cat-agent-skills/submissions/persona-reaction-panel ~/.claude/skills/persona-reaction-panelPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Persona Reaction Panel Simulate how each defined persona will react to the user's draft artefact, then synthesise domain-level risks and concrete edits, ending with a SHIP / REVISE / HOLD verdict. **Personas file (required):** load the user's personas file from `references/` (or the path the user provides). Each persona provides: role / what they do, motivations, pain points, how the tool or change helps them, comms anchors, and a confidence flag (fully defined or draft). Personas are grouped into domains. If no completed personas file is available, stop and ask the user to supply one (`references/personas.template.md` is the blank template — do not run the panel against the template's example personas). **Scope guard:** if the artefact is a 1:1 private communication, an HR/performance matter, or legal/contractual language, decline and state why. Only react to a draft the user supplies — do not write one. ## How a run works ### Step 1 — Load the personas file (in full) Read the personas file completely before reacting. It is the ONLY source of truth for how each persona responds — never simulate from memory or generic assumptions. ### Step 2 — Read the artefact Read the draft in full. Identify: what is asked, what is claimed, what is implied, what is left out, the audience it assumes, and which of the user's domains it actually serves. ### Step 3 — Per-persona reaction (repeat for each persona)
Details
- Skill name
persona-reaction-panel- Repository
- microsoft/cat-agent-skills
- Path
submissions/persona-reaction-panel/SKILL.md- License
- MIT
- Repo updated
- 15 November 2026
FAQ
What does the Persona Reaction Panel skill do?
Pre-simulate how a defined set of role-based personas will react to an internal comms, launch, or enablement artefact before it ships. Use when the user asks to "run the persona panel", "pressure-test this comms against our personas", "QA this launch email/deck before it goes out", "how will each team react to this", or wants persona- and domain-level feedback on a broad internal artefact. Requires a personas file — bring your own (see references/personas.template.md). Do NOT use for 1:1 private comms, HR/performance matters, or legal/contractual language.
How do I install the Persona Reaction Panel skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add microsoft/cat-agent-skills --skill persona-reaction-panel. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Persona Reaction Panel popular?
It lives in microsoft/cat-agent-skills, which has 110 GitHub stars and 122 forks.
Related skills
3 Statements
110microsoft/cat-agent-skills
Completes existing income statement, balance sheet and cash flow templates while preserving layout, grounding historical inputs and linking forecast formulas with reconciliation checks. Use for "fill in a 3-statement template", "complete an IS/BS/CF framework", "populate my integrated financial model", "link statements in this template", or "finish the forecasts in my three-statement workbook". Do NOT use for blank-slate models or general workbook edits (use xlsx), DCF valuation (use dcf-valuation), or buyout modeling (use lbo-model).
Accessibility Pass
110microsoft/cat-agent-skills
Use this skill whenever the user asks to check, review, or fix the accessibility of a PowerPoint deck, Word document, HTML page, or Markdown file, and before handing over any deck or document this agent just generated, so it does not ship with missing alt text, untitled slides, or unreadable colour contrast.
Accessible Learning Materials
110microsoft/cat-agent-skills
Maintains instructionally equivalent, accessible variants of a set of learning materials — lessons, readings, slides, and handouts — with parity checks against the original learning goals and recorded approvals. Use when the user asks to "make these materials accessible", "audit this lesson set for accessibility", "create an accessible version of this reading", "check reading level and alt text", or "keep my accessible variants in sync". Do NOT use for individual student accommodation or support-plan decisions (IEP, EHCP, or local equivalent), and do NOT use for generic document formatting (us
Wcag Power Platform
110microsoft/cat-agent-skills
Ensure web apps, HTML pages, and Power Platform components meet WCAG 2.1 accessibility guidelines. Use this skill WHENEVER building, reviewing, or refactoring any web UI or Power Platform artifact — standalone HTML/CSS/JS pages, websites and single-page apps, React/web artifacts, PCF (PowerApps Component Framework) controls, HTML/JS web resources, model-driven apps and forms, canvas apps, or Power Pages — even if the user does not say "accessibility". Trigger on requests to create pages or components, build forms, style UI, add buttons/inputs/grids/charts, theme an app, apply a Power Apps mode
Lesson Cluster
110microsoft/cat-agent-skills
Clusters cited decisions and retrospective inputs into ranked lesson themes with the deterministic lesson_cluster engine, after asset-identify and before sanitize-check. Use when the user asks for "lessons learned", "cluster the retrospective", "what did we learn?", "group the closeout lessons", "theme the decision log" or "rank the lessons by priority". Do NOT use for loading raw sources (use artifact-assemble), scoring assets (use asset-identify), deciding whether a lesson may be shared or rewriting named-person blame (use sanitize-check), drafting the final narrative (use knowledge-record)
Acceptance Pipeline Feature Design
228pproenca/dot-skills
Designs new features, extensions, or modifications to Uncle Bob's Acceptance Pipeline Specification — new mutation strategies, Gherkin syntax support, report formats, pipeline stages, IR fields, or handler patterns. Trigger when someone asks "how would I add X to the acceptance pipeline" or discusses spec-level changes to the parser, generator, runtime, mutator, or reporter components — even if they don't explicitly say "feature design." Works in tandem with the acceptance-pipeline-catalog skill, which provides the baseline spec reference.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.