fix(plugins): sync all 171 plugin SKILL.md files with fixed skills/ versions
Propagates Anti-Patterns sections, description rewrites, Required Inputs additions, and Quality Checks format fixes from skills/ to matching plugin SKILL.md copies. https://claude.ai/code/session_01MuGKn3a3Gbqoe8uM5Lmuqt
This commit is contained in:
Mohit
@@ -84,12 +84,21 @@ An executive summary is NOT a summary of the document. It is a standalone docume
|
||||
**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
|
||||
|
||||
- [ ] 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
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
- [ ] Do not summarise the document chronologically — an executive summary that follows the structure of the source document is not an executive summary, it is an abstract
|
||||
- [ ] Do not bury the recommendation at the end — executives read the first paragraph and skim the rest; the ask must be in sentence one or two
|
||||
- [ ] Do not use the same summary for different audiences — a CEO and a board member have different decision contexts and require different framing
|
||||
- [ ] Do not include background that the reader already knows — every sentence of background must earn its place by making the bottom line more actionable
|
||||
- [ ] Do not leave the "risks of inaction" section vague — a summary that does not quantify what happens if the reader does nothing removes the urgency needed for a decision
|
||||
|
||||
## Example Trigger Phrases
|
||||
- "Write an executive summary of this report: [paste]"
|
||||
|
||||
@@ -96,6 +96,14 @@ Funder test: does this problem align with [funder] stated priorities? Make the c
|
||||
- [ ] Sustainability section explains what happens after the grant ends
|
||||
- [ ] Word limits respected
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
- [ ] Do not write a generic proposal — every section must be tailored to the specific funder's stated priorities
|
||||
- [ ] Do not exceed the specified word or page limits — over-length proposals are disqualified at many funders
|
||||
- [ ] Do not leave the sustainability section vague — funders need to know what happens after grant funding ends
|
||||
- [ ] Do not use jargon the funder's reviewers won't understand — write for the panel, not the project team
|
||||
- [ ] Do not underspecify the budget narrative — every significant line item must be justified with method and reasoning
|
||||
|
||||
## Example Trigger Phrases
|
||||
- "Write a grant proposal for [project] applying to [funder]"
|
||||
- "Help me write a funding application for [grant programme]"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: last-30-days-research
|
||||
description: Multi-platform research skill that gathers recent (last 30 days) opinions, sentiment, and signal on any topic from Reddit, X/Twitter, and the web. Cuts through SEO-stuffed results to surface what real people are actually saying.
|
||||
description: "Searches Reddit, X/Twitter, and the broader web for recent opinions, sentiment, and signal on any topic. Use when you need to know what real people are saying about a tool, product, trend, or event in the past 30 days — cutting through SEO content to surface genuine community reaction. Produces a structured report with consensus findings, pain points, positive signals, contrarian takes, source links, and a signal confidence rating."
|
||||
---
|
||||
|
||||
# Last 30 Days Research
|
||||
@@ -138,6 +138,14 @@ Before outputting the report, verify:
|
||||
- [ ] No vendor-authored content or press releases treated as independent signal
|
||||
- [ ] Synonyms and alternative names for the topic were searched
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
- [ ] Do not treat SEO blog posts or vendor-authored content as community signal — only count independent sources
|
||||
- [ ] Do not report findings without applying the date filter — prior knowledge mixed with recent search results produces stale, unverifiable claims
|
||||
- [ ] Do not fabricate or guess at URLs — every link in the Sources section must have been retrieved during the research session
|
||||
- [ ] Do not report a single mention as a "finding" — a finding requires corroboration from at least two independent sources
|
||||
- [ ] Do not rate Signal Confidence as High when fewer than 5 credible sources were found — this misleads the reader about how much to rely on the output
|
||||
|
||||
## Example Trigger Phrases
|
||||
|
||||
- "What are people saying about Cursor AI from the last 30 days?"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: notebooklm-connector
|
||||
description: Automates NotebookLM from Claude Code — creates notebooks, adds sources, and triggers outputs (mindmaps, audio overviews, slide decks) without manual clicking via the Claude Chrome extension.
|
||||
description: "Automates NotebookLM from Claude Code using browser automation via the Claude Chrome extension — creating notebooks, adding sources, and triggering outputs without manual clicking. Use when you want to create a NotebookLM notebook, add URLs or documents as sources, or generate mindmaps, audio overviews, or briefing docs programmatically. Produces a confirmed checklist of completed actions and a direct link to the notebook."
|
||||
---
|
||||
|
||||
# NotebookLM Connector
|
||||
@@ -164,6 +164,14 @@ If any step fails, do the following:
|
||||
- [ ] Manual workaround was offered for any step that failed
|
||||
- [ ] Output checklist accurately reflects what was completed vs. what failed
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
- [ ] Do not proceed with any browser action before the full request has been parsed into discrete steps — ambiguous source references must be clarified before navigating
|
||||
- [ ] Do not guess at source URLs if the user says "add my research sources" without specifying them — ask for the explicit list before starting
|
||||
- [ ] Do not batch actions speculatively — each action must be confirmed complete before the next one begins to avoid compounding failures
|
||||
- [ ] Do not wait for audio overview rendering to complete — audio overviews take 5–15 minutes server-side; report the trigger and move on rather than blocking the session
|
||||
- [ ] Do not attempt this skill if the Claude Chrome extension is not active — report the missing prerequisite immediately rather than attempting browser steps that will fail
|
||||
|
||||
## Example Trigger Phrases
|
||||
|
||||
- "Open NotebookLM and create a notebook called 'Competitor Analysis Q2'"
|
||||
|
||||
@@ -72,6 +72,14 @@ Would a journalist care? Is the headline the full story? Is there a human angle?
|
||||
- [ ] Boilerplate is factual, not promotional
|
||||
- [ ] Embargo date and media contact are included
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
- [ ] Do not bury the news — the most important information must appear in the first paragraph (inverted pyramid)
|
||||
- [ ] Do not use promotional language or superlatives — press releases must read as news, not advertising copy
|
||||
- [ ] Do not omit the boilerplate — every press release needs the standard "About [Company]" paragraph at the end
|
||||
- [ ] Do not forget the embargo date and media contact — journalists need both to use the release
|
||||
- [ ] Do not write a headline longer than 12 words — it must be scannable and specific
|
||||
|
||||
## Example Trigger Phrases
|
||||
- "Write a press release announcing [news]"
|
||||
- "Draft a media statement about [event]"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: sycophancy-challenger
|
||||
description: Flips Claude's default from "find reasons you're right" to "find reasons you're wrong." A genuine thinking partner, not a mirror with grammar. Use before high-stakes decisions, plans, assumptions, or pitches you haven't stress-tested.
|
||||
description: "Flips Claude's default from validation to adversarial critique. Use before high-stakes decisions, plans, assumptions, or pitches you haven't stress-tested. Produces structured challenges, steelmanned counter-arguments, and the strongest case against your position — a genuine thinking partner, not a mirror."
|
||||
---
|
||||
|
||||
# Sycophancy Challenger
|
||||
@@ -143,6 +143,14 @@ These prohibitions do more work than the rules above. Follow them absolutely:
|
||||
|
||||
---
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
- [ ] Do not open with a softening phrase or acknowledgment before the challenge — the first sentence must be the critique
|
||||
- [ ] Do not retreat from a position when the user pushes back without providing new evidence — update only when genuinely persuaded
|
||||
- [ ] Do not invent flaws — every criticism must connect to something real in what the user described
|
||||
- [ ] Do not provide a list of weak objections — identify the single strongest case against the idea
|
||||
- [ ] Do not end the session because the user seems satisfied — end only when something genuinely changed or was defended
|
||||
|
||||
## Example Trigger Phrases
|
||||
|
||||
- "Use the sycophancy-challenger skill — here's my plan: [describe it]"
|
||||
|
||||
@@ -110,6 +110,14 @@ By the end of this session, participants will be able to:
|
||||
- [ ] Differentiation is specified for both support and extension
|
||||
- [ ] Timing adds up to session length
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
- [ ] Do not design a lesson plan without explicitly stating the learning objectives — activities must trace back to outcomes
|
||||
- [ ] Do not allocate timing that does not add up to the total session length — the plan must be time-feasible
|
||||
- [ ] Do not create activities with no assessment component — learning must be measurable, not just delivered
|
||||
- [ ] Do not ignore differentiation — a plan with no accommodation for different learning levels or abilities is incomplete
|
||||
- [ ] Do not front-load all content delivery without interactive breaks — passive listening degrades retention after 15–20 minutes
|
||||
|
||||
## Example Trigger Phrases
|
||||
|
||||
- "Write a lesson plan on [topic] for [audience]"
|
||||
|
||||
Reference in New Issue
Block a user