Proposed Skills

Skills are reusable, testable tool packages. Sam currently has zero custom skills — everything is implemented as ad-hoc instructions in MEMORY.md. The decomposed setup should package these patterns as proper skills.

What Skills Are (and Why They Matter)

In OpenClaw, a skill is a SKILL.md file that packages:

• A description of what the skill does and when to use it
• Specific API patterns, authentication methods, and response handling
• Edge cases and known quirks
• Example usage

Skills are:

• Reusable across agents (the Braze skill can go to Prospect Agent without rewriting)
• Versioned (update the skill file, all agents using it get the update)
• Testable (you can audit a skill in isolation)
• Context-efficient (the agent loads only the skills it needs for a task)

---

Priority Skills to Build

Tier 1 — Build First (Blocking for Decomposition)

posthog-funnel

For: Data Agent, Funnel Agent What it does: Query PostHog funnel CVR for all 4 paths. Return structured data suitable for comparison. Key patterns to encode:

• Always use POSTHOG_PERSONAL_API_KEY (phx_ prefix), never POSTHOG_API_KEY (phc_)
• Source-of-truth insight: uC2ZuA1y (ID: 6389092)
• Use us.posthog.com endpoint (not app.posthog.com)
• HogQL for event counts; events API for property breakdown
• conv_purchase double-counts upsells — never use for revenue totals
• affid lives on person.properties, not event properties
• Attribution codes: 1000=Meta, 1001=Google, 1003=TikTok, 1033=Braze

---

braze-ops

For: Prospect Agent What it does: Canvas health checks, subscriber lookups, entry count monitoring. Key patterns to encode:

• Endpoint: https://rest.iad-02.braze.com
• Auth: Authorization: Bearer $BRAZE_API_KEY
• 6 app IDs to know
• Legacy hex ID format vs Firebase UID — use Firebase UID format
• Dead canvases signal: 0 entries for 7+ days = broken
• The 3-layer fix pattern for purchaser gap

---

github-funnel-watch

For: Funnel Agent (or cron-only implementation) What it does: Check 4 repos for new commits, compare to stored SHA, log changes. Key patterns to encode:

• Repos: funnel, funnel-cms, landing-pages, checkout
• Auth: Authorization: Bearer $GITHUB_PAT_TAGIATELLE
• State file: memory/github-watch-state.json
• Change log: memory/funnel-changes.md
• Alert threshold: only notify if correlated with >5% CVR shift

---

sanity-funnel

For: Funnel Agent What it does: Read and draft-write Sanity CMS funnel content. Key patterns to encode:

• Project ID: k8thhqoj, dataset: production
• Current token: read-only viewer (needs editor token for write)
• Frontend URLs: start.fh.co/{slug} for landing, start.fh.co/questionnaire/{slug} for funnels
• Draft mode: /api/draft-mode/enable?secret=<token>
• SEMA/MICRO/WEGO-PILL routing is server-side (not in Sanity)

---

Tier 2 — Build for Full Agent Capability

meta-ads-reporting

For: Media Buying Agent, Creative Agent (read) What it does: Pull campaign performance metrics, CPA, ROAS, spend by creative. Key context: efunnel account #7 (act_2108575489887376), LA timezone

---

looker-dashboard

For: Data Agent What it does: Query Looker API, pull dashboard tiles by ID. Key context: OAuth flow, api_viewer_product user (ID 124, read-only), key dashboard IDs

---

braze-creative-sync

For: Creative Agent What it does: Read active Braze campaign copy for consistency with new ad creative. Key context: Read-only access, no writes from Creative Agent

---

northbeam-spend

For: Data Agent, Media Buying Agent What it does: Pull spend and order data from NorthBeam. Key context: Two headers required (Data-Client-ID + Authorization: Bearer), only /v1/spend and /v1/orders work

---

Tier 3 — Nice to Have

higgsfield-video-gen

For: Creative Agent What it does: Submit AI video generation jobs, poll for completion. Key context: Docs at https://docs.higgsfield.ai/

---

shotstack-compose

For: Creative Agent What it does: Compose video from segments with overlays, transitions, text. Key context: Docs at https://shotstack.io/docs/guide/

---

zendesk-support-summary

For: Prospect Agent What it does: Pull recent support tickets, categorize contact drivers. Key context: API token auth, agent role

---

google-calendar-check

For: Master Agent, Prospect Agent What it does: Check upcoming events in next 24–48 hours. Key context: OAuth refresh tokens stored, auto-renew

---

Skills Sam Already Has (But Not Packaged)

These exist as scripts in the workspace. They should be converted into proper skills:

Existing Script	Should Become Skill	Target Agent
braze-audit.js	braze-ops	Prospect Agent
braze-audit-full.js	braze-ops (extended)	Prospect Agent
braze-check-fields.js	braze-ops (field checker)	Prospect Agent
scripts/github-funnel-monitor.sh	github-funnel-watch	Funnel Agent
scripts/posthog_sankey.py	posthog-funnel	Data Agent
scripts/google-auth.js	Part of Google skill	Master Agent

---

OpenClaw Bundled Skills Worth Keeping

Skill	Keep?	Why
slack	✅ Yes	All agents need Slack communication
skill-creator	✅ Master only	Useful for creating new skills programmatically
healthcheck	🟡 Optional	Useful on the host machine, not per-agent
weather	❌ Can remove	Not used in any workflow

---

See also: Proposed Agents | Current Skills | Migration Plan