New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

F5 Health Check

by automateyournetwork in automateyournetwork/netclaw

F5 BIG-IP health monitoring - virtual server status, pool member health, log analysis, performance statistics, and systematic health assessment.

Apache-2.0Auto-check passedDevOps & Cloud

Install F5 Health Check

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

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

GitHub CLI
$ gh skill install automateyournetwork/netclaw f5-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/f5-health-check .claude/skills/f5-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/

Facts

Skill name
f5-health-check
GitHub stars
676
Token cost
~3.7k tokens
SKILL.md length
1,274 words
Files
1
Skills in repo
120
Repo updated
First seen
Licence
Apache-2.0

At a glance

F5 BIG-IP health monitoring - virtual server status, pool member health, log analysis, performance statistics, and systematic health assessment.

  • Works in 8 steps: Virtual Server Inventory and Status → Virtual Server Statistics (Per VIP) → Pool Inventory and Member Health → …
  • Routine/periodic checks: checking F5 load balancer health
  • SKILL.md covers When to Use, How to Call the Tools, Health Check Procedure and Health Report Format, plus 4 more sections
  • Calls python3

What it does

F5 Health Check is an agent skill from automateyournetwork/netclaw. F5 BIG-IP health monitoring - virtual server status, pool member health, log analysis, performance statistics, and systematic health assessment. Use for routine/periodic checks: checking F5 load balancer health, running a pre-change or post-change validation, a first pass on pool member failures, or auditing SSL certificate expiration. For root-cause diagnosis of an active incident (VIP down, SSL errors, iRule TCL errors), use f5-troubleshoot instead. For LTM/GTM configuration detail this skill doesn't cover —…

Its SKILL.md is about 3.7k 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 Cloud networking, Statistics and Go-to-market strategy. The repository describes itself as: An AI agent that claws through your network. The licence is Apache-2.0.

When your agent uses it

  • Routine/periodic checks: checking F5 load balancer health
  • Running a pre-change
  • Post-change validation
  • A first pass on pool member failures

Example prompts

  • “/f5-health-check”

Requirements

  • Python 3

Workflow steps

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

  1. Virtual Server Inventory and Status
  2. Virtual Server Statistics (Per VIP)
  3. Pool Inventory and Member Health
  4. Pool Statistics (Per Pool)
  5. Profile Inventory
  6. iRule Inventory
  7. System Logs Analysis
  8. Extended Log Analysis (If Issues Detected)

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

F5 Health Check loads about 3.7k tokens when it runs. Until then it costs about 154 tokens; SKILL.md has 1,274 words of instructions outside code blocks.

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

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). 1,274 words, ~3,717 tokens.

Download SKILL.mdSave it as .claude/skills/f5-health-check/SKILL.md (or your agent's skills folder).
name
f5-health-check
description
F5 BIG-IP health monitoring - virtual server status, pool member health, log analysis, performance statistics, and systematic health assessment. Use for routine/periodic checks: checking F5 load balancer health, running a pre-change or post-change validation, a first pass on pool member failures, or auditing SSL certificate expiration. For root-cause diagnosis of an active incident (VIP down, SSL errors, iRule TCL errors), use `f5-troubleshoot` instead. For LTM/GTM configuration detail this skill doesn't cover — iRules, persistence profiles, GTM wide IPs/DNS, data groups — use `pyats-f5-ltm`.
license
Apache-2.0
user-invocable
true

F5 BIG-IP Health Check

When to Use

  • Proactive daily/weekly BIG-IP health monitoring
  • Pre-change and post-change validation for load balancer changes
  • Incident response -- first thing to run when application delivery is impacted
  • Capacity planning for virtual server and pool utilization
  • Compliance checks for operational readiness of ADC infrastructure

How to Call the Tools

The F5 MCP server provides 6 tools. Call them via mcp-call with the required environment variables:

bash
IP_ADDRESS=$F5_IP_ADDRESS Authorization_string=$F5_AUTH_STRING python3 $MCP_CALL "python3 -u $F5_MCP_SCRIPT" <tool_name> '{"param":"value"}'
Available Tools
ToolPurposeKey Arguments
list_toolList F5 objects by typeobject_name, object_type (virtual/pool/irule/profile)
show_stats_toolShow statistics for an F5 objectobject_name, object_type (virtual/pool/irule/profile)
show_logs_toolShow N lines of system logslines_number
create_toolCreate an F5 object via POSTurl_body, object_type
update_toolUpdate an F5 object via PATCHurl_body, object_type, object_name
delete_toolDelete an F5 objectobject_type, object_name

Health Check Procedure

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

Step 1: Virtual Server Inventory and Status

List all virtual servers to establish the baseline inventory.

bash
IP_ADDRESS=$F5_IP_ADDRESS Authorization_string=$F5_AUTH_STRING python3 $MCP_CALL "python3 -u $F5_MCP_SCRIPT" list_tool '{"object_name":"","object_type":"virtual"}'

Extract and report:

  • Virtual server names and destination addresses (VIP:port)
  • Enabled/disabled state
  • Availability status (available, offline, unknown)
  • Associated pool name
  • IP protocol (TCP, UDP, any)
  • Source address translation type (automap, SNAT pool, none)
  • Assigned profiles (HTTP, SSL, TCP, persistence)

Flags:

  • Virtual server status offline -> CRITICAL: VIP not serving traffic
  • Virtual server status unknown -> WARNING: Cannot determine health
  • Virtual server disabled -> INFO: Intentionally taken out of service (verify with change records)
  • No pool assigned -> WARNING: Virtual server has no backend pool
Step 2: Virtual Server Statistics (Per VIP)

For each virtual server discovered in Step 1, collect detailed statistics:

bash
IP_ADDRESS=$F5_IP_ADDRESS Authorization_string=$F5_AUTH_STRING python3 $MCP_CALL "python3 -u $F5_MCP_SCRIPT" show_stats_tool '{"object_name":"my_virtual_server","object_type":"virtual"}'

Key metrics to evaluate:

MetricHEALTHYWARNINGCRITICAL
Status availabilityavailableunknownoffline
Current connections< 80% of connection limit80-95% of limit> 95% of limit or at limit
Packets in/outNon-zero, balanced ratioHighly asymmetric (>100:1)Zero in either direction
Bits in/outNon-zeroSudden drop >50% from baselineZero (no traffic flowing)
Total requests (HTTP VIPs)IncrementingFlat (stalled)Decreasing or zero
Client-side connection rateSteady or growingSpike >200% baselineZero

Thresholds:

  • Current connections at 0 on a production VIP -> CRITICAL: No clients connecting
  • Bits in = 0, bits out > 0 -> WARNING: VIP responding but no client data (possible health monitor traffic only)
  • Connection limit reached -> CRITICAL: New clients being rejected (connection queue filling)
  • 5xx response count incrementing -> WARNING: Backend servers returning errors
Step 3: Pool Inventory and Member Health

List all pools and their members:

bash
IP_ADDRESS=$F5_IP_ADDRESS Authorization_string=$F5_AUTH_STRING python3 $MCP_CALL "python3 -u $F5_MCP_SCRIPT" list_tool '{"object_name":"","object_type":"pool"}'

Extract and report for each pool:

  • Pool name and load balancing method (round-robin, least-connections, ratio, etc.)
  • Monitor assignment (HTTP, HTTPS, TCP, ICMP, custom)
  • Total members vs active members
  • Each member: address:port, state (enabled/disabled), availability (available/offline/unknown)
  • Minimum active members setting
  • Action on service down (none, reject, drop, reselect)

Flags:

  • All members offline -> CRITICAL: Pool is down, no healthy backends
  • Members < minimum active threshold -> CRITICAL: Below minimum, failover action triggered
  • Any single member offline -> WARNING: Reduced capacity

  • 50% members offline -> HIGH: Significant capacity degradation

  • Member disabled but not offline -> INFO: Intentionally drained (verify with change records)
  • No monitor assigned -> WARNING: Pool health is not being checked
Step 4: Pool Statistics (Per Pool)

For each pool, collect statistics to assess utilization:

bash
IP_ADDRESS=$F5_IP_ADDRESS Authorization_string=$F5_AUTH_STRING python3 $MCP_CALL "python3 -u $F5_MCP_SCRIPT" show_stats_tool '{"object_name":"my_pool","object_type":"pool"}'

Key metrics to evaluate:

MetricHEALTHYWARNINGCRITICAL
Active member countAll members active< 75% active< 50% active or zero
Current connections per memberEvenly distributedSkewed >3:1 ratioSingle member handling all traffic
Server-side connectionsIncrementingFlatZero
Total requests servedIncrementingFlatDecreasing
Bytes in/outBalancedAsymmetricZero

Connection distribution analysis:

  • Even distribution across members -> HEALTHY: Load balancing working correctly
  • Uneven distribution with round-robin -> WARNING: Possible persistence override or health issue
  • Single member with all connections -> CRITICAL: All other members likely down
  • Zero connections on a member -> WARNING: Member may be failing health checks intermittently
Step 5: Profile Inventory

List all profiles to document the configuration posture:

bash
IP_ADDRESS=$F5_IP_ADDRESS Authorization_string=$F5_AUTH_STRING python3 $MCP_CALL "python3 -u $F5_MCP_SCRIPT" list_tool '{"object_name":"","object_type":"profile"}'

Check for:

  • SSL/TLS profiles: certificate expiration dates, cipher suite strength, TLS version minimums
  • HTTP profiles: X-Forwarded-For insertion, response compression, request/response size limits
  • TCP profiles: idle timeout values, Nagle algorithm setting, keep-alive intervals
  • Persistence profiles: type (cookie, source-addr, SSL), timeout values
  • OneConnect profiles: connection pooling settings

Flags:

  • SSL cert expiring within 30 days -> WARNING: Plan renewal
  • SSL cert expiring within 7 days -> CRITICAL: Immediate renewal required
  • SSL cert expired -> CRITICAL: Service will fail for HTTPS clients
  • TLS 1.0 or 1.1 enabled -> WARNING: Deprecated protocols, security risk
  • Weak cipher suites (RC4, DES, 3DES, export ciphers) -> WARNING: Security vulnerability
Step 6: iRule Inventory

List all iRules to document traffic manipulation logic:

bash
IP_ADDRESS=$F5_IP_ADDRESS Authorization_string=$F5_AUTH_STRING python3 $MCP_CALL "python3 -u $F5_MCP_SCRIPT" list_tool '{"object_name":"","object_type":"irule"}'

Check for:

  • iRules assigned to virtual servers vs orphaned iRules
  • iRule event types in use (HTTP_REQUEST, HTTP_RESPONSE, CLIENT_ACCEPTED, etc.)
  • Deprecated Tcl commands or known-problematic patterns
  • iRules performing logging (potential performance impact at scale)

Flags:

  • iRule with log statements in high-traffic path -> WARNING: Performance impact
  • iRule using HTTP::collect without HTTP::release -> CRITICAL: Memory leak risk
  • Orphaned iRule (not assigned to any virtual server) -> INFO: Cleanup candidate
  • iRule with catch blocks -> INFO: Error handling present (good practice)
Show full SKILL.md (470 more words)Show less
Step 7: System Logs Analysis

Pull recent system logs to detect errors and anomalies:

bash
IP_ADDRESS=$F5_IP_ADDRESS Authorization_string=$F5_AUTH_STRING python3 $MCP_CALL "python3 -u $F5_MCP_SCRIPT" show_logs_tool '{"lines_number":"200"}'

Scan for these critical patterns:

PatternSeverityMeaning
01010028CRITICALNo members available for pool
01010029CRITICALPool member monitor status down
0107142fCRITICALSSL handshake failure
01070417CRITICALHTTP parse error
01060102HIGHConnection rate limit reached
01010025HIGHVirtual server connection limit reached
01071681WARNINGPool member has been marked down
01071682INFOPool member has been marked up
01010240WARNINGConnection queue full
0107143cWARNINGSSL certificate verification failure
01070727WARNINGPool member rate limit reached
MCP errorHIGHManagement plane communication issue
disk_usageWARNINGDisk space issue on BIG-IP
memoryHIGHMemory pressure on BIG-IP
ha_statusCRITICALHigh availability state change
failoverCRITICALHA failover event detected

Log analysis guidelines:

  • Group errors by type and count occurrences
  • Note timestamps of first and last occurrence
  • Identify trending errors (increasing frequency)
  • Correlate pool member down events with specific health monitors
  • Identify SSL errors that indicate certificate or cipher issues
Step 8: Extended Log Analysis (If Issues Detected)

If Step 7 reveals errors, pull more log lines for deeper analysis:

bash
IP_ADDRESS=$F5_IP_ADDRESS Authorization_string=$F5_AUTH_STRING python3 $MCP_CALL "python3 -u $F5_MCP_SCRIPT" show_logs_tool '{"lines_number":"1000"}'

Advanced log analysis:

  • Correlate timestamps: Did pool member down events coincide with traffic spikes?
  • Check for flapping: Is a member repeatedly going up/down? (indicates marginal health)
  • Identify blast radius: Which virtual servers were affected by pool member failures?
  • Check HA events: Any failover or sync-related messages?

Health Report Format

Always produce a summary table after completing all steps:

F5 BIG-IP Health Report
Device: $F5_IP_ADDRESS
Date: YYYY-MM-DD HH:MM UTC

+---------------------------+----------+------------------------------------------+
| Check                     | Status   | Details                                  |
+---------------------------+----------+------------------------------------------+
| Virtual Servers           | HEALTHY  | 5/5 available, all serving traffic       |
| Pool Health               | WARNING  | pool_web: 3/4 members active (node3 dn) |
| Connection Utilization    | HEALTHY  | Peak VIP at 45% connection limit         |
| Traffic Distribution      | HEALTHY  | Even distribution across pool members    |
| SSL/TLS Profiles          | WARNING  | www_ssl cert expires in 21 days          |
| iRules                    | HEALTHY  | 3 active, no problematic patterns        |
| System Logs               | HIGH     | 47x 01010029 (monitor down) in last hour |
+---------------------------+----------+------------------------------------------+

Overall: WARNING -- 2 items need attention

Action Items:
1. [WARNING] Investigate pool_web node3 health check failures
2. [WARNING] Renew SSL certificate for www_ssl profile (expires in 21 days)
3. [HIGH] Investigate spike in pool member monitor-down log messages

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

Fleet Health Check (Multiple BIG-IP Devices)

When monitoring multiple F5 appliances, run the full procedure on each device and produce a fleet summary:

+------------------+----------+----------+--------+--------+-----------+
| BIG-IP           | Virtuals | Pools    | SSL    | Logs   | Overall   |
+------------------+----------+----------+--------+--------+-----------+
| bigip-prod-01    | HEALTHY  | WARNING  | HEALTHY| HEALTHY| WARNING   |
| bigip-prod-02    | HEALTHY  | HEALTHY  | WARN   | HIGH   | HIGH      |
| bigip-dr-01      | HEALTHY  | HEALTHY  | HEALTHY| HEALTHY| HEALTHY   |
+------------------+----------+----------+--------+--------+-----------+

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

Integration with Other Skills

  • Use f5-config-mgmt to remediate issues found during health checks (e.g., update pool members, modify monitors)
  • Use f5-troubleshoot for deep-dive investigation when health check reveals CRITICAL or HIGH findings
  • Use drawio-diagram to visualize the BIG-IP topology (virtual servers -> pools -> members)
  • Use markmap-viz to create hierarchical health status mind maps
  • Use servicenow-change-workflow to create incidents for CRITICAL findings requiring remediation

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 '{"artifacts":["f5-health-report.txt"],"user_text":"F5 BIG-IP health check on $F5_IP_ADDRESS","assistant_text":"Health check completed. Virtual servers: 5/5 HEALTHY. Pools: WARNING (pool_web 3/4 members). SSL: WARNING (cert expires 21 days). Logs: HIGH (47x monitor-down events). Overall: WARNING. Action items: investigate pool_web node3, renew SSL cert, investigate log spike."}'

Failure Behavior

  • If a tool call fails with an authentication or connection error, check that F5_MCP_SCRIPT, GAIT_MCP_SCRIPT, MCP_CALL 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.
  • Do not automatically retry a write/mutating operation after a failure — surface the error and get explicit confirmation before retrying, since a blind retry on a partially-applied change can leave state inconsistent.

Audit examples are illustrative. Replace their request and outcomes with observed session evidence; inspect MCP isError, returned ok and recorded GAIT text.

© 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/f5-health-check of automateyournetwork/netclaw.

Open the folder on GitHubat commit aa90e7d

Compare with similar skills

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

F5 Health Check compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
F5 Health Check this skillautomateyournetwork/netclaw676—~3.7kAutomated safety check: PassApache-2.0
Log Error Digestzebbern/claude-code-guide4.7k—~923Automated safety check: PassMIT
Prod Log AuditJulian-adv/OpenMMO1.8k—~1.3kAutomated safety check: PassCustom licence
Review PRapache/shardingsphere21k—~6.5kAutomated safety check: PassApache-2.0
Kubeshark KFL2 Filter Referencekubeshark/kubeshark12k—~3.6kAutomated safety check: PassApache-2.0
Nginx To Higress Migrationhigress-group/higress9.5k—~3.9kAutomated safety check: PassApache-2.0

Similar skills

  • Log Error Digest

    zebbern/claude-code-guide

    Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports.

    4.7k GitHub stars~923 tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Prod Log Audit

    Julian-adv/OpenMMO

    Investigate OpenMMO production warnings, errors, suspicious behavior, and unresolved incidents within a deployment interval; correlate journald, nginx, and targeted evidence, then write a dated note…

    1.8k GitHub stars~1.3k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Review PR

    apache/shardingsphere

    Review Apache ShardingSphere or user-authorized downstream pull requests and PR discussions from public or authorized repository evidence.

    21k GitHub stars~6.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Kubeshark KFL2 Filter Reference

    kubeshark/kubeshark

    Syntax reference for KFL2, the CEL-based display filter language used to search Kubernetes network traffic captured by Kubeshark, loaded before any filter is written.

    12k GitHub stars~3.6k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Nginx To Higress Migration

    higress-group/higress

    Migrate from ingress-nginx to Higress in Kubernetes environments.

    9.5k GitHub stars~3.9k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed

  • CI Failure Triage and Repair

    Chachamaru127/claude-code-harness

    Diagnoses failing CI pipelines and tests, deciding first whether the test or the implementation is at fault, and hands hard cases to a dedicated fixer subagent.

    3.2k GitHub starsUsed in 1 repo~1.1k tokens
    DevOps & CloudAuto-check: notes

More from automateyournetwork/netclaw

All 120 skills in this repo

  • EVE-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.

    677 GitHub stars~612 tokensUpdated today
    Auto-check passed

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

    677 GitHub stars~4.2k tokensUpdated today
    Auto-check passed

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

    677 GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Anta Validation

    automateyournetwork/netclaw

    Validate Arista EOS network state against ANTA's pre-built 208-test catalogue, with structured pass/fail verdicts.

    677 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Arista Cvp

    automateyournetwork/netclaw

    Arista CloudVision Portal (CVP) automation via REST API — device inventory, events, connectivity monitoring, tag management (4 tools).

    677 GitHub stars~2.2k tokensUpdated today
    Auto-check: notes

  • AWS Cloud Monitoring

    automateyournetwork/netclaw

    AWS CloudWatch monitoring — metrics, alarms, log queries, VPC flow log analysis, network performance.

    677 GitHub stars~1k tokensUpdated today
    Auto-check passed

Categories

Questions about F5 Health Check

What does F5 Health Check do?

F5 BIG-IP health monitoring - virtual server status, pool member health, log analysis, performance statistics, and systematic health assessment. F5 Health Check is an agent skill from automateyournetwork/netclaw. F5 BIG-IP health monitoring - virtual server status, pool member health, log analysis, performance statistics, and systematic health assessment.

When should I use F5 Health Check?

F5 Health Check fits situations like: routine/periodic checks: checking F5 load balancer health; running a pre-change; post-change validation; A first pass on pool member failures.

How do I install F5 Health Check in Claude Code?

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

How do I install F5 Health Check in Codex?

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

Can I use F5 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 f5-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/f5-health-check, .gemini/skills/f5-health-check, .github/skills/f5-health-check and .opencode/skills/f5-health-check in your project.

What does F5 Health Check need to run?

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

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

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

About 3.7k tokens (SKILL.md is roughly 15k 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 F5 Health Check?

Skills that share tags, products or a category with F5 Health Check: Log Error Digest (zebbern/claude-code-guide, 4.7k stars), Prod Log Audit (Julian-adv/OpenMMO, 1.8k stars), Review PR (apache/shardingsphere, 21k stars) and Kubeshark KFL2 Filter Reference (kubeshark/kubeshark, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains F5 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.