AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
Review a HaloPSA / HaloITSM ticket for resolution context — its detail, action/note history, linked assets, and related KB runbooks — read-only.
Install Halo Ticket Context
$ npx skills add automateyournetwork/netclaw --skill halo-ticket-context -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install automateyournetwork/netclaw halo-ticket-context --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/halo-ticket-context .claude/skills/halo-ticket-context && 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 "halo-ticket-context" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/halo-ticket-context into .claude/skills/halo-ticket-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "halo-ticket-context", 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/halo-ticket-contextType 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 halo-ticket-context -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install automateyournetwork/netclaw halo-ticket-context --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/halo-ticket-context .agents/skills/halo-ticket-context && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "halo-ticket-context" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/halo-ticket-context into .agents/skills/halo-ticket-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "halo-ticket-context", 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 halo-ticket-context -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install automateyournetwork/netclaw halo-ticket-context --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/halo-ticket-context .cursor/skills/halo-ticket-context && 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 "halo-ticket-context" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/halo-ticket-context into .cursor/skills/halo-ticket-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "halo-ticket-context", 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/halo-ticket-context--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 halo-ticket-context -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install automateyournetwork/netclaw halo-ticket-context --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/halo-ticket-context .gemini/skills/halo-ticket-context && 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 "halo-ticket-context" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/halo-ticket-context into .gemini/skills/halo-ticket-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "halo-ticket-context", 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 halo-ticket-contextInstalls 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 halo-ticket-context -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/halo-ticket-context .github/skills/halo-ticket-context && 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 "halo-ticket-context" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/halo-ticket-context into .github/skills/halo-ticket-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "halo-ticket-context", 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 halo-ticket-context -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 halo-ticket-context --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/halo-ticket-context .opencode/skills/halo-ticket-context && 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 "halo-ticket-context" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/halo-ticket-context into .opencode/skills/halo-ticket-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "halo-ticket-context", 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
halo-ticket-context- GitHub stars
- 676
- Token cost
- ~1.8k tokens
- SKILL.md length
- 765 words
- Files
- 1
- Skills in repo
- 120
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Review a HaloPSA / HaloITSM ticket for resolution context — its detail, action/note history, linked assets, and related KB runbooks — read-only.
- Works in 6 steps: Identify the ticket. If you only have a… → Read the ticket detail → Read the note history (the core step) → …
- Investigating a Halo ticket
- SKILL.md covers MCP Server, Available Tools, Key Concepts and Workflow, plus 4 more sections
- Calls python3; needs HALO_CLIENT_SECRET
What it does
Halo Ticket Context is an agent skill from automateyournetwork/netclaw. Review a HaloPSA / HaloITSM ticket for resolution context — its detail, action/note history, linked assets, and related KB runbooks — read-only. Use when investigating a Halo ticket, gathering resolution context, reading a ticket's note history, or finding runbooks for an open issue.
Its SKILL.md is about 1.8k 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 DevOps & Cloud, covering Runbooks and postmortems. It works with Model Context Protocol and Python. The repository describes itself as: An AI agent that claws through your network. The licence is Apache-2.0.
When your agent uses it
- Investigating a Halo ticket
- Gathering resolution context
- Reading a tickets note history
- Finding runbooks for an open issue
Example prompts
- “/halo-ticket-context”
Requirements
- Python 3
- A credential in HALO_CLIENT_SECRET
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Identify the ticket. If you only have a description, find its id first
- Read the ticket detail
- Read the note history (the core step)
- Inspect linked assets surfaced in step 2
- Find related runbooks in the knowledge base
- Report a resolution-context summary: the issue, timeline of actions to date, affected assets, applicable KB runbooks, and the recommended…
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:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
HALO_CLIENT_SECRET
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Halo Ticket Context loads about 1.8k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 765 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). 765 words, ~1,808 tokens.
Download SKILL.mdSave it as
.claude/skills/halo-ticket-context/SKILL.md (or your agent's skills folder).- name
- halo-ticket-context
- description
- Review a HaloPSA / HaloITSM ticket for resolution context — its detail, action/note history, linked assets, and related KB runbooks — read-only. Use when investigating a Halo ticket, gathering resolution context, reading a ticket's note history, or finding runbooks for an open issue.
- license
- Apache-2.0
- user-invocable
- true
Halo Ticket Context
Review a ticket in Halo to gather everything needed to understand and resolve it — the ticket detail, its full action/note history, the assets it touches, and related knowledge-base runbooks. Entirely read-only. Halo is HaloPSA / HaloITSM (the same product and REST API); tickets are called "Faults" in Halo's API vocabulary.
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_SECRETagainstHALO_BASE_URL - Python: 3.10+ · Dependencies:
fastmcp,httpx,python-dotenv - Read/write posture: The whole server is read-only except one gated write (
halo_create_change_request, in the halo-change-request skill). Every tool in this skill is read-only.
Available Tools
| Tool | Parameters | What It Does |
|---|---|---|
halo_get_ticket | ticket (numeric id) | Read one ticket ("Fault") — summary, details, status, priority, client/site/user, and linked assets |
halo_get_ticket_actions | ticket (numeric id) | The ticket's actions/notes history (the investigation timeline) |
halo_list_tickets | ticket_type?, customer?, asset_id?, status?, open_only?, search? | Find a ticket by type, customer, asset, status, or free text |
halo_get_asset | asset (name / inventory-number / id) | Read a linked asset surfaced on the ticket |
halo_list_kb_articles | search? | Search the Halo knowledge base for related runbooks |
halo_get_kb_article | article (numeric id) | Read one KB article, including its body |
Key Concepts
- Halo == HaloPSA == HaloITSM. Same API for both editions.
- Tickets are "Faults" and are addressed by numeric id only — they are not name-resolvable. If you don't have the id, find it with
halo_list_tickets(bycustomer,asset_id,status, orsearch) first. - The Halo "Client" is the customer. Filter ticket lists to an org with the
customerparam (a client name or id). - Actions are the story.
halo_get_ticket_actionsreturns the note/action timeline — the richest source of what has already been tried and what remains. - Assets link tickets to devices.
halo_get_ticketreturns linked assets; read them withhalo_get_asset(or pivot to the halo-asset-context skill). - KB articles are the runbooks. Search with
halo_list_kb_articles, then read the full body withhalo_get_kb_articlefor resolution/runbook context. - Read-only. Nothing here writes. If a change is warranted, hand off to halo-change-request.
Workflow
Assemble resolution context for a ticket:
Identify the ticket. If you only have a description, find its id first:
halo_list_tickets(customer="<client>", search="<keywords>", open_only=true)Read the ticket detail:
halo_get_ticket(ticket=<id>)Capture status, priority, client/site/requesting user, and any linked assets.
Read the note history (the core step):
halo_get_ticket_actions(ticket=<id>)Reconstruct the timeline: what was diagnosed, what was tried, current state.
Inspect linked assets surfaced in step 2:
halo_get_asset(asset="<linked asset name or id>")For the device's own ticket history and CI dependencies, switch to halo-asset-context.
Find related runbooks in the knowledge base:
halo_list_kb_articles(search="<symptom / technology>") halo_get_kb_article(article=<id>) # read the full runbook bodyReport a resolution-context summary: the issue, timeline of actions to date, affected assets, applicable KB runbooks, and the recommended next step (resolve, escalate, or raise a change via halo-change-request).
Show full SKILL.md (334 more words)Show less
Integration with Other Skills
| Skill | Integration |
|---|---|
| gait-session-tracking | Mandatory. Record every ticket/action/KB query in the GAIT audit trail |
| halo-asset-context | Pivot from a linked asset to its full device context (tickets + CI relationships) |
| halo-change-request | If resolution requires a change, hand off here (preview -> confirm -> submit) |
| rag | Cross-reference vendor documentation in the RAG knowledge base alongside Halo KB runbooks |
| memory | Recall prior sessions about the same ticket, client, or recurring symptom |
Environment Variables
| Variable | Required | Description |
|---|---|---|
HALO_BASE_URL | Yes | Halo host, e.g. https://<tenant>.halopsa.com |
HALO_CLIENT_ID | Yes | OAuth2 client-credentials application id |
HALO_CLIENT_SECRET | Yes | OAuth2 client secret |
HALO_TENANT | Optional | Tenant identifier |
HALO_SCOPE | Optional | OAuth2 scope (default all) |
HALO_AUTH_URL | Optional | Override the auth-server URL for self-hosted layouts |
HALO_VERIFY_SSL | Optional | true/false TLS verification (default true) |
HALO_TIMEOUT | Optional | Per-request timeout in seconds (default 30) |
HALO_PAGE_SIZE / HALO_MAX_PAGES | Optional | Pagination tuning (defaults 50 / 20) |
HALO_RATE_LIMIT | Optional | Requests/minute cap (0 = disabled) |
Important Rules
- Read-only skill. None of these tools change Halo. The only write in the entire
halo-mcpserver ishalo_create_change_request(halo-change-request skill). - Tickets are addressed by numeric id only. Use
halo_list_ticketsto find the id when you don't have it; scope by the Halocustomer(Client) in multi-client tenants. - Halo == HaloPSA == HaloITSM — identical behavior for both editions.
- GAIT logging is mandatory for all queries.
- Escalate, don't mutate. If the context implies a change, route it through halo-change-request (preview -> confirm -> submit); never try to write from this skill.
Failure Behavior
- If a tool call fails with an authentication or connection error, check that
HALO_BASE_URL,HALO_CLIENT_ID,HALO_CLIENT_SECRETare 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.
- For a confirmed read-only call, check connectivity and retry once if appropriate. For any call that changes state or sends a message, a timeout does not prove the action failed: inspect current state or delivery status before retrying, preserve the required approval/change gates, and do not repeat an action whose outcome is unknown.
© 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/halo-ticket-context of automateyournetwork/netclaw.
Open the folder on GitHubat commit aa90e7d
Compare with similar skills
Halo Ticket Context 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 |
|---|---|---|---|---|---|---|
| Halo Ticket Context this skillautomateyournetwork/netclaw | 676 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| AWS Cdk Developmentzxkane/aws-skills | 367 | 2 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Prepare Cloudflare Production DeploymentLubomirGeorgiev/cloudflare-workers-nextjs-saas-template | 786 | — | ~5.9k | Automated safety check: Notes | MIT | |
| Unraiddinglebear-ai/unraid | 135 | — | ~5.4k | Automated safety check: Notes | MIT | |
| Unraiddinglebear-ai/unraid | 135 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Flow Contextflowexec/flow | 138 | — | ~654 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Prepare Cloudflare Production Deployment
LubomirGeorgiev/cloudflare-workers-nextjs-saas-template
Source-of-truth runbook for preparing this Vinext Cloudflare Workers SaaS template for production deployment.
Unraid
dinglebear-ai/unraid
This skill should be used when the user mentions Unraid, asks to check server health, monitor array or disk status, list or restart Docker containers, start or stop VMs, read system logs, check…
Unraid
dinglebear-ai/unraid
Query and monitor an Unraid NAS/homelab server — array health, disk temperatures, Docker containers, virtual machines, system metrics, notifications, alerts, shares, UPS status, log files, network…
Flow Context
flowexec/flow
This project uses flow for automation. An agent skill from flowexec/flow.
- Official
Dv Solution
microsoft/Dataverse-skills
Dataverse solution lifecycle — create, export, import, promote across environments, and validate deployments.
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 Halo Ticket Context
What does Halo Ticket Context do?
Review a HaloPSA / HaloITSM ticket for resolution context — its detail, action/note history, linked assets, and related KB runbooks — read-only. Halo Ticket Context is an agent skill from automateyournetwork/netclaw. Review a HaloPSA / HaloITSM ticket for resolution context — its detail, action/note history, linked assets, and related KB runbooks — read-only.
When should I use Halo Ticket Context?
Halo Ticket Context fits situations like: investigating a Halo ticket; gathering resolution context; reading a tickets note history; finding runbooks for an open issue.
How do I install Halo Ticket Context in Claude Code?
Run `npx skills add automateyournetwork/netclaw --skill halo-ticket-context -a claude-code`. Or copy the skill folder (workspace/skills/halo-ticket-context in automateyournetwork/netclaw) into .claude/skills/halo-ticket-context in your project. Claude Code loads it when a task matches its description.
How do I install Halo Ticket Context in Codex?
Run `npx skills add automateyournetwork/netclaw --skill halo-ticket-context -a codex`. Or copy the skill folder (workspace/skills/halo-ticket-context in automateyournetwork/netclaw) into .agents/skills/halo-ticket-context in your project. Codex loads it when a task matches its description.
Can I use Halo Ticket Context 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 halo-ticket-context -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/halo-ticket-context, .gemini/skills/halo-ticket-context, .github/skills/halo-ticket-context and .opencode/skills/halo-ticket-context in your project.
What does Halo Ticket Context need to run?
Going by SKILL.md and its folder, Halo Ticket Context needs the command-line tools its instructions call (python3) and credentials named HALO_CLIENT_SECRET. Our summary lists: Python 3; A credential in HALO_CLIENT_SECRET.
Does Halo Ticket Context access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Halo Ticket Context 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 Halo Ticket Context use?
Halo Ticket Context 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 Halo Ticket Context use?
About 1.8k tokens (SKILL.md is roughly 7.2k 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 Halo Ticket Context?
Skills that share tags, products or a category with Halo Ticket Context: AWS Cdk Development (zxkane/aws-skills, 367 stars), Prepare Cloudflare Production Deployment (LubomirGeorgiev/cloudflare-workers-nextjs-saas-template, 786 stars), Unraid (dinglebear-ai/unraid, 135 stars) and Unraid (dinglebear-ai/unraid, 135 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Halo Ticket Context?
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.