Itential introduces Agentic Builder Skills for Claude Code

Itential’s Agentic Builder Skills for Claude Code let teams generate and deploy Itential Platform automation assets from a plain-language spec, with one installation providing multiple skills, agents, and a platform plugin. The update matters because it changes how automation work is packaged, from task-by-task wiring toward spec-driven construction inside controlled enterprise environments.

Research Overview

The blog describes Itential Agentic Builder Skills as a set of skills published to the Claude Marketplace that enable Artificial Intelligence (AI) coding agents to build, deploy, and manage assets inside the Itential Platform based on a natural-language specification. It also frames the approach as spec-driven development, contrasting spec-first intent capture with platform-first task wiring.

As an implementation example, the post walks through a demo that provisions a Domain Name System (DNS) A record workflow against Infoblox. The stated goal is to demonstrate a full path from a single spec file to a deployed automation asset in one pass.

Key Findings

One installation of the Builder Skills package includes 13 skills and 5 agents, plus a plugin that connects Claude Code to the Itential environment using service account credentials. The post says the skills cover building and deploying workflow-related artifacts and automation components beyond workflows.

The demo reports deploying a complete 10-task DNS A record provisioning workflow, an Operations Manager form with a manual trigger, and a project named in alignment with the spec within under 20 minutes. The blog also states that the workflow execution produced an email confirmation with record details after the form was completed.

Technical Breakdown

The blog states that the Agentic Builder Skills support creation of multiple Itential Platform asset types, including workflows, FlowAgents, command templates, Configuration Manager assets, configuration templates, Lifecycle Manager assets, IAG services, Python scripts, and Ansible playbooks. For Ansible integration, the post references use through the Itential Automation Gateway.

In the DNS example, the spec includes an Operations Manager form as the entry point and defines form fields such as hostname, zone, IP version, TTL, and an FQDN dropdown sourced dynamically via the Infoblox adapter. The workflow logic described in the spec covers merging FQDN variables, building the A record payload, creating the record in Infoblox, extracting the record reference, sending a confirmation email, and handling errors through a warning variable.

Operational Impact

The post states that the spec is not code and may be represented as markdown, bullet lists, Unified Modeling Language (UML) diagrams, or other structured descriptions, as long as it captures intent with enough clarity for an AI agent to execute. It says the spec-driven approach shifts time from mechanical construction tasks such as task wiring and adapter configuration toward discovery, logic design, and validation.

For deployment and governance, the blog says generated assets land in the Itential Platform where they are handled through existing enterprise controls, including Internal Developer Platform (IDP) and Single Sign-On (SSO) integrations and Role-Based Access Control (RBAC). It also describes the spec as serving as design input and as-built documentation, with the blog stating that the Builder Skills can generate solution design documents from the spec.

The blog’s core update is that Itential packages Claude Code “Agentic Builder Skills” to turn a spec into deployable Itential Platform automation assets, demonstrated through a DNS A record workflow built and run from a single spec file. This “Blog Signals brief” is a fact-based summary of the vendor blog.