scanner-status

Diagnose scanner connectivity issues using activity, handshake, and data quality metrics.

Updated Oct 21, 2024
One-click install
npx skills add https://github.com/fulviomanente/IQRight_Local --skill scanner-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scanner-status
Source: https://github.com/fulviomanente/IQRight_Local/tree/main/.claude/skills/scanner-status
Command: npx skills add https://github.com/fulviomanente/IQRight_Local --skill scanner-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Check the connectivity and health of a specific scanner node. Shows last activity, handshake history, error rate, and data quality. Use when verifying a scanner is connected or diagnosing scanner issues.

Core Features & Use Cases

  • Last Activity: Identify the most recent data packets and HELLO handshakes from the scanner, with timestamps and TTL interpretation.
  • HELLO Handshake History: Track handshake events and compute healthy vs. data ratios to assess stability and restart frequency.
  • Data Quality & Error Analysis: Count total data packets, successful lookups, failed lookups, and responses to surface data integrity issues.
  • Report: Generate a concise status summary with recommended actions for connection or health issues.

Quick Start

Run the scanner-status command with a specific scanner-node-id to generate its health report.

Frequently Asked Questions about scanner-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check scanner connectivity and diagnose a disconnected scanner node?

To check scanner connectivity, synthesize the scanner's last activity timestamps, handshake history, and data quality metrics. This produces a health report diagnosing connection issues and verifying if the scanner node is active.

What does HELLO handshake history reveal about scanner health and stability?

HELLO handshake history reveals scanner stability by tracking handshake events and computing healthy versus data ratios. Frequent handshakes indicate restart frequency, helping you assess node stability and connectivity drops over time.

How do I monitor data quality and error rates for scanner nodes in the 100-199 range?

Monitor data quality by counting total data packets, successful lookups, failed lookups, and responses from log analysis. This applies to scanner nodes in the 100-199 range to surface data integrity issues and error rates.

Can I generate a status summary with recommended actions for troubleshooting scanner health issues?

Yes, you can generate a concise status summary that includes recommended actions for connection or health issues. It synthesizes last activity, TTL interpretation, and error logs to provide actionable troubleshooting diagnostics.

Why is my scanner node not receiving data or showing recent activity?

A scanner node may show no recent activity due to failed handshakes or high error rates. Analyze last activity timestamps, TTL interpretation, and error logs from data packets to identify the specific connectivity failure.