agentleFS
timscheueraitimscheuerai/gtm-architecture-template/.agents/skills/oxygen-dedupe/SKILL.md

oxygen-dedupe

Skill2 starsChanged 2 months agoMITView on GitHub

Review duplicate companies, people and source events before ingestion while preserving provenance and holding uncertain identity matches.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the runtime contract.

    line 8

≈ “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

Resolve identity before merging

Read the runtime contract. Establish the record type and destination before choosing a key.

  • Companies: verified canonical domain or provider/company LinkedIn identity. Subsidiaries and shared domains require a deliberate rule.
  • People: canonical profile URL or stable provider person ID, reconciled with current employer. A name alone is insufficient.
  • Signals: provider plus stable event ID; retain separate events for one account.
  • Outcomes: event ID plus enrollment/cohort identity, as required by analyse_results.

Inspect the current schema and bounded existing identities. Normalise URL scheme, host, trailing slash and query parameters without changing the actual identity path. Retain original values. Missing keys go to a review queue; never collapse all nulls into one record.

Produce insert / existing / possible_match / invalid decisions with the matched ID and reason. Repeated signals enrich provenance; they do not create repeated people. Conflicting non-null fields need a field-level resolution rule.

Preview counts and collisions before an authorized upsert. Re-query an ambiguous write result before retrying. For a repeat import, verify it creates no extra identities while still preserving new signals. Do not delete records or merge people solely because names match.

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.