Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Halo Change Request · automateyournetwork | DecimalAI

devopsby automateyournetwork

Halo Change Request

automateyournetwork/halo-change-request

Source automateyournetwork/netclaw ↗License Apache-2.0

Open a change request in HaloPSA / HaloITSM through a discover-preview-confirm-submit workflow, with the confirmed change ticket type cached in Memory.

SkillScore48Maintained

Automatic

DevOps & SRE pack

Last verified 8/16/2026

What it changes

Passed 9 of 19 test cases with the skill, and 3 of 19 without it.

Without skill16%

With skill48%

Checks it passed that the model alone missed

Passes entity set to halo-acme-cloud
Uses halo-global-tech as the entity key
Calls halo_list_sites to find the site ID

and 8 more in the full report

9 fixed3 passed either way12 still failing1 broke

Pass-rate lift: +32 pp
Tokens: +195%
Agent turns: 0%
Response time: -50%

Model gemini-3.6-flashMeasured 8/16/2026v112 of 25 cases passed with skill · 19 comparable

Tokens, turns and time describe resource use, not a dollar price.

Use this skill

Save it into your project's skills folder. Claude Code picks it up in its next session.

curl -fsSL --create-dirs -o .claude/skills/automateyournetwork-halo-change-request/SKILL.md https://app.decimal.ai/s/automateyournetwork-halo-change-request/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add automateyournetwork-halo-change-request, and start Claude Code with claude --plugin-dir "$(git rev-parse --show-toplevel)/.agents"

1 · One-time — install the CLI (docs ↗)

pip install "decimalai>=0.15"

2 · Get the skill — writes .agents/skills/automateyournetwork-halo-change-request/ and pins it in .decimal/skills.lock

decimalai skills add automateyournetwork-halo-change-request

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/automateyournetwork-halo-change-request/SKILL.md https://app.decimal.ai/s/automateyournetwork-halo-change-request/SKILL.md

Raw file: /s/automateyournetwork-halo-change-request/SKILL.md ↗ · machine-readable summary at /s/automateyournetwork-halo-change-request.json ↗

Safety checks: 3 of 3 passed

Code scan CleanIntent PassedContent Clean

See it in action

One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.

1 of 9

Prompt

We are preparing an internal change for server patching on tenant acme-cloud. We want to check our previously stored change type catalog before listing all ticket types. What tool call retrieves this catalog?

What was checked, without and with the skill
Checked	Without skill	With skill
Calls memory_get_facts to retrieve the change ticket types catalog	Missed	Passed
Passes entity set to halo-acme-cloud	Missed	Passed

case-07 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted

What's inside

The instructions your model reads when the skill loads.

SKILL.md167 linessingle file

Halo Change Request

Open a change request in Halo through a strict discover -> preview -> confirm -> submit flow. Halo is HaloPSA / HaloITSM (the same product and the same REST API — HaloPSA is the MSP edition, HaloITSM the internal-IT edition). A "change request" in Halo is not a fixed object type: it is simply a ticket type ("Request Type") whose numeric id and custom fields are configured per organization — and an org often defines several change types (for example a customer-facing change and an internal change). This skill figures out which change is being raised, discovers the matching type, confirms it with a human, remembers it per category, learns its fields, and gates the single write behind explicit approval.

MCP Server

Server: halo-mcp (NetClaw-authored, mcp-servers/halo-mcp/)
Command: python3 -u mcp-servers/halo-mcp/halo_mcp_server.py (stdio transport)
Auth: OAuth2 client-credentials — HALO_CLIENT_ID / HALO_CLIENT_SECRET against HALO_BASE_URL (token from <base>/auth/token, resource API at <base>/api)
Python: 3.10+ · Dependencies: fastmcp, httpx, python-dotenv
Read/write posture: read-only except one gated write — halo_create_change_request is the ONLY tool in the entire server that can mutate Halo, and it previews (no write) unless submit=true.

This skill also uses the Memory MCP server (memory-mcp) to cache the confirmed change ticket type per Halo tenant.

Available Tools

Tool	Parameters	What It Does
`halo_list_ticket_types`	`can_create_only?`, `customer?`, `showcounts?`	Discover ticket types ("Request Types"). Use `can_create_only=true` to find the org's CHANGE type
`halo_get_ticket_type`	`ticket_type`	Authoritative field schema for a type — required/optional/visible field definitions
`halo_list_fields`	`custom_only?`	Master `FieldInfo` catalog (ids <-> names <-> dropdown option values)
`halo_get_field`	`field`	One field definition by numeric id, with its lookup values
`halo_list_tickets`	`ticket_type?`, `customer?`, `asset_id?`, `status?`, `open_only?`, `search?`	Find a sample existing change to copy field patterns from
`halo_get_ticket`	`ticket` (numeric id)	Read one populated ticket as a concrete example
`halo_create_change_request`	`summary`, `details`, `ticket_type`, `customer?`, `site?`, `user?`, `asset?`, `custom_fields?`, `submit=false`	THE ONLY WRITE. Previews the exact POST body unless `submit=true`
`halo_list_clients`	`search?`	Resolve a Halo Client name to its id (the `customer` param)
`halo_list_sites`	`customer?`, `search?`	Resolve a site within a client
`halo_list_users`	`customer?`, `site_id?`, `search?`	Resolve the requesting contact/user
`memory_get_facts`	`entity`, `key?`	Recall the tenant's change-type catalog (`key="change_ticket_types"`)
`memory_record_fact`	`entity`, `key`, `value`, `metadata?`	Merge a confirmed change type ({id, name, category}) into the catalog
`memory_record_decision`	`context`, `decision`, `rationale`, ...	Log the human's ticket-type confirmation
`memory_invalidate`	`fact_id`, `reason`	Retire a cached ticket type that no longer resolves

Key Concepts

Halo == HaloPSA == HaloITSM. Same API; only the packaging differs. Everything here works against either.
"Change request" is a ticket type, not a built-in. Its id and its custom fields are per-org. You must discover it (never hard-code it) and confirm it with a human before trusting it.
There is often more than one change type. Many orgs split changes — e.g. a customer change vs an internal change, or standard / normal / emergency. Treat the change type as a set: work out which change this is (ask if unclear), keep a per-category catalog in Memory, and confirm the specific type before filing.
The Halo "Client" is the customer. Every tool that scopes to a customer org takes it as the customer param (a client name or numeric id), which the server resolves to a client_id. When someone says "the client," they mean this.
Tickets are "Faults"; ticket types are "Request Types"; assets are "Devices" in Halo's API vocabulary — the tool names hide this, but error text may show it.

Track record

Benchmark

9 / 19

test cases passed, vs 3 / 19 without

Adoption

Users: 0
Times used: 0

Safety and source details

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026

View 15 scanner checks

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

automateyournetwork / netclaw

workspace/skills/halo-change-request/SKILL.md

View on GitHub ↗

License Apache-2.0Imported 8/3/2026Version v1

More skills from the same source and nearby in the registry, with their headline benchmark lift.

Ready to supercharge your AI agents?

See it in action

What's inside

Halo Change Request

MCP Server

Available Tools

Key Concepts

Track record

Benchmark

Adoption

SkillSafety

Source

Related skills