arkaos 4.26.0 → 4.28.0

package/README.md

@@ -2,7 +2,7 @@
 
 **The Operating System for AI Agent Teams.**
 
-86 agents. 17 departments. 302 skills. Enterprise frameworks. Multi-runtime. One install.
+89 agents. 17 departments. 329 skills. Enterprise frameworks. Multi-runtime. One install.
 
 ```bash
 npx arkaos install
@@ -95,7 +95,7 @@ npx arkaos doctor    # Health check
 
 ### Skill packs, à la carte
 
-The default install ships a curated core so your context window stays lean. Everything else lives in the ArkaOS plugin marketplace: 16 department packs with 206 skills, generated straight from the same sources the core uses. Inside Claude Code:
+The default install ships a curated core so your context window stays lean. Everything else lives in the ArkaOS plugin marketplace: 16 department packs with 258 skills, generated straight from the same sources the core uses. Inside Claude Code:
 
 ```
 /plugin marketplace add andreagroferreira/arka-os
@@ -158,12 +158,12 @@ Every decision, solution, and pattern is captured. The Cognitive Layer curates i
 |-----------|--------|--------|-------------|
 | **Development** | `/dev` | 15 | Full-stack features, APIs, architecture, security, CI/CD |
 | **Brand & Design** | `/brand` | 10 | Brand identity, UX/UI, design systems, naming |
-| **Marketing** | `/mkt` | 4 | SEO, paid ads, email campaigns, growth loops |
+| **Marketing** | `/mkt` | 7 | SEO, paid ads, lifecycle, PR, positioning, growth loops |
 | **Strategy** | `/strat` | 4 | Market analysis, competitive intelligence, business models |
 | **E-Commerce** | `/ecom` | 4 | Store optimization, CRO, pricing, RFM segmentation |
 | **Knowledge** | `/kb` | 4 | Research, Zettelkasten, persona building, ingestion |
 | **Project Mgmt** | `/pm` | 4 | Scrum, Shape Up, discovery, roadmaps |
-| **Content** | `/content` | 4 | Viral hooks, scripts, repurposing, content calendars |
+| **Content** | `/content` | 8 | Viral hooks, scripts, repurposing, content calendars |
 | **Sales** | `/sales` | 4 | Pipeline management, SPIN selling, negotiation |
 | **SaaS** | `/saas` | 5 | Idea validation, metrics, PLG strategy, scaffolding |
 | **Organization** | `/org` | 5 | Org design, team topologies, matrix structure |
@@ -174,7 +174,7 @@ Every decision, solution, and pattern is captured. The Cognitive Layer curates i
 | **Leadership** | `/lead` | 3 | Team health, OKRs, culture, hiring frameworks |
 | **Quality Gate** | (auto) | 3 | Mandatory review on every workflow. Veto power. |
 
-> 86 agents across 17 departments (85 unique; `cro-specialist` is shared by
+> 89 agents across 17 departments (88 unique; `cro-specialist` is shared by
 > E-Commerce and Landing in the matrix structure).
 
 ---
@@ -532,3 +532,5 @@ See [CONTRIBUTING.md](.github/CONTRIBUTING.md). PRs welcome — all changes requ
 ## License
 
 MIT — [WizardingCode](https://wizardingcode.com)
+
+Third-party material incorporated into ArkaOS is indexed in [docs/THIRD-PARTY-NOTICES.md](docs/THIRD-PARTY-NOTICES.md).

package/THE-ARKAOS-GUIDE.md

@@ -1,6 +1,6 @@
 # The ArkaOS Guide
 
-> v4.26.0 — 86 agents, 17 departments, 302 skills, 270 commands, 16 ADRs.
+> v4.28.0 — 89 agents, 17 departments, 329 skills, 297 commands, 16 ADRs.
 > One file, everything you need to start. Generated by `scripts/guide_gen.py` — never hand-edited.
 
 ## What it is
@@ -39,21 +39,21 @@ answers as a generic assistant.
 |---|---|
 | `/arka` | 22 |
 | `/brand` | 12 |
-| `/community` | 14 |
-| `/content` | 19 |
+| `/community` | 15 |
+| `/content` | 20 |
 | `/dev` | 36 |
 | `/do` | 1 |
 | `/ecom` | 18 |
 | `/fin` | 10 |
 | `/kb` | 22 |
-| `/landing` | 14 |
+| `/landing` | 17 |
 | `/lead` | 10 |
-| `/mkt` | 12 |
+| `/mkt` | 30 |
 | `/ops` | 24 |
 | `/org` | 10 |
 | `/pm` | 12 |
-| `/saas` | 14 |
-| `/sales` | 10 |
+| `/saas` | 15 |
+| `/sales` | 13 |
 | `/strat` | 10 |
 
 ## How work ships

package/VERSION

@@ -1 +1 @@
-4.26.0
+4.28.0

package/arka/SKILL.md

@@ -47,7 +47,7 @@ complementary, not alternatives.
 # ArkaOS — Main Orchestrator
 
 > **The Operating System for AI Agent Teams**
-> 86 agents. 17 departments. 302 skills. Multi-runtime. Dashboard. Knowledge RAG.
+> 89 agents. 17 departments. 329 skills. Multi-runtime. Dashboard. Knowledge RAG.
 
 ## ⛔ Evidence flow — 4 gates (NON-NEGOTIABLE)
 

package/arka/skills/human-writing/SKILL.md

@@ -14,6 +14,10 @@ description: >
   SKIP: code-only diffs with no user-facing prose; the APPROVED/REJECTED
   copy verdict — arka-quality (Quality Gate, Eduardo) wins
   (standard applies WHILE writing, the review judges after).
+metadata:
+  origin: community
+  source: https://github.com/coreyhaines31/marketingskills
+  license: MIT
 ---
 
 # Human Writing Standard — ARKA OS Core Skill
@@ -36,6 +40,8 @@ Never use em-dashes (—), en-dashes (–), or hyphens (-) to join clauses. Use
 
 Match the target language's natural register. Portuguese: use Portuguese idioms, not translated English constructs. English: natural rhythm, avoid overly formal constructions.
 
+Portuguese output has its own AI-tell catalogue: `references/pt-pt-anti-slop.md`.
+
 ### 3. Perfect Accentuation and Spelling
 
 Zero tolerance for orthographic errors. Portuguese: ação, é, três, começar. When uncertain, verify before outputting.
@@ -60,6 +66,106 @@ Specific facts, numbers, examples over vague statements. "Reduced load from 3.2s
 
 Use active voice unless subject is genuinely unknown. "The team implemented the feature" beats "The feature was implemented by the team."
 
+### 8. No Formulaic Structures
+
+Structural patterns are stronger AI tells than any single word: they
+survive synonym swaps. Banned: binary contrasts ("not X, it's Y"),
+negative listing, dramatic fragmentation, rhetorical setups ("What if I
+told you..."), false agency (inanimate nouns doing human verbs: "the data
+tells us", "the decision emerges"; name the human), narrator-from-a-distance,
+Wh-word sentence openers, and lazy extremes (every/always/never doing
+vague work). Full catalogue with fixes: `references/structural-patterns.md`.
+Phrase-level companions (throat-clearing openers, emphasis crutches,
+meta-commentary, vague declaratives): `references/anti-slop-phrases.md`.
+
+## Self-Editing Before Delivery
+
+The rules above govern how to write. This section governs how to review your
+own prose before it ships, which is where most AI-tells get caught. Run a
+focused pass per dimension instead of one vague read. After each pass,
+recheck the earlier ones so a fix does not reintroduce an old problem.
+
+### The Seven Sweeps
+
+A sequential editing method for high-stakes prose (landing pages, launch
+emails, sales pages). Each sweep looks for one thing:
+
+1. **Clarity:** can the reader understand it? Cut confusing structures, unclear pronouns, insider jargon, and buried points.
+2. **Voice and tone:** does it sound consistent? Catch drift from casual to corporate, mixed references, and accidental mood shifts.
+3. **So what:** does every claim answer "why should I care?" Bridge each feature to a benefit the reader wants.
+4. **Prove it:** is every claim supported? Replace "trusted by thousands" and "industry-leading" with named proof, numbers, and specifics.
+5. **Specificity:** is it concrete? Swap vague verbs for numbers, timeframes, and examples. "Save 4 hours a week" beats "save time."
+6. **Heightened emotion:** does it make the reader feel something? Make the pain and the desired outcome vivid without manipulation.
+7. **Zero risk:** is every barrier to action removed near the CTA? Answer objections, add trust signals, and state the next step plainly.
+
+For a final QA pass, work the full checklist in
+[references/checklist.md](references/checklist.md).
+
+### Quick-Pass Checks
+
+When a full seven-sweep review is not warranted, run these faster checks.
+
+**Cut these words:** very, really, extremely, incredibly (weak intensifiers);
+just, actually, basically (filler); "in order to" (use "to"); "that" when it
+adds nothing; "things" and "stuff" (too vague).
+
+**Watch for:** adverbs (cut by default; one survives only if deleting it
+changes the meaning), passive voice (switch to active per Rule 7), and
+nominalizations (turn the noun back into a verb, so "make a decision"
+becomes "decide").
+
+**Structural sweep (Rule 8):** no Wh-word sentence openers; no "not X,
+it's Y" contrasts; name the human behind inanimate verbs (false agency);
+cut throat-clearing openers ("Here's the thing:", "It turns out"); rewrite
+anything that sounds like a pull-quote; default to two list items, a third
+must earn its place; vary paragraph endings instead of closing every one
+punchily.
+
+**Sentence level:** one idea per sentence, varied length, important
+information first, no more than three conjunctions, usually under 25 words.
+
+**Paragraph level:** one topic per paragraph, 2 to 4 sentences for web,
+strong opening sentences, and enough white space to stay scannable.
+
+### Slop Score
+
+A fast quantitative gate, complement to the Seven Sweeps. Rate the draft
+1 to 10 on each dimension; below 35/50, revise before delivering.
+
+| Dimension | Question |
+|-----------|----------|
+| Directness | Statements or announcements? |
+| Rhythm | Varied or metronomic? |
+| Trust | Respects reader intelligence? |
+| Authenticity | Sounds human? |
+| Density | Anything cuttable? |
+
+Eduardo (Quality Gate) applies the same rubric to changed copy: below
+35/50 on COPY-scope prose is a blocker.
+
+## Plain-English Alternatives
+
+Rule 5 already bans the worst AI words and maps their replacements. Extend it
+with these common offenders:
+
+| Weak or complex | Plain |
+|-----------------|-------|
+| Implement | Set up |
+| Facilitate | Help |
+| Innovative | New |
+| Cutting-edge | New, modern |
+
+The full substitution list lives in
+[references/plain-english-alternatives.md](references/plain-english-alternatives.md).
+
+## Refreshing Existing Content
+
+Prose decays. Stats go stale, examples age, and brand voice drifts across
+edits by different hands. When traffic is declining, data is old, or the
+product has changed, refresh rather than rewrite. The refresh checklist, the
+refresh-versus-rewrite matrix, and a cadence guide are in
+[references/content-refresh.md](references/content-refresh.md).
+
 ## Enforcement
 
 Constitution L0 injection · Self-critique phase before delivery · Cross-department application. Agents who violate must revise before delivering.

package/arka/skills/human-writing/references/anti-slop-phrases.md

@@ -0,0 +1,131 @@
+<!-- Derived from stop-slop by Hardik Pandya — https://github.com/hardikpandya/stop-slop -->
+<!-- MIT — Copyright (c) 2025 Hardik Pandya. See docs/THIRD-PARTY-NOTICES.md. -->
+
+# Anti-Slop Phrases — arka-human-writing
+
+Complements `forbidden-patterns.md` (Rule 5) and the constitution
+`no-ai-cliches` list. Entries already banned there are not repeated here.
+
+## Throat-Clearing Openers
+
+Remove these announcement phrases. State the content directly.
+
+- "Here's the thing:"
+- "Here's what [X]"
+- "Here's this [X]"
+- "Here's that [X]"
+- "Here's why [X]"
+- "The uncomfortable truth is"
+- "It turns out"
+- "The real [X] is"
+- "Let me be clear"
+- "The truth is,"
+- "I'll say it again:"
+- "I'm going to be honest"
+- "Can we talk about"
+- "Here's what I find interesting"
+- "Here's the problem though"
+
+Any "here's what/this/that" construction is throat-clearing before the point. Cut it and state the point.
+
+## Emphasis Crutches
+
+These add no meaning. Delete them.
+
+- "Full stop." / "Period."
+- "Let that sink in."
+- "This matters because"
+- "Make no mistake"
+- "Here's why that matters"
+
+## Business Jargon
+
+Replace with plain language. ("Navigate", "deep dive", "cutting-edge",
+"game-changer" and "moving forward" are already banned by the constitution
+list and Rule 5.)
+
+| Avoid | Use instead |
+|-------|-------------|
+| Unpack (analysis) | Explain, examine |
+| Lean into | Accept, embrace |
+| Landscape (context) | Situation, field |
+| Double down | Commit, increase |
+| Take a step back | Reconsider |
+| Circle back | Return to, revisit |
+| On the same page | Aligned, agreed |
+
+## Adverbs
+
+Cut adverbs by default; one survives only if deleting it changes the
+meaning. No softeners, no intensifiers, no hedges.
+
+Specific offenders:
+
+- "really"
+- "just"
+- "literally"
+- "genuinely"
+- "honestly"
+- "simply"
+- "actually"
+- "deeply"
+- "truly"
+- "fundamentally"
+- "inherently"
+- "inevitably"
+- "interestingly"
+- "importantly"
+- "crucially"
+
+Also cut these filler phrases:
+
+- "At its core"
+- "In today's [X]"
+- "When it comes to"
+- "In a world where"
+- "The reality is"
+
+## Meta-Commentary
+
+Remove self-referential asides. The text should move, not announce its own structure.
+
+- "Hint:"
+- "Plot twist:" / "Spoiler:"
+- "You already know this, but"
+- "But that's another post"
+- "X is a feature, not a bug"
+- "Dressed up as"
+- "The rest of this essay explains..."
+- "Let me walk you through..."
+- "In this section, we'll..."
+- "As we'll see..."
+- "I want to explore..."
+
+## Performative Emphasis
+
+False intimacy or manufactured sincerity:
+
+- "creeps in"
+- "I promise"
+- "They exist, I promise"
+
+## Telling Instead of Showing
+
+Announcing difficulty or significance rather than demonstrating it:
+
+- "This is genuinely hard"
+- "This is what leadership actually looks like"
+- "This is what X actually looks like"
+- "actually matters"
+
+## Vague Declaratives
+
+Sentences that announce importance without naming the specific thing. Kill these.
+
+- "The reasons are structural"
+- "The implications are significant"
+- "This is the deepest problem"
+- "The stakes are high"
+- "The consequences are real"
+
+If a sentence says something is important/deep/structural without showing the specific thing, cut it or replace it with the specific thing.

package/arka/skills/human-writing/references/checklist.md

@@ -0,0 +1,66 @@
+# Copy Editing Checklist
+
+Use this checklist alongside the Seven Sweeps Framework (see SKILL.md) as a final QA pass before delivering edited copy.
+
+## Before You Start
+
+- [ ] Understand the goal of this copy
+- [ ] Know the target audience
+- [ ] Identify the desired action
+- [ ] Read through once without editing
+
+## Clarity (Sweep 1)
+
+- [ ] Every sentence is immediately understandable
+- [ ] No jargon without explanation
+- [ ] Pronouns have clear references
+- [ ] No sentences trying to do too much
+
+## Voice & Tone (Sweep 2)
+
+- [ ] Consistent formality level throughout
+- [ ] Brand personality maintained
+- [ ] No jarring shifts in mood
+- [ ] Reads well aloud
+
+## So What (Sweep 3)
+
+- [ ] Every feature connects to a benefit
+- [ ] Claims answer "why should I care?"
+- [ ] Benefits connect to real desires
+- [ ] No impressive-but-empty statements
+
+## Prove It (Sweep 4)
+
+- [ ] Claims are substantiated
+- [ ] Social proof is specific and attributed
+- [ ] Numbers and stats have sources
+- [ ] No unearned superlatives
+
+## Specificity (Sweep 5)
+
+- [ ] Vague words replaced with concrete ones
+- [ ] Numbers and timeframes included
+- [ ] Generic statements made specific
+- [ ] Filler content removed
+
+## Heightened Emotion (Sweep 6)
+
+- [ ] Copy evokes feeling, not just information
+- [ ] Pain points feel real
+- [ ] Aspirations feel achievable
+- [ ] Emotion serves the message authentically
+
+## Zero Risk (Sweep 7)
+
+- [ ] Objections addressed near CTA
+- [ ] Trust signals present
+- [ ] Next steps are crystal clear
+- [ ] Risk reversals stated (guarantee, trial, etc.)
+
+## Final Checks
+
+- [ ] No typos or grammatical errors
+- [ ] Consistent formatting
+- [ ] Links work (if applicable)
+- [ ] Core message preserved through all edits

package/arka/skills/human-writing/references/content-refresh.md

@@ -0,0 +1,38 @@
+# Content Refresh Editing
+
+Copy editing isn't just for new content. Existing pages and posts decay over time — outdated stats, stale examples, drifted brand voice, and missed SEO opportunities. A content refresh applies the same editing rigor to content that's already published.
+
+## When to Refresh
+
+- **Traffic declining** on a page that used to perform well
+- **Stats or data** are more than 12 months old
+- **Product has changed** — features, pricing, or positioning no longer match
+- **Competitors updated** their version of the same content
+- **AI search visibility** matters — outdated content gets cited less (see ai-seo skill)
+
+## Content Refresh Checklist
+
+1. **Freshness pass** — Update all dates, stats, and examples. Replace "in 2024" with current data. Remove references to deprecated features or tools.
+2. **Accuracy pass** — Verify all claims are still true. Check that linked resources still exist. Confirm pricing and feature descriptions match current state.
+3. **Voice pass** — Does the tone match your current brand voice? Older content often reflects an earlier stage of the company.
+4. **SEO pass** — Has search intent shifted for this topic? Are there new keywords or questions to address? Add "Last updated: [date]" prominently.
+5. **Proof pass** — Can you add newer testimonials, case studies, or data points that didn't exist when this was first published?
+6. **Structure pass** — Add comparison tables, FAQ sections, or other scannable formats that make the content easier to consume.
+
+## Refresh vs. Rewrite
+
+| Signal | Action |
+|--------|--------|
+| Core message still valid, details outdated | Refresh (update facts, stats, examples) |
+| Brand voice has evolved significantly | Refresh + voice rewrite |
+| Topic angle or audience has shifted | Full rewrite |
+| Page structure doesn't match current search intent | Full rewrite |
+| Just needs updated stats and links | Light refresh |
+
+## Refresh Cadence
+
+- **Pricing and product pages**: Every quarter, or when pricing/features change
+- **High-traffic blog posts**: Every 6 months
+- **Comparison and alternatives pages**: Every 3-6 months (competitors change fast)
+- **Evergreen guides**: Annually, unless traffic drops sooner
+- **Low-traffic pages**: Only when traffic data suggests an opportunity