fix: remove internal paths and hardcoded GA4 ID from public repo

thatrebeccarae · claude · thatrebeccarae · commit 01e0c1e97a4b · 2026-03-20T09:22:57.000-04:00
Genericize example paths in social-preview, sync-repos, and repo-health
EXAMPLES.md files — replaced internal hostnames and directory structures
with generic ~/projects/ paths. Move GA4 tracking ID to environment
variable in generate-skill-pages.py.

Co-Authored-By: Claude Opus 4.6 (1M context) &lt;noreply@anthropic.com&gt;
diff --git a/scripts/generate-skill-pages.py b/scripts/generate-skill-pages.py
@@ -18,7 +18,7 @@
 CATALOG_PATH = DOCS_DIR / "catalog.json"
 OUTPUT_DIR = DOCS_DIR / "skill"
 
-GA4_ID = "G-00XHYRHCX4"
+GA4_ID = os.environ.get("GA4_ID", "")
 BASE_URL = "https://thatrebeccarae.github.io/claude-marketing"
 REPO_URL = "https://github.com/thatrebeccarae/claude-marketing"
 
diff --git a/skills/repo-health/EXAMPLES.md b/skills/repo-health/EXAMPLES.md
@@ -4,7 +4,7 @@ Practical examples showing repo-health audit output for different scenarios.
 
 ## Example 1: New Public Repo (Low Score)
 
-**User Request**: `/repo-health ~/Popoloto/Repos.nosync/my-new-tool`
+**User Request**: `/repo-health ~/projects/my-new-tool`
 
 A freshly created public repo with only source code committed. No standard files, no GitHub configuration.
 
@@ -66,18 +66,18 @@ Overall Score: 22/100 (Grade: F)
 12.[LOW]  Add PR template — consistent pull request descriptions.
 13.[LOW]  Commit package-lock.json — ensures reproducible installs.
 
-Run /repo-health ~/Popoloto/Repos.nosync/my-new-tool --fix to auto-generate missing files.
+Run /repo-health ~/projects/my-new-tool --fix to auto-generate missing files.
 ```
 
 ## Example 2: Mature Public Repo (High Score)
 
-**User Request**: `/repo-health ~/Popoloto/Repos.nosync/aouda`
+**User Request**: `/repo-health ~/projects/my-agent`
 
 A well-maintained public repo with most standard files in place.
 
 **Output**:
 ```
-=== Repo Health Report: aouda ===
+=== Repo Health Report: my-agent ===
 Visibility: public
 Overall Score: 85/100 (Grade: B)
 
@@ -127,13 +127,13 @@ Overall Score: 85/100 (Grade: B)
 
 ## Example 3: Pre-Open-Source Audit (Private to Public)
 
-**User Request**: `/repo-health ~/Popoloto/Repos.nosync/clawclip-build`
+**User Request**: `/repo-health ~/projects/my-dashboard-dev`
 
 Auditing a private repo before making it public. The report highlights everything that needs to be added.
 
 **Output**:
 ```
-=== Repo Health Report: clawclip-build ===
+=== Repo Health Report: my-dashboard-dev ===
 Visibility: private
 Overall Score: 58/100 (Grade: F)
 
@@ -174,7 +174,6 @@ Re-run without the public flag to see private-only scoring.
   [FAIL] Tracked .env file: .env.example — review contents before open-sourcing
 
 --- Community (10%) --- Score: 25/100
-  [PASS] CONTRIBUTING.md — wait, this is missing
   [MISS] CODE_OF_CONDUCT.md
   [MISS] CONTRIBUTING.md
   [MISS] Issue templates
@@ -201,7 +200,7 @@ NICE TO HAVE:
 12.[LOW]  Add CODEOWNERS — auto-assign reviewers.
 13.[LOW]  Clean up 5 stale branches before going public.
 
-Run /repo-health ~/Popoloto/Repos.nosync/clawclip-build --fix to auto-generate missing files.
+Run /repo-health ~/projects/my-dashboard-dev --fix to auto-generate missing files.
 ```
 
 The pre-open-source audit adds a dedicated checklist section that separates "must do" (legal/security blockers) from "should do" (quality) and "nice to have" (polish). It also flags the need to run `/safe-push` to scan commit history for leaked secrets before the repo becomes publicly visible.
diff --git a/skills/social-preview/EXAMPLES.md b/skills/social-preview/EXAMPLES.md
@@ -9,29 +9,28 @@ description: "Usage examples for the social-preview skill."
 
 **User:**
 ```
-/social-preview generate ~/Popoloto/Repos.nosync/aouda
+/social-preview generate ~/projects/my-agent
 ```
 
 **What happens:**
 
-1. Skill scans the repo: name is `aouda`, description is "Autonomous AI agent framework", primary language is TypeScript, logo found at `branding/logo.png`.
+1. Skill scans the repo: name is `my-agent`, description is "Autonomous AI agent framework", primary language is TypeScript, logo found at `branding/logo.png`.
 2. Asks user for template preference. User picks **dark** (default).
 3. Generates `social-preview.html`:
 
 ```html
 <body>
   <div class="accent-bar"></div>
-  <div class="project-name">aouda</div>
+  <div class="project-name">my-agent</div>
   <div class="tagline">Autonomous AI agent framework</div>
   <div class="language-badge">TypeScript</div>
-  <div class="attribution">github.com/thatrebeccarae</div>
+  <div class="attribution">github.com/your-username</div>
 </body>
 ```
 
-4. Guides user to render via Puppeteer on TARS:
+4. Guides user to render via Puppeteer:
 ```bash
-ssh tars
-cd ~/Popoloto/Repos.nosync/aouda
+cd ~/projects/my-agent
 node -e "const p=require('puppeteer');(async()=>{const b=await p.launch({headless:true});const pg=await b.newPage();await pg.setViewport({width:1280,height:640,deviceScaleFactor:2});await pg.goto('file://$(pwd)/social-preview.html',{waitUntil:'networkidle0'});await pg.screenshot({path:'social-preview.png',clip:{x:0,y:0,width:1280,height:640}});await b.close();})()"
 ```
 
@@ -44,12 +43,12 @@ node -e "const p=require('puppeteer');(async()=>{const b=await p.launch({headles
 
 **User:**
 ```
-/social-preview generate ~/Popoloto/Repos.nosync/ouras
+/social-preview generate ~/projects/my-tracker
 ```
 
 **What happens:**
 
-1. Skill scans the repo: name is `ouras`, description is "Time tracking with presence", primary language is TypeScript. Detects Tailwind config with custom dark palette (`#08080d` background).
+1. Skill scans the repo: name is `my-tracker`, description is "Time tracking with presence", primary language is TypeScript. Detects Tailwind config with custom dark palette (`#08080d` background).
 2. Asks user for template. User says: "Use the project's dark palette -- #08080d background, zinc text."
 3. Skill modifies the dark template to use the project's brand colors:
 
@@ -76,12 +75,12 @@ body {
 
 **User:**
 ```
-/social-preview audit ~/Popoloto/Repos.nosync/clawclip
+/social-preview audit ~/projects/my-dashboard
 ```
 
 **Output:**
 ```
-=== Social Preview Audit: clawclip ===
+=== Social Preview Audit: my-dashboard ===
 
 Custom preview set: NO (using auto-generated)
 Description:       "AI-powered agent orchestration dashboard"
diff --git a/skills/sync-repos/EXAMPLES.md b/skills/sync-repos/EXAMPLES.md
@@ -2,13 +2,13 @@
 
 ## Example 1: Check Drift Between Dev and Public Repos
 
-**User Request**: "Check if aouda-dev and aouda are in sync"
+**User Request**: "Check if my-app-dev and my-app are in sync"
 
-**Invocation**: `/sync-repos check ~/Popoloto/Repos.nosync/aouda-dev ~/Popoloto/Repos.nosync/aouda`
+**Invocation**: `/sync-repos check ~/projects/my-app-dev ~/projects/my-app`
 
 **Steps Taken**:
 1. Validate both paths are git repos
-2. Locate `scripts/sync-public.sh` and `scripts/sync-public.conf` in aouda-dev
+2. Locate `scripts/sync-public.sh` and `scripts/sync-public.conf` in dev repo
 3. Parse exclusion list from `sync-public.conf`
 4. Generate file manifests for both repos, filtering exclusions
 5. Compare file hashes for files present in both
@@ -18,8 +18,8 @@
 Sync Repos — Check Report
 ==========================
 
-Dev repo:    ~/Popoloto/Repos.nosync/aouda-dev (142 files)
-Public repo: ~/Popoloto/Repos.nosync/aouda (98 files)
+Dev repo:    ~/projects/my-app-dev (142 files)
+Public repo: ~/projects/my-app (98 files)
 Sync script: scripts/sync-public.sh (found)
 
 Files only in dev (expected exclusions): 38
@@ -44,9 +44,9 @@ Recommendation: SYNC NEEDED — 3 unexpected files missing from public, 1 file d
 
 ## Example 2: Full Sync Workflow
 
-**User Request**: "Sync ouras dev repo to public"
+**User Request**: "Sync my-app dev repo to public"
 
-**Invocation**: `/sync-repos sync ~/Popoloto/Repos.nosync/v0-ouras-landing-page ~/Popoloto/Repos.nosync/ouras`
+**Invocation**: `/sync-repos sync ~/projects/my-app-dev ~/projects/my-app`
 
 **Steps Taken**:
 1. Run check (as in Example 1). Drift detected: 5 files diverged, 2 new files missing.
@@ -82,13 +82,13 @@ Next step: Review changes in the public repo, then /safe-push when ready.
 
 ## Example 3: Set Up Sync for a New Repo Pair
 
-**User Request**: "Set up sync between clawclip-build (dev) and clawclip (public)"
+**User Request**: "Set up sync between my-dashboard-dev (dev) and my-dashboard (public)"
 
-**Invocation**: `/sync-repos setup ~/Popoloto/Repos.nosync/clawclip-build ~/Popoloto/Repos.nosync/clawclip`
+**Invocation**: `/sync-repos setup ~/projects/my-dashboard-dev ~/projects/my-dashboard`
 
 **Steps Taken**:
 1. Confirm both paths exist and are git repos.
-2. Scan clawclip-build for files that should not sync:
+2. Scan dev repo for files that should not sync:
    - Found `.env` (secrets)
    - Found `data/` directory (SQLite databases)
    - Found `.claude/` directory (project config)
@@ -104,8 +104,8 @@ Next step: Review changes in the public repo, then /safe-push when ready.
 Sync Repos — Setup
 ====================
 
-Dev repo:    ~/Popoloto/Repos.nosync/clawclip-build
-Public repo: ~/Popoloto/Repos.nosync/clawclip
+Dev repo:    ~/projects/my-dashboard-dev
+Public repo: ~/projects/my-dashboard
 
 Detected exclusion patterns:
   .env, .env.*           (secrets)
