Individual skill

harborcrm-reconciliation

HarborCRM API reconciliation for CRM handoff, event sponsorship and badge audits, trade-show exhibitor prospecting, and import-batch cleanup. Use this skill whenever a task asks Codex to query a HarborCRM task environment or API, fill an answer_template.json, produce JSON-only CRM-ready lead/sponsor/import output, normalize contacts, match CRM accounts or campaign members, classify trade-show exhibitors, deduplicate raw import contacts, or summarize CRM action counts.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_001/fewshot/cc/fewshot_attempt_01/SKILL.md

Read pinned source

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.

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 Reconciliation

Use this skill to solve HarborCRM tasks that require API data analysis and a JSON-only answer matching a provided `answer_template.json`.

## Required Inputs

Before computing anything:

1. Read the user prompt completely.
2. Read the provided `input/payloads/answer_template.json`.
3. Identify the API base URL supplied by the runner or task environment.
4. Read any local environment access file if one is present, and treat it plus the prompt as the boundary for network requests.

The template is authoritative for output keys, enum spellings, nullability, ordering, and whether extra fields are forbidden. Do not add commentary outside the final JSON.