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.
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.
24 skills
Skills
Portable expertise an agent loads on demand — review checklists, diagnosis playbooks, authoring recipes. Files, not magic.
Browse skills12 servers
MCP servers
Live tools the agent can call: query a warehouse, read a catalog, run a profiler. The hands behind the reasoning.
Browse mcp servers10 hooks
Hooks
Guardrails that intercept agent actions — block destructive SQL, scan secrets, stop runaway cost before it happens.
Browse hooks12 agents
Agents
Composed workflows: inputs, tools, skills and guardrails wired into a repeatable job like incident triage.
Browse agents10 plugins
Plugins
Battery-included bundles that install skills, hooks, commands and MCP servers as one coherent toolkit.
Browse plugins15 patterns
Patterns
Architecture patterns the agent knows by name — so "make this idempotent" means something specific.
Browse patternsBlast 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.
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
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
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
Audit an MCP server's tool contracts
- Read a tool schema and predict its side effects
- Classify tools by blast radius
Details
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
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
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
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
Production gotchas — untrusted content, destructive actions, permission scope
An agent executes with your credentials, so its context and config are an attack surface.
Details
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
MCP Tool Contract Auditor
- Read a tool schema and predict its side effects
- Classify tools by blast radius
Details
Fetch MCP Server
Retrieves a URL and converts it to markdown for the model.
Details
Filesystem MCP Server
Reference server that exposes a sandboxed set of directories as readable and (optionally) writable tools.
Details
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
GitHub MCP Server
First-party GitHub server exposing repositories, issues, pull requests and code search, plus optional write operations.
Details
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
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
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
Daily Life as a Jenkins Administrator
Jenkins Kubernetes setup As a team, we introduced Jenkins Kubernetes for every user a few months ago.
Details
GSoC 2026 Final Blog: How It Was to Be a Contributor at Jenkins
Hello everyone!
Details
Jenkins and AI Agents: The Trusted Engine for Faster Software Delivery
The 2026 Reality Check By 2026, software development has crossed a threshold.
Details
kitfunso/hippo-memory
Stop re-teaching your agent.
Details
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
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
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
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
Go deeper
Read the contracts
The exact shapes behind every primitive — content model, skill anatomy and the tool contract.
Skill anatomy
What a SKILL.md contains, how progressive disclosure works, and the files a skill ships with.
Read the anatomyTool & MCP contract
How MCP servers, tools, hooks and plugins declare what they touch — transports, permissions, permissions again.
Read the contractContent object model
The canonical Resource shape every entry normalizes into, and the 16 fields a complete record fills.
Read the model