Menu

Individual skill

harborcrm-handoff

0upvotes

Reconcile HarborCRM API data into structured handoff summaries covering event sponsors, qualified leads, badge-only contacts, import-batch preparation, and trade-show exhibitor prospecting. Use the read-only HarborCRM API, cross-reference across CRM entities, apply controlled classification and normalization rules, then return a single JSON object conforming to the provided answer template.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_001/fewshot/naive/fewshot_attempt_01/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 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

## Quick Start

When the task asks you to audit, reconcile, prepare, or prospect against
HarborCRM data for an event, trade show, or import batch:

1. Read the answer template at `input/payloads/answer_template.json` first -- it
   is the authoritative output schema.
2. Fetch every API endpoint the prompt references. Use parallel GET requests
   whenever possible.
3. Cross-reference all fetched data: events to sponsors, badges to CRM accounts
   and contacts, exhibitors to CRM and meeting-interest records, raw contacts to
   suppression lists and CRM.
Back to top