Individual skill

harborcrm-handoff

Use for HarborCRM API tasks that require producing strict JSON handoffs from event, trade-show, import-batch, CRM, finance, sponsor, badge, exhibitor, meeting-interest, suppression, or campaign-member data. Apply this skill whenever a prompt mentions HarborCRM, CRM import preparation, sponsor finance handoff, event badge reconciliation, qualified lead/prospect lists, or trade-show exhibitor qualification, especially when an answer_template.json must be filled from a supplied API base URL.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_001/fewshot/opencode/fewshot_attempt_02/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
121
Repository last updated
Oct 29, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# HarborCRM Handoff

Use this skill to turn HarborCRM API records into the exact JSON object requested by the task prompt and `input/payloads/answer_template.json`.

## First Pass

1. Read the user prompt and `input/payloads/answer_template.json` completely.
2. Identify the task family:
   - Event handoff: event details, sponsors/orders, badges, finance invoices, opportunities, campaign members.
   - Trade-show prospecting: exhibitors, meeting interest, CRM overlap, platform qualification.
   - Import batch cleanup: raw contacts, suppression, CRM account/contact matching, duplicate removal.
3. Resolve the API base URL supplied by the runner. Do not hard-code training URLs or IDs.
4. Fetch every endpoint named by the prompt for the requested event, show, or batch ID. Also fetch shared CRM tables when existing account, contact, opportunity, or campaign-member decisions are required.
5. Read [references/rules.md](references/rules.md) for the detailed reusable rules before making classification or counting decisions.