inspect-tool

Generate a read-only markdown inspection report for a single Pixie tool.

6|1|Updated May 17, 2026
One-click install
npx skills add https://github.com/AlexKapadia/Pixie --skill inspect-tool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inspect-tool
Source: https://github.com/AlexKapadia/Pixie/tree/main/.claude/skills/inspect-tool
Command: npx skills add https://github.com/AlexKapadia/Pixie --skill inspect-tool

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a read-only snapshot of a single Pixie tool, showing its current schema, inputs, outputs, dependencies, secrets, and validator status without modifying any state.

Core Features & Use Cases

  • Read tool.json and display a prettified JSON representation with key fields such as id, name, version, category, and inputs/outputs.
  • Read the Pixie database to surface latest validation and run status for the specified tool.
  • Render a markdown inspection report that users can share or reference when discussing a specific tool.

Quick Start

Ask to inspect a specific tool to generate its read-only inspection report.

Frequently Asked Questions about inspect-tool

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

FAQPage Schema
How do I inspect a Pixie tool's schema and validation status?

You can inspect a Pixie tool by requesting a read-only snapshot of the specific tool. The system reads disk data from tool.json and pixie.db to generate a markdown report displaying the tool's inputs, outputs, dependencies, secrets, and current validator status.

What details are included in a Pixie tool.json inspection report?

A Pixie tool inspection report includes a prettified JSON representation of key fields such as id, name, version, category, inputs, and outputs. It also surfaces the latest validation and run status from the Pixie database without modifying any state.

Can I check a Pixie tool's dependencies and secrets without running it?

Yes, you can check a Pixie tool's dependencies and secrets without running it by requesting a focused read-only inspection report. This process reads configuration data directly from disk and does not execute the validator, modify state, or install dependencies.

Does inspecting a Pixie tool execute its validator or modify its state?

No, inspecting a Pixie tool does not execute its validator or modify its state. The inspection process is strictly read-only, reading existing disk data from tool.json and pixie.db to surface the latest validation and run status without making any changes.

What is the best way to view a single Pixie tool's configuration without listing all tools?

The best way to view a single Pixie tool's configuration is to ask the inspector to generate a focused report for the named tool. This applies a read-only snapshot to the specific tool, presenting its schema, inputs, outputs, and dependencies without listing all available tools.