Individual skill

harborcrm-structured-json

Analyze HarborCRM event, trade-show, sponsor, import-batch, and CRM reconciliation tasks that require producing one JSON object from API data and a provided answer template. Use when a prompt references HarborCRM endpoints such as `/api/events`, `/api/tradeshows`, `/api/import_batches`, `/api/crm`, `/api/finance`, or `/api/policies` and asks for JSON-only output with filtering, classification, ranking, deduplication, normalization, counts, or follow-up summaries.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_001/fewshot/deepagents/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
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 Structured JSON

## Workflow

1. Read the prompt and `input/payloads/answer_template.json` first.
2. Treat the template as the contract for required keys, allowed values, list ordering, and numeric precision.
3. Use the runner-provided base URL. Query only the endpoints named in the prompt; use `/api/manifest` or `/api/policies` only when you need endpoint discovery or controlled values.
4. Identify the task family:
   - event / sponsor handoff
   - trade-show prospecting
   - import-batch cleanup
   - badge / campaign-member reconciliation
5. Build the final object in template order. Keep qualified records, exclusions, and summaries separate.
6. Normalize exactly as the schema asks. Lowercase emails only when requested, strip phones to digits only when requested, and use `null` vs empty string exactly as specified.