Claude.ai Skills Migration Audit — Ven Agency

Scope: Inventory 160+ existing skills from /Users/venagency/ven-ai/workspaces/charlie/skills/ and /Users/venagency/ven-ai/team-ven/ven-skills/, classify by service line and security tier, plan migration to Claude.ai Skills format (SKILL.md + ZIP), and identify gaps.

Target: Claude.ai Team plan, Org-wide and personal skill provisioning via Customize → Skills.

Format: SKILL.md (YAML frontmatter + Markdown) packaged as ZIP files. No plugin.json, no hooks/, no commands/ — those are Claude Code only.

---

STEP 1: Audit — Existing Skills Inventory

Total skills identified: 160+ skills across two directories.

Charlie's workspace skills (/Users/venagency/ven-ai/workspaces/charlie/skills/):

• ad-monitor, ad-video-prompt-engineering, agent-bridge, agent-browser, agent-builder, agentmail, ai-council, ai-humanizer, aircall, aircall-webhooks, anomaly-detection, anthropic-prompting, approval-patterns, bambu-3d-printing, bonus-policy, budget-pacing, calendar-manager, carousel-photo-composite, chatwoot, claudeception, clickup-api, clickup-digests, clickup-docs-api, clickup-gmail-sync, clickup-sales-pipeline-management, clickup-task-creator, clickup-webhooks, client-facing-deploy-gate, client-hub-onboarding, client-hub-routing, client-hub-topic-wake, client-onboarding, client-topic-onboard, cloudflare-crawl, cloudflare-pages, codex-agent, cold-outreach-pre-screening, cold-outreach-sequence-tracker, colima-external-drive, competitor-intel, crm-notes, cron-silent-success, effective-delegation, email-approval-worker, email-attachment-sending, email-follow-up, evolution-engine, fal-flux-pulid, ffmpeg-video-processing, figma-api, figma-mcp, figma-sites-replication, file-organiser, follow-up-email-drafting, frontend-design, gateway-pairing-troubleshooting, gmail-alert-triage, gmail-draft-thread, gmail-inbox-monitor, gmail-sales-labeller, godaddy-api, google-ads, google-ads-api, google-ads-auction-insights, google-ads-tool, google-analytics-4, google-docs, google-docs-comments, google-docs-tables, google-oauth, google-search-console, google-sheets, google-tag-manager, gws, high-ticket-sales-presentation, home-assistant, html-report-pdf-export, immich-colima, james-first-touch-email, kb-ingest, launchd-gog-auth, lead-qualification, learn-command, linkedin-research, lobster-workflows, macbook-control, maintenance-ticketing, marketing-strategy, meeting-actions, meeting-prep-from-calendar, meta-ads, meta-ads-excel-export-parsing, meta-ads-tool, meta-budget-scaling, missive-reference, model-picker, model-router, mrh-weekly-report, nano-banana-pro, native-gmail-signature-formatting, onboarding-handoff, openclaw-agent-creator, openclaw-agent-infra, openclaw-cross-topic-send, openclaw-hooks-agent, openclaw-scout, paper-design, payroll-verification, pipeline-follow-up-sweep, platform-expertise, platform-updates, playwright-report-pdf-export, premium-maintenance-updates, prompt-defence, qantas-reward-finder, recipe-finder, recruitment-reply-drafter, replicate-face-swap, replicate-video-api, report-analysis, resend-email, runcloud-digitalocean, runcloud-mcp-server, sales-ops, sanity-cms, seo-audit, seo-local-business, session-wrapup, smart-retrieval, smooth-browser, smooth-cli, social-content-strategy, stalwart, synergy-wholesale, tcp-react-app, tcp-wordpress-backend, telegram-bot-api, telegram-topic-routing, tracking-monitor, travel-fund-calculator, trend-watcher, update-live-proposal-site, ux-audit, ven-agency-cv-screener, ven-data-collector, ven-design-presentation, ven-design-system, ven-qa, ven-reports, ven-seo-automation, ven-service-positioning, video-animation-analyzer, visual-explainer, warm-reply-delay-handling, web-dev-workflow, web-research, wise-api, workspace-router, workspace-standard, x-tweet-reader, xero

Key observations:

• All skills have SKILL.md files with YAML frontmatter and Markdown body
• Many reference external APIs (ClickUp, Google, Meta, Figma, Wise, etc.)
• Several are OpenClaw/Telegram-specific infrastructure skills
• Numerous client-facing and operational workflow skills
• Multiple skills depend on executables, scripts, or external services

---

STEP 2: Group and Classify

By Service Line

Total: ~142 skills accounted for in service lines (some cross-category).

By Client vs. Internal

---

STEP 3: Security & Permissions Plan

Data Sensitivity Flags

CRITICAL: Contains hardcoded or reference credentials/API keys

• wise-api (business account profile, recipient IDs)
• google-ads-api (MCC login, credential paths)
• godaddy-api (Tom's keychain-backed credential)
• xero (Tom-only keychain credential)
• runcloud-digitalocean (API token paths)
• gmail-inbox-monitor (OAuth paths for andy@ven.com.au)
• gws (Google Workspace context andy@ven.com.au)

HIGH: References salary, payroll, or banking data

• payroll-verification (salary data, bank details, Vietnamese names)
• bonus-policy (staff compensation policy)
• ven-data-collector (client performance metrics, revenue data)
• report-analysis (client metrics, spend data)
• mrh-weekly-report (client financial data)

HIGH: Client-specific confidential info

• tcp-wordpress-backend, tcp-react-app (client code/architecture)
• ven-agency-cv-screener (hiring criteria, candidate feedback)
• high-ticket-sales-presentation (proprietary sales frameworks)
• seo-local-business (client website templates)
• ven-service-positioning (client positioning strategy)

MEDIUM: Personal data (names, emails, contact details)

• linkedin-research (personal profile extraction)
• crm-notes (client contact data)
• recruitment-reply-drafter (candidate data)
• james-first-touch-email (prospect email templates)

MEDIUM: Email/contact workflows (draft-only, approval gates)

• email-approval-worker, email-follow-up, follow-up-email-drafting, gmail-alert-triage, gmail-draft-thread, resend-email, james-first-touch-email

Recommended Access Tiers

Flagged Skills Requiring Remediation

---

STEP 4: Migration Plan — Claude.ai Plugins via venagency/claude-plugins

Deployment Target: Ven's Private Plugin Marketplace

All migrated skills commit to: https://github.com/venagency/claude-plugins (private repo)

This repo is already connected as Ven's private plugin marketplace in Claude.ai Org Settings (Libraries > Plugins). Plugins synced from this repo appear for all team members and can be set to "Installed by default" or "Available for install" per plugin.

Current state (28 Mar 2026):

• Repo connected and synced via GitHub integration
• One plugin live: report-generator (v0.3.0, installed by default, last updated 28 Mar 2026)
• Owner: Steve (steve@ven.com.au)
• Local clone: /Users/venagency/ven-ai/workspaces/tom/projects/claude-plugins/

Repo Structure (Anthropic Plugin Convention)

claude-plugins/
├── .claude-plugin/
│   └── marketplace.json          # Root manifest listing all plugins
└── plugins/
    └── <plugin-name>/
        ├── .claude-plugin/
        │   └── plugin.json       # Plugin manifest (name, version, description)
        ├── README.md
        └── skills/
            └── <skill-name>/
                └── SKILL.md      # YAML frontmatter + Markdown body

marketplace.json: Lists all plugins with name, description, category, and source path.

plugin.json: Per-plugin manifest with name, version, description, author, and license.

SKILL.md: The actual skill content with YAML frontmatter (name, description, argument-hint, version) and Markdown instructions.

Packaging Strategy

One plugin can contain multiple skills. Group by service line or functional domain:

Each plugin gets its own directory under plugins/ and entry in marketplace.json.

User Access Control

In Claude.ai Org Settings, each plugin can be set to:

• Installed by default — all team members get it automatically
• Available for install — team members opt in
• Not available — hidden from team

This maps directly to the security tiers from Step 3:

• Org-wide tier → "Installed by default"
• Restricted tiers → "Available for install" (with team guidance on who should use it)
• Personal/sensitive → not committed to this repo (stay local or personal upload)

Migration Priority & Complexity

Deployment Channels

Migration Checklist per Skill

### [skill-name]

**Current**: /skills/[name]/SKILL.md
**Target plugin**: plugins/[plugin-name]/skills/[skill-name]/SKILL.md in venagency/claude-plugins
**Status**: [ ] Audit | [ ] Refactor secrets | [ ] Write/update SKILL.md | [ ] Commit to repo | [ ] Sync Claude.ai | [ ] Test

**SKILL.md Metadata:**
- name: `[lowercase-hyphens]`
- description: `[50-150 chars, include triggers]`
- argument-hint: `[usage hint]`
- version: `[semver]`

**Repo work:**
- [ ] Which plugin does this belong to?
- [ ] plugin.json updated with version bump?
- [ ] marketplace.json updated if new plugin?
- [ ] Credential handling: Env vars or placeholder paths only (no hardcoded values)?

**Claude.ai Deployment:**
- User access: [Installed by default | Available for install]
- After commit: click Update in Org Settings → Plugins to sync

**Security Audit:**
- [ ] No hardcoded secrets or credential values
- [ ] Credential paths documented as placeholders
- [ ] Sensitive data flagged in description
- [ ] Approval gate needed? (Yes/No)

---

STEP 5: Gap Analysis

Community Skills Worth Installing (from github.com/anthropics/skills)

Rather than build from scratch, consider official Anthropic Skills available for direct use:

| theme-factory | ven-design-system (partial) | Built | Compare; Anthropic skill may streamline color/spacing workflows |

| internal-comms | ven-service-positioning, follow-up-email-drafting | Built | Use as reference for internal communication patterns |

Gaps Ven Should Build (Skills NOT in Anthropic repo)

Recommended Immediate Installs from Anthropic

For the Claude.ai Team:

1. pdf — Client document work (extract, merge, form fill)
2. xlsx — Data analysis, pivot tables for reporting
3. docx — Word document generation for client comms
4. pptx — Compare with ven-reports; may be better for slide generation
5. mcp-builder — If building new integrations (Slack, Notion, etc.)
6. skill-creator — Team reference for authoring new skills

---

Migration Roadmap

Phase 1: Foundation (Weeks 1-2)

• Audit all 160+ skills (DONE via this document)
• Repo confirmed: venagency/claude-plugins connected to Claude.ai Org Plugins (Preview). report-generator already live.
• Set org-wide provisioning rules and access tiers (see Step 3)
• Refactor credentials: move API keys to env vars, document paths as placeholders
• Create first 3-4 plugin bundles in the repo (commit + sync):
• paid-media: google-ads, meta-ads, budget-pacing, ad-monitor
• seo: seo-audit, seo-local-business, google-search-console
• sales-ops: lead-qualification, cold-outreach-pre-screening, pipeline-follow-up-sweep, email-follow-up
• design-dev: frontend-design, web-dev-workflow, ven-design-system, figma-api

Phase 2: Core Operations (Weeks 3-4)

• Migrate 20-25 P1 Medium skills:
• clickup-api, clickup-task-creator, wise-api, ven-reports, payroll-verification, gmail-inbox-monitor, crm-notes, calendar-manager, figma-api
• Provision org-wide core skills
• Set up personal/restricted tiers for Andy, ops team, sales team

Phase 3: Extended Workflows (Weeks 5-6)

• Migrate 30-40 P2 skills (weekly use, simple/medium)
• Including: linkedin-research, competitor-intel, cold-outreach-*, google-analytics-4, tracking-monitor, meeting-prep
• Test cross-skill composition (e.g., sales-ops + email-follow-up)

Phase 4: Specialized & Experimental (Weeks 7+)

• Migrate remaining 60+ skills as needed
• Keep infrastructure skills (openclaw-*) for reference only; not suitable for Claude.ai Skills format
• Archive/deprecate non-essential skills

Phase 5: Community Skills Integration

• Install official Anthropic Skills (pdf, xlsx, docx, etc.)
• Compare with Ven equivalents; retire if Anthropic version sufficient
• Document when to use Anthropic vs. Ven custom skills

---

Key Decisions for Andy

1. Deployment target confirmed: venagency/claude-plugins GitHub repo → Claude.ai Org Settings → Plugins (Preview). Already connected and synced. report-generator is live and installed by default. All new plugins commit here.

1. Credentials Handling: All API keys → env vars or OpenClaw Keychain only. Credential paths documented in plugin skills as placeholders, never hardcoded values.

1. Plugin grouping: Group skills by service line into plugins (e.g. paid-media, seo, sales-ops). Each plugin = one directory under plugins/ + one entry in marketplace.json. See plugin table in Step 4.

1. User access per plugin: Set in Claude.ai Org Settings per plugin. Core workflows → "Installed by default". Specialist or ops tools → "Available for install". Sensitive/personal skills → not committed to this repo.

1. Infrastructure Skills (OpenClaw-specific): Do not commit to venagency/claude-plugins. These are OpenClaw/Telegram-specific and have no value in Claude.ai context. Keep local only.

---

Summary Table: Skills Status

---

Document version: 28 Mar 2026

Status: Ready for Andy decision on packaging, provisioning, and credential handling

Next step: Approve migration approach → begin Phase 1 (foundation skills)