Individual skill

task-group-001-fewshot-attempt-03

HarborCRM JSON-output procedures for event sponsor/lead reconciliation, tradeshow prospecting, and CRM import-batch cleanup using HarborCRM API data and answer templates. Use when a task asks Codex to produce structured JSON from HarborCRM events, sponsor packages/orders, badges, invoices, CRM accounts/contacts/opportunities, campaign members, tradeshow exhibitors/meeting interest, import batches/raw contacts/suppression, or policy metadata.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_001/demonstration_skill/demonstration_skill_attempt_03/demonstration-skill-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
Yes
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 Input/Output Skill

## Core Workflow

1. Read the user prompt and `input/payloads/answer_template.json` first.
2. Use the API base URL supplied by the runner or prompt. Fetch only the records needed for the requested `event_id`, `show_id`, or `batch_id`, plus CRM and policy lookup data.
3. Return exactly one JSON object matching the template: no prose, no extra keys, no missing required keys, exact enum spelling, integer counts/USD, and required sort order.
4. Validate the final object with `jq` or an equivalent JSON parser before answering.

Useful API paths:

- Policies: `GET /api/policies`
- Event work: `GET /api/events/{event_id}`, `/orders`, `/badges`, `/sponsor_packages`, `/api/finance/invoices?event_id={event_id}`, `/api/crm/campaign_members?event_id={event_id}`
- CRM lookups: `GET /api/crm/accounts`, `/api/crm/contacts`, `/api/crm/opportunities`