Individual skill

harborcrm-prepare

Prepare HarborCRM event handoff, trade-show prospecting, and import-cleanup JSON outputs from task API data and a provided template. Use when a prompt names HarborCRM records, asks for sponsor status reconciliation, exhibitor qualification, contact import cleanup, normalization, exclusion counts, due dates, or any other strict JSON handoff from the HarborCRM task environment.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_001/fewshot/codex/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
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 Workflows

## Overview
Use this skill for HarborCRM tasks that must return one JSON object only.

The template is the schema authority. The prompt supplies the task-specific rules. The API data supplies the records.

## Workflow
1. Read the prompt and the answer template first.
2. Fetch the runner-supplied HarborCRM base URL and only the endpoints named by the prompt or required by the template.
3. Load `GET /api/policies` early so controlled enums and qualification rules stay consistent.
4. Build the output in the exact shape the template expects. Do not add fields or reuse example values.
5. Normalize contact facts before comparing records:
   - emails: trim and lowercase