agentleFS
timscheueraitimscheuerai/gtm-architecture-template/.agents/skills/crm-presync-check/SKILL.md

crm-presync-check

Skill2 starsChanged 2 months agoMITView on GitHub

Check an OXYGEN cohort against the connected CRM and produce existing, new, ambiguous or failed lookup decisions before a sync.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the runtime contract and the actual CRM connection/schema.

    line 8
  2. Very specific:

    Keep a decision for each row: source_id, identity_key, lookup_status, crm_id, matched_ids, checked_at, reason.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Check the CRM before syncing

Read the runtime contract and the actual CRM connection/schema. No CRM adapter or credentials are bundled. Establish company versus person identity with oxygen-dedupe.

Inspect the CRM's supported exact identity attributes and query operators. Do not assume one vendor's response path or LinkedIn slug format works elsewhere. Use a bounded read-only lookup, with any applicable provider cost visible.

Keep a decision for each row: source_id, identity_key, lookup_status, crm_id, matched_ids, checked_at, reason.

  • One confirmed identity match: existing.
  • Successful lookup with no match: new.
  • Multiple or conflicting matches: ambiguous.
  • Timeout, error, incomplete pagination or unusable key: failed.

A null CRM ID does not prove the row is new. Separate an error from a genuine zero-result lookup. Resolve conflicts before proposing writes.

Deliver counts, matches and held rows with destination IDs. This skill prepares a sync plan; an actual CRM write uses the user's separately requested scope, field ownership rules and a re-check for concurrent changes.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.