Menu

Individual skill

harborcrm-handoff-solver

0upvotes

Solve HarborCRM public-API tasks for CRM event handoff, sponsor reconciliation, trade-show prospecting, and import-batch cleanup.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_001/self/self_attempt_01/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
Instructions only
Last checked
Nov 11, 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 Solver

Use this skill when a task asks for a JSON answer from HarborCRM event, trade-show, CRM, finance, campaign-member, or import-batch data. The answer template is authoritative: preserve its top-level keys, field names, enum spellings, null-vs-empty-string conventions, and ordering rules. Return one JSON object only.

## Standard SOP

1. Read the prompt and `input/payloads/answer_template.json` first. Copy the required shape mentally before fetching data; do not add explanatory fields.
2. Use only the HarborCRM public API base URL supplied by the runner or environment note. Do not inspect local source.
3. Fetch `/api/policies` plus the task-specific records. Policies are usually brief, so also use the prompt, template enums, descriptions, and CRM state.
4. Build lookup tables before classifying:
   - CRM accounts by `account_id`, normalized `name`, and `domain`.
   - CRM contacts by normalized `email`, digits-only `phone`, `contact_id`, and account.
   - Campaign members by event/campaign plus contact/account identifiers.
   - Finance invoices by `event_id` and `account_id`.
Back to top