Menu

Individual skill

reflect-3_attempt_03

0upvotes

Not available

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_001/reflect-3/reflect-3_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
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.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

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.

Declared tags are partial or unavailable.

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 Reconciliation And Prospecting SOP

Use this skill for HarborCRM tasks that ask for JSON-only CRM handoffs, event reconciliations, trade-show prospect lists, or import-batch cleanup. Work from the staged prompt, its answer template, and the public HarborCRM API endpoints named or implied by the prompt. Do not add prose, extra fields, or alternative enum values to the final JSON.

## Source Habits

1. Read the answer template first and mirror its top-level keys, item keys, enum spelling, nullability, and ordering rules exactly.
2. Fetch all relevant public records before deciding: event or show metadata, sponsor orders/packages, badges, invoices, CRM accounts, CRM contacts, opportunities, campaign members, import raw rows, suppression lists, meeting-interest records, and policies.
3. Join records by the strongest key available: `account_id`, `contact_id`, `event_id`, `show_id`, `crm_account_id`, normalized email, normalized phone, then company/contact name only when IDs are absent.
4. Use policy enums as controlled values. For platform coverage, use only `AUV`, `ROV`, and `Underwater Camera` in that order.
5. Treat money as integer USD and dates as `YYYY-MM-DD`. Follow-up dates are event end date plus the event's configured follow-up day count.

## Output Conventions

1. Return one JSON object only. Keep field names exactly as declared in the template.
Back to top