Menu

Individual skill

harborcrm-workflows

0upvotes

Process HarborCRM API tasks that ask for event handoffs, trade-show prospecting, badge reconciliation, import-batch cleanup, sponsor finance follow-up, or any JSON-only CRM report built from HarborCRM endpoints and a provided answer template.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_001/fewshot/cc/fewshot_attempt_02/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 Workflows

Read the prompt and answer template first. Treat the template as the contract; use its keys, enums, ordering rules, and number formats exactly.

## Procedure

1. Identify the task family and read the matching section in [references/workflows.md](references/workflows.md).
2. Fetch the base record and the endpoint collections named in the prompt.
3. Join records on the most stable shared key available: `event_id`, `show_id`, `batch_id`, `account_id`, `contact_id`, normalized email, company name, or `row_id`.
4. Normalize contact data before matching: trim whitespace, lowercase emails, and strip phones to digits only.
5. Classify each record with only the values allowed by the prompt, template, or policy docs.
6. Sort every list exactly as specified.
7. Compute counts, totals, and due dates from the final surviving records.
8. Return one JSON object only, with no prose outside the JSON.
Back to top