Individual skill

harbor-crm-handoff

Solve HarborCRM data-reconciliation tasks by following reusable patterns for sponsor handoffs, lead qualification, badge classification, import-batch cleaning, trade-show prospecting, campaign-member management, and contact normalization. This skill covers the HarborCRM REST API entity model and the cross-entity business rules that the API data itself does not declare.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_001/fewshot/naive/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 Handoff Skill

This skill teaches reusable patterns for solving HarborCRM event-handoff, trade-show prospecting, and import-batch cleaning tasks. HarborCRM is a self-describing REST API whose entity model and cross-entity business rules remain consistent across related task types. The skill does not contain task-specific answer values; it encodes only the reusable domain logic, entity relationships, normalization rules, and workflow patterns.

## Conventions

- The API base URL is always supplied by the runner as `<TASK_ENV_BASE_URL>`.
- Every task supplies an `answer_template.json` in `input/payloads/`. Read it first so you understand the exact output shape before fetching any API data.
- Sort rules appear in the prompt or template. Default sorts when unspecified: `company_name` ascending, `row_id` ascending, `rank` ascending.
- All monetary values are integer USD. Round down after summing (use floor).
- Dates use `YYYY-MM-DD` format.

## Core API Endpoints
Back to top