DE//AGENT
Explore

Docs · Project

Contributing a Resource

How to propose a new registry entry: what gets accepted, what the record needs, and how curation works.

The registry grows by curation, not by submission volume. One well-scored, verified entry beats ten unreviewed links. Here’s how to contribute.

What belongs

Resources that help someone do data engineering with an agent alongside:

  • Skills, MCP servers, hooks, plugins, agents — executable primitives with clear contracts (see the tool contract and skill anatomy).
  • Templates, starter projects, runbooks, patterns — the buildable and the reusable.
  • References — documentation, specs and books worth pointing at, scored on the quality rubric, not on popularity.

Hard rules, enforced by the build: one canonical category per resource; a declared license; and for proprietary sources, we link and summarise — we never reproduce content.

The process

  1. Open an issue on the repository with the resource’s URL, what it does, and which category you think it fits. Check the taxonomy first — if you can’t find its category, that conversation is worth having before you write the record.
  2. A curator drafts the record as YAML (or you can draft it following the existing files as a template) against the content object model: classification, provenance, security flags, learning objectives where they apply.
  3. Verification is asserted, not assumed. New entries land at community (metadata captured, nothing checked) and are promoted to reviewed (source, license and docs checked) and tested (install + example actually run) as the checks are performed. See Verification levels.
  4. The build decides. Normalization, schema validation, referential integrity checks and scoring run on every build; a malformed record fails loudly instead of shipping half-broken.

The bar

  • Would a data engineer with an agent actually use this within a month?
  • Is the blast radius honestly declared (code execution, network, credentials)?
  • Is the license identified and respected?
  • Does the description say what it does — not what it aspires to?

If all four are yes, it belongs here.

Promotion checklist

Drafts become records through an evidence gate, not enthusiasm. Run node pipelines/promote.mjs --draft <file> — it moves nothing by default, only renders a verdict. Add --apply to move a passing draft into data/curated/.

The gate requires: a unique id and slug, a known type and category, a declared license, a description of 200+ characters, and — for any claim above community — passed evidence entries matching the level (license and source checks for reviewed, plus build and test runs for tested, plus smoke and output validation for verified). Drafts ship as community unless that evidence rides along. After promotion, run the pipeline and the build; both must stay green.