Individual skill

harbor-crm

Query the HarborCRM REST API to retrieve accounts, contacts, events, tradeshows, finance records, policies, import batches, and related business data, then cross-reference results, apply policy-driven qualification rules, and produce a strictly conformant JSON output. Use this skill whenever the user mentions HarborCRM, Harbor CRM, CRM data retrieval, event handoff, trade-show prospecting, batch import preparation, lead qualification, sponsor reconciliation, campaign-member management, or any task that asks you to query a CRM API and return structured JSON.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/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 API

Use the HarborCRM REST API (`<TASK_ENV_BASE_URL>`) to retrieve business data, cross-reference results across endpoints, apply policy-driven qualification, and produce strictly conformant JSON against a supplied answer template.

## Workflow

Follow this ordered approach for every HarborCRM task. Skip steps only when the task clearly does not need them.

### 1. Read the answer template first

The prompt always names an answer template file (usually `input/payloads/answer_template.json`). Read it immediately. It defines the exact output shape: required top-level keys, enum values for every controlled field, sort orders, nesting, and field presence/absence rules. Every structural decision flows from the template -- do not improvise key names, enum values, or sort directions.

When the template declares enum values (e.g., `"allowed_values": ["AUV", "ROV", "Underwater Camera"]`), use only those exact strings. When it declares sort orders, follow them literally. When it says "do not add fields not declared in this template", respect that.