@growthub/cli 0.14.5 → 0.14.6

package/assets/worker-kits/growthub-geo-seo-v1/templates/llmstxt-plan.md

@@ -1,173 +0,0 @@
-# llms.txt Plan
-
-> Template: `templates/llmstxt-plan.md`
-> Save output to: `output/<client-slug>/<project-slug>/LlmstxtPlan_v<N>_<YYYYMMDD>.md`
-
----
-
-## Domain
-
-| Field | Value |
-|---|---|
-| Domain | <!-- https://domain.com --> |
-| Client | <!-- client_name --> |
-| Plan Date | <!-- YYYY-MM-DD --> |
-| Execution Mode | <!-- local-fork / agent-only --> |
-| Auto-generation available | <!-- yes (use scripts/llmstxt_generator.py) / no (manual) --> |
-
----
-
-## Current Status
-
-| File | Status | URL Checked | Notes |
-|---|---|---|---|
-| `llms.txt` | <!-- exists / missing / malformed --> | `https://domain.com/llms.txt` | <!-- contents summary if exists --> |
-| `llms-full.txt` | <!-- exists / missing --> | `https://domain.com/llms-full.txt` | <!-- contents summary if exists --> |
-
-**Current llms.txt contents (if present):**
-
-```
-<!-- Paste current llms.txt here, or mark as "File not found" -->
-```
-
----
-
-## Why llms.txt Matters
-
-`llms.txt` is a plain-text file that signals to AI language model crawlers which content on your site is intended to be read, indexed, and cited by AI systems. It follows the pattern of `robots.txt` but is specifically designed for LLM training and retrieval systems.
-
-Sites without `llms.txt` rely on AI crawlers interpreting `robots.txt` rules only — missing an opportunity to explicitly surface high-quality content for AI citation.
-
----
-
-## Proposed llms.txt
-
-```
-# llms.txt for <!-- domain.com -->
-# Generated: <!-- YYYY-MM-DD -->
-# Documentation: https://llmstxt.org
-
-# === Allowed for all AI systems ===
-User-agent: *
-
-# Primary content for AI training and citation
-Allow: /blog/
-Allow: /resources/
-Allow: /case-studies/
-Allow: /documentation/
-Allow: /about/
-Allow: /services/
-
-# === Explicitly disallow private or non-content paths ===
-Disallow: /admin/
-Disallow: /checkout/
-Disallow: /account/
-Disallow: /api/
-Disallow: /wp-admin/
-Disallow: /search/
-
-# === Content description ===
-# Site-name: <!-- Client Name -->
-# Site-description: <!-- One sentence describing what the site is about -->
-# Primary-language: en
-# Content-types: articles, guides, case studies, product documentation
-# Last-updated: <!-- YYYY-MM-DD -->
-```
-
----
-
-## Proposed llms-full.txt
-
-`llms-full.txt` is an extended version that provides AI systems with a structured content index — similar to a sitemap but optimized for LLM retrieval.
-
-```
-# llms-full.txt for <!-- domain.com -->
-# Generated: <!-- YYYY-MM-DD -->
-# Full content index for AI language model retrieval
-
-## Site Overview
-- Name: <!-- Client Name -->
-- Domain: <!-- https://domain.com -->
-- Primary Service: <!-- one-line description -->
-- Industry: <!-- industry category -->
-- Language: English
-
-## Primary Content Categories
-
-### Blog / Articles
-- <!-- https://domain.com/blog/ --> — All blog posts and articles
-- <!-- https://domain.com/blog/category-1/ --> — <!-- Category description -->
-- <!-- https://domain.com/blog/category-2/ --> — <!-- Category description -->
-
-### Resources
-- <!-- https://domain.com/resources/ --> — Guides, whitepapers, tools
-- <!-- https://domain.com/resources/guide-1/ --> — <!-- Guide title and description -->
-
-### Services / Products
-- <!-- https://domain.com/services/ --> — Service overview
-- <!-- https://domain.com/services/service-1/ --> — <!-- Service name and description -->
-- <!-- https://domain.com/services/service-2/ --> — <!-- Service name and description -->
-
-### About / Trust
-- <!-- https://domain.com/about/ --> — Company background and team
-- <!-- https://domain.com/case-studies/ --> — Client case studies and results
-
-## Contact
-- <!-- support@domain.com -->
-
-## Sitemap
-- <!-- https://domain.com/sitemap.xml -->
-```
-
----
-
-## Implementation Steps
-
-| Step | Action | Owner | Tool | Estimated Time |
-|---|---|---|---|---|
-| 1 | Create `llms.txt` file at domain root | <!-- Dev / Content --> | Text editor | 15 min |
-| 2 | Verify file is accessible at `https://domain.com/llms.txt` | <!-- Dev --> | curl or browser | 5 min |
-| 3 | Create `llms-full.txt` with content index | <!-- Content --> | Text editor / generator | 30 min |
-| 4 | Verify `llms-full.txt` accessible | <!-- Dev --> | curl or browser | 5 min |
-| 5 | Add `llms.txt` reference in robots.txt | <!-- Dev --> | Text editor | 5 min |
-| 6 | Re-run crawler access check to confirm access | <!-- Operator --> | `/geo crawlers` | 10 min |
-| 7 | Set calendar reminder to update llms-full.txt monthly | <!-- Owner --> | Calendar | 2 min |
-
----
-
-## robots.txt Addition
-
-Add this line to `robots.txt` to surface `llms.txt` to AI crawlers:
-
-```
-# AI Content Access
-LLMs-txt: https://<!-- domain.com -->/llms.txt
-```
-
----
-
-## Auto-generation Command Reference
-
-If the geo-seo-claude fork is available, generate `llms.txt` automatically:
-
-```bash
-# Generate llms.txt from sitemap
-python scripts/llmstxt_generator.py --domain https://domain.com --from-sitemap
-
-# Generate llms-full.txt with content index
-python scripts/llmstxt_generator.py --domain https://domain.com --full
-
-# Preview without writing files
-python scripts/llmstxt_generator.py --domain https://domain.com --dry-run
-```
-
----
-
-## Maintenance Schedule
-
-| Task | Frequency | Trigger |
-|---|---|---|
-| Update `llms-full.txt` content index | Monthly | New content published |
-| Verify `llms.txt` is still accessible | Weekly (automated) | robots.txt or server change |
-| Review disallow rules | Quarterly | New product areas or pages |
-| Re-run `/geo crawlers` after any change | On change | Any robots.txt or llms.txt edit |

package/assets/worker-kits/growthub-geo-seo-v1/templates/project.md

@@ -1,48 +0,0 @@
----
-# .growthub-fork/project.md — session memory primitive (v1)
-#
-# Written by the CLI at init/import time. Append-only, human-readable; sits
-# alongside the machine-readable `trace.jsonl`. Approvals, self-eval outcomes,
-# and sub-skill runs all record here.
-#
-# Replaceable tokens (seeded at init time):
-#   {{KIT_ID}}   {{FORK_ID}}   {{STARTED_AT}}   {{SOURCE}}   {{SOURCE_REF}}
-
-kitId: "{{KIT_ID}}"
-forkId: "{{FORK_ID}}"
-startedAt: "{{STARTED_AT}}"
-source: "{{SOURCE}}"
-sourceRef: "{{SOURCE_REF}}"
-skillManifestVersion: 1
-approvals: []
-selfEvalHistory: []
-subSkillRuns: []
----
-
-# Project journal — fork `{{FORK_ID}}`
-
-Baseline primitive: `{{KIT_ID}}`. Seeded at `{{STARTED_AT}}` from `{{SOURCE}}` (`{{SOURCE_REF}}`).
-
-This is your cross-session continuity surface. Read the last few entries before every session; append after every material change, approval, and self-eval boundary.
-
-## How to use this file
-
-1. **Session start.** Read the last 3 entries + tail 20 events in `.growthub-fork/trace.jsonl`. State your plan.
-2. **Material change.** Record as a dated bullet (what, why, outcome). Simultaneously append a typed event to `trace.jsonl` via the Fork Sync Agent — never bypass.
-3. **Approval boundary.** Add a row to `approvals` in the frontmatter (verbatim decision).
-4. **Self-eval boundary.** Append to `selfEvalHistory`: `attempt`, `criteria`, `outcome`, `notes`. Enforce `maxRetries: 3`.
-5. **Sub-skill spawn.** Append to `subSkillRuns`: `subSkill`, `startedAt`, `result`.
-
-## Session log
-
-<!-- Append newest entries at the bottom. Format:
-
-### {{YYYY-MM-DD HH:mm UTC}} · {{skill-slug}}
-- **Plan.** What you intend to do.
-- **Changes.** Material changes (each must correspond to a trace event).
-- **Outcome.** Pass / fail / parked. Reference self-eval criteria.
-- **Next.** What the next session should pick up.
-
--->
-
-_No sessions recorded yet. Populated as the fork is operated._

package/assets/worker-kits/growthub-geo-seo-v1/templates/remediation-roadmap.md

@@ -1,150 +0,0 @@
-# Remediation Roadmap
-
-> Template: `templates/remediation-roadmap.md`
-> Save output to: `output/<client-slug>/<project-slug>/RemediationRoadmap_v<N>_<YYYYMMDD>.md`
-
----
-
-## Client / URL
-
-| Field | Value |
-|---|---|
-| Client | <!-- client_name --> |
-| Target URL | <!-- https://... --> |
-| Roadmap Date | <!-- YYYY-MM-DD --> |
-| Roadmap Owner | <!-- account_owner --> |
-| Overall GEO Score Before | <!-- N / 100 (Grade) --> |
-| Target GEO Score | <!-- N / 100 (Grade) --> |
-| Timeline | <!-- 4-week sprint starting YYYY-MM-DD --> |
-
----
-
-## Current vs. Target Score
-
-| Component | Current Score | Target Score | Gap |
-|---|---|---|---|
-| AI Citability & Visibility | <!-- N --> | <!-- N --> | <!-- +N --> |
-| Brand Authority | <!-- N --> | <!-- N --> | <!-- +N --> |
-| Content Quality & E-E-A-T | <!-- N --> | <!-- N --> | <!-- +N --> |
-| Technical Foundations | <!-- N --> | <!-- N --> | <!-- +N --> |
-| Structured Data | <!-- N --> | <!-- N --> | <!-- +N --> |
-| Platform Optimization | <!-- N --> | <!-- N --> | <!-- +N --> |
-| **Composite GEO Score** | **<!-- N -->** | **<!-- N -->** | **<!-- +N -->** |
-
----
-
-## Priority Matrix
-
-Issues are ranked by Impact × Urgency:
-
-| ID | Issue | Component | Impact | Urgency | Priority |
-|---|---|---|---|---|---|
-| R01 | <!-- issue description --> | <!-- component --> | <!-- High / Med / Low --> | <!-- Immediate / Sprint / Backlog --> | P0 |
-| R02 | <!-- issue description --> | <!-- component --> | <!-- High / Med / Low --> | <!-- Immediate / Sprint / Backlog --> | P0 |
-| R03 | <!-- issue description --> | <!-- component --> | <!-- High / Med / Low --> | <!-- Immediate / Sprint / Backlog --> | P1 |
-| R04 | <!-- issue description --> | <!-- component --> | <!-- High / Med / Low --> | <!-- Immediate / Sprint / Backlog --> | P1 |
-| R05 | <!-- issue description --> | <!-- component --> | <!-- High / Med / Low --> | <!-- Immediate / Sprint / Backlog --> | P2 |
-| R06 | <!-- issue description --> | <!-- component --> | <!-- High / Med / Low --> | <!-- Immediate / Sprint / Backlog --> | P2 |
-| R07 | <!-- issue description --> | <!-- component --> | <!-- High / Med / Low --> | <!-- Immediate / Sprint / Backlog --> | P3 |
-
----
-
-## 4-Week Sprint Plan
-
-### Week 1 — Technical Unblocking and Crawler Access
-
-| # | Action | Issue ID | Owner | Expected Score Impact | Priority |
-|---|---|---|---|---|---|
-| 1.1 | <!-- e.g., Remove GPTBot block from robots.txt --> | R01 | <!-- Dev --> | +<!-- N --> pts (AI Citability) | P0 |
-| 1.2 | <!-- e.g., Create llms.txt at domain root --> | R02 | <!-- Dev / Content --> | +<!-- N --> pts (AI Citability) | P0 |
-| 1.3 | <!-- e.g., Add Sitemap directive to robots.txt --> | R03 | <!-- Dev --> | +<!-- N --> pts (Technical) | P1 |
-| 1.4 | <!-- e.g., Enforce HTTPS redirect from HTTP --> | R04 | <!-- Dev --> | +<!-- N --> pts (Technical) | P1 |
-| 1.5 | <!-- e.g., Add Organization schema to homepage --> | R05 | <!-- Dev --> | +<!-- N --> pts (Structured Data) | P1 |
-
-**Week 1 projected score gain:** +<!-- N --> points (<!-- current → new -->)
-
----
-
-### Week 2 — Schema and Content Infrastructure
-
-| # | Action | Issue ID | Owner | Expected Score Impact | Priority |
-|---|---|---|---|---|---|
-| 2.1 | <!-- e.g., Add FAQPage schema to top 3 service pages --> | R06 | <!-- Dev --> | +<!-- N --> pts (Structured Data) | P1 |
-| 2.2 | <!-- e.g., Add Article schema to all blog posts --> | R07 | <!-- Dev --> | +<!-- N --> pts (Structured Data) | P2 |
-| 2.3 | <!-- e.g., Rewrite top 5 pages' intro paragraphs for answer-block quality --> | R08 | <!-- Content --> | +<!-- N --> pts (Content) | P2 |
-| 2.4 | <!-- e.g., Add statistical data to 3 thin service pages --> | R09 | <!-- Content --> | +<!-- N --> pts (Content) | P2 |
-| 2.5 | <!-- e.g., Add author byline and bio to all blog posts --> | R10 | <!-- Content --> | +<!-- N --> pts (E-E-A-T) | P2 |
-
-**Week 2 projected score gain:** +<!-- N --> points
-
----
-
-### Week 3 — E-E-A-T Depth and Citability Optimization
-
-| # | Action | Issue ID | Owner | Expected Score Impact | Priority |
-|---|---|---|---|---|---|
-| 3.1 | <!-- e.g., Publish original research study or data report --> | R11 | <!-- Content --> | +<!-- N --> pts (E-E-A-T) | P2 |
-| 3.2 | <!-- e.g., Add llms-full.txt with content index --> | R12 | <!-- Content / Dev --> | +<!-- N --> pts (AI Citability) | P2 |
-| 3.3 | <!-- e.g., Reduce pronoun-to-noun ratio on 5 key pages --> | R13 | <!-- Content --> | +<!-- N --> pts (Citability) | P2 |
-| 3.4 | <!-- e.g., Add 3 external authority citations per blog post --> | R14 | <!-- Content --> | +<!-- N --> pts (E-E-A-T) | P2 |
-| 3.5 | <!-- e.g., Implement BreadcrumbList schema site-wide --> | R15 | <!-- Dev --> | +<!-- N --> pts (Structured Data) | P2 |
-
-**Week 3 projected score gain:** +<!-- N --> points
-
----
-
-### Week 4 — Brand Authority and Platform Seeding
-
-| # | Action | Issue ID | Owner | Expected Score Impact | Priority |
-|---|---|---|---|---|---|
-| 4.1 | <!-- e.g., Create and optimize LinkedIn company page --> | R16 | <!-- Marketing --> | +<!-- N --> pts (Brand Authority) | P3 |
-| 4.2 | <!-- e.g., Answer 5 Quora questions in target niche --> | R17 | <!-- Marketing --> | +<!-- N --> pts (Brand Authority) | P3 |
-| 4.3 | <!-- e.g., Post original thread on HackerNews or Reddit --> | R18 | <!-- Marketing --> | +<!-- N --> pts (Brand Authority) | P3 |
-| 4.4 | <!-- e.g., Set up monthly GEO rescore monitoring --> | R19 | <!-- Operator --> | Baseline maintenance | P3 |
-| 4.5 | <!-- e.g., Run /geo audit rescore and compare to baseline --> | R20 | <!-- Operator --> | Measurement | P3 |
-
-**Week 4 projected score gain:** +<!-- N --> points
-
----
-
-## Quick Wins (This Week — Under 2 Hours Each)
-
-These items require minimal effort and have immediate score impact:
-
-- [ ] **Remove GPTBot block from robots.txt** — unblocks ChatGPT indexing immediately
-- [ ] **Add Sitemap directive to robots.txt** — 5-minute fix, improves Technical score
-- [ ] **Create a basic llms.txt** — 15-minute task, signals AI-crawler intent
-- [ ] **Add Organization JSON-LD to homepage** — copy from Schema Validation report code snippet
-- [ ] **Verify llms.txt is accessible** — `curl https://domain.com/llms.txt`
-
----
-
-## Medium-Term Actions (Weeks 2–3)
-
-- Schema deployment across all primary page types
-- Content rewrites targeting citability metrics (answer blocks, statistical density)
-- E-E-A-T improvements: author bios, external citations, original data
-
----
-
-## Strategic Actions (Week 4+)
-
-- Brand authority platform seeding (LinkedIn, Quora, Reddit, HackerNews)
-- Original research publication for uniqueness signals
-- Monthly rescore loop using `/geo audit` to track improvements
-
----
-
-## Estimated Score After Full Roadmap
-
-| Component | Before | After | Change |
-|---|---|---|---|
-| AI Citability & Visibility | <!-- N --> | <!-- N --> | <!-- +N --> |
-| Brand Authority | <!-- N --> | <!-- N --> | <!-- +N --> |
-| Content Quality & E-E-A-T | <!-- N --> | <!-- N --> | <!-- +N --> |
-| Technical Foundations | <!-- N --> | <!-- N --> | <!-- +N --> |
-| Structured Data | <!-- N --> | <!-- N --> | <!-- +N --> |
-| Platform Optimization | <!-- N --> | <!-- N --> | <!-- +N --> |
-| **Composite GEO Score** | **<!-- N (Grade) -->** | **<!-- N (Grade) -->** | **<!-- +N -->** |
-
-**Rescore date:** <!-- YYYY-MM-DD (30 days from roadmap start) -->

package/assets/worker-kits/growthub-geo-seo-v1/templates/schema-validation.md

@@ -1,177 +0,0 @@
-# Schema Validation Report
-
-> Template: `templates/schema-validation.md`
-> Save output to: `output/<client-slug>/<project-slug>/SchemaValidation_v<N>_<YYYYMMDD>.md`
-
----
-
-## URL Analyzed
-
-| Field | Value |
-|---|---|
-| Target URL | <!-- https://... --> |
-| Client | <!-- client_name --> |
-| Page Type | <!-- homepage / article / product / local business / other --> |
-| Analysis Date | <!-- YYYY-MM-DD --> |
-| Execution Mode | <!-- local-fork / agent-only --> |
-| Schema Format Found | <!-- JSON-LD / Microdata / RDFa / none --> |
-
----
-
-## Schema Types Found
-
-| Schema Type | Format | Count | Location | Complete? |
-|---|---|---|---|---|
-| <!-- e.g., Organization --> | <!-- JSON-LD --> | <!-- N --> | <!-- <head> / inline --> | <!-- yes / partial / no --> |
-| <!-- e.g., WebSite --> | <!-- JSON-LD --> | <!-- N --> | <!-- <head> / inline --> | <!-- yes / partial / no --> |
-| <!-- e.g., Article --> | <!-- JSON-LD --> | <!-- N --> | <!-- <head> / inline --> | <!-- yes / partial / no --> |
-| <!-- e.g., BreadcrumbList --> | <!-- JSON-LD --> | <!-- N --> | <!-- <head> / inline --> | <!-- yes / partial / no --> |
-| <!-- e.g., FAQPage --> | <!-- JSON-LD --> | <!-- N --> | <!-- <head> / inline --> | <!-- yes / partial / no --> |
-| <!-- e.g., HowTo --> | <!-- JSON-LD --> | <!-- N --> | <!-- <head> / inline --> | <!-- yes / partial / no --> |
-| <!-- e.g., Product --> | <!-- JSON-LD --> | <!-- N --> | <!-- <head> / inline --> | <!-- yes / partial / no --> |
-| <!-- e.g., LocalBusiness --> | <!-- JSON-LD --> | <!-- N --> | <!-- <head> / inline --> | <!-- yes / partial / no --> |
-
-**Total schema types found:** <!-- N -->
-
----
-
-## Raw Schema Markup
-
-```json
-// Paste JSON-LD block(s) found on the page, or mark as "No JSON-LD found"
-```
-
----
-
-## Validation Errors
-
-| Schema Type | Property | Error Type | Severity | Notes |
-|---|---|---|---|---|
-| <!-- e.g., Organization --> | <!-- e.g., `url` --> | <!-- Missing required / Incorrect type / Invalid value --> | <!-- Critical / Warning / Info --> | <!-- description of the error --> |
-| <!-- schema type --> | <!-- property --> | <!-- error type --> | <!-- severity --> | <!-- notes --> |
-| <!-- schema type --> | <!-- property --> | <!-- error type --> | <!-- severity --> | <!-- notes --> |
-
-**Total errors found:** <!-- N critical / N warnings / N info -->
-
----
-
-## Missing Recommended Schema Types
-
-| Schema Type | Why It Matters | Page Type It Applies To | Priority |
-|---|---|---|---|
-| Organization | Required for brand entity graph — enables Knowledge Panel signals | Homepage | P0 |
-| WebSite | Enables Sitelinks search box in Google; signals site structure to AI | Homepage | P0 |
-| FAQPage | Directly feeds Google AI Overviews and Perplexity answer blocks | FAQ / Service pages | P1 |
-| Article | Required for Google News inclusion and AI content citation | Blog posts | P1 |
-| BreadcrumbList | Improves AI understanding of site hierarchy | All pages | P1 |
-| HowTo | Direct AI-citable structured content for how-to queries | Tutorial pages | P2 |
-| Product | Required for e-commerce AI visibility | Product pages | P2 |
-| LocalBusiness | Required for local AI search and map packs | Location pages | P2 |
-| SpeakableSpecification | Signals to Google which content is suitable for voice / AI reading | Articles | P3 |
-
-> Note: Only list types that apply to this site's actual page types. Remove rows that don't apply.
-
----
-
-## Schema Coverage Score
-
-| Metric | Value | Notes |
-|---|---|---|
-| Schema types present | <!-- N --> | |
-| Schema types with no errors | <!-- N --> | |
-| Schema types with errors | <!-- N --> | |
-| Coverage completeness | <!-- N% --> | <!-- types complete / total types found --> |
-| Schema score | <!-- 0–100 --> | |
-
----
-
-## Implementation Priority Table
-
-| Priority | Schema Type | Action | Effort | Expected Impact |
-|---|---|---|---|---|
-| P0 | <!-- type --> | <!-- Add / Fix / Remove --> | <!-- Low / Medium / High --> | <!-- Critical / High --> |
-| P0 | <!-- type --> | <!-- Add / Fix / Remove --> | <!-- Low / Medium / High --> | <!-- Critical / High --> |
-| P1 | <!-- type --> | <!-- Add / Fix / Remove --> | <!-- Low / Medium / High --> | <!-- High --> |
-| P1 | <!-- type --> | <!-- Add / Fix / Remove --> | <!-- Low / Medium / High --> | <!-- High --> |
-| P2 | <!-- type --> | <!-- Add / Fix / Remove --> | <!-- Low / Medium / High --> | <!-- Medium --> |
-| P3 | <!-- type --> | <!-- Add / Fix / Remove --> | <!-- Low / Medium / High --> | <!-- Low --> |
-
----
-
-## Code Snippets: Recommended Additions
-
-### Organization (add to homepage `<head>`)
-
-```json
-{
-  "@context": "https://schema.org",
-  "@type": "Organization",
-  "name": "<!-- Company Name -->",
-  "url": "<!-- https://domain.com -->",
-  "logo": "<!-- https://domain.com/logo.png -->",
-  "sameAs": [
-    "<!-- https://twitter.com/handle -->",
-    "<!-- https://linkedin.com/company/slug -->",
-    "<!-- https://github.com/org -->"
-  ],
-  "contactPoint": {
-    "@type": "ContactPoint",
-    "contactType": "customer support",
-    "email": "<!-- support@domain.com -->"
-  }
-}
-```
-
-### FAQPage (add to FAQ or service pages)
-
-```json
-{
-  "@context": "https://schema.org",
-  "@type": "FAQPage",
-  "mainEntity": [
-    {
-      "@type": "Question",
-      "name": "<!-- Question 1? -->",
-      "acceptedAnswer": {
-        "@type": "Answer",
-        "text": "<!-- Answer 1. Be specific and self-contained. -->"
-      }
-    },
-    {
-      "@type": "Question",
-      "name": "<!-- Question 2? -->",
-      "acceptedAnswer": {
-        "@type": "Answer",
-        "text": "<!-- Answer 2. Be specific and self-contained. -->"
-      }
-    }
-  ]
-}
-```
-
-### Article (add to blog post pages)
-
-```json
-{
-  "@context": "https://schema.org",
-  "@type": "Article",
-  "headline": "<!-- Article title -->",
-  "author": {
-    "@type": "Person",
-    "name": "<!-- Author Name -->",
-    "url": "<!-- https://domain.com/author/slug -->"
-  },
-  "datePublished": "<!-- YYYY-MM-DD -->",
-  "dateModified": "<!-- YYYY-MM-DD -->",
-  "publisher": {
-    "@type": "Organization",
-    "name": "<!-- Company Name -->",
-    "logo": {
-      "@type": "ImageObject",
-      "url": "<!-- https://domain.com/logo.png -->"
-    }
-  },
-  "image": "<!-- https://domain.com/article-image.jpg -->",
-  "description": "<!-- 155-character description -->"
-}
-```

package/assets/worker-kits/growthub-geo-seo-v1/templates/self-eval.md

@@ -1,67 +0,0 @@
-# Self-evaluation template — v1 primitive (Growthub, capability-agnostic)
-
-A skill's `selfEval` contract declares **what good looks like** (`criteria[]`) and **the retry ceiling** (`maxRetries`). The agent drives the loop; this file is the pattern the agent follows at every unit of work.
-
-The contract is defined in `@growthub/api-contract/skills::SkillSelfEval` and is **capability-agnostic** — the same primitive applies to code edits, copy drafts, CRM rules, API payloads, asset renders, audit passes, and every other domain. The "unit of work" is the smallest reversible change the skill operates on; concrete boundaries are defined in the kit's own `skills.md` operator runbook, not here.
-
-## Loop
-
-```
-for attempt in 1..maxRetries:          # default maxRetries = 3
-  generate       — produce a proposal (whatever the skill produces)
-  apply          — materialise the proposal against the fork
-  self-evaluate  — for each criterion in skill.selfEval.criteria:
-                     check → pass / fail / needs-confirmation
-  record         — append to project.md (human) + trace.jsonl (machine)
-
-  if all criteria pass: break
-  if attempt == maxRetries: park with needs_confirmation note. Stop.
-```
-
-## What each attempt writes
-
-### Human row — append to `.growthub-fork/project.md` "Session log"
-
-```md
-### 2026-04-23 18:40 UTC · <skill-slug>
-- **Plan.** What you intend to do this unit of work.
-- **Changes.** Material change applied (must correspond to a trace event).
-- **Self-eval.** attempt 2/3 — criterion "<one of skill.selfEval.criteria>" ✗ (<note>). Retrying.
-- **Outcome.** retry-pending / pass / parked.
-- **Next.** What the next attempt (or next session) should pick up.
-```
-
-### Machine row — append to `.growthub-fork/trace.jsonl` (via `appendKitForkTraceEvent`)
-
-```json
-{
-  "ts": "2026-04-23T18:40:00.000Z",
-  "forkId": "<fork-id>",
-  "kitId": "<kit-id>",
-  "type": "self_eval_recorded",
-  "summary": "attempt 2/3 failed on <criterion>",
-  "detail": {
-    "skill": "<skill-slug>",
-    "attempt": 2,
-    "maxRetries": 3,
-    "criterion": "<one of skill.selfEval.criteria>",
-    "outcome": "fail",
-    "notes": "<short explanation>"
-  }
-}
-```
-
-## Hard rules
-
-1. **Never exceed `maxRetries`.** At the ceiling, park with a `needs_confirmation` note and stop. Do not loop forever.
-2. **Record every attempt.** Even the first pass. Continuity depends on a complete journal.
-3. **Keep `project.md` and `trace.jsonl` in sync.** One without the other is a protocol violation.
-4. **Preserve prior entries.** Append-only. Never rewrite history.
-
-## Bound the blast radius
-
-Evaluate at the smallest unit of work the skill operates on, not only at the end of a multi-step run. The retry ceiling applies to that unit — so a bad attempt does not sink the whole job.
-
-What counts as a "unit of work" is **kit-specific** and lives in that kit's `skills.md` operator runbook — not in this agnostic template. A kit picks its own smallest reversible boundary and documents it in `skills.md`; this template does not prescribe one.
-
-The agnostic SDK (`@growthub/api-contract/skills::SkillSelfEval`) does not encode any domain-specific boundaries — it only carries `criteria[]`, `maxRetries`, and `traceTo`. See `SKILL.md::selfEval.criteria` in this kit for the concrete checks, and `skills.md` for the kit-specific unit of work.