DE//AGENT
Explore

Agentic Data Engineering

Capabilities for coding agents

The registry is built so a coding agent can do data engineering with you: load the right skill, call the right tool, stay inside the guardrails. Five primitives, one trust model.

68 executable resources trust signals on every entry

Primitives

Five building blocks

Each primitive has a strict contract — what it is, what it can do, and what it must never do. Mix them deliberately.


Blast radius

Know what you are installing

Every resource declares what it can touch. These counts update with every registry build — check them before you grant access.

196 entries

read-only resources

57 entries

touch your code or files

58 entries

need credentials

53 entries

access the network

The 180-day staleness rule and per-resource security flags are detailed in Verification levels and Security & trust.


Stage 13

Agentic stage curriculum

The dedicated stage of the roadmap — skills, servers and references specifically about working with agents.

Tutorial 34 adequate

Keep an agent read-only until a human approves

Coding agents can do real data-engineering work, but can also ship a schema change or drop a table.

Details
beginner tutorialagentic community
Tutorial 34 adequate

What makes an agent — model, tools, loop, guardrails

Build the map before touching anything: an agent is a model that reasons, tools that act, a loop that iterates, and guardrails that bound it.

Details
beginner tutorialagentic community
Tutorial 34 adequate

Wire the core MCP servers for a data repo

Wire the three reference MCP servers a data repo needs: filesystem for the working directory, git for history and commits, and GitHub for issues and pull requests.

Details
beginner tutorialmcp community
Tutorial 34 adequate

Audit an MCP server's tool contracts

  • Read a tool schema and predict its side effects
  • Classify tools by blast radius
Details
intermediate tutorialmcp community
Tutorial 34 adequate

Hooks — deterministic gates around an agent

  • Explain where hooks run — on tool-call and pre-run events, outside the model
  • Match each safety hook to the failure it prevents
Details
intermediate tutorialagentic community
Tutorial 34 adequate

Inside a skill — SKILL.md, references, examples, the loading protocol

A skill is the unit of reusable agent behavior: one SKILL.md with front-matter, plus directories the agent loads on demand.

Details
intermediate tutorialagentic community
Tutorial 34 adequate

Onboard an agent with the DE Data Toolkit

Onboard an agent onto a data repo with the DE Data Toolkit plugin: the SQL/Spark review skills, the destructive-SQL guard, a secret scanner, and the file/git MCP servers already wired.

Details
intermediate tutorialagentic community
Tutorial 34 adequate

Capstone — the guarded agent checklist

Run the whole series against one agent setup: skills that load on demand, tools scoped at the connection, least-privilege credentials, audited tool contracts, hooks that fail closed, and a human gate on anything irreversible.

Details
advanced tutorialagentic community
Tutorial 34 adequate

Production gotchas — untrusted content, destructive actions, permission scope

An agent executes with your credentials, so its context and config are an attack surface.

Details
advanced tutorialagentic community
Tutorial 34 adequate

When an agent does the wrong thing — contain, audit, postmortem

  • Contain the damage before diagnosing — rollback first
  • Reconstruct what the agent did from the audit trail
Details
advanced tutorialagentic community
Skill 41 adequate

MCP Tool Contract Auditor

  • Read a tool schema and predict its side effects
  • Classify tools by blast radius
Details
Python advanced mcpsecurity community
MCP server 46 adequate

Fetch MCP Server

Retrieves a URL and converts it to markdown for the model.

Details
beginner mcpfetch community
MCP server 48 adequate

Filesystem MCP Server

Reference server that exposes a sandboxed set of directories as readable and (optionally) writable tools.

Details
beginner mcpfilesystem community
MCP server 48 adequate

Git MCP Server

Exposes local Git operations — status, diff, log, commit, branch — as tools, so an agent can inspect history and prepare changes without shelling out blindly.

Details
beginner mcpgit community
MCP server 41 adequate

GitHub MCP Server

First-party GitHub server exposing repositories, issues, pull requests and code search, plus optional write operations.

Details
beginner mcpgithub community
Plugin 34 adequate

DE Data Toolkit

The opinionated starter plugin: SQL/Spark review skills, the destructive-SQL guard, a secret scanner and the file/git MCP servers, wired for data engineers.

Details
beginner pluginstarter community
Pattern 36 adequate

Agent-in-the-Loop Review

Coding agents can do real data-engineering work, but can also ship a schema change or drop a table.

Details
intermediate architectureagentic community
Reference 28 adequate

Agent Skills (open format)

The Agent Skills format specification — a SKILL.md file with front-matter (name, description, version), plus references/, scripts/, and examples/ directories that an agent loads on demand. The format this platform's Skill object is modelled on — portable across compatible agents. Covers the SKILL.md schema, the directory layout convention, and the agent loading protocol.

Details
agenticskills community
Reference 24 unproven

Daily Life as a Jenkins Administrator

Jenkins Kubernetes setup As a team, we introduced Jenkins Kubernetes for every user a few months ago.

Details
community
Reference 24 unproven

GSoC 2026 Final Blog: How It Was to Be a Contributor at Jenkins

Hello everyone!

Details
community
Reference 24 unproven

Jenkins and AI Agents: The Trusted Engine for Faster Software Delivery

The 2026 Reality Check By 2026, software development has crossed a threshold.

Details
community
Reference 24 unproven

kitfunso/hippo-memory

Stop re-teaching your agent.

Details
community
Reference 28 adequate

MCP Registry (official)

The official MCP Registry — community-driven registry of MCP servers with a metadata schema for discovery. The canonical place to discover MCP servers — treat entries as *discovery*, never as a trust signal. The metadata schema defines server capabilities, transport, and authentication; essential for building MCP-aware tooling.

Details
mcpregistry community
Reference 28 adequate

Model Context Protocol Specification

definitive reference for transports (stdio, SSE, HTTP), tool definitions, resource templates, prompts, and the security model. The security section is required reading before connecting any MCP server to real data; the transport section explains stdio vs HTTP tradeoffs. The canonical reference for all MCP server implementations on this platform.

Details
mcpspec community
Reference 24 unproven

Monitoring MWAA-orchestrated ETL pipelines with Amazon OpenSearch Service

Troubleshooting a multi-service, MWAA-orchestrated ETL pipeline often means hunting across scattered Amazon CloudWatch log groups.

Details
community
Reference 24 unproven

oaslananka/kicad-mcp-pro

MCP server for KiCad, connecting AI agents to schematic and PCB workflows, ERC/DRC validation, DFM checks, BOM analysis, and manufacturing preparation—with controlled edits and human-gated release wor

Details
community

Go deeper

Read the contracts

The exact shapes behind every primitive — content model, skill anatomy and the tool contract.