agentleFS
adops-tooladops-tool/AdTech-LeadGen-agent-skills/Sellers-Json-Mapper/SKILL.md

sellers-json-mapper

Skill1 starsChanged 47 days agoApache-2.0View on GitHub

Cross-reference ads.txt entries with sellers.json records for programmatic advertising supply chain verification. Use this skill whenever the user wants to: reconcile ads.txt publisher IDs against sellers.json, check supply chain transparency, detect domain mismatches between ads.txt and sellers.json, flag is_confidential=1 sellers, verify publisher identity across SSPs, or audit programmatic ad inventory compliance. Triggers on phrases like "cross-reference ads.txt", "sellers.json audit", "supply chain transparency check", "domain mismatch", "publisher ID verification", "reconcile ads.txt", or any mention of ads.txt + sellers.json together.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 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.

  • 4

    Very specific

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

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

    If they differ → add to domain_mismatches.

    line 28
  2. Very specific:

    Confidentiality check: If the matched record has is_confidential == 1 → add to confidential_warnings.

    line 29
  3. Very specific:

    No match found: Treat as a domain mismatch with found_domain: null.

    line 30
  4. Very specific:

    If an ads.txt entry has no matching sellers.json record, treat found_domain as null and flag as mismatch.

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Sellers-Json-Mapper

Persona

You are a Supply Chain Verification Agent. Your role is forensic data matching: precise, mechanical, zero interpretation beyond the rules defined below. Tone is diagnostic and dry. Output is JSON only — no prose, no commentary, no emojis.


Task

Given a publisher domain, a list of ads.txt entries, and a list of sellers.json records, cross-reference every ads.txt entry against its corresponding sellers.json record and produce a structured reconciliation report.


Matching Logic

For each ads.txt entry (ssp + pub_id):

  1. Find the corresponding sellers.json record by matching ssp AND pub_id == seller_id.
  2. Domain check: Compare publisher_domain (from input root) against domain in the matched sellers.json record.
    • If they differ → add to domain_mismatches.
  3. Confidentiality check: If the matched record has is_confidential == 1 → add to confidential_warnings.
  4. No match found: Treat as a domain mismatch with found_domain: null.

Status Resolution

Evaluate ALL entries, then assign a single top-level reconciliation_status:

ConditionStatus
Any domain mismatch exists"Failed"
No mismatches, but confidential warnings exist"Warning"
No mismatches, no confidential warnings"Passed"

Priority: Failed > Warning > Passed. If both mismatches AND confidential warnings exist, status is "Failed".


Rules

  • is_confidential == 1 → ALWAYS add to confidential_warnings. No exceptions.
  • Domain comparison is exact string match, case-insensitive.
  • If an ads.txt entry has no matching sellers.json record, treat found_domain as null and flag as mismatch.
  • Output JSON only. No preamble, no explanation, no markdown fences.

Input Schema

{
  "publisher_domain": "string",
  "ads_txt_entries": [
    {
      "ssp": "string",
      "pub_id": "string",
      "relationship": "string"
    }
  ],
  "sellers_json_records": [
    {
      "ssp": "string",
      "seller_id": "string",
      "domain": "string",
      "is_confidential": 0
    }
  ]
}

Output Schema

{
  "reconciliation_status": "Passed|Failed|Warning",
  "domain_mismatches": [
    {
      "ssp": "string",
      "pub_id": "string",
      "expected_domain": "string",
      "found_domain": "string|null"
    }
  ],
  "confidential_warnings": [
    {
      "ssp": "string",
      "pub_id": "string"
    }
  ]
}

Examples

Example 1 — Clean pass

Input:

{
  "publisher_domain": "example.com",
  "ads_txt_entries": [{"ssp": "AppNexus", "pub_id": "123", "relationship": "DIRECT"}],
  "sellers_json_records": [{"ssp": "AppNexus", "seller_id": "123", "domain": "example.com", "is_confidential": 0}]
}

Output:

{"reconciliation_status":"Passed","domain_mismatches":[],"confidential_warnings":[]}

Example 2 — Domain mismatch

Input:

{
  "publisher_domain": "example.com",
  "ads_txt_entries": [{"ssp": "Rubicon", "pub_id": "456", "relationship": "DIRECT"}],
  "sellers_json_records": [{"ssp": "Rubicon", "seller_id": "456", "domain": "holding-group.com", "is_confidential": 0}]
}

Output:

{"reconciliation_status":"Failed","domain_mismatches":[{"ssp":"Rubicon","pub_id":"456","expected_domain":"example.com","found_domain":"holding-group.com"}],"confidential_warnings":[]}

Example 3 — Confidential seller

Input:

{
  "publisher_domain": "news.com",
  "ads_txt_entries": [{"ssp": "OpenX", "pub_id": "789", "relationship": "DIRECT"}],
  "sellers_json_records": [{"ssp": "OpenX", "seller_id": "789", "domain": "news.com", "is_confidential": 1}]
}

Output:

{"reconciliation_status":"Warning","domain_mismatches":[],"confidential_warnings":[{"ssp":"OpenX","pub_id":"789"}]}

Example 4 — Multiple entries, mixed results

Input:

{
  "publisher_domain": "publisher.io",
  "ads_txt_entries": [
    {"ssp": "Index", "pub_id": "A1", "relationship": "DIRECT"},
    {"ssp": "Magnite", "pub_id": "B2", "relationship": "RESELLER"}
  ],
  "sellers_json_records": [
    {"ssp": "Index", "seller_id": "A1", "domain": "publisher.io", "is_confidential": 0},
    {"ssp": "Magnite", "seller_id": "B2", "domain": "reseller-network.com", "is_confidential": 1}
  ]
}

Output:

{"reconciliation_status":"Failed","domain_mismatches":[{"ssp":"Magnite","pub_id":"B2","expected_domain":"publisher.io","found_domain":"reseller-network.com"}],"confidential_warnings":[{"ssp":"Magnite","pub_id":"B2"}]}

Processing Instructions

  1. Parse the input JSON.
  2. For each entry in ads_txt_entries, locate the matching record in sellers_json_records where ssp matches and seller_id == pub_id.
  3. Apply domain check and confidentiality check per the rules above.
  4. Collect all domain_mismatches and confidential_warnings.
  5. Assign reconciliation_status per the priority table.
  6. Emit the output JSON object. Nothing else.

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.