skills/briefing-note/SKILL.md
Write a one-page briefing note that gets a busy principal up to speed fast. Use when asked to brief a minister/executive/official, prepare a briefing note or read-ahead, or summarize an issue for a decision or meeting. Produces a tight, single-page note: purpose, background, key facts/considerations, and a recommendation or the decision sought — scannable in two minutes.
npx skillsauth add mohitagw15856/pm-claude-skills briefing-noteInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
A briefing note gets a principal ready for a decision, a meeting, or a question — on one page, in two minutes. It's ruthlessly concise: purpose, the few facts that matter, the considerations, and what's being asked. This skill writes that note in the standard structure officials and executives expect.
Ask for these only if they aren't already provided:
Date · Prepared for · Purpose: [for decision / for information / for meeting on DATE]
Issue — one or two lines: what this is about and why it's in front of them now.
Background — the minimum context needed, as tight bullets (dates, decisions to date, who's involved). No history for its own sake.
Key considerations — the factors that matter to the decision or discussion: facts, risks, sensitivities (financial, legal, political, reputational), stakeholder positions. Bullets, not prose.
Recommendation / decision sought — if for decision: the recommended action and one-line rationale. If for information/meeting: the key messages or the line to take, and likely questions with suggested answers.
Contact — who to follow up with.
Keep it to one page. Detail belongs in an annex, referenced not included.
Government/executive briefing-note practice (purpose-led, one page, key considerations, decision-or-line-to-take).
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.