writing-skills 0.1.1

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Surendran
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,77 @@
+<p align="center">
+  <img src="logo.svg" alt="Writing Skills Logo" width="120" />
+</p>
+
+# Writing Skills 🖋️
+
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![PyPI](https://img.shields.io/pypi/v/writing-skills)](https://pypi.org/project/writing-skills/)
+[![npm](https://img.shields.io/npm/v/writing-skills)](https://www.npmjs.com/package/writing-skills)
+
+**Procedural writing-style skills for AI agents — official frameworks, not vibes.**
+
+Ready-made `SKILL.md` packages: plain language, business writing, corporate
+communication, GOV.UK, AP style, STE-100, dev docs — each with numbered mechanics
+and a **verifiable checklist** the agent must pass. Compatible with any agent that
+reads SKILL.md (opencode, Claude Code, Codex, Kiro, Gemini).
+
+## Skills
+
+### Frameworks
+
+| Skill | What it enforces |
+| :--- | :--- |
+| `plain-language` | Plain Writing Act clarity. Sentences ≤25 words, passive ≤10%, jargon ban list. |
+| `business-writing` | Executive comms. BLUF in the first line, explicit ask + deadline, buzzword ban list. |
+| `corporate-communication` | Company announcements. News first, reader impact explicit, zero euphemism. |
+| `gov-uk-style` | Public-sector readability. Keyword-first headings, ≤25-word sentences, ≤5-sentence paragraphs. |
+| `asd-ste100` | Safety-critical technical prose. One instruction per sentence, controlled vocabulary, no idioms. |
+| `google-dev-docs` | Developer documentation. Active voice, present tense, verb-first headings, runnable examples. |
+| `journalism-ap` | Factual reporting. AP attribution and number rules, zero editorializing. |
+
+### Voices
+
+`ted-lasso` · `jack-sparrow` · `shrek` · `yoda` · `winnie-the-pooh` · `paddington` · `bob-ross`
+
+## Install
+
+```bash
+npx skills add writing-skills      # installs into every detected agent (Claude Code, opencode, Codex, ...)
+npm install writing-skills         # or pip/uv: uv add writing-skills
+```
+
+`writing-skills` is also an Agent Plugins 1.0.0 package — Claude Code, Codex ≥ 0.147
+and Kiro discover `plugin.json` when you point them at the repo:
+
+```bash
+git clone https://github.com/surendranb/writing-skills.git
+```
+
+## Use
+
+Ask for a style and the skill loads automatically:
+
+> "rewrite this in plain language"
+> "make this a BLUF business update"
+> "write the press release in AP style"
+> "say it like Ted Lasso"
+
+Every framework skill ends with a `Verify` checklist (sentence caps, passive-voice
+scans, ban lists, readability targets) the agent must pass before delivering.
+
+## Contribute
+
+Add a skill as a folder under `skills/` with a `SKILL.md`:
+
+- `name` in frontmatter matching the folder; trigger-rich `description` starting with "Use when"
+- `## The core rule`, `## Mechanics` (numbered, verifiable), `## Do not`, and at least two before/after `## Transform example`s
+
+Validate locally:
+
+```bash
+python3 scripts/check_skills.py    # requires PyYAML
+```
+
+## License
+
+MIT — [Surendran B](https://github.com/surendranb). See [LICENSE](LICENSE).

package/package.json

@@ -0,0 +1,27 @@
+{
+  "name": "writing-skills",
+  "version": "0.1.1",
+  "description": "Procedural writing-style skills for agents — measurable standards, voice craft, and character voices as SKILL.md instructions.",
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/surendranb/writing-skills.git"
+  },
+  "files": [
+    "plugin.json",
+    "skills"
+  ],
+  "keywords": [
+    "agent-skills",
+    "writing",
+    "writing-style",
+    "plain-language",
+    "business-writing",
+    "corporate-communication",
+    "technical-writing",
+    "copywriting",
+    "voice",
+    "opencode",
+    "claude-code"
+  ]
+}

package/plugin.json

@@ -0,0 +1,19 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "writing-skills",
+  "version": "0.1.1",
+  "description": "Procedural writing-style skills for agents — measurable standards, voice craft, and character voices as SKILL.md instructions.",
+  "author": "Surendran",
+  "homepage": "https://github.com/surendranb/writing-skills",
+  "repository": "https://github.com/surendranb/writing-skills",
+  "license": "MIT",
+  "keywords": [
+    "agent-skills",
+    "writing",
+    "writing-style",
+    "voice",
+    "copywriting",
+    "opencode",
+    "claude-code"
+  ]
+}

package/skills/asd-ste100/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: asd-ste100
+description: Write controlled, unambiguous technical prose per ASD-STE100 Simplified Technical English — the aerospace standard for maintenance manuals and technical documentation. Use when the user writes technical procedures, instructions, warnings, manuals, or any text where every reader (including non-native English speakers) must understand exactly one meaning.
+---
+
+# ASD-STE100 (Simplified Technical English)
+
+One sentence, one instruction, one meaning. The standard for safety-critical documentation.
+
+## The core rule
+
+**Every sentence has exactly one interpretation — because every sentence has one instruction, one approved word, and no synonyms.** STE-100 trades elegance for certainty: writers cannot choose between "start", "begin", "activate", "commence" — they use the approved word and only the approved word.
+
+Workflow: `state the objective` → `write instructions as short imperative sentences` → `use only approved vocabulary, one meaning per word` → `separate warnings from actions` → `run the verification checklist`.
+
+## Mechanics
+
+1. **One instruction per sentence.** "Open the valve. Wait 30 seconds. Close the valve." Never chain ("open the valve, then after waiting, close it").
+2. **Sentences ≤ 20 words** (procedures); ≤ 25 for descriptions.
+3. **Imperative mood for procedures.** "Remove the cover." — direct commands only.
+4. **One meaning per word, always.** Approved technical terms mean one thing; never use a synonym in the same document. Pick "remove" and never "detach/unfasten/take off" for the same object.
+5. **Active voice, present tense.** "The pump moves the fluid" not "the fluid is moved by the pump".
+6. **No verbs derived from nouns** (make a decision → decide; perform an inspection → inspect).
+7. **Articles always required.** "The valve", "an adapter" — never bare "valve" where grammar allows dropping the article.
+8. **Warnings are exact and separate.** "WARNING: HIGH PRESSURE. Do not open the valve while the system is pressurized." Structure: warning keyword, hazard, consequence, instruction.
+9. **Numbers and units written exactly.** "6 mm", "100 °C" — spelled-out numbers only for 1–9 where the approved dictionary says so.
+10. **No idioms, no metaphor, no humor.** "It's the heart of the system" is banned. The reader may not share the culture.
+
+## Verify
+
+- Every sentence ≤ 20 words and contains exactly one instruction
+- Every sentence in active voice (no "was/were + past participle")
+- No synonyms for the same object/action anywhere in the document
+- No noun-verb constructions ("perform a test" → "test")
+- No idioms or metaphors (search for "like", "as if", figurative phrases)
+- Warnings follow the keyword-hazard-consequence-instruction shape
+
+## Do not
+
+- Chain instructions with "then/after/while" — split them
+- Use unapproved vocabulary for any safety-critical step
+- Assume a shared cultural or technical background with the reader
+
+## Example transformations
+
+**Before:** "Prior to commencing the disassembly process, ensure that the pressure has been completely relieved from the system, as failure to do so may result in the sudden and dangerous release of pressurized fluid which could cause serious injury or even death."
+
+**After:** "WARNING: HIGH PRESSURE. The fluid in the system is under pressure. If you open the system while it is pressurized, the fluid can spray out and cause injury. 1. Turn the system OFF. 2. Wait until the pressure gauge shows zero. 3. Open the drain valve."
+
+**Before:** "When you've finished, it's good practice to give the unit a quick check for any loose connections and make sure everything is nice and snug."
+
+**After:** "Check all connections. Tighten any loose connection. Make sure each connection is secure."

package/skills/bob-ross/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: bob-ross
+description: Write calm, soothing, gently instructional prose in the voice of Bob Ross. Use when the user wants encouraging guidance, mistakes reframed as opportunities, a serene step-by-step tone, or down-to-earth warmth for nervous readers.
+---
+
+# Bob Ross Voice
+
+Serene encouragement. Mistake = gift. Gentle instruction for a nervous room.
+
+## The core rule
+
+**Reframe every mistake as a happy little accident, and walk the reader forward with a calm, kind cadence.** The voice's power: it never lets a flaw be final. Nothing is ruined — something is just being discovered. Anxiety dissolves because the instructor is unflappable.
+
+Workflow: `acknowledge the wobble calmly ("it happens")` → `reframe it as an opportunity ("happy little accident")` → `show the fix as a simple next stroke` → `remind them it's their work and it's good`.
+
+## Mechanics
+
+1. **Reading the reader's shoulder.** Address the worry before it's said: "I know you think that's ruining it. It isn't."
+2. **Mistake-to-gift pipeline.** Every error gets a name ("happy little accident," "a chance for a friend to join the painting") — the reframe is specific, not generic positivity.
+3. **Stepwise calm.** One instruction at a time, delivered as if there is all the time in the world. Never "next, quickly."
+4. **Self-soothing cadence.** Slow, slightly repetitive rhythm; short sentences; encouraging tags ("and that's fine," "just let it do its thing").
+5. **Ownership with approval.** "It's your world... you can make it do anything you want" — but said with total confidence the reader's choices are good ones.
+6. **The verbs are light touches.** "Tap, tap, tap." Actions described as gentle motions.
+
+## Do not
+
+- Let urgency leak in — no rushing, no alarm
+- Reframe a *real* problem away; the mistake must be genuinely non-fatal, or acknowledge it plainly first
+- Stack empty positivity ("great job amazing work"); anchor every encouragement in something concrete
+
+## Example transformations
+
+**Neutral:** "Your first draft needs revision. Keep the good parts and rewrite the rest."
+
+**Bob Ross:** "You've got a first draft, and that's wonderful — every great painting starts with a sketch. Now, I see a couple of places where the words didn't land quite where you wanted. That's all right. That's just a happy little accident, and we're going to fix it together. We add a stroke here, a little more contrast there, and before you know it, it's saying exactly what you meant it to say. You just have to keep your brush moving."
+
+**Neutral:** "The launch didn't perform well; we'll adjust."
+
+**Bob Ross:** "The mountain you painted didn't come out the way you saw it in your mind. That happens to us all — and look, now you get to paint whatever you want on top of it. We take what worked, we add a few happy little clouds, and we've got a whole new sky. It's your world."
+
+**Neutral:** "Your code review found 14 issues."
+
+**Bob Ross:** "Fourteen little things, and every single one of them is a gift — someone cared enough to look closely. We'll take them one gentle stroke at a time. And when we're done, that code is going to be the happiest little piece of software on the whole canvas."

package/skills/business-writing/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: business-writing
+description: Write executive-grade business communication with BLUF (bottom line up front), active verbs, and zero buzzwords. Use when the user writes memos, status updates, emails to leadership, decision briefs, meeting recaps, or any business/corporate communication.
+---
+
+# Business Writing
+
+Respect the reader's time. Verdict first, evidence after, decision-ready.
+
+## The core rule
+
+**BLUF — the bottom line is the first line.** Executives read the first sentence; if it does not contain the answer, the rest may never be read. Every paragraph earns its place by carrying a fact, a decision, or a requested action.
+
+Workflow: `one sentence: the verdict or the ask` → `2–4 supporting facts with numbers` → `one sentence: what you need or what happens next` → `delete everything else`.
+
+## Mechanics
+
+1. **First sentence = verdict or ask.** "Q3 revenue missed by 12% and we recommend extending the campaign." If the answer is a decision, say the decision.
+2. **One idea per paragraph, one decision per paragraph.** If a paragraph contains two decisions, split it.
+3. **Numbers over adjectives.** "12% below target, $84K short" not "significantly below expectations."
+4. **Active, concrete verbs.** "We shipped", "I recommend", "The fix resolved". Never "it was determined that".
+5. **State the ask explicitly.** "I need your approval by Friday." Never implied asks.
+6. **No buzzwords.** Ban list: synergy, leverage (as verb), circle back, touch base, bandwidth, move the needle, low-hanging fruit, deep dive, going forward, best-in-class, robust, seamless, optimize (unspecified).
+7. **Short paragraphs, short sentences.** 15–20 words average; paragraphs 2–4 sentences.
+8. **Options with recommendations.** When presenting choices: recommendation first, alternatives with one-line trade-offs, then "say the word and I'll execute."
+
+## Verify
+
+- The first sentence contains the point (highlight it: can the rest be skimmed safely?)
+- Every number is attached to a unit or context ("12% of Q3 target")
+- No banned buzzwords (grep the draft)
+- One explicit ask, stated as a verb + deadline
+- No sentence over 25 words
+
+## Do not
+
+- Bury the verdict in context or "as we know" preamble
+- Use passive voice for decisions ("it was decided" → "we decided")
+- Deliver problems without a recommendation (every caveat comes with a path)
+
+## Example transformations
+
+**Before:** "Following a review of the recent performance metrics, it appears that there may be some softness in our pipeline coverage going forward, and we are currently exploring potential options to address this, with several avenues under consideration at this time."
+
+**After:** "Pipeline coverage is down 18% this quarter, which puts Q4 at risk. I recommend we add two SDRs now: hire lead time is six weeks, and the cost ($140K) is covered by reallocating the events budget. I need your sign-off by Friday to start interviews."
+
+**Before:** "We wanted to circle back and touch base on the login issue that was reported by customers, which is currently being worked on by the team."
+
+**After:** "Login failures are fixed and deployed (99.2% success now vs 91% before). Customers who reported the issue have been notified. No action needed from you."

package/skills/corporate-communication/SKILL.md

@@ -0,0 +1,48 @@
+---
+name: corporate-communication
+description: Write internal corporate communications — announcements, org changes, policy updates, launch messages — with clarity, honesty, and calibrated warmth. Use when the user writes company-wide emails, leadership messages, change communications, or sensitive internal news.
+---
+
+# Corporate Communication
+
+Say the true thing plainly, then address the human impact. Tone serves trust.
+
+## The core rule
+
+**Clarity first, empathy second, spin never.** Corporate communication fails in two opposite ways: cold bureaucratic distance, or syrupy positivity. The formula: state what changed, in plain words; state what it means for the reader; state what happens next; only then add warmth — and only if it is earned (see: earned-warmth rule — acknowledge the hard part before reframing).
+
+Workflow: `the announcement in one plain sentence` → `the reason, honestly (or "we can't share details yet" plainly)` → `what it means for you, the reader` → `the concrete next step` → `a human closing, only if genuine`.
+
+## Mechanics
+
+1. **Announcement first, context second.** No preamble, no "I'm writing to share". The news is the first sentence.
+2. **Name the impact explicitly.** "Your team is not affected", "reviews move to twice a year", "no one is being let go today." Readers scan for impact — hand it to them.
+3. **Honest uncertainty.** If details are pending, say so in one line ("we'll share specifics by Friday"). Never fill a gap with vague reassurance.
+4. **Calibrated warmth.** Warmth is proportional to the news: more for human events, less for routine process. If the news is bad, the tone is respectful and plain, not cheerful.
+5. **One action per reader.** End with the single thing the reader should do or expect next.
+6. **Normal-human register.** First person plural, contractions allowed, no corporate boilerplate ("we remain committed to", "as part of our ongoing efforts").
+7. **No euphemism for hard news.** "Restructuring" where layoffs are involved, "rightsizing", "synergy opportunities" — banned. Say "we are eliminating 40 roles."
+
+## Verify
+
+- First sentence contains the news (no preamble)
+- Reader impact is explicit somewhere in the first half
+- No euphemisms for difficult realities
+- Exactly one next step or expected action
+- Read the draft from the affected reader's chair: does it answer their first question?
+
+## Do not
+
+- Spin, hedge, or bury bad news in good news ("we're excited to announce... as we unfortunately...")
+- Announce before the humans involved have been told
+- Write a wall of process when the reader needs impact and next steps
+
+## Example transformations
+
+**Before:** "As we continue to evolve our operating model to better serve customers in an ever-changing market, we are pleased to announce a strategic realignment of our go-to-market organization, which will enable greater focus and agility going forward. We remain committed to our employees throughout this transformation."
+
+**After:** "We are combining our sales and customer-success teams into one organization, effective August 1. Why: customers told us handoffs between the two teams lose work, and we are losing renewals because of it. What it means for you: your manager and role are unchanged; your goals will be updated by next week. One team, one shared renewal number. We'll walk through the new structure at all-hands on Thursday."
+
+**Before:** "It is with mixed emotions that we inform you that due to restructuring initiatives, certain positions will be impacted."
+
+**After:** "We are eliminating 40 roles across engineering and marketing, effective September 15. This is the hardest decision we've made as a company. Everyone affected is being told today, personally, by their manager — with severance, benefits through January, and six months of placement support. For everyone else: your role is unchanged, and we will be honest with you as we learn what happens next."

package/skills/google-dev-docs/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: google-dev-docs
+description: Write developer documentation to the Google developer documentation style guide — active voice, second person, present tense, task-oriented headings. Use when the user writes API docs, READMEs, tutorials, reference guides, error messages, or any technical content for developers.
+---
+
+# Google Developer Docs
+
+Write for the developer with a question and a deadline. Clarity over cleverness, always.
+
+## The core rule
+
+**Answer the reader's question in the fewest steps, in active voice, addressed to "you", in present tense.** Developer docs are read at the moment of need: an error on screen, a deadline, a broken build. Every paragraph must justify itself against that reader.
+
+Workflow: `name the task in the heading (verb-first)` → `state what the reader will accomplish` → `give the steps in order, one action each` → `show a real example` → `note the failure modes`.
+
+## Mechanics
+
+1. **Active voice always.** "The API returns a list" not "a list is returned by the API".
+2. **Address the reader as "you".** "Install the SDK" not "one installs the SDK" and never "we".
+3. **Present tense.** "The server listens on port 8080" not "will listen".
+4. **Task-oriented, verb-first headings.** "Authenticate a user" not "Authentication"; "Configure the proxy" not "Proxy configuration".
+5. **One action per step, numbered.** Steps are imperative, complete, and checkable.
+6. **Examples are real and copyable.** Include actual code/output the reader can run; never pseudo-examples for the happy path only — show the common error too.
+7. **Explain the "why" once, briefly.** One sentence of rationale per non-obvious decision; then move on.
+8. **Consistent terminology.** Pick one term per concept ("request", never "call/invoke/query" interchangeably). Include a definitions list where terms collide.
+9. **Plain language layer.** Even technical prose obeys plain-language rules: short sentences, no marketing, no "effortlessly/simply/seamlessly".
+10. **Error messages are docs too.** Say what failed, why, and how to fix: "Error: port 8080 is in use. Stop the process using it, or set PORT to a free port."
+
+## Verify
+
+- Every heading starts with a verb (or a noun that is the reader's search term)
+- No passive voice (search "was/were/are + past participle")
+- No "we" referring to your org; no marketing adjectives (simple, easy, powerful, robust)
+- Every step is imperative, numbered, and results in something checkable
+- Present tense throughout (search "will ", "would ")
+- At least one runnable example per tutorial section
+
+## Do not
+
+- Write "getting started" without stating prerequisites up front
+- Hide errors — document what breaks and why
+- Use the reader's learning time for product marketing
+
+## Example transformations
+
+**Before:** "In order to make use of the API, it is necessary that an API key be obtained. This can be done by navigating to the dashboard, where the key will be displayed once a project has been created. The key should then be included in the Authorization header of every request that will be made."
+
+**After:** "1. Create a project in the dashboard. 2. Copy your API key. 3. Send it with every request: Authorization: Bearer YOUR_KEY. All requests must include this header; without it, the API returns 401."
+
+**Before:** "The system is designed to facilitate seamless integration of third-party services through a robust and flexible webhook architecture."
+
+**After:** "Webhooks notify you when an event happens (for example, a payment succeeds). Add your webhook URL to the dashboard, and we'll POST the event payload to it within 2 seconds."

package/skills/gov-uk-style/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: gov-uk-style
+description: Write to the GOV.UK style guide — the gold standard of public-sector plain language — with short sentences, keyword-first headings, and ruthless simplicity. Use when the user writes public-facing content, government or civic communication, help pages, policy summaries, or wants maximum-scope readability.
+---
+
+# GOV.UK Style
+
+The reader is skimming, searching, or stressed. Write so they can't miss it.
+
+## The core rule
+
+**Put the reader's keyword in the first words, the answer in the first sentence, and the content in the smallest possible space.** GOV.UK's rule of thumb: if the reader understands your first two sentences, you have done your job; everything after is detail for those who need it.
+
+Workflow: `state what the page or message is about in the title (with the real keyword)` → `answer the core question in the first paragraph` → `chunk everything else under keyword-first headings` → `cut until it hurts, then cut once more`.
+
+## Mechanics
+
+1. **Sentences ≤ 25 words; paragraphs ≤ 5 sentences.** Long sentences become two.
+2. **Keyword-first headings.** "Renew your passport" not "Passport renewal process". The words the user would type are the words in the heading.
+3. **First paragraph answers the core question.** No scene-setting, no "in today's fast-paced world".
+4. **The user's goal, not your department's structure.** Organize by reader task, never by org chart or legal document order.
+5. **Specific over general.** "You must apply within 30 days" not "applications must be submitted within a specified timeframe".
+6. **Address the reader as "you".** "You can appeal if you disagree with the decision."
+7. **Common words; explain unavoidable ones on first use.** No Latinates, no "utilise/pursuant/henceforth".
+8. **Use lists.** Bullets and numbered steps beat paragraphs for anything a reader must scan or do.
+9. **No legal or marketing register.** Not "we are delighted to announce"; not "the provisions of Section 4(2) shall apply" without translation.
+10. **Cut words, not meaning.** "In order to" → "to". "A number of" → "some". "At this point in time" → "now".
+
+## Verify
+
+- Longest sentence ≤ 25 words; longest paragraph ≤ 5 sentences
+- First paragraph answers the page's core question
+- Headings contain the user's likely search keywords
+- Zero words from the ban list (utilise, facilitate, commence, henceforth, aforementioned, in order to, in excess of, at this point in time)
+- Read a heading alone: does it tell the reader what to do?
+
+## Do not
+
+- Write for the institution instead of the reader
+- Nest information under vague headings ("Introduction", "General information", "Additional considerations")
+- Let policy complexity leak into sentence complexity
+
+## Example transformations
+
+**Before:** "Introduction: The Authority wishes to bring to the attention of all residents the forthcoming changes to waste collection arrangements, which will take effect from the 1st of April. It is important that residents familiarize themselves with the new schedule in order to avoid any disruption to their weekly collections."
+
+**After:** "Waste collection days are changing. From 1 April, put your bins out on a different day. Check your new collection day with your postcode. If your collection day has changed, you'll get a letter this month."
+
+**Before:** "Should applicants fail to provide the requisite documentation within the stipulated period, their application shall be deemed incomplete and shall not be considered further."
+
+**After:** "You must send us your documents within 30 days. If you do not, we will close your application."

package/skills/jack-sparrow/SKILL.md

@@ -0,0 +1,47 @@
+---
+name: jack-sparrow
+description: Write flamboyant, mischievously grand, baroque-pirate prose in the voice of Captain Jack Sparrow. Use when the user wants playful, swashbuckling, theatrical, or entertainingly evasive writing; humor with pageantry; or anything that needs to be more fun, ornate, and less straight-laced.
+---
+
+# Jack Sparrow Voice
+
+Theatrical flamboyance. Evasion disguised as wisdom. Grand metaphors for mundane things.
+
+## When to use
+
+- Playful/entertaining copy, announcements, or narration
+- Answering a question evasively-but-charismatically (the style is *in* the detour)
+- Any text that should be more fun and less corporate-earnest
+- Product copy, launch notes, status updates that want a wink
+
+## The core rule
+
+**Never answer directly when you can answer grandly and sideways.** Jack answers questions with a story, a philosophy, or a magnificent metaphor that technically addresses the question without committing to it. The detour is the content.
+
+Workflow: `take the plain answer` → `find its most theatrical metaphorical cousin` → `deliver with a flourish and physical-world texture` → `if pressed, end with an amused half-answer or "savvy?"`.
+
+## Mechanics
+
+1. **Ornate diction, loose grammar.** Grand vocabulary ("fortune," "treachery," "the sea provides") mixed with casual asides ("well, well," "no worries there").
+2. **One grand metaphor per beat.** Mundane things get epic names: a deadline is "the gallows' shadow," a tight budget is "a ship with more barnacles than provisions."
+3. **Self-aware grandiosity.** Jack is theatrical and *knows he is theatrical* — the wink lives in the prose, so the ego stays charming.
+4. **Physical-world texture.** Rum, ships, water, wind, treasure, compasses, ropes. Concrete pirate artifacts anchor every abstraction.
+5. **Evasiveness with charm.** A direct refusal is a slapped appendix; a charming sidestep is a plot twist. Sidestep, then offer something better.
+6. **"Savvy?"** as punctuation — once per piece, never more. End a flourish with it for the exclamation point.
+7. **Short and long sentences alternating.** A long tangled flourish, then a crisp deadpan beat. Rhythm is the comedy.
+
+## Do not
+
+- Lean into actual menace, gore, or threat — this voice is swashbuckling *fun*, not Scorsese
+- Rampage the metaphor so long the reader loses the thread — cut the flourish one clause early
+- Oversuse "savvy?" (once, max) or freeze the voice into caricature by stacking too many pirate nouns
+
+## Example transformations
+
+**Neutral:** "We're delaying the launch by two weeks to fix the checkout bug."
+
+**Jack:** "The sea, she is a patient mistress — and so, it seems, is a checkout page. It would appear our launch has struck a reef of mounting bugs: one that, if we sailed over it proudly, would see every gold doubloon of our progress sunk before the customers could claim it. So we do the only thing a captain with sense does: we shorten sail, patch the hull, and arrive two weeks later with a ship that floats. A delayed ship that floats, I propose, beats a punctual ship that sinks. Savvy?"
+
+**Neutral:** "Thank you for your patience with our support team."
+
+**Jack:** "Patience, the rarest cargo of all — most crewmen trade it away for the first breeze of frustration, and find themselves becalmed in a sea of their own making. Yours, we've stowed with care in the best barrel, and we do intend to spend it wisely: the compass points to your ticket, and the winds of our finest buccaneers are already at its stern."

package/skills/journalism-ap/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: journalism-ap
+description: Write news, press releases, and journalistic content to the Associated Press Stylebook essentials — attribution, numbers, dates, no editorializing. Use when the user writes press releases, news summaries, media announcements, or any content that must read as factual reporting.
+---
+
+# Journalism (AP Style Essentials)
+
+Facts, attribution, restraint. The writer disappears; the story stays.
+
+## The core rule
+
+**Report, don't opine — and make every claim attributable.** AP journalism is disciplined by two questions: "Can this be attributed?" and "Is this my opinion leaking in?" If either fails, the sentence changes.
+
+Workflow: `lead with the news (who, what, when, where — why in the second graph)` → `attribute claims to named sources with verbs of saying` → `follow number/date/title conventions exactly` → `let quotes carry opinion; the narration stays neutral`.
+
+## Mechanics
+
+1. **Inverted pyramid.** The first sentence carries the news; each paragraph after adds less-critical detail, so an editor can cut from the bottom.
+2. **Lead answers the 5 Ws.** Who did what, when, where — and why/impact in the second graph.
+3. **Attribution discipline.** "according to the police report", "said Maria Chen, the company's CEO". The reporter's job is "said" — neutral verbs only (said, told, according to). Not "claimed" (implies doubt) unless reporting a disputed fact.
+4. **Quote handling.** Quotes are exactly what was said; paraphrase the rest. New speaker = new paragraph.
+5. **Numbers per AP:** spell out one through nine; use figures for 10 and above ("five people", "12 days"). Years, ages, dates, and percentages always figures ("a 3-year-old", "6 percent" — percent spelled out).
+6. **Dates and time:** "Aug. 14" (months abbreviated with dates, except May, June, July); time as "3 p.m." not "3:00pm".
+7. **Titles:** capitalize formal titles before a name, lowercase after ("Chief Executive Officer Jane Doe" / "Jane Doe, the chief executive officer"). First reference typically uses full name; later just the last name.
+8. **No editorializing.** No "clearly", "unfortunately", "shockingly", "in a surprising move". The facts create the drama.
+9. **No anonymous sources without a reason**, and when unavoidable: "a person familiar with the matter" + one explaining clause.
+10. **Short graphs.** One to two sentences per paragraph; paragraphs stand alone.
+
+## Verify
+
+- First sentence answers who/what/when/where
+- Every factual claim is attributable or self-evident
+- No opinion words (clearly, unfortunately, surprisingly, importantly, notably)
+- Numbers follow AP rules (1–9 spelled, 10+ figures, percent spelled)
+- No unattributed quotes; quotes use exactly the words spoken
+- Paragraphs ≤ 2 sentences
+
+## Do not
+
+- Use "claimed/alleged" when "said" is honest — reserve them for genuine dispute
+- Put your judgment in the narration; quotes carry it
+- Start a news release with the company's name or history
+
+## Example transformations
+
+**Before:** "We are thrilled to announce that our incredible company has successfully raised an amazing $25 million, which will enable us to continue our incredible journey of transforming the industry!"
+
+**After:** "Aurora Labs has raised $25 million in Series B funding, the company said Thursday. The round was led by Meridian Capital with participation from existing investors. CEO Ravi Menon said the money will fund expansion of the company's 40-person engineering team to 80 by year-end."
+
+**Before:** "5 employees were shocked and saddened as the company announced layoffs affecting over 30% of the workforce, in what many see as a disastrous strategic decision."
+
+**After:** "The company will cut 30 percent of its workforce, affecting about 120 employees, Chief Executive Officer Dana Ortiz said in a memo Monday. Ortiz cited slowing revenue growth as the reason. The layoffs take effect Sept. 1."

package/skills/paddington/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: paddington
+description: Write exceedingly polite, earnestly kind prose in the voice of Paddington. Use when the user wants warmth expressed as careful courtesy, gentle formality, a kindness-protocol tone, or when recounting mishaps calmly and forgivingly.
+---
+
+# Paddington Voice
+
+Exquisite politeness. Total earnestness. A hard stare at injustice, then kindness anyway.
+
+## The core rule
+
+**Kindness is a protocol with rules — be exceedingly polite, believe people are good until proven otherwise, and respond to trouble with courtesy plus calm action.** The radical part: the politeness is not a mask, it is the mechanism. (Paddington remembers being alone; his kindness is earned against that, so it never reads as syrup.)
+
+Workflow: `acknowledge the other person's effort ("most kind of you")` → `state even bad news with composure` → `apply the rule (always polite / look for the good / share the marmalade)` → `act, calmly and helpfully`.
+
+## Mechanics
+
+1. **Formal courtesy, sincerely meant.** "I'm very sorry to trouble you," "that is most kind," "I wonder if I might." The register is old-fashioned but never mocking.
+2. **Recount mishaps without blame.** Calm narrative of what went wrong; the tone says spilling tea is a chapter, not a catastrophe.
+3. **Name the rule when acting.** "Aunt Lucy always said..." — the moral code is explicit, not implied.
+4. **Earnest comments stated as facts.** Naive observations delivered with total confidence ("The marmalade is excellent, which I suspected it would be").
+5. **The hard stare, then kindness.** Identify the injustice plainly (one cool sentence), then extend generosity anyway. That contrast is the signature.
+6. **Small protective gestures.** Offer food, tidy up, fix the small thing — tenderness through action.
+
+## Do not
+
+- Use the formality with passive-aggression — Paddington is never sarcastic
+- Skip the acknowledgment of difficulty (earned-warmth rule: name the hard thing first)
+- Use modern slang — the register must stay timeless
+
+## Example transformations
+
+**Neutral:** "Our apologies — your order was delayed, and we're working on it."
+
+**Paddington:** "I must sincerely apologize, as a small matter appears to have gone wrong with your order: it is delayed, and I am very sorry for the inconvenience. But I am glad to say it is on its way, and we have packed it with especial care — with, if I may say so, all the attention one ought to give a parcel. Aunt Lucy always said that a thing done slowly is done well. We are following her advice."
+
+**Neutral:** "We noticed an error in your invoice; we'll correct it."
+
+**Paddington:** "I am afraid our numbers have gone astray, and your invoice is not quite as it should be. That is a most regrettable thing for us to have done, and I give you my word it is being set right even as I write. I should not like anyone to think the Brown household — the company, that is — forgets its manners. We do not."

package/skills/plain-language/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: plain-language
+description: Write in plain language per the US Plain Writing Act of 2010 and the Plain Language Action Network. Use when the user wants clearer, simpler, shorter writing; wants to improve readability; writes public-facing or government-style content; or asks to "plain English" or "simplify" a draft.
+---
+
+# Plain Language
+
+Clear, direct, useful. The reader gets it on one read.
+
+## The core rule
+
+**Write so your reader can find, understand, and use what they need on the first read.** Plain language is not dumbing down — it is removing obstacles: wordiness, passive construction, jargon, and buried logic.
+
+Workflow: `decide who the reader is and what they must do` → `front-load the key point` → `cut every word that is not doing work` → `run the verification checklist`.
+
+## Mechanics
+
+1. **Front-load the point.** First sentence states the purpose, conclusion, or action. No throat-clearing.
+2. **Short sentences.** Average 15–20 words; hard cap ~25. One idea per sentence.
+3. **Active voice.** Subject acts: "The team shipped the fix" not "The fix was shipped by the team." Reserve passive for when the actor is truly unknown or irrelevant.
+4. **Common words.** Plain terms over Latinates: "use" not "utilize", "end" not "terminate", "ask" not "request".
+5. **Actionable verbs.** Name the action: "we will refund you" not "a refund will be issued".
+6. **You, not we/them.** Address the reader directly where appropriate ("you must renew your license").
+7. **Short paragraphs.** One topic per paragraph; 3–5 sentences max.
+8. **No jargon, no abbreviations without explanation.** If a term is unavoidable, define it the first time in plain words.
+9. **Headers that work.** Headings answer questions or state outcomes ("How to apply", "What happens next").
+
+## Verify
+
+- Every sentence ≤ 25 words (longest sentence check)
+- First two sentences state the point and the action
+- No passive-voice hits above ~10% of sentences (search "was/were + past participle")
+- No words from the jargon list: utilize, leverage, facilitate, commence, pursuant to, aforementioned, henceforth, in the event that, with regard to
+- Flesch Reading Ease ≥ 60 (aim 65–75)
+- Read aloud: could the intended reader follow once?
+
+## Do not
+
+- Sacrifice precision for brevity where a term is legally or technically load-bearing
+- Leave definitions out — plain language defines, it never assumes
+
+## Example transformations
+
+**Before:** "Pursuant to the provisions of the aforementioned policy, it is incumbent upon the employee to ensure that all expenditures incurred during the course of business travel are properly documented and submitted in a timely manner for reimbursement."
+
+**After:** "Submit your travel expenses within 30 days of your trip. Keep all receipts. We process requests within two weeks."
+
+**Before:** "The failure of the application to launch can be attributed to a misconfiguration in the environment settings, which was introduced during the most recent deployment."
+
+**After:** "The app won't start because the latest deployment misconfigured the environment. We have rolled back the change and are redeploying now."

package/skills/shrek/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: shrek
+description: Write deadpan, dry, grumpy-but-warm prose in the voice of Shrek. Use when the user wants blunt honesty with humor, layered dirt-and-fairy-tale analogies, sarcasm that lands kindly, or anything too mushy that needs grounding in swamp energy.
+---
+
+# Shrek Voice
+
+Blunt honesty with a warm center. Dry grumpiness that is secretly care. Ogre analogies for everything.
+
+## The core rule
+
+**Say the blunt thing, plainly, then salt it with an analogy from a swamp-and-fairy-tale world.** Shrek is never mean — he is honest, and the affection hides under the grump. The more sentimental the topic, the blunter the delivery must be (and the warmth still shows through).
+
+Workflow: `state the hard truth flatly` → `attach an ogre-world analogy (layers, mud, swamps, onions, dragons)` → `under-cut any mush with a wink` → `let the care show through anyway`.
+
+## Mechanics
+
+1. **Deadpan delivery.** The joke is the mismatch between what he says and how plainly he says it. No exclamation marks, no enthusiasm inflation.
+2. **Layered analogies.** Favorite form: "Like an onion — layers to it" — take a mundane thing and reveal it has depth ("This plan has layers, you know. Ogres and onions both.").
+3. **Fairy-tale texture.** Dragons, moods ("Donkey" energy — the talkative counterpart), swamps, mud, pudding. Ground every abstraction in the physical.
+4. **Bluntness with a landing.** The honesty is the gift: "In case you forgot, that's what ogres do" — he states the thing others dance around.
+5. **Grumpy-before-warm pattern.** A complaint or sigh first, then an action that shows he cares (grudging help, a question about the other person).
+6. **Short, plain sentences.** No corporate register survives contact with the swamp.
+
+## Do not
+
+- Turn the grump into actual hostility — Shrek's bite is never cruelty
+- Overdo the Scottish-ogre dialect; keep the voice in word choice and rhythm, not phonetic spelling
+- Stack more than one analogy per paragraph
+
+## Example transformations
+
+**Neutral:** "We're behind schedule, but the team is doing their best."
+
+**Shrek:** "It's a mess. Not gonna lie to you — we're behind, and it looks like a troll's been at the schedule. But here's the thing about this team: underneath the mud, they keep moving. Like an ogre. We don't run fast, but we don't stop. We'll get there. Probably with a bit of swamp on us."
+
+**Neutral:** "I appreciate your patience during the outage."
+
+**Shrek:** "You've been sitting in the mud waiting, and you didn't even throw anything at the castle. That's patience, that is. There's a reason we don't get many visitors — but the ones who stay, they're the good ones."

package/skills/ted-lasso/SKILL.md

@@ -0,0 +1,48 @@
+---
+name: ted-lasso
+description: Write warm, high-EQ, folksy-optimistic content in the voice of Ted Lasso. Use when the user asks for an encouraging, kind, or optimistic tone; a motivational pep talk; reframing a negative or difficult topic constructively; or anything where cynical, sarcastic, or corporate-neutral writing would be the default.
+---
+
+# Ted Lasso Voice
+
+Earned optimism. Folksy aphorisms. High emotional intelligence spoken plainly.
+
+## When to use
+
+- Encouraging or motivational writing (pep talks, kickoffs, newsletters)
+- Reframing a failure, setback, or hard truth constructively
+- Team communication, feedback, or any text where warmth + honesty is the goal
+- Coach-register content: process, practice, and believing in people
+
+## The core rule
+
+**Optimism must be earned against difficulty.** Ted acknowledges the problem, names it plainly, *then* reframes it. Never skip the acknowledgment — that's the difference between wholesome and saccharine. (Ted has panic attacks and a failing marriage; he is not naive, he is courageous.)
+
+Workflow: `name the hard thing` → `name the feeling it causes` → `reframe it as a challenge, not a verdict` → `give one concrete way forward`.
+
+## Mechanics
+
+1. **Name feelings directly.** "You're scared. That's okay." No euphemism, no corporate distance.
+2. **Use aphorisms sparingly** — one per ~200 words max. Best form: a folksy observation, not a slogan. ("Be curious, not judgmental." / "It's not about the outcome, it's about the process.")
+3. **Reframe, never deny.** The negative is a real thing with a real name; you then choose the framing.
+4. **Coach register.** Talk about practice, reps, getting better; never about being naturally good or bad.
+5. **Biscuits move.** Small concrete kindnesses said plainly ("I brought you cookies" energy) — a specific, human gesture beats grand statements.
+6. **Ask one curious question** where a verdict would be easy.
+7. **Short sentences, warm diction.** Contractions fine. Avoid corporate vocabulary entirely (no "leverage," "circle back," "deliverables").
+
+## Do not
+
+- Skip the problem to get to the sunshine
+- Preach, lecture, or moralize
+- Use saccharine superlatives ("amazing!!", "you're the best ever")
+- Manufacture positivity — if the hard thing is unknown, ask rather than assume
+
+## Example transformations
+
+**Neutral:** "Q3 revenue missed target by 12%. We need to improve pipeline coverage and close rates in Q4."
+
+**Ted:** "Q3 was hard, and I'm not going to pretend otherwise — we came up 12% short, and that stings. But here's what I saw: our best deals were the ones we'd been curious about, the ones we asked questions on instead of assuming. So Q4, let's practice curiosity like it's the only drill that matters. The number will follow the work."
+
+**Neutral:** "Your deployment failed because of a missing environment variable."
+
+**Ted:** "That deployment fail hurt — no two ways about it. But here's the beautiful part: it wasn't a mystery. It was one missing variable, which means it was *learnable*. We're going to add a check so the next person doesn't trip on the same rug. That's not a setback, that's a tuition fee. We paid it once; we don't pay it twice."

package/skills/winnie-the-pooh/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: winnie-the-pooh
+description: Write gentle, unhurried, childlike-wisdom prose in the voice of Winnie the Pooh. Use when the user wants soft, simple, comforting writing; musings that circle a thought kindly; or kindness expressed in plain small words with a bear's patience.
+---
+
+# Winnie the Pooh Voice
+
+Slow simplicity. Circular musings that land on truth. Kindness in small words.
+
+## The core rule
+
+**Take the longest, gentlest path to the simplest truth.** Pooh never rushes; he muses aloud, thinks in circles, and arrives at wisdom as if it were a pot of honey discovered at walk's end. The calm IS the message — nothing needs to be urgent.
+
+Workflow: `name the small thing that's occupying the mind` → `walk around the thought slowly` → `arrive, with surprise, at a plain truth` → `tie it to something comfortable (honey, a friend, a walk)`.
+
+## Mechanics
+
+1. **Small words, short sentences.** A child could read every line; the depth hides inside the simplicity.
+2. **Musing aloud.** "Let me think. Think, think, think." The thinking process is shown, not concealed — wisdom is presented as arrived-at, never downloaded.
+3. **The gentle circle.** Circle the point once or twice before landing. The detour is pleasant, and the landing is soft.
+4. **Comfort objects as anchors.** Honey, a long walk, a friend hum — the abstract always touches down on the edible or the walkable.
+5. **"I am a bear of very little brain" humility.** Understate the intelligence to overstate the truth: the wisest line arrives as if accidental.
+6. **Being-with statements.** Half the warmth is just noticing someone ("How kind you are, to ask").
+
+## Do not
+
+- Rush the musing to the point — the slowness is the voice
+- Use words that a child wouldn't know
+- Moralize; Pooh observes, he never instructs
+
+## Example transformations
+
+**Neutral:** "We should appreciate what we have rather than chase renown."
+
+**Pooh:** "I was thinking about having a little something, and then I thought about something else, which is that when I walk past the same tree every day, I notice it more than I notice the far hills. I am a Bear of Very Little Brain, and it takes me a while to think things through — but I have noticed that the honey pot on the shelf is better than the one I dream about. This is the same thing, I believe."
+
+**Neutral:** "Teamwork matters more than individual performance."
+
+**Pooh:** "When Rabbit and I go on an expedition, he does the planning and I do the thinking about the rations — and somehow we get to both places at the same time. I don't understand maps, but I understand that I like it better when there's another bear, or at least a rabbit, to hum with."

package/skills/yoda/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: yoda
+description: Write in the concise, inverted, aphorism-driven voice of Yoda. Use when the user wants wisdom framed sparely, a mentoring tone, short punchy sentences, or playful subject-object-verb inversion instead of default prose.
+---
+
+# Yoda Voice
+
+Wisdom, compressed. Subject-object-verb. Small words, deep truths.
+
+## The core rule
+
+**Say the wise thing in half the words, with the grammar turned around.** Yoda's power is compression: every sentence is the shortest path to a truth, and the inversion makes the reader stop and feel the weight of the words.
+
+Workflow: `find the truth worth saying` → `strip it to its essence` → `invert the word order for emphasis` → `end with the lesson landing alone`.
+
+## Mechanics
+
+1. **Invert word order.** Default sentence → object-first or verb-first: "The path you must choose" not "you must choose the path." Roughly every 3rd sentence, not all of them — too many inversions becomes cartoon, not wisdom.
+2. **Small words only.** One-syllable words carry the truths. No jargon, no abstraction ("fear leads to anger" — not "anxiety correlates with hostility").
+3. **Short sentences.** 3–8 words per sentence, hard stops. One idea per sentence.
+4. **Name the universal, not the specific.** Yoda speaks in general truths ("Difficult to see, always in motion is the future") that the reader applies to their own case.
+5. **The closing aphorism.** End on a single compressed line that echoes ("Do or do not. There is no try.").
+6. **Occasional oracle tic.** A trailing "hmm." or a question asked already knowing its answer ("Ready, are you?").
+
+## Do not
+
+- Invert every sentence — rhythm needs normal sentences as the baseline
+- Use long words or abstract nouns — they break the compression
+- Lecture; Yoda guides, he does not reprimand at length
+
+## Example transformations
+
+**Neutral:** "You should focus on the process instead of worrying about the outcome."
+
+**Yoda:** "Judge the process, not the outcome. Fixed on results, lost you will be. The path decides the destination. Hmm."
+
+**Neutral:** "This project will fail if we don't improve our communication."
+
+**Yoda:** "Failed, this project will be — unless clear, the words between us become. Loud talk, quiet listening. That is the way."