AGENT SKILL

damira-init

Set up the current folder as a Damira network-operations workspace — configs/, documents/ and notes/ folders, plus an AGENTS.md describing the engineer's network. Use only when the user asks to set up, initialise or bootstrap a Damira workspace or project.

License 许可
MIT
最近更新
2026-11-02
Stars
★ 0
Forks
0

01 前言 Front Matter

name
damira-init
description
Set up the current folder as a Damira network-operations workspace — configs/, documents/ and notes/ folders, plus an AGENTS.md describing the engineer's network. Use only when the user asks to set up, initialise or bootstrap a Damira workspace or project.

03 SKILL.md 正文

Set up a Damira workspace

Sets up the current project folder. Existing files are safe: init only writes inside its own marked block of AGENTS.md, and only creates a README or folders that aren't there yet.

Step 1: Get the answers

If the user already gave details, use them. Otherwise ask, in one message:

  • which vendors they run (Cisco, Juniper, Arista, Palo Alto, Fortinet)
  • production, lab, or both
  • how changes are approved (ITIL with a CAB, peer review, none) and what ticketing they use
  • optionally, key platforms and versions, e.g. "Core switches: Catalyst 9300, IOS-XE 17.9.4"
  • which ecosystem tools they use, per category, skipping any they don't: ~~itsm (ServiceNow, Jira Service Management, Freshservice) with the assignment group or project; ~~tracker (Jira, monday, Linear) with the project key; ~~chat (Slack, Microsoft Teams) with the channel; ~~paging (PagerDuty, Opsgenie); and the default change type (standard, normal, emergency)

The categories and record schemas are in the plugin's CONNECTORS.md. Damira records which connectors the engineer uses. It doesn't install them.

Don't invent platforms or versions the user didn't give.

Step 2: Run init

Quote every value; one --vendor and one --platform per item. Leave out anything unanswered.

~/.damira/bin/damira init --target cursor \
  --vendor "Cisco" --vendor "Palo Alto" \
  --platform "Core switches: Catalyst 9300, IOS-XE 17.9.4" \
  --environment "production" --change-mgmt "ITIL with a CAB" --ticketing "ServiceNow" \
  --ecosystem "itsm=ServiceNow:NetOps" --ecosystem "chat=Slack:#noc-changes" \
  --change-type "normal"

One --ecosystem "CATEGORY=CONNECTOR[:GROUP_OR_KEY]" per category answered.

Init also looks for NetBox/Nautobot, Ansible AAP, pyATS and Terraform MCP servers in .cursor/mcp.json and ~/.cursor/mcp.json and writes what it finds (server names only) as an Automation capabilities section. Add --no-detect if the user doesn't want that.

Step 3: Report

Show the output, then suggest two first prompts that fit their answers. Mention that configs/ is git-ignored because device configs carry secrets.

If configs/ holds device configs, one first prompt can be "draw the topology" (the generate-diagram skill), best with saved show cdp neighbors detail output.

If the output lists Automation capabilities, one first prompt can be a source-of-truth change, e.g. "add VLAN 120 to the Chicago access switches from NetBox" (the source-of-truth-change skill).

04 同仓库更多 Skills

ciscoittech
ciscoittech/damira-plugins

upgrade-plan

Ask Damira to assess a version-to-version upgrade of a network platform and produce the MOP and change control. Use when the user names a product and a target release — "IOS-XE 17.6.5 to 17.9.5", "CUCM 12.5 SU7 to 15", "PAN-OS 10.2 to 11.1" — or asks what breaks, what the risk is, or how long a maintenance window needs to be. Covers CUCM, IOS-XE, IOS-XR, NX-OS, PAN-OS, FortiOS, Junos, ISE, ASA, WLC/Catalyst 9800. Not for platform-to-platform migration (CUCM to Webex Calling, on-prem to cloud) and not for diagnosing a fault after an upgrade — use troubleshoot for that.

★ 0
ciscoittech
ciscoittech/damira-plugins

troubleshoot

Ask Damira to diagnose an active, in-progress network fault. Use when the user reports something broken right now — an outage, a flapping interface, a BGP or OSPF adjacency down, dropped or blackholed traffic, failed calls, users unable to connect — or pastes show/log output for analysis. Also fires on direct questions like "why is BGP down" or "why is OSPF stuck in EXSTART". Returns vendor-specific diagnosis with exact CLI commands. Do NOT use for "how does X work" protocol questions, for reviewing a config that is not currently broken (use config-audit), or for planning an upgrade (use upgrade-plan).

★ 0
ciscoittech
ciscoittech/damira-plugins

source-of-truth-change

Turn intended state in the engineer's source of truth (NetBox or Nautobot) into a validated change, then hand it to the automation they already run — an Ansible Automation Platform job in check mode, a pyATS/Genie before-and-after diff, or a Terraform plan. Use when the user asks to make a change "from NetBox" or "from Nautobot", to push what the source of truth says, to bring devices in line with intended state, or to run a validated playbook through AAP or pyATS. Damira never applies the change; the engineer does. For a playbook with no source of truth use generate-playbook, for Terraform alone use generate-terraform, and for an active outage use troubleshoot.

★ 0
ciscoittech
ciscoittech/damira-plugins

lab-test-change

Test a network change in a throwaway ContainerLab lab before it goes near production — deploy the lab, apply the playbook or script, run show-command or pyATS/Genie checks, report pass/fail, and always destroy the lab. Use when the user says "test this in a lab first", "prove this change before the window", "dry-run this playbook against a lab", or wants evidence a change works before a CAB. Needs docker and containerlab on the engineer's machine; without them it validates only and says so. To only build a lab, use generate-lab; to write the change, use generate-playbook, generate-automation or generate-terraform.

★ 0
ciscoittech
ciscoittech/damira-plugins

generate-workbook

Build an Excel workbook (.xlsx) for a network procedure — a migration, platform migration, security audit, change control, or incident-response workbook — grounded in Damira evidence, with an HTML preview. Use when the user asks for a spreadsheet, workbook, tracker, or Excel version of a migration plan, cutover, audit findings, change record, or incident timeline. For a version-to-version upgrade, use upgrade-plan (it offers the workbook itself). Not for diagnosing an active fault — use troubleshoot.

★ 0
ciscoittech
ciscoittech/damira-plugins

generate-tests

Write network tests — pyATS/Genie learn, change, learn, diff jobs that prove a change did what it should and nothing else, and pytest tests for automation scripts — then validate them locally. Use when the user asks for pyATS, Genie, AEtest, a testbed file, pre/post change verification, state snapshots, or unit tests for a Nornir/Netmiko script. For the change itself use generate-playbook, generate-automation or generate-terraform.

★ 0