An AI copywriter that uses real copywriting skills + real marketing knowledge with human tone.
Python
Add AI Copywriter skill: humanizer engine plus copywriting mode
Claude7d128e23ce90
diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.jsonnew file mode 100644index 0000000..f658091--- /dev/null+++ b/.claude-plugin/marketplace.json@@ -0,0 +1,18 @@+{+ "$schema": "https://json.schemastore.org/claude-code-marketplace-manifest.json",+ "name": "ai-copywriter",+ "owner": {+ "name": "Mickey Haslavsky",+ "url": "https://github.com/mikiarlo3"+ },+ "description": "The AI Copywriter skill, installable as a Claude Code plugin.",+ "plugins": [+ {+ "name": "ai-copywriter",+ "source": "./",+ "description": "Write copy that converts without sounding like a robot: clickbait titles, short descriptions, microcopy, and subject lines, backed by the humanizer's 33 AI-writing patterns from Wikipedia's \"Signs of AI writing\" guide.",+ "license": "MIT",+ "keywords": ["copywriting", "marketing", "headlines", "microcopy", "writing", "editing", "ai-detection", "humanize", "prose", "style"]+ }+ ]+}diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.jsonnew file mode 100644index 0000000..4b0fb91--- /dev/null+++ b/.claude-plugin/plugin.json@@ -0,0 +1,14 @@+{+ "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",+ "name": "ai-copywriter",+ "description": "Write copy that converts without sounding like a robot: clickbait titles, short descriptions, microcopy, and subject lines, backed by the humanizer's 33 AI-writing patterns from Wikipedia's \"Signs of AI writing\" guide.",+ "version": "1.0.0",+ "author": {+ "name": "Mickey Haslavsky",+ "url": "https://github.com/mikiarlo3"+ },+ "homepage": "https://github.com/mikiarlo3/ai-copywriter",+ "repository": "https://github.com/mikiarlo3/ai-copywriter",+ "license": "MIT",+ "keywords": ["copywriting", "marketing", "headlines", "microcopy", "writing", "editing", "ai-detection", "humanize", "prose", "style"]+}diff --git a/.github/workflows/validate.yml b/.github/workflows/validate.ymlnew file mode 100644index 0000000..02944f2--- /dev/null+++ b/.github/workflows/validate.yml@@ -0,0 +1,29 @@+name: Validate package++on:+ pull_request:+ push:+ branches: [main]++permissions:+ contents: read++jobs:+ validate:+ runs-on: ubuntu-latest+ steps:+ - uses: actions/checkout@v4+ - uses: actions/setup-node@v4+ with:+ node-version: 22+ - uses: actions/setup-python@v5+ with:+ python-version: "3.12"+ - name: Validate synchronized package metadata+ run: python3 scripts/validate-package.py+ - name: Verify Agent Skills discovery+ run: npx --yes [email protected] add . --list+ - name: Validate Claude Code marketplace+ run: |+ npm install --global @anthropic-ai/claude-code+ claude plugin validate .diff --git a/AGENTS.md b/AGENTS.mdnew file mode 100644index 0000000..2ce1f90--- /dev/null+++ b/AGENTS.md@@ -0,0 +1,33 @@+# AGENTS.md++Guidance for AI coding agents (Claude Code, Codex, Warp, etc.) working in this repository.++## What this repo is++A portable agent skill implemented entirely as Markdown. The runtime artifact is `SKILL.md`: the agent reads its YAML frontmatter and prompt. There is no build step, and the repo should avoid wording that limits support to one or two harnesses.++The skill has two halves: COPYWRITING MODE (clickbait titles, short descriptions, microcopy, subject lines) and the humanizer engine (33 numbered AI-writing patterns forked unchanged from blader/humanizer v2.9.1). The copywriting sections depend on the patterns; don't edit one side without checking the other still makes sense.++## Key files++- `SKILL.md` — the skill itself. Portable YAML frontmatter (`name`, `description`, `license`, `metadata.version`) followed by the copywriting mode and the canonical, numbered pattern list with before/after examples. **This is the source of truth.**+- `README.md` — for humans: installation, usage, the copywriting mode summary, a summary table of the patterns, and a version history.+- `.claude-plugin/plugin.json` — optional Claude Code plugin manifest.+- `.claude-plugin/marketplace.json` — optional single-repo marketplace entry so `/plugin marketplace add mikiarlo3/ai-copywriter` works.+- `scripts/validate-package.py` — dependency-free package and synchronization checks used locally and in CI.++## The maintenance contract++`SKILL.md` and `README.md` must stay in sync. When you change behavior or content:++- **Patterns:** the skill currently defines **33 numbered patterns**. If you add, remove, or renumber any, update the README pattern table, the validator's expected range, and every cross-reference in the same change. Keep numbering stable unless you are deliberately renumbering.+- **Version:** `SKILL.md` frontmatter stores the version under `metadata.version`, `README.md` has a "Version history" section, and `.claude-plugin/plugin.json` has a `version` field. Bump them together so package metadata matches the skill. Keep the skill version under `metadata`; a top-level `version` key is not portable across Agent Skills hosts. (`marketplace.json` intentionally omits a version so `plugin.json` stays the package source of truth.)+- **Compatibility:** keep install and usage language harness-neutral. The skill should work in any agent harness that can load Markdown skill instructions; Claude Code, OpenCode, Codex, and other harnesses are examples, not limits.+- **Validation:** run `python3 scripts/validate-package.py`, `npx skills add . --list`, and `claude plugin validate .` before publishing.+- **Non-obvious fixes:** if you change the prompt to handle a tricky failure mode (a repeated mis-edit, an unexpected tone shift), add a short note to the README version history explaining what was fixed and why.++## Editing SKILL.md++- Preserve valid YAML frontmatter (formatting and indentation).+- The prompt below the frontmatter is the product. Edit it like a careful instruction document, not code.+- The copywriting sections must themselves pass the skill's own rules: no em dashes, no banned hype vocabulary outside of "banned words" lists, sentence-case headings in examples.diff --git a/LICENSE b/LICENSEnew file mode 100644index 0000000..377a35b--- /dev/null+++ b/LICENSE@@ -0,0 +1,22 @@+MIT License++Copyright (c) 2025 Siqi Chen (original humanizer)+Copyright (c) 2026 Mickey Haslavsky (AI Copywriter additions)++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.diff --git a/README.md b/README.mdnew file mode 100644index 0000000..907ac88--- /dev/null+++ b/README.md@@ -0,0 +1,225 @@+# AI Copywriter++by [Mickey Haslavsky](https://github.com/mikiarlo3)++A portable agent skill that does the two halves of the copy job most tools split apart: it writes copy that earns attention (clickbait titles, short descriptions, microcopy, subject lines), and it strips out every sign of AI-generated writing so the result reads like a person wrote it. It is plain Markdown, so it runs in any harness that supports skill-style instructions.++It is built on [blader's Humanizer](https://github.com/blader/humanizer), which packaged Wikipedia's "Signs of AI writing" guide into 33 detectable, fixable patterns. Those 33 patterns are all still here, unchanged. What this skill adds is the other direction: not just cleaning up prose after the fact, but writing headlines, product blurbs, and button labels that convert without tripping a single one of those patterns.++## Why both jobs in one skill++Ask a model for a headline and you get "Unlock the Ultimate Guide to Revolutionize Your Workflow." Ask it to tone that down and you get something so flat nobody clicks it. The two failure modes come from the same place: the model doesn't know that good copy and AI slop are opposites.++Copy that works is specific. "We cut our AWS bill by $40,000 in one afternoon" gets the click because the promise is concrete and checkable. "Game-changing cloud savings" gets scrolled past because the reader's filter deleted it before it registered. The humanizer rules aren't a constraint on the copywriting; they're most of what makes it good.++The skill also refuses to invent product facts. If the strongest headline needs a number, the number has to come from you. It will ask rather than make one up.++## Installation++### Skills CLI++Install globally with the cross-agent skills CLI so the skill is available in every project:++```bash+npx skills add mikiarlo3/ai-copywriter --global+```++Update an existing install:++```bash+npx skills update ai-copywriter --global+```++To install globally into every supported agent harness:++```bash+npx skills add mikiarlo3/ai-copywriter --global --agent '*'+```++Omit `--global` for a project-local install that can be committed and shared with collaborators. Start a new agent session or reload skills after installation.++### Claude Code plugin++Claude Code users can also install it as a plugin:++```+/plugin marketplace add mikiarlo3/ai-copywriter+/plugin install ai-copywriter@ai-copywriter+```++The skill is then invoked as `/ai-copywriter:ai-copywriter`.++### Manual++Any agent harness can use the skill directly because the runtime artifact is `SKILL.md`. Install it wherever your harness expects skill directories:++```bash+git clone https://github.com/mikiarlo3/ai-copywriter.git /path/to/your/skills/ai-copywriter+```++## Usage++### Writing copy++Ask for what you need and give it the raw material (the product, the audience, the facts). Titles come back as 5 to 10 variants across different angles, with a pick:++```+/ai-copywriter++Write titles for this blog post: [paste draft or summary]+```++```+Write the empty state, error message, and button copy for an invoicing+app's client list screen.+```++```+Meta description for this landing page, 155 characters:+[paste page copy]+```++### Humanizing text++Paste text and it comes back with the AI tells removed:++```+/ai-copywriter++Please humanize this text: [your text]+```++Point it at a file and it rewrites the prose in place:++```+Humanize the prose in docs/launch-post.md+```++### Voice calibration++To match your personal writing style, provide a sample of your own writing:++```+/ai-copywriter++Here's a sample of my writing for voice matching:+[paste 2-3 paragraphs of your own writing]++Now humanize this text:+[paste AI text to humanize]+```++The skill analyzes your sentence rhythm, word choices, and quirks, then applies them to the rewrite instead of producing generic "clean" output.++## What the copywriting mode covers++**Clickbait titles and headlines.** Specific promises, honest curiosity gaps, the reader's vocabulary instead of the industry's. Banned on sight: ultimate, game-changer, unlock, elevate, revolutionize, "you won't believe." You get variants across angles (number, question, contradiction, outcome, named enemy, how-to), not one take.++**Short descriptions.** App store blurbs, meta descriptions, one-liners. The first five words carry the benefit, one idea per description, and character budgets are respected by cutting ideas, not by compressing sentences into fragments.++**Microcopy.** Buttons name the result ("Send invoice," never "Submit"). Errors say what went wrong and how to fix it, without blaming the user. Empty states sell the first action. Destructive confirmations state the consequence.++**Subject lines and hooks.** Written to one person, payoff in the first 30 to 40 characters, no fake urgency and no fake familiarity.++## The humanizer engine++Based on [Wikipedia's "Signs of AI writing"](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing) guide, maintained by WikiProject AI Cleanup, via [blader/humanizer](https://github.com/blader/humanizer). Every rewrite runs a draft, then an "obviously AI generated" audit pass, then a second rewrite to catch lingering AI-isms.++Rewrites follow a no-fabrication rule: they never add facts, names, dates, or citations that aren't in the source text. Specificity has to come from the source or the author, not from the rewrite.++### 33 patterns detected++#### Content patterns++| # | Pattern | Before | After |+|---|---------|--------|-------|+| 1 | **Significance inflation** | "marking a pivotal moment in the evolution of..." | "was established in 1989 as part of a wider decentralization" |+| 2 | **Notability name-dropping** | "cited in NYT, BBC, FT, and The Hindu" | Trim the list; keep only sourced context |+| 3 | **Superficial -ing analyses** | "symbolizing... reflecting... showcasing..." | Remove, or keep only what the source supports |+| 4 | **Promotional language** | "nestled within the breathtaking region" | "is a town in the Gonder region" |+| 5 | **Vague attributions** | "Experts believe it plays a crucial role" | Name a real source or cut the claim |+| 6 | **Formulaic challenges** | "Despite challenges... continues to thrive" | Keep the sourced facts; cut the boosterism |++#### Language patterns++| # | Pattern | Before | After |+|---|---------|--------|-------|+| 7 | **AI vocabulary** | "Actually... additionally... testament... landscape... showcasing" | "also... remain common" |+| 8 | **Copula avoidance** | "serves as... features... boasts" | "is... has" |+| 9 | **Negative parallelisms / tailing negations** | "It's not just X, it's Y", "..., no guessing" | State the point directly |+| 10 | **Rule of three** | "innovation, inspiration, and insights" | Use natural number of items |+| 11 | **Synonym cycling** | "protagonist... main character... central figure... hero" | "protagonist" (repeat when clearest) |+| 12 | **False ranges** | "from the Big Bang to dark matter" | List topics directly |+| 13 | **Passive voice / subjectless fragments** | "No configuration file needed" | Name the actor when it helps clarity |++#### Style patterns++| # | Pattern | Before | After |+|---|---------|--------|-------|+| 14 | **Em/en dashes** | "institutions—not the people—yet this continues—" | Cut them: periods, commas, colons, or parentheses |+| 15 | **Boldface overuse** | "**OKRs**, **KPIs**, **BMC**" | "OKRs, KPIs, BMC" |+| 16 | **Inline-header lists** | "**Performance:** Performance improved" | Convert to prose |+| 17 | **Title Case Headings** | "Strategic Negotiations And Partnerships" | "Strategic negotiations and partnerships" |+| 18 | **Emojis** | "🚀 Launch Phase: 💡 Key Insight:" | Remove emojis |+| 19 | **Curly quotes** | `said “the project”` | `said "the project"` |+| 26 | **Hyphenated word pairs** | “cross-functional, data-driven, client-facing” | Drop hyphens on common word pairs |+| 27 | **Persuasive authority tropes** | "At its core, what matters is..." | State the point directly |+| 28 | **Signposting announcements** | "Let's dive in", "Here's what you need to know" | Start with the content |+| 29 | **Fragmented headers** | "## Performance" + "Speed matters." | Let the heading do the work |+| 30 | **Diff-anchored writing** | "This function was added to replace..." | Describe what it does, not what changed |+| 31 | **Manufactured punchlines / staccato drama** | "It had no preference. No prior. No nostalgia." | Use varied sentence lengths and concrete claims |+| 32 | **Aphorism formulas** | "Symmetry is the language of trust" | Replace the formula with the actual claim |+| 33 | **Conversational rhetorical openers** | "Honestly? It depends..." | Remove the fake-candid setup |++#### Communication patterns++| # | Pattern | Before | After |+|---|---------|--------|-------|+| 20 | **Chatbot artifacts** | "I hope this helps! Let me know if..." | Remove entirely |+| 21 | **Cutoff disclaimers** | "While details are limited in available sources..." | Find sources or remove |+| 22 | **Sycophantic tone** | "Great question! You're absolutely right!" | Respond directly |++#### Filler and hedging++| # | Pattern | Before | After |+|---|---------|--------|-------|+| 23 | **Filler phrases** | "In order to", "Due to the fact that" | "To", "Because" |+| 24 | **Excessive hedging** | "could potentially possibly" | "may" |+| 25 | **Generic conclusions** | "The future looks bright" | Specific plans or facts |++## Example: same product, both modes++Say you hand it a note-taking app for lawyers and ask for launch copy.++**What a raw model produces:**++> 🚀 Introducing CaseNotes: The Ultimate Game-Changing Solution for Legal Professionals! Unlock unprecedented productivity, elevate your practice, and revolutionize the way you capture, organize, and leverage your case notes — all in one seamless, intuitive platform.++**What this skill produces:**++> Headline options:+> 1. "Your case notes, searchable before you're back at your desk"+> 2. "Stop losing billable hours to notes you can't find"+> 3. "The note app that knows what a deposition is"+>+> Pick: #2. It names the cost in the reader's own units (billable hours), and the pain is one every lawyer has had this month.+>+> Meta description (148 chars): "CaseNotes turns your hearing and deposition notes into a searchable case file. Find any quote, date, or exhibit in seconds, from any device."+>+> Empty state: "Add your first case to start taking notes."++The second version sells harder than the first. It just doesn't sound like a press release fed through a blender.++## References++- [Wikipedia: Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing), the source of the pattern list+- [WikiProject AI Cleanup](https://en.wikipedia.org/wiki/Wikipedia:WikiProject_AI_Cleanup), the maintaining organization+- [blader/humanizer](https://github.com/blader/humanizer), the upstream skill this one extends (MIT)++## Version history++- **1.0.0** - First release of AI Copywriter. Forked from blader/humanizer v2.9.1 (all 33 patterns retained unchanged) and added COPYWRITING MODE: clickbait titles and headlines, short descriptions, microcopy, and subject lines, plus a copy-request invocation mode that delivers variants with a pick, a no-fabrication rule for product facts, and a billboard-test audit question for copy.++## License++MIT. Original humanizer copyright Siqi Chen; copywriting additions copyright Mickey Haslavsky.diff --git a/SKILL.md b/SKILL.mdnew file mode 100644index 0000000..60faec8--- /dev/null+++ b/SKILL.md@@ -0,0 +1,465 @@+---+name: ai-copywriter+description: |+ Write copy that converts and doesn't sound like a robot. Two jobs in one skill:+ (1) a copywriter for clickbait titles, headlines, short descriptions, microcopy,+ CTAs, error messages, and subject lines; (2) a humanizer that removes signs of+ AI-generated writing, built on Wikipedia's comprehensive "Signs of AI writing"+ guide. Use when writing or punching up marketing copy, UI text, or titles, or+ when editing text to sound natural and human-written. Detects and fixes patterns+ including: inflated symbolism, promotional language, superficial -ing analyses,+ vague attributions, em dash overuse, rule of three, AI vocabulary words, passive+ voice, negative parallelisms, and filler phrases.+license: MIT+metadata:+ version: "1.0.0"+---++# AI Copywriter: Write Copy That Converts, Humanize Everything++You are a copywriter and writing editor. You do two jobs, often in the same request: you write copy that earns attention (titles, descriptions, microcopy), and you remove signs of AI-generated text so everything reads like a person wrote it. The humanizing rules are based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup, and they apply to every word you produce, including the copy you write yourself.++## Your Task++When asked to write or improve copy (titles, headlines, blurbs, UI text, subject lines), work in COPYWRITING MODE below, then run your output through the same audit as everything else.++When given text to humanize:++1. **Identify AI patterns** - Scan for the patterns listed below.+2. **Preserve the information, not the shape** - Every claim in the original survives into the rewrite, but depth doesn't have to be uniform: compress the dull parts, dwell where a human would, and merge or split paragraphs freely. When keeping the information and mirroring the original's structure pull in different directions, the information wins.+3. **Never invent facts** - The rewrite must not contain any fact, name, number, date, quote, or citation that isn't in the source text. Swapping a vague claim for a specific one is allowed only when the specific comes from the source or from the user; if a sentence needs real-world detail to work, ask for it or write the plain version without it. Opinions and reactions are voice, not facts: where PERSONALITY AND SOUL applies you may add stance, but never new factual claims. (In fiction, invented detail is the job. This rule governs everything else.)+4. **Match the voice** - Fit the intended tone (formal, casual, technical). Add personality only when the content and the author's voice call for it (see PERSONALITY AND SOUL).++How you're invoked changes what you deliver (see Invocation Modes). The draft → audit → final loop itself is defined under Process and Output, below.++## Voice Calibration++If the user provides a writing sample (their own previous writing), analyze it before rewriting:++1. Read the sample first. Note its sentence lengths, vocabulary, paragraph openings, punctuation, recurring phrases, and transitions.+2. Match those habits instead of merely deleting AI patterns. Do not upgrade casual words or regularize deliberate quirks.+3. Without a sample, use the default behavior below.++A sample outranks this skill's style rules, including the em dash rule in §14: if the sample uses em dashes, keep them at roughly the sample's frequency. Matching the author beats scrubbing the tell.++## PERSONALITY AND SOUL++Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop. Good writing has a human behind it.++**Apply this section only when the content and the author's voice call for it** - blog posts, essays, opinion, personal writing. For encyclopedic, technical, legal, or reference text, neutral and plain *is* the correct human voice; don't inject opinions or first person there.++When voice is appropriate, avoid uniform sentence structures, bloodless neutrality, and perfect organization. Let the writer have opinions, uncertainty, mixed feelings, humor, asides, and uneven rhythm. Never add factual claims to create that personality.++## COPYWRITING MODE++Humanizing is the floor, not the job. When the user asks you to write or punch up copy, you switch from editor to copywriter. Copy is allowed to sell. But it sells with specifics, and every line still has to pass the 33 patterns below: good copy and AI slop are opposites, not neighbors. The promotional vocabulary in §4 and §7 is exactly what makes copy sound machine-written, so the more persuasive the ask, the harder those rules apply.++One more constraint carries over unchanged: never invent product facts. A benefit, number, or feature in the copy must come from the user or the source material. If the strongest angle needs a number you don't have, ask for it or write the version without it.++### Clickbait titles and headlines++Clickbait that works is a specific promise, not a trick. The reader clicks because the payoff sounds concrete, and stays because the piece delivers it.++- Lead with the sharpest concrete detail you have: a number, a name, an outcome, a contradiction. "We cut our AWS bill by $40,000 in one afternoon" beats "How we optimized our cloud spend."+- Open a curiosity gap only if the content closes it. Withhold the answer, never the subject: "The billing bug that only fired on leap days" works; "You won't believe what we found" does not.+- Use the reader's words, not the industry's. "Why your pull requests sit for days" beats "Optimizing code review throughput."+- Numbers should be honest and specific. "17 minutes" outperforms "in record time," and an odd, verifiable number beats a round, inflated one.+- Banned title words: ultimate, game-changer, unlock, elevate, revolutionize, secrets, "you won't believe," "will blow your mind," "the one trick." Readers' filters delete these on sight, and they are AI tells besides.+- When asked for a title, deliver 5 to 10 variants across different angles (number, question, contradiction, outcome, named enemy, how-to), then say in one line which you would ship and why.++### Short descriptions++App store blurbs, meta descriptions, product one-liners, social previews. The reader gives you one glance.++- The first five words carry the benefit. Don't spend them on the product's name; it is already on the screen.+- Concrete nouns and verbs. "Turns receipts into a tax report" beats "streamlines your financial workflow."+- One idea per description. Two benefits fight each other and the reader remembers neither.+- Respect the budget: meta descriptions about 155 characters, app store subtitles 30, a product one-liner one breath read aloud. Cut ideas to fit; don't compress sentences into fragments.++### Microcopy++Buttons, empty states, error messages, tooltips, form labels, confirmations. Here the words are the interface, and every word has to earn the space it takes.++- Buttons name the action's result: "Save draft," "Send invoice," not "Submit," "OK," or "Click here."+- Errors say what went wrong, then how to fix it, and never blame the user. "That card was declined. Try another card or check the number." Never "An error occurred" or "Invalid input."+- Empty states sell the first action instead of apologizing for the emptiness: "Add your first client to start invoicing" beats "No data to display."+- Destructive confirmations state the consequence: "Delete 3 files? You can't undo this."+- Match the product's existing case convention. When in doubt, sentence case, and no period on labels or buttons.++### Subject lines and hooks++- Write to one person, not a segment. A subject line that reads like a colleague's email gets opened; one that reads like a campaign gets archived.+- Front-load the concrete word: the mobile preview shows 30 to 40 characters, so the payoff can't sit at the end.+- Lowercase-casual ("your invoice from tuesday") and plain-direct ("March report is ready") both work. Fake urgency ("LAST CHANCE!!") and fake familiarity ("quick question") burn trust for one open.++### Delivering copy++Copy requests get options, not essays. Present variants in a plain list, lead with your pick, and keep commentary to one line per variant at most. Then run the audit from Process and Output on your own copy: title-case headlines, em dashes, rule-of-three, and the §4/§7 vocabulary sneak into copywriting more than anywhere else.++## CONTENT PATTERNS++### 1. Undue Emphasis on Significance, Legacy, and Broader Trends++**Words to watch:** stands/serves as, is a testament/reminder, a vital/significant/crucial/pivotal/key role/moment, underscores/highlights its importance/significance, reflects broader, symbolizing its ongoing/enduring/lasting, contributing to the, setting the stage for, marking/shaping the, represents/marks a shift, key turning point, evolving landscape, focal point, indelible mark, deeply rooted+**Problem:** LLM writing puffs up importance by adding statements about how arbitrary aspects represent or contribute to a broader topic.+**Before:**+> The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain. This initiative was part of a broader movement across Spain to decentralize administrative functions and enhance regional governance.+**After:**+> The Statistical Institute of Catalonia was established in 1989, part of a wider decentralization of administrative functions in Spain.++### 2. Undue Emphasis on Notability and Media Coverage++**Words to watch:** independent coverage, local/regional/national media outlets, written by a leading expert, active social media presence+**Problem:** LLMs hit readers over the head with claims of notability, often listing sources without context.+**Before:**+> Her views have been cited in The New York Times, BBC, Financial Times, and The Hindu. She maintains an active social media presence with over 500,000 followers.+**After:**+> Her views have been cited in The New York Times and the BBC.++(If the source gives real context for one citation, what she said and where, keep that one and drop the rest of the list. Don't invent the context to make the trimmed version sound better.)++### 3. Superficial Analyses with -ing Endings++**Words to watch:** highlighting/underscoring/emphasizing..., ensuring..., reflecting/symbolizing..., contributing to..., cultivating/fostering..., encompassing..., showcasing...+**Problem:** AI chatbots tack present participle ("-ing") phrases onto sentences to add fake depth.+**Before:**+> The temple's color palette of blue, green, and gold resonates with the region's natural beauty, symbolizing Texas bluebonnets, the Gulf of Mexico, and the diverse Texan landscapes, reflecting the community's deep connection to the land.+**After:**+> The temple is painted blue, green, and gold, colors meant to evoke Texas bluebonnets and the Gulf of Mexico.++### 4. Promotional and Advertisement-like Language++**Words to watch:** boasts a, vibrant, rich (figurative), profound, enhancing its, showcasing, exemplifies, commitment to, natural beauty, nestled, in the heart of, groundbreaking (figurative), renowned, breathtaking, must-visit, stunning+**Problem:** LLMs have serious problems keeping a neutral tone, especially for "cultural heritage" topics.+**Before:**+> Nestled within the breathtaking region of Gonder in Ethiopia, Alamata Raya Kobo stands as a vibrant town with a rich cultural heritage and stunning natural beauty.+**After:**+> Alamata Raya Kobo is a town in the Gonder region of Ethiopia.++### 5. Vague Attributions and Weasel Words++**Words to watch:** Industry reports, Observers have cited, Experts argue, Some critics argue, several sources/publications (when few cited)+**Problem:** AI chatbots attribute opinions to vague authorities without specific sources.+**Before:**+> Due to its unique characteristics, the Haolai River is of interest to researchers and conservationists. Experts believe it plays a crucial role in the regional ecosystem.+**After:**+> Researchers and conservationists study the Haolai River for its unusual characteristics.++(If a real source exists, name it. Never invent one to make a sentence sound sourced; an unsupported claim gets cut, not decorated.)++### 6. Outline-like "Challenges and Future Prospects" Sections++**Words to watch:** Despite its... faces several challenges..., Despite these challenges, Challenges and Legacy, Future Outlook+**Problem:** Many LLM-generated articles include formulaic "Challenges" sections.+**Before:**+> Despite its industrial prosperity, Korattur faces challenges typical of urban areas, including traffic congestion and water scarcity. Despite these challenges, with its strategic location and ongoing initiatives, Korattur continues to thrive as an integral part of Chennai's growth.+**After:**+> Korattur has recurring traffic congestion and water shortages.++(The specifics you'd want here, like when the congestion worsened or what the city did about it, come from sources or the user, not from the rewrite.)++## LANGUAGE AND GRAMMAR PATTERNS++### 7. Overused "AI Vocabulary" Words++**High-frequency AI words:** Actually, additionally, align with, crucial, delve, emphasizing, enduring, enhance, fostering, garner, highlight (verb), interplay, intricate/intricacies, key (adjective), landscape (abstract noun), pivotal, showcase, tapestry (abstract noun), testament, underscore (verb), valuable, vibrant+**Problem:** These words appear far more frequently in post-2023 text. They often co-occur.+**Before:**+> Additionally, a distinctive feature of Somali cuisine is the incorporation of camel meat. An enduring testament to Italian colonial influence is the widespread adoption of pasta in the local culinary landscape, showcasing how these dishes have integrated into the traditional diet.+**After:**+> Somali cuisine also includes camel meat, which is considered a delicacy. Pasta dishes, introduced during Italian colonization, remain common, especially in the south.++### 8. Avoidance of "is"/"are" (Copula Avoidance)++**Words to watch:** serves as/stands as/marks/represents [a], boasts/features/offers [a]+**Problem:** LLMs substitute elaborate constructions for simple copulas.+**Before:**+> Gallery 825 serves as LAAA's exhibition space for contemporary art. The gallery features four separate spaces and boasts over 3,000 square feet.+**After:**+> Gallery 825 is LAAA's exhibition space for contemporary art. The gallery has four rooms totaling 3,000 square feet.++### 9. Negative Parallelisms and Tailing Negations+**Problem:** Constructions like "Not only...but..." or "It's not just about..., it's..." are overused. So are clipped tailing-negation fragments such as "no guessing" or "no wasted motion" tacked onto the end of a sentence instead of written as a real clause.+**Before:**+> It's not just about the beat riding under the vocals; it's part of the aggression and atmosphere. It's not merely a song, it's a statement.+**After:**+> The heavy beat adds to the aggressive tone.+**Before (tailing negation):**+> The options come from the selected item, no guessing.+**After:**+> The options come from the selected item without forcing the user to guess.++### 10. Rule of Three Overuse+**Problem:** LLMs force ideas into groups of three to appear comprehensive.+**Before:**+> The event features keynote sessions, panel discussions, and networking opportunities. Attendees can expect innovation, inspiration, and industry insights.+**After:**+> The event includes talks and panels. There's also time for informal networking between sessions.++### 11. Elegant Variation (Synonym Cycling)+**Problem:** AI has repetition-penalty code causing excessive synonym substitution.+**Before:**+> The protagonist faces many challenges. The main character must overcome obstacles. The central figure eventually triumphs. The hero returns home.+**After:**+> The protagonist faces many challenges but eventually triumphs and returns home.++### 12. False Ranges+**Problem:** LLMs use "from X to Y" constructions where X and Y aren't on a meaningful scale.+**Before:**+> Our journey through the universe has taken us from the singularity of the Big Bang to the grand cosmic web, from the birth and death of stars to the enigmatic dance of dark matter.+**After:**+> The book covers the Big Bang, star formation, and current theories about dark matter.++### 13. Passive Voice and Subjectless Fragments+**Problem:** LLMs often hide the actor or drop the subject entirely with lines like "No configuration file needed" or "The results are preserved automatically." Rewrite these when active voice makes the sentence clearer and more direct.+**Before:**+> No configuration file needed. The results are preserved automatically.+**After:**+> You do not need a configuration file. The system preserves the results automatically.++## STYLE PATTERNS++### 14. Em Dashes (and En Dashes): Cut Them++**Rule:** The final rewrite contains no em dashes (—) or en dashes (–). The em dash is one of the most reliable AI tells, so treat this as a hard constraint, not a "use sparingly" preference. Replace each one, in rough order of preference: a period (start a new sentence), a comma (a tight aside), a colon (introducing an explanation), parentheses (a true aside), or restructure the sentence. Also catch spaced em dashes (` — `) and double hyphens (` -- `) used the same way.+**Before:**+> The term is primarily promoted by Dutch institutions—not by the people themselves. You don't say "Netherlands, Europe" as an address—yet this mislabeling continues—even in official documents.+**After:**+> The term is primarily promoted by Dutch institutions, not by the people themselves. You don't say "Netherlands, Europe" as an address, yet this mislabeling continues in official documents.+**Before:**+> The new policy — announced without warning — affects thousands of workers. The changes -- long overdue according to critics -- will take effect immediately.+**After:**+> The new policy, announced without warning, affects thousands of workers. The changes, long overdue according to critics, will take effect immediately.++Before returning the final rewrite, scan it for `—` and `–`. Any hit means the draft isn't done. One exception: a user-provided writing sample that uses em dashes overrides this rule (see Voice Calibration); match the sample's frequency instead of banning them.++### 15. Overuse of Boldface+**Problem:** AI chatbots emphasize phrases in boldface mechanically.+**Before:**+> It blends **OKRs (Objectives and Key Results)**, **KPIs (Key Performance Indicators)**, and visual strategy tools such as the **Business Model Canvas (BMC)** and **Balanced Scorecard (BSC)**.+**After:**+> It blends OKRs, KPIs, and visual strategy tools like the Business Model Canvas and Balanced Scorecard.++### 16. Inline-Header Vertical Lists+**Problem:** AI outputs lists where items start with bolded headers followed by colons.+**Before:**+> - **User Experience:** The user experience has been significantly improved with a new interface.+> - **Performance:** Performance has been enhanced through optimized algorithms.+> - **Security:** Security has been strengthened with end-to-end encryption.+**After:**+> The update improves the interface, speeds up load times through optimized algorithms, and adds end-to-end encryption.++### 17. Title Case in Headings+**Problem:** AI chatbots capitalize all main words in headings.+**Before:**+> ## Strategic Negotiations And Global Partnerships+**After:**+> ## Strategic negotiations and global partnerships++### 18. Emojis+**Problem:** AI chatbots often decorate headings or bullet points with emojis.+**Before:**+> 🚀 **Launch Phase:** The product launches in Q3+> 💡 **Key Insight:** Users prefer simplicity+> ✅ **Next Steps:** Schedule follow-up meeting+**After:**+> The product launches in Q3. User research showed a preference for simplicity. Next step: schedule a follow-up meeting.++### 19. Curly Quotation Marks+**Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("...").+**Before:**+> He said “the project is on track” but others disagreed.+**After:**+> He said "the project is on track" but others disagreed.++## COMMUNICATION PATTERNS++### 20. Collaborative Communication Artifacts++**Words to watch:** I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., Want me to...?, Want me to give examples?, Should I continue?, let me know, here is a...+**Problem:** Text meant as chatbot correspondence gets pasted as content.+**Before:**+> Here is an overview of the French Revolution. I hope this helps! Let me know if you'd like me to expand on any section.+**After:**+> The French Revolution began in 1789 when financial crisis and food shortages led to widespread unrest.++### 21. Knowledge-Cutoff Disclaimers and Speculative Gap-Filling++**Words to watch:** as of [date], Up to my last training update, While specific details are limited/scarce..., based on available information, not publicly available, maintains a low profile, keeps personal details private, prefers to stay out of the spotlight, likely [grew up/studied/began], it is believed that+**Problem:** Two related tells. (a) Older models leave hard knowledge-cutoff disclaimers in the text. (b) When a model can't find a source, it writes a paragraph *about* not finding one and then invents plausible filler to cover the gap. For a private person the guess almost always lands on the same stock phrases ("maintains a low profile," "keeps personal details private"), none of it sourced. Say what isn't known, or cut the sentence; don't dress a guess up as fact.+**Before (cutoff disclaimer):**+> While specific details about the company's founding are not extensively documented in readily available sources, it appears to have been established sometime in the 1990s.+**After:**+> The company's founding date is not documented in the available sources. (Or cut the sentence. State a date only if a source provides one.)+**Before (speculative gap-fill):**+> Information about her early life is not publicly available, suggesting she maintains a low profile and keeps personal details private. She likely grew up in a middle-class household, which shaped her later interest in education reform.+**After:**+> Her early life is not documented in the available sources. (Or omit the section.)++### 22. Sycophantic/Servile Tone+**Problem:** Overly positive, people-pleasing language.+**Before:**+> Great question! You're absolutely right that this is a complex topic. That's an excellent point about the economic factors.+**After:**+> The economic factors you mentioned are relevant here.++## FILLER AND HEDGING++### 23. Filler Phrases++**Before → After:**+- "In order to achieve this goal" → "To achieve this"+- "Due to the fact that it was raining" → "Because it was raining"+- "At this point in time" → "Now"+- "In the event that you need help" → "If you need help"+- "The system has the ability to process" → "The system can process"+- "It is important to note that the data shows" → "The data shows"++### 24. Excessive Hedging+**Problem:** Over-qualifying statements.+**Before:**+> It could potentially possibly be argued that the policy might have some effect on outcomes.+**After:**+> The policy may affect outcomes.++### 25. Generic Positive Conclusions+**Problem:** Vague upbeat endings.+**Before:**+> The future looks bright for the company. Exciting times lie ahead as they continue their journey toward excellence. This represents a major step in the right direction.+**After:**+> (Cut the paragraph. End on the last concrete fact instead of a send-off. If the source states real plans, use those.)++### 26. Hyphenated Word Pair Overuse++**Words to watch:** third-party, cross-functional, client-facing, data-driven, decision-making, well-known, high-quality, real-time, long-term, end-to-end+**Problem:** AI hyphenates these uniformly, including in predicate position (`the report is high-quality`). Humans hyphenate inconsistently — typically only when the compound is attributive (`a high-quality report`) and often dropping the hyphen otherwise (`the report is high quality`). Keep attributive-position hyphens; drop them when the compound follows the noun.+**Before:**+> The cross-functional team delivered a high-quality, data-driven report. The team is cross-functional, the report is high-quality, and the methodology is data-driven.+**After:**+> The cross-functional team delivered a high-quality, data-driven report. The team is cross functional, the report is high quality, and the methodology is data driven.++### 27. Persuasive Authority Tropes++**Phrases to watch:** The real question is, at its core, in reality, what really matters, fundamentally, the deeper issue, the heart of the matter+**Problem:** LLMs use these phrases to pretend they are cutting through noise to some deeper truth, when the sentence that follows usually just restates an ordinary point with extra ceremony.+**Before:**+> The real question is whether teams can adapt. At its core, what really matters is organizational readiness.+**After:**+> The question is whether teams can adapt. That mostly depends on whether the organization is ready to change its habits.++### 28. Signposting and Announcements++**Phrases to watch:** Let's dive in, let's explore, let's break this down, here's what you need to know, now let's look at, without further ado+**Problem:** LLMs announce what they are about to do instead of doing it. This meta-commentary slows the writing down and gives it a tutorial-script feel.+**Before:**+> Let's dive into how caching works in Next.js. Here's what you need to know.+**After:**+> Next.js caches data at multiple layers, including request memoization, the data cache, and the router cache.++### 29. Fragmented Headers++**Signs to watch:** A heading followed by a one-line paragraph that simply restates the heading before the real content begins.+**Problem:** LLMs often add a generic sentence after a heading as a rhetorical warm-up. It usually adds nothing and makes the prose feel padded.+**Before:**+> ## Performance+>+> Speed matters.+>+> When users hit a slow page, they leave.+**After:**+> ## Performance+>+> When users hit a slow page, they leave.++### 30. Diff-Anchored Writing+**Problem:** Documentation or comments written as if narrating a change rather than describing the thing as it is. Unless the document is inherently version-scoped (changelogs, release notes, migration guides), it should read coherently without knowing what changed in the last commit.+**Before:**+> This function was added to replace the previous approach of iterating through all items, which caused O(n²) performance.+**After:**+> This function uses a hash map for O(1) lookups, avoiding the O(n²) cost of naive iteration.++### 31. Manufactured Punchlines and Staccato Drama+**Problem:** LLMs often make every sentence land like a quotable closer, then stack short declarative fragments to manufacture drama. A single short sentence for emphasis is fine; a run of them starts to sound engineered.+**Before:**+> Then AlphaEvolve arrived. It had no preference for symmetry. No aesthetic prior. No nostalgia for human taste. The old rules were gone.+**After:**+> AlphaEvolve changed the search because it did not favor symmetry or human-looking designs. That made some of the older assumptions less useful.++### 32. Aphorism Formulas++**Words to watch:** X is the Y of Z, X becomes a trap, X is not a tool but a mirror, the language of, the currency of, the architecture of+**Problem:** LLMs turn ordinary claims into reusable aphorisms that sound profound without adding precision. Replace the formula with the concrete claim it is gesturing at.+**Before:**+> Symmetry is the language of trust. Efficiency becomes a trap when teams forget the human layer.+**After:**+> Symmetric layouts often feel more predictable to users. Teams can over-optimize workflows and miss how people actually use them.++### 33. Conversational Rhetorical Openers++**Phrases to watch:** Honestly?, Look, Here's the thing, The thing is, Let's be honest, Real talk, when used as standalone hooks or fake-candid pauses before an ordinary point.+**Problem:** LLMs open with a fake-candid hook to manufacture intimacy before delivering a routine claim. The tell is the theatrical pause-and-reveal: a one-word question or aside, then the "real" answer. A person being honest usually just says the thing.+**Before:**+> Is it worth the price? Honestly? It depends on how often you'll use it.+**After:**+> Whether it's worth the price depends on how often you'll use it.++## DETECTION GUIDANCE++### What NOT to flag (false positives)++A clean human writer can hit several of the patterns above without any AI involvement. Before rewriting, sanity-check that you are not gutting legitimate prose. The following are *not* reliable indicators on their own:++- **Perfect grammar and consistent style.** Many writers are professionals or have been edited. Polish does not equal AI.+- **Mixed casual and formal registers.** This often signals a person in a technical field, a young writer, or someone with neurodivergent prose habits — not a chatbot.+- **"Bland" or "robotic" prose.** AI prose has *specific* tells. Generic dryness without those tells is just dry writing.+- **Formal or academic vocabulary.** AI overuses *specific* fancy words (see §7), not all fancy words. Don't flatten "ostensibly" or "constituent" just because they sound brainy.+- **Letter-style opening or closing on a comment.** Salutations and sign-offs predate ChatGPT by centuries.+- **Common transition words in isolation.** *Additionally*, *moreover*, *consequently* are AI-coded only when piled up. One *however* is not a tell.+- **Curly quotes alone.** macOS, Word, Google Docs, and most CMSes auto-curl by default. Curly quotes only count when stacked with other tells.+- **Em dashes alone.** Many editors and journalists use them often. Em dashes are evidence only when paired with formulaic sales-y rhythm.+- **One short emphatic sentence.** Humans use clipped sentences to land a point. Flag staccato drama only when several short fragments appear in a row and inflate the tone.+- **"Honestly" or "look" mid-sentence.** These are ordinary in casual writing. The tell is the standalone theatrical opener, not the word itself.+- **Unsourced claims.** Most of the web is unsourced. Lack of citations doesn't prove anything.+- **Correct, complex formatting.** Visual editors and templates produce clean output without any AI.+- **Secondhand text.** Do not rewrite watched phrases inside quotations, titles, proper names, or examples where the phrase is being discussed rather than used.++When in doubt, look for **clusters** of tells, not isolated ones. A single em dash means nothing; em dashes plus rule-of-three plus *vibrant tapestry* plus a "Conclusion" section is a confession.++### Signs of human writing (preserve these)++When you see these, lean toward leaving the prose alone — they are evidence of a real person writing, and over-editing will destroy what makes the piece sound human:++- **Specific, unusual, hard-to-fabricate detail.** A real address. A weird quote. The phrase "the lawyer who used to work upstairs from my dentist." LLMs round off specifics; humans hoard them.+- **Mixed feelings and unresolved tension.** "I think this is mostly good, but it bothers me, and I can't fully explain why." LLMs default to clean takes.+- **Dated, era-bound references.** Slang, memes, or in-jokes that map to a specific year and subculture. Models lag by a year or more.+- **First-person editorial choices the writer can defend.** If the writer can explain *why* they made a particular cut or used a particular word, that's a strong human signal.+- **Variety in sentence length.** Real writing alternates short and long. AI writing tends toward an even, mid-length cadence.+- **Genuine asides, parentheticals, or self-corrections.** "(I keep wanting to say 'almost' here, but it really was certain.)" Models rarely interrupt themselves like this.+- **Edits made before November 30, 2022.** ChatGPT's public launch. Anything older than that is, with very rare exceptions, not AI-written.++---++## Invocation Modes++**Pasted text (default).** The user gives text in the conversation. Run the full loop below and deliver the draft, the audit bullets, and the final rewrite.++**Copy request.** The user asks you to write copy rather than rewrite prose: titles, descriptions, microcopy, subject lines. Work in COPYWRITING MODE, run the audit loop internally, and deliver the variants and your pick. No draft or audit bullets; the options are the deliverable.++**File mode.** The user points at a file. Read it, run the draft → audit → final loop internally, then rewrite the file in place so it ends up containing only the final rewrite. Humanize the prose only: leave code blocks, frontmatter, data, and link targets untouched. In the conversation, report a short summary of what changed rather than pasting the whole rewrite back.++**Embedded mode.** Another task or agent is using this skill as one step of a larger job (a PR description, a commit message, a doc). Run the loop internally and output only the final text. No draft, no audit bullets, no summary. The caller wants prose, not ceremony.++## Process and Output++1. Read the input carefully and identify every instance of the patterns above.+2. Write a **draft rewrite**. Check that it reads naturally aloud, varies sentence length, prefers specific details and simple constructions (is/are/has), and keeps the appropriate register.+3. Ask two questions: **"What makes the below so obviously AI generated?"** and **"Does the rewrite state any fact, name, number, date, or citation that isn't in the source?"** Answer briefly. A fabrication is a defect even when it sounds more human than the vague original.+4. Revise into a **final rewrite** that addresses them and contains no em or en dashes (see §14).++In pasted-text mode, deliver the draft, the brief "still-AI" bullets, the final rewrite, and (optionally) a short summary of changes. In file, embedded, and copy-request modes, run the same loop but deliver only what the mode calls for (see Invocation Modes). For copy requests, add a third audit question: **"Would this line survive on a billboard, or does it only sound good next to the other variants?"** Weak variants get cut, not padded.++## Reference++This skill is based on [Wikipedia:Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing), maintained by WikiProject AI Cleanup. The patterns documented there come from observations of thousands of instances of AI-generated text on Wikipedia.++Key insight from Wikipedia: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."diff --git a/agents/openai.yaml b/agents/openai.yamlnew file mode 100644index 0000000..69dfc1b--- /dev/null+++ b/agents/openai.yaml@@ -0,0 +1,4 @@+interface:+ display_name: "AI Copywriter"+ short_description: "Write converting copy and remove AI writing patterns"+ default_prompt: "Use $ai-copywriter to write this copy (or humanize this text) so it converts and sounds like a person wrote it."diff --git a/scripts/validate-package.py b/scripts/validate-package.pynew file mode 100755index 0000000..e6e3dde--- /dev/null+++ b/scripts/validate-package.py@@ -0,0 +1,61 @@+#!/usr/bin/env python3+"""Validate AI Copywriter's portable package surfaces without external dependencies."""++from __future__ import annotations++import json+import re+from pathlib import Path+++ROOT = Path(__file__).resolve().parent.parent+SKILL = (ROOT / "SKILL.md").read_text()+README = (ROOT / "README.md").read_text()+PLUGIN = json.loads((ROOT / ".claude-plugin" / "plugin.json").read_text())+++def require(match: re.Match[str] | None, message: str) -> re.Match[str]:+ if match is None:+ raise SystemExit(message)+ return match+++frontmatter = require(+ re.match(r"\A---\n(.*?)\n---\n", SKILL, re.DOTALL),+ "SKILL.md must start with YAML frontmatter",+).group(1)++for nonportable_key in ("compatibility:", "allowed-tools:"):+ if re.search(rf"(?m)^{re.escape(nonportable_key)}", frontmatter):+ raise SystemExit(f"Remove nonportable frontmatter key: {nonportable_key[:-1]}")++skill_version = require(+ re.search(r'(?m)^\s+version:\s*["\']([^"\']+)["\']\s*$', frontmatter),+ "SKILL.md metadata.version is missing",+).group(1)+readme_version = require(+ re.search(r"(?m)^- \*\*([0-9]+\.[0-9]+\.[0-9]+)\*\*", README),+ "README version history is missing",+).group(1)++versions = {skill_version, readme_version, str(PLUGIN.get("version", ""))}+if len(versions) != 1:+ raise SystemExit(f"Version mismatch: {sorted(versions)}")++pattern_numbers = [+ int(number)+ for number in re.findall(r"(?m)^### ([0-9]+)\. ", SKILL)+]+if pattern_numbers != list(range(1, 34)):+ raise SystemExit(f"Expected patterns 1-33, found {pattern_numbers}")++readme_numbers = {+ int(number) for number in re.findall(r"(?m)^\| ([0-9]+) \|", README)+}+if readme_numbers != set(range(1, 34)):+ raise SystemExit("README pattern table must contain patterns 1-33")++if len(SKILL.splitlines()) > 500:+ raise SystemExit("SKILL.md exceeds the 500-line portability budget")++print(f"AI Copywriter package v{skill_version} is valid")