Menu

Individual skill

harborcrm-front-of-funnel

0upvotes

Solve HarborCRM front-of-funnel CRM/marketing tasks against the read-only HarborCRM JSON API: post-event sponsor reconciliation and CRM handoff, trade-show exhibitor prospecting/qualification, raw contact-import hygiene (dedupe/suppress/normalize), sponsor/lead follow-up planning, and CRM create/update/no-action decisions. Use whenever a task references HarborCRM, an event_id (sponsor orders/badges/invoices), a trade-show show_id (exhibitors/meeting_interest), or an import batch of raw contacts, and asks for a structured JSON answer matching an answer_template.

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_001/demonstration_skill/demonstration_skill_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 Front-of-Funnel Solver

HarborCRM is a read-only JSON CRM/marketing workspace. Tasks ask you to read
shared domain records over HTTP, apply business rules, and emit ONE JSON object
that conforms exactly to a supplied `answer_template.json`. There are no
answer endpoints — you must compute everything yourself.

## Golden rules (apply to every task)

1. **The answer template is law.** Read `input/payloads/answer_template.json`
   first. Emit exactly the declared top-level keys and item keys, use only the
   declared enum values, respect the declared ordering, and add NO extra fields.
   Output JSON only — no prose, no markdown fences.
2. **Enum vocabularies vary per task.** Do not assume enums carry across tasks.