Menu

Individual skill

harborcrm-reconciliation

0upvotes

Use this skill for HarborCRM API tasks that require a strict CRM-ready JSON answer from event, tradeshow, prospecting, import-batch, sponsor, badge, campaign-member, account, contact, opportunity, suppression, invoice, or policy data. It is especially useful when the prompt references HarborCRM, TASK_ENV_BASE_URL, answer_template.json, lead qualification, sponsor finance handoff, duplicate cleanup, platform coverage, or controlled enum/count/sorting requirements.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_001/fewshot/opencode/fewshot_attempt_03/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 when a task asks for a JSON-only HarborCRM handoff or audit built from API data and an `input/payloads/answer_template.json` file.

## Start Here

1. Read the task prompt and every payload file before querying the API.
2. Load `input/payloads/answer_template.json` and treat it as the contract for keys, enums, null-vs-empty-string behavior, ordering, and numeric precision.
3. Read the API base URL from the runner prompt or environment. Fetch only public endpoints listed by the prompt or allowed environment instructions.
4. If an endpoint listed in the prompt is unavailable, do not invent records. Use the available collection endpoints and any equivalent aggregate endpoint the environment exposes.
5. Build the answer as one JSON object only. Do not include prose, comments, Markdown fences, or fields not required by the template.

Use [references/harborcrm-playbook.md](references/harborcrm-playbook.md) for reusable decision rules. Use [scripts/harborcrm_utils.py](scripts/harborcrm_utils.py) for deterministic normalization, endpoint fetching, date arithmetic, platform inference, and top-level schema checks.
Back to top