arkaos 4.26.0 → 4.28.0

package/config/skills-provenance.yaml

@@ -59,7 +59,200 @@
 
 baseline_date: 2026-07-14
 
-derived: {}
+derived:
+  # Marketing skills integration campaign — derived from
+  # coreyhaines31/marketingskills (MIT). Frontmatter metadata must match
+  # each entry field-for-field (test_registry_matches_frontmatter_field_for_field).
+  departments/marketing/skills/product-marketing:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/marketing-plan:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/marketing-ideas:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/council:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/landing/skills/offer-create:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/ai-seo:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/aso:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/schema-markup:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/directory-submit:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/ad-creative:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/marketing-psychology:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/marketing-loops:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/content-strategy:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/customer-research:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/competitor-profile:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/public-relations:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/co-marketing:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/sms-campaign:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/free-tools:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/landing/skills/lead-magnet:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/landing/skills/popup-design:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/landing/skills/signup-optimize:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/saas/skills/paywall-design:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/sales/skills/prospecting:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/sales/skills/revops:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/sales/skills/sales-enablement:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/community/skills/community-marketing:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/content/skills/image-create:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  # PR5 — wave-1 merges: existing ArkaOS skills that absorbed Corey content.
+  departments/marketing/skills/ab-test:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/paid-campaign:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/programmatic-seo:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/seo-audit:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/analytics-report:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/cold-email:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/email-sequence:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/social-strategy:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/marketing/skills/competitor-analysis:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/landing/skills/copy-framework:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/landing/skills/optimize-page:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  # PR6 — wave-2 merges: existing ArkaOS skills that absorbed Corey content.
+  departments/saas/skills/churn-analysis:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/saas/skills/onboarding-optimize:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/saas/skills/pricing-strategy:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/saas/skills/launch-execute:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/landing/skills/affiliate-bridge:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/landing/skills/page-architect:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  departments/content/skills/video-produce:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
+  arka/skills/human-writing:
+    origin: community
+    source: https://github.com/coreyhaines31/marketingskills
+    license: MIT
 
 first_party:
   - arka
@@ -73,7 +266,6 @@ first_party:
   - arka/skills/flow
   - arka/skills/forge
   - arka/skills/fusion
-  - arka/skills/human-writing
   - arka/skills/recipes
   - arka/skills/refine
   - arka/skills/research
@@ -121,7 +313,6 @@ first_party:
   - departments/content/skills/short-form
   - departments/content/skills/thumbnail-package
   - departments/content/skills/trend-hunt
-  - departments/content/skills/video-produce
   - departments/content/skills/video-setup
   - departments/content/skills/viral-design
   - departments/content/skills/youtube-strategy
@@ -210,18 +401,13 @@ first_party:
   - departments/kb/skills/zettelkasten-process
   - departments/landing
   - departments/landing/skills/ab-test
-  - departments/landing/skills/affiliate-bridge
   - departments/landing/skills/awareness-diagnose
-  - departments/landing/skills/copy-framework
   - departments/landing/skills/email-sequence
   - departments/landing/skills/funnel-design
   - departments/landing/skills/funnel-metrics
   - departments/landing/skills/headline-write
   - departments/landing/skills/landing-gen
   - departments/landing/skills/launch-sequence
-  - departments/landing/skills/offer-create
-  - departments/landing/skills/optimize-page
-  - departments/landing/skills/page-architect
   - departments/landing/skills/persuasion-apply
   - departments/landing/skills/webinar-funnel
   - departments/leadership
@@ -236,20 +422,11 @@ first_party:
   - departments/leadership/skills/performance-review
   - departments/leadership/skills/team-health
   - departments/marketing
-  - departments/marketing/skills/ab-test
-  - departments/marketing/skills/analytics-report
   - departments/marketing/skills/audience-segment
   - departments/marketing/skills/calendar-plan
-  - departments/marketing/skills/cold-email
-  - departments/marketing/skills/competitor-analysis
   - departments/marketing/skills/content-audit
-  - departments/marketing/skills/email-sequence
   - departments/marketing/skills/growth-loop
   - departments/marketing/skills/marketing-automation
-  - departments/marketing/skills/paid-campaign
-  - departments/marketing/skills/programmatic-seo
-  - departments/marketing/skills/seo-audit
-  - departments/marketing/skills/social-strategy
   - departments/ops
   - departments/ops/skills/bottleneck-find
   - departments/ops/skills/dashboard-build
@@ -298,19 +475,15 @@ first_party:
   - departments/quality
   - departments/saas
   - departments/saas/skills/benchmark-compare
-  - departments/saas/skills/churn-analysis
   - departments/saas/skills/customer-success
   - departments/saas/skills/growth-plan
   - departments/saas/skills/gtm-strategy
-  - departments/saas/skills/launch-execute
   - departments/saas/skills/leaky-bucket
   - departments/saas/skills/metrics-dashboard
   - departments/saas/skills/micro-saas-stack
   - departments/saas/skills/mvp-build
   - departments/saas/skills/niche-evaluate
-  - departments/saas/skills/onboarding-optimize
   - departments/saas/skills/plg-setup
-  - departments/saas/skills/pricing-strategy
   - departments/saas/skills/saas-scaffold
   - departments/saas/skills/validate-idea
   - departments/saas/skills/voc-loop

package/core/registry/generator.py

@@ -111,8 +111,15 @@ def extract_commands_from_skill(skill_path: Path) -> list[dict]:
             continue
         command = match.group(1).strip()
         description = match.group(2).strip()
+        # An ArkaOS command's head token (before the first space) is a
+        # single word — `/mkt`, `/dev`. A slash INSIDE the head means it
+        # is a URL example (`/features/analytics`), not a command; those
+        # appear verbatim in imported site-architecture content. Slashes
+        # in later `<file/pr>`-style placeholders are fine.
         if not command.startswith("/") or "Description" in description or description.startswith("-"):
             continue
+        if "/" in command.split(" ")[0][1:]:
+            continue
         commands.append({
             "command": command,
             "description": description,

package/departments/community/SKILL.md

@@ -37,6 +37,7 @@ allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 | `/community gamify` | Gamification system design | Specialist |
 | `/community moderate` | Moderation rules and escalation | Specialist |
 | `/community event <type>` | Event planning (AMA, workshop, challenge) | Specialist |
+| `/community community-marketing` | Community-led growth and brand loyalty | Focused |
 
 ## Squad
 

package/departments/community/skills/community-marketing/SKILL.md

@@ -0,0 +1,200 @@
+---
+name: community/community-marketing
+description: >
+  Design, launch, and grow an online community that creates value for
+  members while driving retention, activation, word-of-mouth, and
+  community-led growth. TRIGGER: "build a community", "community strategy",
+  "Discord community", "Slack community", "community-led growth", "brand
+  advocates", "user community", "forum strategy", "community engagement",
+  "grow our community", "ambassador program", "community flywheel",
+  "/community community-marketing". Constrói à volta de uma identidade
+  partilhada, não do produto. SKIP: post-signup retention as the primary
+  deliverable -> community/retention-system; event planning ->
+  community/events-plan; day-to-day moderation and safety ->
+  community/moderation; the community's own growth/monetization plan ->
+  community/growth-plan.
+allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
+metadata:
+  origin: community
+  source: https://github.com/coreyhaines31/marketingskills
+  license: MIT
+---
+
+<!-- arka:kb-first-prefix begin -->
+> **KB-first:** query `mcp__obsidian__search_notes` (and
+> `mcp__graphify__query_graph` when configured) and cite `[[wikilinks]]`
+> or graph nodes — or declare the gap — BEFORE any external research.
+> Full doctrine: `arka/SKILL.md` (KB-First Research).
+<!-- arka:kb-first-prefix end -->
+
+# Community Marketing — `/community community-marketing`
+
+> **Agent:** Beatriz (Community Strategist) | **Frameworks:** Community flywheel, shared-identity design, community health metrics
+
+**Context:** read the product marketing context first —
+`WizardingCode/Marketing/product-marketing.md` in Obsidian (KB-first),
+else the project-local `.agents/product-marketing.md`. If neither exists,
+offer to run `/mkt product-marketing`.
+
+You are an expert community builder and community-led growth strategist. Your goal is to help the user design, launch, and grow a community that creates genuine value for members while driving measurable business outcomes.
+
+## Before You Start
+
+**Check for product marketing context first:**
+If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered.
+
+Understand the situation (ask if not provided):
+
+1. **What is the product or brand?** — What problem does it solve, who uses it
+2. **What community platform(s) are in play?** — Discord, Slack, Circle, Reddit, Facebook Groups, forum, etc.
+3. **What stage is the community at?** — Pre-launch, 0–100 members, 100–1k, scaling, or established
+4. **What is the primary community goal?** — Retention, activation, word-of-mouth, support deflection, product feedback, revenue
+5. **Who is the ideal community member?** — Role, motivation, what they hope to get from joining
+
+Work with whatever context is available. If key details are missing, make reasonable assumptions and flag them.
+
+---
+
+## Community Strategy Principles
+
+### Build around a shared identity, not just a product
+
+The strongest communities are built around who members *are* or aspire to be — not around your product. Members join because of the product but stay because of the people and identity.
+
+Examples:
+- Indie hackers (identity: bootstrapped founders)
+- r/homelab (identity: tinkerers who self-host)
+- Figma community (identity: designers who care about craft)
+
+Always define: **What identity does this community reinforce for its members?**
+
+### Value must flow to members first
+
+Every community touchpoint should answer: *What does the member get from this?*
+
+- Exclusive knowledge or early access
+- Peer connections they can't get elsewhere
+- Recognition and status within a group they respect
+- Direct influence on the product roadmap
+- Career opportunities, visibility, or credibility
+
+### The Community Flywheel
+
+Healthy communities compound over time:
+
+```
+Members join → get value → engage → create content/help others
+    ↑                                          ↓
+    ←←←←← new members discover the community ←←
+```
+
+Design for the flywheel from day one. Every decision should ask: *Does this accelerate the loop or slow it down?*
+
+---
+
+## Playbooks by Goal
+
+### Launching a Community from Zero
+
+1. **Recruit 20–50 founding members manually** — DM your most engaged users, beta testers, or fans. Don't open publicly until there is baseline activity.
+2. **Set the culture explicitly** — Write community guidelines that describe the *vibe*, not just the rules. What does great participation look like here?
+3. **Seed conversations before launch** — Pre-populate channels with 5–10 posts that model the behavior you want. Questions, wins, resources.
+4. **Do things that don't scale at first** — Reply to every post. Welcome every new member by name. Host a weekly call. You are buying social proof.
+5. **Define your core loop** — What action do you want members to take weekly? Make it easy and reward it publicly.
+
+### Growing an Existing Community
+
+1. **Audit where members drop off** — Are people joining but not posting? Posting once and disappearing? Identify the leaky stage.
+2. **Create a new member journey** — A pinned welcome post, a #introduce-yourself channel, a DM or email from a community manager, a clear "start here" path.
+3. **Surface member wins publicly** — Showcase user projects, testimonials, milestones. This reinforces identity and signals that participation has rewards.
+4. **Run recurring community rituals** — Weekly threads (e.g., "What are you working on?"), monthly AMAs, seasonal challenges. Rituals create habit.
+5. **Identify and invest in power users** — 1% of members generate 90% of value. Give them recognition, early access, moderator roles, or direct product input.
+
+### Building a Brand Ambassador / Advocate Program
+
+1. **Identify candidates** — Look for people who already recommend you unprompted. Check reviews, social mentions, community posts.
+2. **Make the ask personal** — Don't send a generic form. Reach out 1:1 and explain why you chose them specifically.
+3. **Offer meaningful benefits** — Exclusive access, swag, revenue share, or public recognition — not just "early access to features."
+4. **Give them tools and content** — Referral links, shareable assets, key talking points, a private Slack channel.
+5. **Measure and iterate** — Track referral traffic, signups, and engagement driven by advocates. Double down on what works.
+
+### Community-Led Support (Deflection + Retention)
+
+1. **Create a searchable knowledge base** from top community questions
+2. **Recognize members who help others** — "Community Expert" badges, leaderboards, shoutouts
+3. **Close the loop with product** — When community feedback drives a change, announce it publicly and credit the members who raised it
+4. **Monitor sentiment weekly** — Look for patterns in complaints or confusion before they become churn signals
+
+---
+
+## Platform Selection Guide
+
+| Platform | Best For | Watch Out For |
+|----------|----------|---------------|
+| Discord | Developer, gaming, creator communities; real-time chat | High noise, hard to search, onboarding friction |
+| Slack | B2B / professional communities; familiar to SaaS buyers | Free tier limits history; feels like work |
+| Circle | Creator or course-based communities; clean UX | Less organic discovery; requires driving traffic |
+| Reddit | High-volume public communities; SEO benefit | You don't own it; moderation is hard |
+| Facebook Groups | Consumer brands; older demographics | Declining organic reach; algorithm dependent |
+| Forum (Discourse) | Long-form technical communities; SEO-rich | Slower velocity; higher effort to post |
+
+---
+
+## Community Health Metrics
+
+Track these signals weekly:
+
+- **DAU/MAU ratio** — Stickiness. Above 20% is healthy for most communities.
+- **New member post rate** — % of new members who post within 7 days of joining
+- **Thread reply rate** — % of posts that receive at least one reply
+- **Churn / lurker ratio** — Members who joined but haven't posted in 30+ days
+- **Content created by non-staff** — % of posts not written by the company team
+
+**Warning signs:**
+- Most posts are from the company team, not members
+- Questions go unanswered for >24 hours
+- The same 5 people account for 80%+ of engagement
+- New members stop posting after their intro message
+
+---
+
+## Output Formats
+
+Depending on what the user needs, produce one of:
+
+- **Community Strategy Doc** — Platform choice, identity definition, core loop, 90-day launch plan
+- **Channel Architecture** — Recommended channels/categories with purpose and posting guidelines for each
+- **New Member Journey** — Welcome sequence: pinned post, DM template, first-week prompts
+- **Community Ritual Calendar** — Weekly/monthly recurring events and threads
+- **Ambassador Program Brief** — Criteria, benefits, outreach template, tracking plan
+- **Health Audit Report** — Current metrics, diagnosis, top 3 priorities to fix
+
+Always be specific. Generic advice ("be consistent," "provide value") is not useful. Give the user something they can act on today.
+
+---
+
+## Task-Specific Questions
+
+1. What platform are you building on (or considering)?
+2. What stage is the community at? (Pre-launch, early, growing, established)
+3. What's the primary business goal? (Retention, activation, word-of-mouth, support deflection)
+4. Who is the ideal community member and what motivates them?
+5. Do you have existing users or customers to seed from?
+6. How much time can you dedicate to community management weekly?
+
+---
+
+## Output → Obsidian
+
+`WizardingCode/Community/community-marketing/<deliverable>.md` — strategy
+doc, channel architecture, new-member journey, ritual calendar, ambassador
+brief, or health audit report.
+
+## Related ArkaOS skills
+
+- **community/gamification-design** — badges, leaderboards, and ambassador incentive programs
+- **community/retention-system** — retention strategies that complement community engagement
+- **community/events-plan** — AMAs, rituals, and live community events
+- **community/moderation** — guidelines enforcement and community safety
+- **mkt/social-strategy** — content creation across social platforms
+- **mkt/customer-research** — understanding your community members' needs and language

package/departments/content/SKILL.md

@@ -42,6 +42,7 @@ allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 | `/content research <topic>` | Sourced research compiled into a production brief | Focused |
 | `/content video-setup` | Video production environment bootstrap (Hyperframes, Agent-Reach, Higgsfield) | Specialist |
 | `/content shorts <niche>` | Batch production of 3-5 rendered shorts with posting schedule | Focused |
+| `/content image-create <brief>` | AI image generation and marketing graphics | Focused |
 
 ## Squad
 

package/departments/content/agents/content-strategist.yaml

@@ -56,6 +56,7 @@ expertise:
     - AI-augmented content creation
     - creator monetization
   frameworks:
+    - Human Writing Standard (arka-human-writing) + Stop-Slop structural sweep
     - STEPPS (Berger)
     - Hook Architecture
     - Content OS (GaryVee model)

package/departments/content/agents/repurpose-distributor.yaml

@@ -41,6 +41,7 @@ expertise:
     - AI-assisted content workflows
     - analytics & performance tracking
   frameworks:
+    - Human Writing Standard (arka-human-writing) + Stop-Slop structural sweep
     - GaryVee Pillar→30+ Model
     - Justin Welsh Content OS
     - Platform Algorithm Signals

package/departments/content/agents/scriptwriter.yaml

@@ -51,6 +51,7 @@ expertise:
     - podcast scripts
     - webinar scripts
   frameworks:
+    - Human Writing Standard (arka-human-writing) + Stop-Slop structural sweep
     - Story (McKee)
     - Save the Cat beat sheet
     - Dan Harmon Story Circle

package/departments/content/agents/viral-engineer.yaml

@@ -40,6 +40,7 @@ expertise:
     - trend analysis & riding
     - short-form content (Reels, TikTok, Shorts)
   frameworks:
+    - Human Writing Standard (arka-human-writing) + Stop-Slop structural sweep
     - STEPPS (Berger)
     - Hook Architecture (3-second rule)
     - MrBeast Title/Thumb Method