Create a New Sensors Parser

Implement custom output parsers for sensors-cli command-line tools.

15|1|Updated May 21, 2026
One-click install
npx skills add https://github.com/birgitta410/sensors-cli --skill create-a-new-sensors-parser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Create a New Sensors Parser
Source: https://github.com/birgitta410/sensors-cli/tree/main/.claude/skills/_new-parser
Command: npx skills add https://github.com/birgitta410/sensors-cli --skill create-a-new-sensors-parser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a standardized workflow for adding support for new tool outputs to the sensors-cli system, ensuring that custom command-line tools can be monitored and parsed effectively.

Core Features & Use Cases

  • Plugin Architecture: Guides the implementation of custom parsers that transform raw tool output into structured SensorReading objects.
  • Standardized Testing: Provides a clear path for writing unit tests to ensure parser reliability across success, failure, and edge-case scenarios.
  • Use Case: If you need to monitor a specific internal tool or a niche CLI utility that isn't natively supported, this skill walks you through creating a parser that extracts metrics and findings from that tool's output.

Quick Start

Use the Create a New Sensors Parser skill to guide you through implementing and registering a new parser for your specific tool output.

Frequently Asked Questions about Create a New Sensors Parser

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

FAQPage Schema
How do I add a custom parser for command-line tool output to a monitoring system?

To add a custom parser for command-line tool output, you implement a parser that transforms raw tool output into structured SensorReading objects and register it within the sensors-cli codebase. This process follows an established plugin contract.

What is a sensors parser and when do I need to create one?

A sensors parser is a plugin that transforms raw diagnostic tool output into structured SensorReading objects. You need to create one when you want to monitor a specific internal or niche CLI utility that lacks native support in the sensors-cli framework.

How do I test a custom CLI output parser for edge cases and failures?

To test a custom CLI output parser for edge cases and failures, you write unit tests that verify parser reliability across success, failure, and edge-case scenarios. This standardized testing ensures the parser correctly transforms output into SensorReading objects.

Can I integrate an arbitrary diagnostic tool into the sensors-cli monitoring framework?

Yes, you can integrate an arbitrary diagnostic tool into the sensors-cli monitoring framework by creating a custom output parser. This parser extracts metrics and findings from the tool's output, provided you adhere to the established Parser contract and registration process.

Does adding a new parser require any specific dependencies or environment setup?

Adding a new parser requires no external dependencies, but demands adherence to the established Parser contract within the sensors-cli codebase. You must implement the plugin to output structured SensorReading objects and complete the registration process.