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:
@@ -149,6 +149,14 @@ Ask the user for these if not provided:
|
||||
- [ ] Board asks are specific and actionable
|
||||
- [ ] Deck is ≤ 15 slides (excluding appendix)
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
- [ ] Do not bury bad news after slides full of good news — boards lose trust when they discover problems were de-emphasised; lead with the honest narrative
|
||||
- [ ] Do not include slides without a "so what" — a chart that shows data without a takeaway wastes board time and signals the presenter hasn't done the analysis
|
||||
- [ ] Do not exceed 15 slides in the main deck — a longer deck usually means the presenter hasn't decided what matters most
|
||||
- [ ] Do not attend a board meeting without at least one specific ask — a board meeting with no asks is a missed opportunity to leverage the room
|
||||
- [ ] Do not report metrics without comparing them to plan or a prior period — a metric shown in isolation gives the board no basis for judgement
|
||||
|
||||
## Example Trigger Phrases
|
||||
|
||||
- "Build a board deck structure for our Q[N] board meeting"
|
||||
|
||||
@@ -119,6 +119,14 @@ Hi [Investor names or "all"],
|
||||
- [ ] Total length is skimmable in 3–4 minutes
|
||||
- [ ] No spin or buzzwords
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
- [ ] Do not omit challenges or bad news — sanitised updates erode investor trust faster than bad results do
|
||||
- [ ] Do not bury the lead — use BLUF structure and put the most important news in the first paragraph
|
||||
- [ ] Do not send an update without a clear "Ask" section — investors who want to help need to know how
|
||||
- [ ] Do not use buzzwords or spin — investors see hundreds of updates and will see through vague positive language
|
||||
- [ ] Do not report metrics without a comparison baseline — numbers without context (vs. last period or target) are meaningless
|
||||
|
||||
## Example Trigger Phrases
|
||||
|
||||
- "Write an investor update for [month/quarter]"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: job-application
|
||||
description: "Tailor a CV and cover letter to a specific job description. Use when asked to write a cover letter, tailor a CV or resume, optimise for ATS, match a job description, or prepare a job application. Produces an ATS-optimised tailored CV summary and a personalised cover letter."
|
||||
description: "Tailors a CV and cover letter to a specific job description. Use when asked to write a cover letter, tailor a CV or resume, optimise for ATS, match a job description, or prepare a job application. Produces an ATS-optimised tailored CV summary and a personalised cover letter aligned to the role's requirements."
|
||||
---
|
||||
|
||||
# Job Application Skill
|
||||
@@ -120,6 +120,14 @@ Before submitting:
|
||||
- [ ] Cover letter is 250–350 words
|
||||
- [ ] Gaps are either addressed or strategically omitted
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
- [ ] Do not fabricate or embellish experience — only use real achievements from the provided CV
|
||||
- [ ] Do not use the same cover letter template for every role — every letter must reference specific details of the job description
|
||||
- [ ] Do not address selection criteria that aren't in the JD — match keywords the employer actually used
|
||||
- [ ] Do not omit ATS optimisation — ensure role-specific keywords from the JD appear naturally in the CV summary
|
||||
- [ ] Do not write a cover letter that re-summarises the CV — it must add context and motivation, not repeat bullet points
|
||||
|
||||
## Example Trigger Phrases
|
||||
|
||||
- "Help me apply for this job: [paste JD]"
|
||||
|
||||
Reference in New Issue
Block a user