Claude Docs Consultant
centminmod/my-claude-code-setup
Consult official Claude Code documentation from code.claude.com using selective fetching.
Itential Automation Platform (IAP) — network automation orchestration, device configuration management, compliance enforcement, workflow execution, golden config, lifecycle management, and gateway…
Install Itential Automation
$ npx skills add automateyournetwork/netclaw --skill itential-automation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install automateyournetwork/netclaw itential-automation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/workspace/skills/itential-automation .claude/skills/itential-automation && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "itential-automation" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/itential-automation into .claude/skills/itential-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itential-automation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/itential-automationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add automateyournetwork/netclaw --skill itential-automation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install automateyournetwork/netclaw itential-automation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/workspace/skills/itential-automation .agents/skills/itential-automation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "itential-automation" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/itential-automation into .agents/skills/itential-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itential-automation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add automateyournetwork/netclaw --skill itential-automation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install automateyournetwork/netclaw itential-automation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/workspace/skills/itential-automation .cursor/skills/itential-automation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "itential-automation" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/itential-automation into .cursor/skills/itential-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itential-automation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/automateyournetwork/netclaw.git --path workspace/skills/itential-automation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add automateyournetwork/netclaw --skill itential-automation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install automateyournetwork/netclaw itential-automation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/workspace/skills/itential-automation .gemini/skills/itential-automation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "itential-automation" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/itential-automation into .gemini/skills/itential-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itential-automation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install automateyournetwork/netclaw itential-automationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add automateyournetwork/netclaw --skill itential-automation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/workspace/skills/itential-automation .github/skills/itential-automation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "itential-automation" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/itential-automation into .github/skills/itential-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itential-automation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add automateyournetwork/netclaw --skill itential-automation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install automateyournetwork/netclaw itential-automation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/workspace/skills/itential-automation .opencode/skills/itential-automation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "itential-automation" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/itential-automation into .opencode/skills/itential-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itential-automation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
itential-automation- GitHub stars
- 676
- Token cost
- ~4.6k tokens
- SKILL.md length
- 1,516 words
- Files
- 1
- Skills in repo
- 120
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Itential Automation Platform (IAP) — network automation orchestration, device configuration management, compliance enforcement, workflow execution, golden config, lifecycle management, and gateway…
- Works in 7 steps: Platform Health Check → Device Configuration Audit → Golden Config Deployment → …
- The change should go through IAPs governed workflow/golden-config engine: automating network changes through Itential
- SKILL.md covers MCP Server, Environment Variables, Tools by Category and Workflows
- Calls pip; needs ITENTIAL_MCP_PLATFORM_PASSWORD
What it does
Itential Automation is an agent skill from automateyournetwork/netclaw. Itential Automation Platform (IAP) — network automation orchestration, device configuration management, compliance enforcement, workflow execution, golden config, lifecycle management, and gateway services via 65+ MCP tools. Use when the change should go through IAP's governed workflow/golden-config engine: automating network changes through Itential, running compliance plans, deploying golden configs, or orchestrating IAP workflows. For a direct, ad-hoc pyATS-based config push/baseline/rollback outside Itential…
Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol. The repository describes itself as: An AI agent that claws through your network. The licence is Apache-2.0.
When your agent uses it
- The change should go through IAPs governed workflow/golden-config engine: automating network changes through Itential
- Running compliance plans
- Deploying golden configs
- Orchestrating IAP workflows
Example prompts
- “/itential-automation”
Requirements
- Python 3
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit aa90e7d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pip
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
ITENTIAL_MCP_PLATFORM_PASSWORD
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Itential Automation loads about 4.6k tokens when it runs. Until then it costs about 146 tokens; SKILL.md has 1,516 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from automateyournetwork/netclaw at commit aa90e7d, republished under its Apache-2.0 licence (© automateyournetwork). 1,516 words, ~4,561 tokens.
Download SKILL.mdSave it as
.claude/skills/itential-automation/SKILL.md (or your agent's skills folder).- name
- itential-automation
- description
- Itential Automation Platform (IAP) — network automation orchestration, device configuration management, compliance enforcement, workflow execution, golden config, lifecycle management, and gateway services via 65+ MCP tools. Use when the change should go through IAP's governed workflow/golden-config engine: automating network changes through Itential, running compliance plans, deploying golden configs, or orchestrating IAP workflows. For a direct, ad-hoc pyATS-based config push/baseline/rollback outside Itential governance, use `pyats-config-mgmt` instead.
- license
- Apache-2.0
- user-invocable
- true
Itential Automation Platform
MCP Server
| Field | Value |
|---|---|
| Repository | itential/itential-mcp |
| Transport | stdio (default), SSE, HTTP |
| Python | 3.10+ (supports 3.10, 3.11, 3.12, 3.13) |
| Dependencies | fastmcp, ipsdk>=0.7.0, python-toon, wsproto |
| Install | pip install itential-mcp |
| Entry Point | itential-mcp run |
| Auth | Basic (user/pass), OAuth 2.0, JWT |
| Container | ghcr.io/itential/itential-mcp:latest |
Environment Variables
Required
| Variable | Purpose |
|---|---|
ITENTIAL_MCP_PLATFORM_HOST | IAP hostname or IP address |
ITENTIAL_MCP_PLATFORM_USER | Username for platform authentication |
ITENTIAL_MCP_PLATFORM_PASSWORD | Password for platform authentication |
Optional
| Variable | Default | Purpose |
|---|---|---|
ITENTIAL_MCP_PLATFORM_PORT | 443 | Platform connection port |
ITENTIAL_MCP_PLATFORM_TIMEOUT | 30 | Request timeout (seconds) |
ITENTIAL_MCP_PLATFORM_DISABLE_TLS | false | Disable TLS to platform |
ITENTIAL_MCP_PLATFORM_DISABLE_VERIFY | false | Skip certificate verification |
ITENTIAL_MCP_SERVER_TRANSPORT | stdio | Transport type (stdio/sse/http) |
ITENTIAL_MCP_SERVER_LOG_LEVEL | INFO | Log verbosity |
ITENTIAL_MCP_SERVER_TOOLS_PATH | — | Custom tools directory |
Tools by Category
Platform Health (1 tool)
| Tool | Parameters | Description |
|---|---|---|
get_health | — | Comprehensive platform health: status, system, server, applications, adapters (5 parallel API calls) |
Configuration Manager — Devices (4 tools)
| Tool | Parameters | Description |
|---|---|---|
get_devices | — | List all devices known to the platform with connection details |
get_device_configuration | name | Fetch the current running configuration from a device |
backup_device_configuration | name, description?, notes? | Create a config backup with optional metadata; returns backup ID |
apply_device_configuration | device, config | Deploy configuration commands to a target device |
Configuration Manager — Compliance (3 tools)
| Tool | Parameters | Description |
|---|---|---|
get_compliance_plans | — | List all compliance plans (config validation rules for org standards) |
run_compliance_plan | name | Execute a compliance plan against devices; returns pass/fail results |
describe_compliance_report | report_id | Detailed compliance report: rule violations, device status, config analysis |
Configuration Manager — Device Groups (4 tools)
| Tool | Parameters | Description |
|---|---|---|
get_device_groups | — | List all device groups with member devices |
create_device_group | name, description?, devices? | Create a new device group for bulk operations |
add_devices_to_group | name, devices | Add devices to an existing group |
remove_devices_from_group | name, devices | Remove devices from a group |
Configuration Manager — Golden Config (3 tools)
| Tool | Parameters | Description |
|---|---|---|
get_golden_config_trees | — | List all Golden Configuration trees with versions |
create_golden_config_tree | name, device_type, template?, variables? | Create a new Golden Config tree with Jinja2 template |
add_golden_config_node | tree_name, name, version?, path?, template? | Add a hierarchical config node to a tree |
Configuration Manager — Inventory (5 tools)
| Tool | Parameters | Description |
|---|---|---|
get_inventories | — | List all inventories with node counts |
describe_inventory | name | Inventory details: groups, actions, tags, nodes with attributes |
create_inventory | name, groups, description?, devices? | Create a new inventory with groups and optional devices |
add_nodes_to_inventory | inventory_name, nodes | Bulk add nodes with connection attributes and tags |
delete_inventory | name | Permanently remove an inventory |
Configuration Manager — Templates (1 tool)
| Tool | Parameters | Description |
|---|---|---|
render_template | template, variables? | Render a Jinja2 template string with variables |
Operations Manager — Workflows (5 tools)
| Tool | Parameters | Description |
|---|---|---|
get_workflows | — | List all enabled workflow API endpoints with input schemas |
start_workflow | route_name, data? | Execute a workflow by route; returns job ID, tasks, status, metrics |
get_jobs | name?, project? | List workflow execution instances with status and timing |
describe_job | object_id | Full job details: tasks, status, metrics, timestamps |
expose_workflow | name, route_name?, project?, endpoint_name?, endpoint_description?, endpoint_schema? | Create an API endpoint trigger to expose a workflow |
Automation Studio — Command Templates (6 tools)
| Tool | Parameters | Description |
|---|---|---|
get_command_templates | — | List all command templates from global space and projects |
describe_command_template | name, project? | Detailed template info including commands and validation rules |
run_command_template | name, devices, project? | Execute a command template against devices with rule evaluation |
run_command | cmd, devices | Execute a single CLI command across multiple devices |
create_command_template | name, commands, project?, description?, os?, pass_rule?, ignore_warnings? | Create a template with commands and validation rules (<!variable!> syntax) |
update_command_template | name, commands, project?, description?, os?, pass_rule?, ignore_warnings? | Update an existing command template |
Automation Studio — Templates (4 tools)
| Tool | Parameters | Description |
|---|---|---|
get_templates | template_type? | List all templates, optionally filtered by type (textfsm/jinja2) |
describe_template | name, project? | Template details: content, sample data, type, group, command |
create_template | name, template_type, group, project?, command?, template?, sample_data? | Create a new TextFSM or Jinja2 template |
update_template | name, project?, command?, template?, sample_data? | Update existing template (partial update supported) |
Automation Studio — Projects (2 tools)
| Tool | Parameters | Description |
|---|---|---|
get_projects | — | List all Automation Studio projects |
describe_project | name | Project details including component types, folders, references |
Lifecycle Manager (7 tools)
| Tool | Parameters | Description |
|---|---|---|
get_resources | — | List all resource models with descriptions |
create_resource | name, schema, description? | Create a resource model with JSON Schema definition |
describe_resource | name | Resource details including lifecycle actions and input schemas |
get_instances | resource_name | List all instances of a resource model |
describe_instance | resource_name, instance_name | Instance details: data, last action, state |
run_action | resource_name, action_name, instance_name?, instance_description?, input_params? | Execute a lifecycle action; returns job ID and status |
get_action_executions | resource_name, instance_name | Execution history: timestamps, status, before/after states |
Adapters (4 tools)
| Tool | Parameters | Description |
|---|---|---|
get_adapters | — | List all adapters with name, version, state |
start_adapter | name, timeout? | Start a stopped adapter; waits for RUNNING state |
stop_adapter | name, timeout? | Stop a running adapter; waits for STOPPED state |
restart_adapter | name, timeout? | Restart a running adapter (use start_adapter for stopped ones) |
Applications (4 tools)
| Tool | Parameters | Description |
|---|---|---|
get_applications | — | List all applications with name, version, state |
start_application | name, timeout? | Start a stopped application |
stop_application | name, timeout? | Stop a running application |
restart_application | name, timeout? | Restart a running application |
Gateway Manager (3 tools)
| Tool | Parameters | Description |
|---|---|---|
get_services | — | List all services with name, cluster, type, description |
get_gateways | — | List connected gateways with status |
run_service | name, cluster, input_params? | Execute a gateway service; returns stdout, stderr, return code, timing |
Integrations (3 tools)
| Tool | Parameters | Description |
|---|---|---|
get_integrations | model? | List integration instances, optionally filtered by model |
get_integration_models | — | List all integration models with version info |
create_integration_model | model | Create an integration model from OpenAPI spec |
Workflow Engine — Metrics (6 tools)
| Tool | Parameters | Description |
|---|---|---|
get_job_metrics | — | Aggregate job metrics across all workflows |
get_job_metrics_for_workflow | name | Job metrics filtered by workflow name |
get_task_metrics | — | Comprehensive task metrics across all workflows |
get_task_metrics_for_workflow | name | Task metrics filtered by workflow name |
get_task_metrics_for_app | name | Task metrics filtered by application name |
get_task_metrics_for_task | name | Metrics for a specific task across all workflows |
Show full SKILL.md (616 more words)Show less
Dynamic Tool Bindings
The server also supports dynamically registered tools:
- Endpoint bindings — Expose IAP workflow triggers as MCP tools via
ITENTIAL_MCP_TOOL_<NAME>_TYPE=endpoint - Service bindings — Expose Gateway Manager services as MCP tools via
ITENTIAL_MCP_TOOL_<NAME>_TYPE=service
Workflows
1. Platform Health Check
get_health → assess status/system/server/applications/adapters health
→ get_adapters → check for DEAD/STOPPED adapters
→ get_applications → check for stopped applications
→ Report overall platform status → GAIT2. Device Configuration Audit
get_devices → inventory all managed devices
→ get_device_groups → understand grouping strategy
→ get_compliance_plans → list org compliance rules
→ run_compliance_plan(plan_name) → execute against devices
→ describe_compliance_report(report_id) → review violations
→ Severity-sort findings → GAIT3. Golden Config Deployment
get_golden_config_trees → review available configs
→ get_devices → select target devices
→ render_template(jinja2_template, variables) → preview config
→ backup_device_configuration(device) → baseline before change
→ apply_device_configuration(device, rendered_config) → deploy
→ get_device_configuration(device) → verify post-change
→ GAIT4. Workflow Orchestration
get_workflows → discover available automations
→ get_projects → review Automation Studio projects
→ start_workflow(route_name, data) → trigger execution
→ describe_job(object_id) → monitor progress and tasks
→ get_job_metrics_for_workflow(name) → performance analysis
→ GAIT5. Command Template Execution
get_command_templates → list available templates
→ describe_command_template(name) → review commands and rules
→ get_device_groups → select target group
→ run_command_template(name, devices) → execute with rule evaluation
→ Review per-device results → GAIT6. Lifecycle Resource Management
get_resources → discover resource models
→ describe_resource(name) → review lifecycle actions and schemas
→ get_instances(resource_name) → list existing instances
→ run_action(resource, action, instance, params) → execute lifecycle action
→ get_action_executions(resource, instance) → verify execution history
→ GAIT7. Integration Model Onboarding
get_integration_models → review existing integrations
→ create_integration_model(openapi_spec) → register new model
→ get_integrations(model) → verify instance created
→ GAITIntegration with Other Skills
| Skill | Integration |
|---|---|
| pyats-network | Use Itential command templates to run structured commands; compare pyATS parsed output with Itential compliance results |
| pyats-config-mgmt | Itential golden config as the desired state; pyATS for pre/post verification; ServiceNow for CR gating |
| netbox-reconcile | Itential inventories reflect NetBox source of truth; compliance plans validate against NetBox-defined intent |
| nautobot-sot | Same as NetBox — cross-reference Itential device inventory with Nautobot IPAM data |
| infrahub-sot | Cross-reference Infrahub schema-driven nodes with Itential device groups and inventories |
| servicenow-change-workflow | Gate all Itential config deployments behind ServiceNow Change Requests |
| gait-session-tracking | Every Itential workflow execution, config push, and compliance run logged in GAIT |
| fmc-firewall-ops | Itential workflows can orchestrate firewall policy changes validated by FMC search |
| nso-device-ops | Itential as the orchestration layer on top of NSO for multi-vendor service deployment |
| te-network-monitoring | Validate network health via ThousandEyes after Itential config deployments |
| aws-network-ops | Itential workflows for hybrid network automation spanning on-prem and AWS |
| gcp-compute-ops | Itential lifecycle management for resources spanning on-prem and GCP |
Tag-Based Tool Filtering
Itential MCP supports tag-based filtering to restrict which tools are exposed:
| Tag | Tools | Use Case |
|---|---|---|
health | 1 | Platform monitoring |
configuration_manager | 15 | Device config, compliance, golden config, templates, inventories |
operations_manager | 5 | Workflow execution and job management |
automation_studio | 12 | Command templates, projects, device commands, TextFSM/Jinja2 templates |
lifecycle_manager | 7 | Resource models, instances, lifecycle actions |
workflow_engine | 6 | Job and task performance metrics |
adapters | 4 | Adapter lifecycle management |
applications | 4 | Application lifecycle management |
gateway_manager | 3 | Gateway and service operations |
integrations | 3 | Integration model management |
Use --include-tags to restrict to specific categories or --exclude-tags to hide experimental tools.
Itential vs Other Orchestration Platforms
| Capability | Itential IAP | Cisco NSO | Ansible |
|---|---|---|---|
| Focus | Full lifecycle automation orchestration | Network service orchestration | Config management + ad-hoc tasks |
| Device Management | Inventory, groups, config backup/push | CDB, device sync, NED-based | Inventory, groups, playbooks |
| Compliance | Built-in compliance plans + reports | Custom via templates | Custom via assert/compliance roles |
| Golden Config | Hierarchical tree-based with versioning | Config templates via services | Jinja2 templates in roles |
| Workflow Engine | Visual workflow builder + API triggers | Service deployment plans | Playbooks + AWX/Tower |
| Lifecycle Mgmt | Resource models with action schemas | Service lifecycle via FASTMAP | Roles with tags |
| MCP Tools | 65+ tools across 10 categories | 5 tools (devices + services) | N/A |
| Integration | OpenAPI-based integration models | NED packages | Modules + collections |
| Gateway | Gateway Manager for distributed execution | LSA for distributed NSO | Execution environments |
Guardrails
- Gate config deployments — All
apply_device_configurationcalls must be preceded by a ServiceNow Change Request inImplementstate - Always backup first — Call
backup_device_configurationbefore anyapply_device_configuration - Verify after deployment — Call
get_device_configurationafter applying changes to confirm they took effect - Compliance before and after — Run
run_compliance_planpre- and post-change to verify compliance posture - Record in GAIT — Every workflow execution, config push, compliance run, and template operation must be logged
- Adapter health awareness — Check
get_adaptersfor DEAD or STOPPED adapters before attempting device operations - Case-sensitive names — Workflow names, device names, template names, and plan names are all case-sensitive in the IAP API
Failure Behavior
- If a tool call fails with an authentication or connection error, check that
ITENTIAL_MCP_PLATFORM_HOSTis set and valid before assuming a data or device problem. - On a tool error (timeout, unreachable host, malformed response), report the failure and its error message directly to the user rather than fabricating or guessing at results.
- Do not automatically retry a write/mutating operation after a failure — surface the error and get explicit confirmation before retrying, since a blind retry on a partially-applied change can leave state inconsistent.
© automateyournetwork, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in workspace/skills/itential-automation of automateyournetwork/netclaw.
Open the folder on GitHubat commit aa90e7d
Compare with similar skills
Itential Automation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Itential Automation this skillautomateyournetwork/netclaw | 676 | — | ~4.6k | Automated safety check: Pass | Apache-2.0 | |
| Claude Docs Consultantcentminmod/my-claude-code-setup | 2.7k | — | ~959 | Automated safety check: Pass | MIT | |
| Opsanyunixhot/opsany-paas | 181 | — | ~2k | Automated safety check: Pass | Custom licence | |
| Project Releaseswimmwatch/cloakbrowser-mcp | 164 | — | ~1.9k | Automated safety check: Pass | MIT | |
| AWS Agentic AIzxkane/aws-skills | 367 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Setup Xhs MCPautoclaw-cc/xiaohongshu-mcp-skills | 272 | — | ~678 | Automated safety check: Pass | MIT |
Similar skills
Opsany
unixhot/opsany-paas
通过 opsany-mcp-server 连接 OpsAny 运维平台，实现 CMDB 资源查询和操作、模型管理、工单管理、用户管理、作业执行及主机纳管等全栈运维操作。
Project Release
swimmwatch/cloakbrowser-mcp
Prepare, publish, verify, or recover a cloakbrowser-mcp release only when the user explicitly requests release work.
AWS Agentic AI
zxkane/aws-skills
AWS Bedrock AgentCore comprehensive expert for deploying and managing AI agents at scale.
Setup Xhs MCP
autoclaw-cc/xiaohongshu-mcp-skills
安装部署 xiaohongshu-mcp 服务并配置 MCP 连接，引导用户完成从零到可用的全流程. An agent skill from autoclaw-cc/xiaohongshu-mcp-skills.
Devcontainer Dev
stacklok/toolhive-studio
Spin up and interact with ToolHive Studio's containerized dev environment (Xvfb + noVNC + DinD).
More from automateyournetwork/netclaw
All 120 skills in this repoEVE-NG Lab Topology Design
automateyournetwork/netclaw
Entry point for designing EVE-NG network labs: classifies the request, gathers missing requirements, proposes options and validates the resulting topology.
ACI Policy Change Deployment
automateyournetwork/netclaw
Deploys Cisco ACI policy changes only behind an approved ServiceNow Change Request, capturing pre and post-change fault baselines and rolling back automatically on a fault delta.
Cisco ACI Fabric Health Audit
automateyournetwork/netclaw
Runs a phased health audit of a Cisco ACI fabric through MCP tools: node status, links, tenant and policy review, faults and endpoint learning.
Anta Validation
automateyournetwork/netclaw
Validate Arista EOS network state against ANTA's pre-built 208-test catalogue, with structured pass/fail verdicts.
Arista Cvp
automateyournetwork/netclaw
Arista CloudVision Portal (CVP) automation via REST API — device inventory, events, connectivity monitoring, tag management (4 tools).
AWS Cloud Monitoring
automateyournetwork/netclaw
AWS CloudWatch monitoring — metrics, alarms, log queries, VPC flow log analysis, network performance.
Related
Works with
Categories
Questions about Itential Automation
What does Itential Automation do?
Itential Automation Platform (IAP) — network automation orchestration, device configuration management, compliance enforcement, workflow execution, golden config, lifecycle management, and gateway…. Itential Automation is an agent skill from automateyournetwork/netclaw. Itential Automation Platform (IAP) — network automation orchestration, device configuration management, compliance enforcement, workflow execution, golden config, lifecycle management, and gateway services via 65+ MCP tools.
When should I use Itential Automation?
Itential Automation fits situations like: the change should go through IAPs governed workflow/golden-config engine: automating network changes through Itential; running compliance plans; deploying golden configs; orchestrating IAP workflows.
How do I install Itential Automation in Claude Code?
Run `npx skills add automateyournetwork/netclaw --skill itential-automation -a claude-code`. Or copy the skill folder (workspace/skills/itential-automation in automateyournetwork/netclaw) into .claude/skills/itential-automation in your project. Claude Code loads it when a task matches its description.
How do I install Itential Automation in Codex?
Run `npx skills add automateyournetwork/netclaw --skill itential-automation -a codex`. Or copy the skill folder (workspace/skills/itential-automation in automateyournetwork/netclaw) into .agents/skills/itential-automation in your project. Codex loads it when a task matches its description.
Can I use Itential Automation in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add automateyournetwork/netclaw --skill itential-automation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/itential-automation, .gemini/skills/itential-automation, .github/skills/itential-automation and .opencode/skills/itential-automation in your project.
What does Itential Automation need to run?
Going by SKILL.md and its folder, Itential Automation needs the command-line tools its instructions call (pip) and credentials named ITENTIAL_MCP_PLATFORM_PASSWORD. Our summary lists: Python 3.
Does Itential Automation access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Itential Automation safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Itential Automation use?
Itential Automation is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Itential Automation use?
About 4.6k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Itential Automation?
Skills that share tags, products or a category with Itential Automation: Claude Docs Consultant (centminmod/my-claude-code-setup, 2.7k stars), Opsany (unixhot/opsany-paas, 181 stars), Project Release (swimmwatch/cloakbrowser-mcp, 164 stars) and AWS Agentic AI (zxkane/aws-skills, 367 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Itential Automation?
automateyournetwork (a GitHub user) maintains it in automateyournetwork/netclaw, which has 676 GitHub stars. The repository holds 120 skills in this directory. The repository was last updated on October 9, 2026.
Source: automateyournetwork/netclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.