agentleFS
Sign inStart free
selamy-labsselamy-labs/agent-skills/skills/data-connector-building/SKILL.md

data-connector-building

Skill0 starsChanged 5 days agoMITView on GitHub

Use when building integrations or replacing synthetic demos with real data sources. Requires source contracts, idempotent ingestion, validation, observability, and fixture-backed tests.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Add fixtures from sanitized examples and tests for missing or partial data.

    line 22
  2. Distinctive:

    Keep credentials in the repository's established secret-management path.

    line 25

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

Data Connector Building

The connector is the product when outputs depend on external systems.

The failure this guards: a synthetic demo, fixture, or stub mistaken for a real source in production. Green tests and well-formed output prove the shape, not that any byte came from the live system. Confirm the wire before trusting the result.

Workflow

  • Define source ownership, auth path, rate limits, freshness, and allowed use.
  • Ingest once and fan out to consumers; avoid duplicate polling and drift.
  • Preserve raw source references and normalized records so each output traces back to the byte it came from.
  • Validate schema and semantic invariants at the boundary.
  • Add fixtures from sanitized examples and tests for missing or partial data.
  • Emit structured logs, spans, and metrics for fetch, parse, normalize, and publish.
  • Keep credentials in the repository's established secret-management path.

Verify

Confirm the connector hit the real source: a live fetch span with the source's own identifiers/timestamps in the lineage, not a fixture path or seeded value. A connector that passes its tests against fixtures alone is unverified.

Anti-patterns

  • Shipping the fixture/stub path as the production path; the demo becomes the product no one noticed.
  • Output that can't name which source byte produced it (no lineage to verify).
  • Calling it done on green tests without one live fetch against the real source.

Until the connector independently sources the data, label outputs as demos or format validation, not independent results.

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.

Check your setup, free