lint-tool

Lint a single Pixie tool for metadata, imports, secrets, and log hygiene.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Static linting of a single Pixie tool to enforce metadata, labeling, imports, secrets hygiene, and log practices, enabling quick quality reviews before deployment.

Core Features & Use Cases

  • Static checks for tool.json metadata, inputs/outputs, labels, and conformance.
  • Secret smells, import hygiene, and logging quality checks with a structured markdown report.
  • Read-only inspection flow that guides fixes without executing the tool or validator.

Quick Start

Run lint-tool on a target Pixie tool to generate a static lint report.

Frequently Asked Questions about lint-tool

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

FAQPage Schema
How do I run static analysis to check a Pixie tool for hardcoded secrets and metadata issues?

Static analysis for a Pixie tool is performed by running a read-only inspection that checks metadata, imports, hardcoded secrets, and log hygiene, generating a markdown report with recommended fixes.

Can I check Pixie tool conformance without executing the tool or its validator?

Yes, you can check Pixie tool conformance without execution by applying read-only static lint checks to tool.json metadata, inputs, outputs, and labels during code review or quick audits.

What does a Pixie tool lint report include for code review?

A Pixie tool lint report includes structured markdown findings on tool.json metadata, secret smells, import hygiene, and logging quality, providing recommended fixes to guide code review.

When do I need to run static lint checks on a single Pixie tool?

Static lint checks are needed before revalidation, during code review, or for quick audits of a single Pixie tool's conformance to ensure metadata, labeling, and security hygiene.

Does the Pixie linting process inspect logging quality and import hygiene?

Yes, the Pixie linting process inspects logging quality and import hygiene alongside metadata and hardcoded secrets, applying static checks to identify style and security concerns.

What is the best way to audit a single Pixie tool for security concerns before deployment?

The best way to audit a single Pixie tool for security is to run a read-only static lint check that identifies hardcoded secrets and metadata issues, outputting a markdown report with fixes.