feat: add 27 new skills across 7 professions — 80 skills, 21 plugins (v5.0.0)
This commit is contained in:
mohitagw15856
@@ -0,0 +1,13 @@
|
||||
{
|
||||
"$schema": "https://anthropic.com/claude-code/plugin.schema.json",
|
||||
"name": "pm-cross",
|
||||
"version": "1.0.0",
|
||||
"description": "Cross-profession skills: Press Release, Grant Proposal, Executive Summary. Write journalist-ready press releases, structure grant applications aligned to funder priorities, and produce decision-ready executive summaries for any audience.",
|
||||
"author": {
|
||||
"name": "Mohit Aggarwal",
|
||||
"email": "mohit15856@gmail.com"
|
||||
},
|
||||
"homepage": "https://github.com/mohitagw15856/pm-claude-skills",
|
||||
"license": "MIT",
|
||||
"keywords": ["communications", "press-release", "grant", "executive-summary", "briefing", "funding", "media"]
|
||||
}
|
||||
@@ -0,0 +1,98 @@
|
||||
---
|
||||
name: executive-summary
|
||||
description: "Write an executive summary for any document, report, or proposal. Use when asked to write an executive summary, management summary, briefing paper, or one-pager for senior stakeholders. Produces a structured summary that busy executives can read in under 3 minutes and act on."
|
||||
---
|
||||
|
||||
# Executive Summary Skill
|
||||
|
||||
Writes executive summaries that busy decision-makers actually read — front-loaded with conclusions, structured for skimming, ruthless about what to include.
|
||||
|
||||
## Required Inputs
|
||||
- **Source document or topic** (paste or describe)
|
||||
- **Audience** (CEO / board / investor / minister / client / committee)
|
||||
- **Decision or action needed** (what should the reader do after reading?)
|
||||
- **Length limit** (1 page / 2 pages / 500 words)
|
||||
- **Format** (formal report / slide / email / briefing paper)
|
||||
|
||||
## Core Principle
|
||||
|
||||
An executive summary is NOT a summary of the document. It is a standalone document that:
|
||||
- States the conclusion upfront — not at the end
|
||||
- Contains only what the reader needs to make a decision
|
||||
- Can be understood without reading anything else
|
||||
- Recommends a specific action
|
||||
|
||||
## Output Structure
|
||||
|
||||
---
|
||||
|
||||
### [Title]
|
||||
**Executive Summary**
|
||||
*Prepared for: [Audience] | Date: [Date] | Author: [Name]*
|
||||
|
||||
---
|
||||
|
||||
**Bottom line up front:**
|
||||
[The most important thing. The recommendation or finding. 2-3 sentences. A reader who only reads this should know what you are asking or telling them.]
|
||||
|
||||
---
|
||||
|
||||
**Background (why this matters):**
|
||||
[2-3 sentences. Minimum context to understand the bottom line. Not the history — just what the reader needs now.]
|
||||
|
||||
---
|
||||
|
||||
**Key findings / analysis:**
|
||||
- **[Finding 1]:** [One sentence — specific and evidence-based]
|
||||
- **[Finding 2]:** [One sentence]
|
||||
- **[Finding 3]:** [One sentence]
|
||||
|
||||
---
|
||||
|
||||
**Options considered:** (include only if a decision is being presented)
|
||||
|
||||
| Option | Benefit | Risk | Recommendation |
|
||||
|---|---|---|---|
|
||||
| [Option A] | [Benefit] | [Risk] | Recommended |
|
||||
| [Option B] | [Benefit] | [Risk] | Not recommended |
|
||||
|
||||
---
|
||||
|
||||
**Recommendation:**
|
||||
[Specific. "We recommend [action] because [reason]. This will [outcome]." Not "we suggest consideration of options."]
|
||||
|
||||
---
|
||||
|
||||
**Immediate next steps:**
|
||||
- [Action 1 — specific, with owner and date]
|
||||
- [Action 2]
|
||||
|
||||
---
|
||||
|
||||
**Risks of inaction:** [What happens if the reader does nothing]
|
||||
|
||||
**Full report:** [Reference to where the full document can be found]
|
||||
|
||||
---
|
||||
|
||||
## Adapting for Different Audiences
|
||||
|
||||
**CEO/MD:** Lead with financial or strategic impact. 1 page. Make the decision binary. Ask in sentence one.
|
||||
**Board:** Lead with governance or risk. Frame against organisational objectives. State specifically what you need from them.
|
||||
**Investor:** Lead with return or opportunity. Specific numbers. 1 page. Anticipate "why now."
|
||||
**Minister/senior public sector:** Lead with public benefit or policy alignment. Include cost-benefit framing.
|
||||
**Client:** Lead with their problem. Show you understand before presenting recommendation.
|
||||
|
||||
## Quality Checks
|
||||
- Bottom line in first 3 sentences
|
||||
- Standalone — no need to read full document
|
||||
- Recommendation is specific
|
||||
- Fits length limit
|
||||
- Written for audience priorities not author priorities
|
||||
- Next steps have owners and dates
|
||||
|
||||
## Example Trigger Phrases
|
||||
- "Write an executive summary of this report: [paste]"
|
||||
- "Summarise this document for the board: [paste]"
|
||||
- "Create a one-pager from this proposal for the CEO"
|
||||
- "Turn these findings into an exec summary"
|
||||
@@ -0,0 +1,99 @@
|
||||
---
|
||||
name: grant-proposal
|
||||
description: "Write a structured grant proposal or funding application for any grant type. Use when asked to write a grant proposal, funding application, research grant, charitable grant, or innovation fund application. Produces a complete proposal with project summary, rationale, methodology, impact, and budget narrative."
|
||||
---
|
||||
|
||||
# Grant Proposal Skill
|
||||
|
||||
Produces structured grant proposals tailored to the funder priorities — the most common reason grants fail is writing about what you want to do rather than what the funder wants to fund.
|
||||
|
||||
## Required Inputs
|
||||
- **Funder name and grant programme**
|
||||
- **Grant amount sought**
|
||||
- **Project description** (rough notes are fine)
|
||||
- **Your organisation** (type, track record, capacity)
|
||||
- **Funder stated priorities** (copy from their guidance — essential)
|
||||
- **Word or page limits**
|
||||
- **Deadline**
|
||||
|
||||
## Output Structure
|
||||
|
||||
---
|
||||
|
||||
### Project Title
|
||||
[Informative and memorable. Should convey the problem being solved and the approach.]
|
||||
|
||||
### 1. Project Summary / Abstract (200-300 words — written last, placed first)
|
||||
[What you will do, why it matters, who will benefit, measurable outcomes. Every sentence earns its place.]
|
||||
|
||||
### 2. Problem Statement / Need
|
||||
- **The problem:** [Specific, evidenced — use data]
|
||||
- **Who is affected:** [Population, scale, geography]
|
||||
- **Current situation:** [What exists and why it is insufficient]
|
||||
- **Consequence of inaction:** [What happens if not funded]
|
||||
- **Why your organisation:** [Track record, relationships, expertise]
|
||||
|
||||
Funder test: does this problem align with [funder] stated priorities? Make the connection explicit.
|
||||
|
||||
### 3. Project Objectives
|
||||
3-5 SMART objectives:
|
||||
- **Objective 1:** [Specific, Measurable, Achievable, Relevant, Time-bound]
|
||||
|
||||
### 4. Methodology / Approach
|
||||
|
||||
**Phase 1: [Name]** (Months 1-X)
|
||||
[What will happen, who will do it, what is produced]
|
||||
|
||||
**Key activities:**
|
||||
- [Activity — specific]
|
||||
|
||||
**What makes this approach innovative or effective:** [Why this over alternatives]
|
||||
|
||||
### 5. Impact and Outcomes
|
||||
|
||||
| Level | Description | Measure |
|
||||
|---|---|---|
|
||||
| Output | [Tangible deliverable] | [How counted] |
|
||||
| Short-term outcome | [Immediate change] | [How measured] |
|
||||
| Medium-term outcome | [Behaviour change] | [How measured] |
|
||||
| Long-term impact | [Systemic change] | [How evidenced] |
|
||||
|
||||
**Direct beneficiaries:** [Who and how many]
|
||||
**Sustainability:** [How work continues beyond grant period]
|
||||
|
||||
### 6. Evaluation Plan
|
||||
- Who evaluates, how, when, what is measured, how findings are shared
|
||||
|
||||
### 7. Budget Narrative
|
||||
|
||||
| Budget line | Amount | Justification |
|
||||
|---|---|---|
|
||||
| Staff costs | £[amount] | [Role, % FTE, duration, salary] |
|
||||
| Travel | £[amount] | [Specific journeys named] |
|
||||
| Equipment | £[amount] | [Itemised] |
|
||||
| Indirect costs | £[amount] | [[X]% of direct — check policy] |
|
||||
| **Total** | **£[total]** | |
|
||||
|
||||
**Value for money:** [Cost per beneficiary. What could not be done without this grant]
|
||||
|
||||
### 8. Organisational Capacity
|
||||
[Track record of similar projects, governance, financial management. Name previous grants and outputs — be specific]
|
||||
|
||||
### 9. Risk Register
|
||||
|
||||
| Risk | Likelihood | Impact | Mitigation |
|
||||
|---|---|---|---|
|
||||
| [Risk] | H/M/L | H/M/L | [Specific mitigation] |
|
||||
|
||||
---
|
||||
|
||||
## Funder Alignment Check
|
||||
- Every section explicitly references funder stated priorities
|
||||
- Word limits respected
|
||||
- Budget aligns with eligible costs policy
|
||||
- Required attachments prepared
|
||||
|
||||
## Example Trigger Phrases
|
||||
- "Write a grant proposal for [project] applying to [funder]"
|
||||
- "Help me write a funding application for [grant programme]"
|
||||
- "Turn these project notes into a grant proposal: [paste]"
|
||||
@@ -0,0 +1,71 @@
|
||||
---
|
||||
name: press-release
|
||||
description: "Write a professional press release for any announcement. Use when asked to write a press release, media announcement, news release, or press statement. Produces a structured press release with headline, dateline, body, boilerplate, and media contact — ready to send to journalists."
|
||||
---
|
||||
|
||||
# Press Release Skill
|
||||
|
||||
Writes press releases that journalists actually read — structured around the news angle, not the desire to promote.
|
||||
|
||||
## Required Inputs
|
||||
- **The news** (what is actually happening — be specific)
|
||||
- **Company name**
|
||||
- **Date of announcement / embargo date**
|
||||
- **Key quote** (from which executive and approximately what they want to say)
|
||||
- **Why this matters** (to the reader, not the company)
|
||||
- **Target media** (trade / national / local / consumer / investor)
|
||||
- **Media contact details**
|
||||
|
||||
## Output Structure
|
||||
|
||||
---
|
||||
|
||||
FOR IMMEDIATE RELEASE / EMBARGOED UNTIL: [Date and time]
|
||||
|
||||
---
|
||||
|
||||
# [Headline — active verb, specific news, under 10 words]
|
||||
## [Subheadline — the so-what in one sentence, adds context not repetition]
|
||||
|
||||
**[City, Date]** — [Opening paragraph: Who, What, When, Where, Why in 2-3 sentences. A journalist should be able to run this paragraph alone. No background, no context, no company history.]
|
||||
|
||||
[Second paragraph: the significance. Why does this matter? What does it mean for customers or the industry?]
|
||||
|
||||
[Third paragraph: quote from executive. Human and specific. Not a restatement of the headline.]
|
||||
|
||||
"[Quote text — specific, adds something the facts do not say]," said [Name], [Title] at [Company]. "[Second sentence extending the thought]."
|
||||
|
||||
[Fourth paragraph: supporting detail — data, customer names with permission, additional context]
|
||||
|
||||
[Fifth paragraph optional: what happens next, when it goes live, what people can do]
|
||||
|
||||
---
|
||||
|
||||
ENDS
|
||||
|
||||
---
|
||||
|
||||
**Notes to editors:**
|
||||
|
||||
**About [Company]**
|
||||
[Boilerplate: 3-4 sentences. What the company does, when founded, where based, key facts. Factual not promotional.]
|
||||
|
||||
**Media contact:**
|
||||
[Name] | [Title] | [Email] | [Phone] | [Hours/timezone]
|
||||
|
||||
---
|
||||
|
||||
## Headline Rules
|
||||
- Active voice: "Company launches X" not "X is launched by Company"
|
||||
- Specific: "raises 5M" not "secures significant investment"
|
||||
- Under 10 words
|
||||
- Never start with the company name — lead with the news
|
||||
|
||||
## Journalist Test
|
||||
Would a journalist care? Is the headline the full story? Is there a human angle? Is the quote something a human would say? Can the first paragraph stand alone?
|
||||
|
||||
## Example Trigger Phrases
|
||||
- "Write a press release announcing [news]"
|
||||
- "Draft a media statement about [event]"
|
||||
- "We are launching [product] — write the press release"
|
||||
- "Turn this announcement into a press release: [paste notes]"
|
||||
Reference in New Issue
Block a user