Agent skill

Pyats Health Check

by automateyournetwork in automateyournetwork/netclaw

Comprehensive cross-platform network device health monitoring - CPU, memory, interfaces, hardware, NTP, logging, environment, and uptime analysis.

Apache-2.0Auto-check passedBusiness, Finance & HR

Install Pyats Health Check

skills CLI

$ npx skills add automateyournetwork/netclaw --skill pyats-health-check -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install automateyournetwork/netclaw pyats-health-check --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/workspace/skills/pyats-health-check .claude/skills/pyats-health-check && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "pyats-health-check" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/pyats-health-check into .claude/skills/pyats-health-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pyats-health-check", 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

$skill-installer install https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/pyats-health-check

Type 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.

skills CLI

$ npx skills add automateyournetwork/netclaw --skill pyats-health-check -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install automateyournetwork/netclaw pyats-health-check --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/workspace/skills/pyats-health-check .agents/skills/pyats-health-check && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "pyats-health-check" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/pyats-health-check into .agents/skills/pyats-health-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pyats-health-check", 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.

skills CLI

$ npx skills add automateyournetwork/netclaw --skill pyats-health-check -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install automateyournetwork/netclaw pyats-health-check --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/workspace/skills/pyats-health-check .cursor/skills/pyats-health-check && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "pyats-health-check" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/pyats-health-check into .cursor/skills/pyats-health-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pyats-health-check", 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

$ gemini skills install https://github.com/automateyournetwork/netclaw.git --path workspace/skills/pyats-health-check

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add automateyournetwork/netclaw --skill pyats-health-check -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install automateyournetwork/netclaw pyats-health-check --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/workspace/skills/pyats-health-check .gemini/skills/pyats-health-check && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "pyats-health-check" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/pyats-health-check into .gemini/skills/pyats-health-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pyats-health-check", 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.

GitHub CLI

$ gh skill install automateyournetwork/netclaw pyats-health-check

Installs 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).

skills CLI

$ npx skills add automateyournetwork/netclaw --skill pyats-health-check -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/workspace/skills/pyats-health-check .github/skills/pyats-health-check && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "pyats-health-check" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/pyats-health-check into .github/skills/pyats-health-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pyats-health-check", 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.

skills CLI

$ npx skills add automateyournetwork/netclaw --skill pyats-health-check -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install automateyournetwork/netclaw pyats-health-check --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/workspace/skills/pyats-health-check .opencode/skills/pyats-health-check && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "pyats-health-check" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/pyats-health-check into .opencode/skills/pyats-health-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pyats-health-check", 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: pyats-health-check
GitHub stars: 676
Token cost: ~2.9k tokens
SKILL.md length: 823 words
Files: 1
Skills in repo: 120
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Comprehensive cross-platform network device health monitoring - CPU, memory, interfaces, hardware, NTP, logging, environment, and uptime analysis.

Works in 8 steps: Device Identity & Uptime → CPU Utilization → Memory Utilization → …
Running a device health check
SKILL.md covers When to Use, Health Check Procedure, Health Report Format and NetBox Cross-Reference…, plus 3 more sections
Calls python3

What it does

Pyats Health Check is an agent skill from automateyournetwork/netclaw. Comprehensive cross-platform network device health monitoring - CPU, memory, interfaces, hardware, NTP, logging, environment, and uptime analysis. Use when running a device health check, monitoring CPU or memory usage, checking interface errors, or validating NTP sync. For Juniper-specific deep system operations (firewall counters, DDoS protection, chassis alarms, services accounting), use pyats-junos-system instead.

Its SKILL.md is about 2.9k 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 Business, Finance & HR, covering Accounting and bookkeeping. The repository describes itself as: An AI agent that claws through your network. The licence is Apache-2.0.

When your agent uses it

Running a device health check
Checking interface errors
Validating NTP sync

Example prompts

“/pyats-health-check”

Requirements

Python 3

Workflow steps

8 steps, taken from the step headings in SKILL.md.

Device Identity & Uptime
CPU Utilization
Memory Utilization
Interface Status
Hardware & Environment
NTP Synchronization
System Logs
Connectivity Validation

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 no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Pyats Health Check loads about 2.9k tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 823 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~110
When it runs · the whole SKILL.md, loaded when a task matches: ~2.9k

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). 823 words, ~2,869 tokens.

Download SKILL.mdSave it as .claude/skills/pyats-health-check/SKILL.md (or your agent's skills folder).

name: pyats-health-check
description: Comprehensive cross-platform network device health monitoring - CPU, memory, interfaces, hardware, NTP, logging, environment, and uptime analysis. Use when running a device health check, monitoring CPU or memory usage, checking interface errors, or validating NTP sync. For Juniper-specific deep system operations (firewall counters, DDoS protection, chassis alarms, services accounting), use `pyats-junos-system` instead.
license: Apache-2.0
user-invocable: true

Device Health Check

When to Use

Proactive daily/weekly health monitoring
Pre-change and post-change validation
Incident response — first thing you run when alerted
Capacity planning and trending
Compliance checks for operational readiness

Health Check Procedure

Always run health checks in this exact order. Each section builds on the previous one.

Step 1: Device Identity & Uptime

Run show version to establish baseline identity.

bash

PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_run_show_command '{"device_name":"R1","command":"show version"}'

Extract and report:

Hostname, model, serial number
IOS-XE version and image filename
Uptime (flag if < 24 hours — indicates recent reload)
Last reload reason (flag if unexpected: crash, power failure)
Total/available memory
License status

Thresholds:

Uptime < 24h → WARNING: Recent reload
Uptime < 1h → CRITICAL: Very recent reload, check for crash
Last reload reason contains "crash" or "error" → CRITICAL

Step 2: CPU Utilization

bash

PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_run_show_command '{"device_name":"R1","command":"show processes cpu sorted"}'

Thresholds (5-second / 1-minute / 5-minute averages):

< 50% → HEALTHY
50-75% → WARNING: Elevated CPU
75-90% → HIGH: Investigate top processes
90% → CRITICAL: Immediate investigation required

Top processes to watch:

IP Input — high traffic volume or routing loops
BGP Router / BGP I/O — large BGP table or instability
OSPF-1 Hello — OSPF adjacency issues
Crypto IKMP / Crypto Engine — IPsec overhead
SNMP ENGINE — polling storm
ARP Input — ARP storm or L2 loop

Step 3: Memory Utilization

bash

PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_run_show_command '{"device_name":"R1","command":"show processes memory sorted"}'

Also run:

bash

PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_run_show_command '{"device_name":"R1","command":"show platform resources"}'

Thresholds:

Used < 70% → HEALTHY
70-85% → WARNING: Memory pressure
85-95% → HIGH: May impact routing table updates
95% → CRITICAL: Risk of process crashes or OOM

Memory consumers to watch:

BGP Router — large BGP table (full internet table = ~1M routes)
CEF process — large FIB
OSPF Router — large OSPF LSDB
HTTP CORE — web server / RESTCONF overhead
IOSD iomem — I/O memory for packet buffers

Step 4: Interface Status

bash

PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_run_show_command '{"device_name":"R1","command":"show ip interface brief"}'

Then for each active interface, get detailed counters:

bash

PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_run_show_command '{"device_name":"R1","command":"show interfaces"}'

Report for each interface:

Admin status (up/down) and protocol status (up/down)
IP address and subnet
Speed, duplex, MTU
Input/output rate (bps and pps)
Error counters: CRC, input errors, output errors, drops, overruns
Resets counter (flag if incrementing — indicates flapping)
Last input/output timestamps

Flags:

Interface up/down → WARNING: Check physical or protocol
CRC errors > 0 → WARNING: Physical layer issue (cabling, optics, duplex mismatch)
Input errors incrementing → WARNING: Packet corruption
Output drops > 0 → WARNING: Congestion or QoS issue
Resets incrementing → CRITICAL: Interface flapping
Line protocol down on configured interface → CRITICAL

Step 5: Hardware & Environment

bash

PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_run_show_command '{"device_name":"R1","command":"show inventory"}'

bash

PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_run_show_command '{"device_name":"R1","command":"show platform"}'

Report: Module status (ok/fail), serial numbers, PID, transceiver types and DOM readings.

Step 6: NTP Synchronization

bash

PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_run_show_command '{"device_name":"R1","command":"show ntp associations"}'

bash

PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_run_show_command '{"device_name":"R1","command":"show clock"}'

Flags:

No NTP peer synchronized (no * in associations) → CRITICAL for logging/forensics
Clock offset > 100ms → WARNING
Clock offset > 1s → CRITICAL
No NTP configured at all → CRITICAL

Step 7: System Logs

bash

PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_show_logging '{"device_name":"R1"}'

Scan for these patterns:

%SYS-*-RELOAD — reload events
%LINEPROTO-5-UPDOWN — interface flaps
%OSPF-*-ADJCHG — OSPF adjacency changes
%BGP-*-ADJCHANGE — BGP peer state changes
%DUAL-*-NBRCHANGE — EIGRP neighbor changes
%SYS-2-MALLOCFAIL — memory allocation failure (CRITICAL)
%SYS-3-CPUHOG — process monopolizing CPU (HIGH)
%TRACKING-* — IP SLA or object tracking changes
%SEC-* / %AUTHMGR-* — security events
%PLATFORM-*-CRASH — crash events (CRITICAL)
Traceback — software bug (CRITICAL — open TAC case)

Step 8: Connectivity Validation

Test reachability to critical infrastructure:

bash

PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_ping_from_network_device '{"device_name":"R1","command":"ping 8.8.8.8 repeat 5"}'

Thresholds:

100% success, RTT < 50ms → HEALTHY
100% success, RTT > 100ms → WARNING: High latency
80-99% success → WARNING: Packet loss
< 80% success → CRITICAL: Significant packet loss
0% success → CRITICAL: No reachability

Show full SKILL.md (332 more words)Show less

Health Report Format

Always produce a summary table:

Device: R1 (devnetsandboxiosxec8k.cisco.com)
Model: C8000V | IOS-XE: 17.x.x | Uptime: XXd XXh

┌──────────────────┬──────────┬─────────────────────────┐
│ Check            │ Status   │ Details                 │
├──────────────────┼──────────┼─────────────────────────┤
│ CPU (5min avg)   │ HEALTHY  │ 12%                     │
│ Memory           │ HEALTHY  │ 45% used (1.2G/2.6G)   │
│ Interfaces       │ WARNING  │ Gi2 down/down           │
│ Hardware         │ HEALTHY  │ All modules OK          │
│ NTP              │ HEALTHY  │ Synced, offset 2ms      │
│ Logs             │ WARNING  │ 3 OSPF adjacency flaps  │
│ Connectivity     │ HEALTHY  │ 100% to 8.8.8.8, 23ms  │
└──────────────────┴──────────┴─────────────────────────┘

Overall: WARNING — 2 items need attention

Severity order: CRITICAL > HIGH > WARNING > HEALTHY. Overall status = worst individual status.

NetBox Cross-Reference (MISSION02 Enhancement)

When NetBox is available ($NETBOX_MCP_SCRIPT is set), cross-reference device state against the source of truth after Steps 1 and 4:

Interface State Validation

Query NetBox for expected interface states:

bash

python3 $MCP_CALL "python3 -u $NETBOX_MCP_SCRIPT" netbox_get_objects '{"object_type":"dcim.interfaces","filters":{"device":"R1"},"brief":true}'

Compare NetBox intent vs device reality:

NetBox shows interface enabled but device shows down → CRITICAL: Unexpected outage
NetBox shows interface disabled but device shows up → WARNING: Undocumented activation
Interface exists on device but not in NetBox → WARNING: Undocumented interface
Interface in NetBox but not on device → WARNING: NetBox stale data

IP Address Validation

Query NetBox for expected IP assignments:

bash

python3 $MCP_CALL "python3 -u $NETBOX_MCP_SCRIPT" netbox_get_objects '{"object_type":"ipam.ip-addresses","filters":{"device":"R1"}}'

Compare: Flag any IP_DRIFT where the device IP differs from NetBox.

Fleet-Wide Health (pCall)

To run health checks across ALL devices simultaneously, first list all devices:

bash

PYATS_TESTBED_PATH=$PYATS_TESTBED_PATH python3 $MCP_CALL "${PYATS_PYTHON:-python3} -u $PYATS_MCP_SCRIPT" pyats_list_devices

Then run Steps 1-8 on each device concurrently using multiple exec commands. Collect all results and produce a fleet summary:

┌──────────┬──────────┬──────┬────────┬──────────┬─────────────┐
│ Device   │ CPU      │ Mem  │ Intf   │ NTP      │ Overall     │
├──────────┼──────────┼──────┼────────┼──────────┼─────────────┤
│ R1       │ HEALTHY  │ WARN │ HEALTHY│ HEALTHY  │ WARNING     │
│ R2       │ HEALTHY  │ OK   │ CRIT   │ HEALTHY  │ CRITICAL    │
│ SW1      │ HIGH     │ OK   │ HEALTHY│ CRIT     │ CRITICAL    │
└──────────┴──────────┴──────┴────────┴──────────┴─────────────┘

Sort devices by severity (CRITICAL first) for triage prioritization.

GAIT Audit Trail

After completing a health check, record the session in GAIT:

bash

python3 $MCP_CALL "python3 -u $GAIT_MCP_SCRIPT" gait_record_turn '{"user_text":"Example only: replace with the actual authorized request.","assistant_text":"Health check completed on R1: CPU HEALTHY (12%), Memory WARNING (78%), Interfaces HEALTHY, NTP HEALTHY. Overall: WARNING.","artifacts":[]}'

Failure Behavior

If a tool call fails with an authentication or connection error, check that GAIT_MCP_SCRIPT, NETBOX_MCP_SCRIPT, PYATS_MCP_SCRIPT, PYATS_TESTBED_PATH are 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.

Audit examples are illustrative. Replace request, outcomes, identifiers and counts with observed session evidence; do not record these example results as facts. Inspect MCP isError, returned ok, and the recorded turn with gait_show when validating a new client/schema. Follow gait-session-tracking for branch checkout.

Files

Just SKILL.md in workspace/skills/pyats-health-check of automateyournetwork/netclaw.

Open the folder on GitHubat commit aa90e7d

Compare with similar skills

Pyats Health Check 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.

Pyats Health Check compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Pyats Health Check this skillautomateyournetwork/netclaw	676	—	~2.9k	Automated safety check: Pass	Apache-2.0	yesterday
Sync Upstreamnyaruka/phonenumbers	1.6k	—	~2.8k	Automated safety check: Pass	MIT	9 days ago
Radiology Tablehuang-sir1/radiology-skills	1.9k	—	~1.3k	Automated safety check: Pass	Custom licence	20 days ago
ERPClaw ERP Controlleravansaber/erpclaw	116	—	~18k	Automated safety check: Pass	GPL-3.0	2 days ago
Odoo Agency Fleet Reviewerpipe-org/mcp-odoo	421	—	~699	Automated safety check: Pass	MIT	1 mo ago
Beancount Closebex-co/beancount-io	297	—	~1.4k	Automated safety check: Pass	MIT	today

Similar skills

Sync Upstream
nyaruka/phonenumbers
Sync this Go port with a new upstream google/libphonenumber release — regenerate the embedded metadata and reconcile the ported Java logic.
1.6k GitHub stars~2.8k tokensUpdated 9 days ago
Business, Finance & HRAuto-check passed
Radiology Table
huang-sir1/radiology-skills
Create/audit editable publication tables with source reconciliation; not figures or statistical inference.
1.9k GitHub stars~1.3k tokensUpdated 20 days ago
Business, Finance & HRAuto-check passed
ERPClaw ERP Controller
avansaber/erpclaw
Operates the ERPClaw self-hosted ERP in plain language: accounting, invoicing, inventory, purchasing, tax, HR, payroll and reports, treating the ERP as the single source of truth.
116 GitHub stars~18k tokensUpdated 2 days ago
Business, Finance & HRAuto-check passed
Odoo Agency Fleet Review
erpipe-org/mcp-odoo
Review many client Odoo databases at once through odoo-mcp's cross-instance tools — fleet-wide accounting health, per-client aging, partial-failure triage — for agencies and partners managing 5–50…
421 GitHub stars~699 tokensUpdated 1 mo ago
Business, Finance & HRAuto-check passed
Beancount Close
bex-co/beancount-io
Close an accounting period in a Beancount ledger by reconciling each active account through beancount-reconcile, checking assertions and recurring gaps, reviewing flags, then proposing a commit with…
297 GitHub stars~1.4k tokensUpdated today
Business, Finance & HRAuto-check passed
Forward Implementation First
Vuk97/forward-implementation-first
Keeps an agent building and validating real output instead of servicing its own bookkeeping.
176 GitHub stars~1.8k tokensUpdated 1 mo ago
Business, Finance & HRAuto-check passed

Questions about Pyats Health Check

What does Pyats Health Check do?

Comprehensive cross-platform network device health monitoring - CPU, memory, interfaces, hardware, NTP, logging, environment, and uptime analysis. Pyats Health Check is an agent skill from automateyournetwork/netclaw. Comprehensive cross-platform network device health monitoring - CPU, memory, interfaces, hardware, NTP, logging, environment, and uptime analysis.

When should I use Pyats Health Check?

Pyats Health Check fits situations like: running a device health check; checking interface errors; validating NTP sync.

How do I install Pyats Health Check in Claude Code?

Run `npx skills add automateyournetwork/netclaw --skill pyats-health-check -a claude-code`. Or copy the skill folder (workspace/skills/pyats-health-check in automateyournetwork/netclaw) into .claude/skills/pyats-health-check in your project. Claude Code loads it when a task matches its description.

How do I install Pyats Health Check in Codex?

Run `npx skills add automateyournetwork/netclaw --skill pyats-health-check -a codex`. Or copy the skill folder (workspace/skills/pyats-health-check in automateyournetwork/netclaw) into .agents/skills/pyats-health-check in your project. Codex loads it when a task matches its description.

Can I use Pyats Health Check 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 pyats-health-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pyats-health-check, .gemini/skills/pyats-health-check, .github/skills/pyats-health-check and .opencode/skills/pyats-health-check in your project.

What does Pyats Health Check need to run?

Going by SKILL.md and its folder, Pyats Health Check needs the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Pyats Health Check 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 Pyats Health Check 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 Pyats Health Check use?

Pyats Health Check 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 Pyats Health Check use?

About 2.9k tokens (SKILL.md is roughly 11k 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 Pyats Health Check?

Skills that share tags, products or a category with Pyats Health Check: Sync Upstream (nyaruka/phonenumbers, 1.6k stars), Radiology Table (huang-sir1/radiology-skills, 1.9k stars), ERPClaw ERP Controller (avansaber/erpclaw, 116 stars) and Odoo Agency Fleet Review (erpipe-org/mcp-odoo, 421 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pyats Health Check?

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.

Install Pyats Health Check

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Device Health Check

When to Use

Health Check Procedure

Step 1: Device Identity & Uptime

Step 2: CPU Utilization

Step 3: Memory Utilization

Step 4: Interface Status

Step 5: Hardware & Environment

Step 6: NTP Synchronization

Step 7: System Logs

Step 8: Connectivity Validation

Health Report Format

NetBox Cross-Reference (MISSION02 Enhancement)

Interface State Validation

IP Address Validation

Fleet-Wide Health (pCall)

GAIT Audit Trail

Failure Behavior

Files

Compare with similar skills

Similar skills

More from automateyournetwork/netclaw

Related

Questions about Pyats Health Check