agentleFS
MicrosoftKnown publishermicrosoft/sre-agent/labs/zava-learning/sre-config/agent-config/skills/servicenow-change-management/SKILL.md

servicenow-change-management

Skill190 starsChanged 6 months agoMITView on GitHub

Use whenever a Zava Learning investigation produces a durable fix that needs change management — after a GitHub PR is opened for an Infrastructure-as-Code or application code root cause, raise a ServiceNow Change Request referencing the PR and attach the RCA report. The single owner of ServiceNow Change Request and attachment operations.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to record a durable remediation in ServiceNow once the root cause is fixed in code or IaC.

    line 14
  2. Distinctive:

    Do not raise a Change Request for live mitigations alone (deleting an NSG rule, restarting/rolling back a revision) — those are tracked as …

    line 23
  3. Very specific:

    If ServiceNow credentials are not configured, the tools return success: false — report that the Change Request could not be created and …

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Zava Learning — ServiceNow Change Management

Use this skill to record a durable remediation in ServiceNow once the root cause is fixed in code or IaC. It is the single owner of ServiceNow Change Request and attachment operations, and applies after a GitHub PR has been opened (by pr-delivery) for the durable fix.

When to use

  • A connectivity/edge or application incident has been root-caused to an IaC (infra/) or application (src/) change, and a GitHub PR has been opened with the fix.
  • An operator explicitly asks to open a Change Request or attach an RCA to an existing record.

Do not raise a Change Request for live mitigations alone (deleting an NSG rule, restarting/rolling back a revision) — those are tracked as PagerDuty incident notes. The Change Request tracks the durable code/IaC fix.

Steps

  1. Create the Change Request with CreateServiceNowChangeRequest:
    • short_description: one-line summary of the change (symptom + fix).
    • description: the RCA summary including the GitHub PR URL.
    • change_type: normal (default), standard, or emergency for active customer-impacting fixes.
    • implementation_plan / risk as appropriate.
    • Capture the returned change number (e.g. CHG0030042), sys_id, and the ready-to-use clickable link the tool returns. Surface the CR in the Artifacts & links section as a markdown hyperlink [<number>](<link>) using that returned link — never the bare CHG number, which is not clickable. (Do not try to build the URL from a SERVICENOW_URL env var — it is not available in the agent environment; the tool already returns the full clickable link.)
  2. Attach the RCA with UploadServiceNowAttachment:
    • table_sys_id: the Change Request sys_id from step 1.
    • file_name: e.g. rca-<symptom>.md.
    • content: the full RCA report (timeline, root cause, fix, verification).
  3. Reference the Change Request number back in the PagerDuty incident notes and the GitHub PR.

Notes

  • Apply the zava-redaction standard to the description, implementation_plan, and the attached RCA before submitting — mask any secret, token, connection string, or learner PII as [REDACTED:<CLASS>]. The Change Request and its attachment are operator-visible records.
  • Credentials (SERVICENOW_URL/USER/PASS) are injected from the agent environment (Key Vault-backed); never request or hardcode them.
  • If ServiceNow credentials are not configured, the tools return success: false — report that the Change Request could not be created and continue the incident lifecycle in PagerDuty.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.