Individual skill
harborcrm-handoff-solver
Solve HarborCRM CRM handoff, trade-show prospecting, and import-cleanup tasks by fetching the public API data, applying CRM qualification rules, and returning template-shaped JSON only.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_001/fewshot/naive/fewshot_attempt_02/SKILL.md
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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- sales Derived category
- data Derived category
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 Solver
Use this skill when a task asks for a HarborCRM JSON handoff, reconciliation, prospecting summary, or CRM import cleanup using a runner-provided API base URL and an `input/payloads/answer_template.json` file.
## Required Workflow
1. Read the user prompt and `input/payloads/answer_template.json` before fetching data.
2. Extract the task type, identifiers, required endpoints, allowed enum values, required keys, ordering rules, and any explicit campaign-specific formulas from the prompt and template.
3. Fetch only public business endpoints needed for the current identifiers. Prefer endpoints named in the prompt. If the prompt gives only a family of resources, inspect list/detail endpoints for the named `event_id`, `show_id`, or `batch_id`.
4. Build the result from current API data. Do not use remembered values from examples. Do not emit fields outside the template.
5. Validate every enum, date, integer count, currency total, null, empty string, and ordering rule against the template.
6. Return one JSON object only, with no prose outside the JSON.
Useful fetch pattern: