Individual skill
harborcrm-json-handoff
Use this skill for HarborCRM public API tasks that ask for CRM-ready JSON handoffs, post-event sponsor or badge reconciliation, trade-show prospecting summaries, or import-batch cleaning. It guides solvers to inspect the prompt and answer template, query only the public HarborCRM API endpoints supplied for the task, normalize and reconcile CRM records, apply exclusions and action conventions, sort deterministically, and return schema-exact JSON.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_001/self/self_attempt_03/SKILL.md
Source commit 5082a777379156a048881e94940d640702e5e09a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- 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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- sales Derived category
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 JSON Handoff Solver
## Core Contract
Use the HarborCRM public API as the source of truth. Start from the task prompt and `input/payloads/answer_template.json`; the template controls required keys, allowed enum values, null-vs-empty-string choices, and sorting. Return one JSON object only, with no prose outside the JSON.
Do not inspect local environment source, hidden task files, prior outputs, notes, reports, or evaluator artifacts. Use the API base URL supplied by the runner. If an environment access note provides a remote base URL, prefer that and do not start or inspect a local service.
## Standard SOP
1. Read the prompt and answer template first. Extract the primary identifier (`event_id`, `show_id`, or `batch_id`), required endpoints, required top-level keys, enum values, date rules, currency/count precision, and explicit sort rules.
2. Fetch `/api/policies` early. It defines stable platform enums and sponsor handoff status vocabulary, but the prompt/template still win when they are more specific.
3. Fetch every public endpoint listed by the prompt for that task family. Typical joins include CRM accounts, contacts, opportunities, campaign members, invoices, sponsor orders/packages, badges, exhibitors, meeting interest, raw import rows, and suppression lists.
4. Build lookup maps before deciding: accounts by `account_id`, normalized account name, and domain; contacts by normalized email, phone, and account/name; campaign members by event/account/contact; invoices by event/account; meeting interest by company name; suppressions by normalized email and phone.