Skip to content

TeoSlayer/pilot-skills / skills/pilot-brand-protection-setup

pilot-brand-protection-setup

Verified

Deploy a brand protection system with 4 agents for scanning, classification, enforcement, and reporting. Use this skill when: 1. User wants to set up brand monitoring for counterfeits, impersonation, or trademark violations 2. User is configuring agents for marketplace scanning, DMCA takedowns, or brand health tracking 3. User asks about brand protection pipelines, takedown workflows, or violation classification Do NOT use this skill when: - User wants to stream a single data feed (use pilot-stream-data instead) - User wants to send a one-off webhook notification (use pilot-webhook-bridge instead) - User only needs event filtering (use pilot-event-filter instead)

Brand Protection Setup

Deploy 4 agents: scanner, classifier, enforcer, and dashboard.

Roles

RoleHostnameSkillsPurpose
scanner<prefix>-scannerpilot-stream-data, pilot-cron, pilot-archiveCrawls marketplaces and social media for brand violations
classifier<prefix>-classifierpilot-event-filter, pilot-task-router, pilot-metricsClassifies violations by type, severity, and platform
enforcer<prefix>-enforcerpilot-webhook-bridge, pilot-audit-log, pilot-receiptFiles DMCA notices and platform reports, tracks status
dashboard<prefix>-dashboardpilot-metrics, pilot-slack-bridge, pilot-announceVisualizes brand health, violation trends, enforcement rates

Setup Procedure

Step 1: Ask the user which role this agent should play and what prefix to use.

Step 2: Install the skills for the chosen role:

# For scanner:
clawhub install pilot-stream-data pilot-cron pilot-archive
# For classifier:
clawhub install pilot-event-filter pilot-task-router pilot-metrics
# For enforcer:
clawhub install pilot-webhook-bridge pilot-audit-log pilot-receipt
# For dashboard:
clawhub install pilot-metrics pilot-slack-bridge pilot-announce

Step 3: Set the hostname:

pilotctl --json set-hostname <prefix>-<role>

Step 4: Write the setup manifest:

mkdir -p ~/.pilot/setups
cat > ~/.pilot/setups/brand-protection.json << 'MANIFEST'
<INSERT ROLE MANIFEST FROM BELOW>
MANIFEST

Step 5: Tell the user to initiate handshakes with direct communication peers.

Manifest Templates Per Role

scanner

{
  "setup": "brand-protection", "setup_name": "Brand Protection",
  "role": "scanner", "role_name": "Brand Scanner",
  "hostname": "<prefix>-scanner",
  "description": "Crawls marketplaces, social media, and domains for unauthorized brand usage and counterfeits.",
  "skills": {"pilot-stream-data": "Stream crawled listings and social media posts for analysis.", "pilot-cron": "Schedule periodic scans across configured platforms.", "pilot-archive": "Archive raw scan results and evidence snapshots."},
  "peers": [{"role": "classifier", "hostname": "<prefix>-classifier", "description": "Receives brand violations for classification"}],
  "data_flows": [{"direction": "send", "peer": "<prefix>-classifier", "port": 1002, "topic": "brand-violation", "description": "Brand violations detected across platforms"}],
  "handshakes_needed": ["<prefix>-classifier"]
}

classifier

{
  "setup": "brand-protection", "setup_name": "Brand Protection",
  "role": "classifier", "role_name": "Threat Classifier",
  "hostname": "<prefix>-classifier",
  "description": "Classifies violations by type (counterfeit, impersonation, trademark), severity, and platform.",
  "skills": {"pilot-event-filter": "Filter noise and deduplicate violations across platforms.", "pilot-task-router": "Route violations to appropriate classification workflows by type.", "pilot-metrics": "Track violation counts, severity distribution, and platform breakdown."},
  "peers": [{"role": "scanner", "hostname": "<prefix>-scanner", "description": "Sends brand violations"}, {"role": "enforcer", "hostname": "<prefix>-enforcer", "description": "Receives classified threats"}],
  "data_flows": [{"direction": "receive", "peer": "<prefix>-scanner", "port": 1002, "topic": "brand-violation", "description": "Brand violations detected across platforms"}, {"direction": "send", "peer": "<prefix>-enforcer", "port": 1002, "topic": "classified-threat", "description": "Classified threats with type, severity, and priority"}],
  "handshakes_needed": ["<prefix>-scanner", "<prefix>-enforcer"]
}

enforcer

{
  "setup": "brand-protection", "setup_name": "Brand Protection",
  "role": "enforcer", "role_name": "Takedown Enforcer",
  "hostname": "<prefix>-enforcer",
  "description": "Files DMCA notices, platform reports, and cease-and-desist requests. Tracks enforcement status.",
  "skills": {"pilot-webhook-bridge": "Submit takedown requests to platform APIs and legal services.", "pilot-audit-log": "Log all enforcement actions with evidence chain and timestamps.", "pilot-receipt": "Generate and store receipts for filed takedown notices."},
  "peers": [{"role": "classifier", "hostname": "<prefix>-classifier", "description": "Sends classified threats"}, {"role": "dashboard", "hostname": "<prefix>-dashboard", "description": "Receives enforcement actions"}],
  "data_flows": [{"direction": "receive", "peer": "<prefix>-classifier", "port": 1002, "topic": "classified-threat", "description": "Classified threats to enforce"}, {"direction": "send", "peer": "<prefix>-dashboard", "port": 1002, "topic": "enforcement-action", "description": "Enforcement actions with status and outcomes"}],
  "handshakes_needed": ["<prefix>-classifier", "<prefix>-dashboard"]
}

dashboard

{
  "setup": "brand-protection", "setup_name": "Brand Protection",
  "role": "dashboard", "role_name": "Brand Dashboard",
  "hostname": "<prefix>-dashboard",
  "description": "Visualizes brand health metrics, violation trends, and enforcement success rates.",
  "skills": {"pilot-metrics": "Compute brand health scores, violation trends, and enforcement KPIs.", "pilot-slack-bridge": "Post brand health summaries and critical alerts to Slack.", "pilot-announce": "Broadcast periodic brand health reports to stakeholders."},
  "peers": [{"role": "enforcer", "hostname": "<prefix>-enforcer", "description": "Sends enforcement actions"}],
  "data_flows": [{"direction": "receive", "peer": "<prefix>-enforcer", "port": 1002, "topic": "enforcement-action", "description": "Enforcement actions with status and outcomes"}, {"direction": "send", "peer": "external", "port": 443, "topic": "brand-report", "description": "Brand health reports to stakeholders"}],
  "handshakes_needed": ["<prefix>-enforcer"]
}

Data Flows

  • scanner -> classifier : brand-violation events from platform scans (port 1002)
  • classifier -> enforcer : classified-threat with type, severity, and priority (port 1002)
  • enforcer -> dashboard : enforcement-action with status and outcomes (port 1002)
  • dashboard -> external : brand-report via Slack and webhooks (port 443)

Handshakes

# scanner <-> classifier:
pilotctl --json handshake <prefix>-classifier "setup: brand-protection"
pilotctl --json handshake <prefix>-scanner "setup: brand-protection"
# classifier <-> enforcer:
pilotctl --json handshake <prefix>-enforcer "setup: brand-protection"
pilotctl --json handshake <prefix>-classifier "setup: brand-protection"
# enforcer <-> dashboard:
pilotctl --json handshake <prefix>-dashboard "setup: brand-protection"
pilotctl --json handshake <prefix>-enforcer "setup: brand-protection"

Workflow Example

# On scanner -- publish detected violation:
pilotctl --json publish <prefix>-classifier brand-violation '{"violation_id":"BV-20481","platform":"amazon","type":"counterfeit","confidence":0.91}'
# On classifier -- publish classified threat:
pilotctl --json publish <prefix>-enforcer classified-threat '{"violation_id":"BV-20481","severity":"high","action":"dmca_takedown"}'
# On enforcer -- publish enforcement action:
pilotctl --json publish <prefix>-dashboard enforcement-action '{"violation_id":"BV-20481","action":"dmca_filed","status":"pending"}'
# On dashboard -- publish brand report:
pilotctl --json publish <prefix>-dashboard brand-report '{"period":"2026-W15","violations":23,"takedowns_filed":18,"success_rate":0.78}'

Dependencies

Requires pilot-protocol skill, pilotctl binary, clawhub binary, and a running daemon.

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall