Menu

Individual skill

reflect-3_attempt_01

0upvotes

Not available

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

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 CRM Reconciliation SOP

Use this skill for HarborCRM tasks that ask for CRM-ready JSON from public API data: post-event sponsor/lead handoffs, trade-show prospecting summaries, and contact import hygiene. Always read the staged prompt and answer template first, then shape the response exactly to the template.

## Core Workflow

1. Identify the requested object id: `event_id`, `show_id`, or `batch_id`.
2. Pull every public API source named or implied by the prompt before deciding: event/show metadata, sponsor orders/packages, badges or exhibitors, finance invoices, CRM accounts, CRM contacts, opportunities, campaign members, suppression lists, meeting-interest records, and policies.
3. Build joins using stable ids first, then normalized names/domains/emails as fallback.
4. Normalize data before matching:
   - Emails: trim and lowercase.
   - Phones: digits only; leave `""` when no phone exists.
   - Money and counts: integers.
   - Dates: calendar dates in `YYYY-MM-DD`; follow-up due dates are event end date plus the configured day offset.
5. Return JSON only. Do not add undeclared fields or explanatory prose.