perses-lint

Validate Perses dashboards, datasources, and variables with percli lint.

415|44|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/notque/claude-code-toolkit --skill perses-lint
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: perses-lint
Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/perses-lint
Command: npx skills add https://github.com/notque/claude-code-toolkit --skill perses-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Perses configurations often suffer from structural issues that prevent dashboards from loading or plugins from validating. This skill runs lint checks across JSON/YAML resources and surfaces actionable fixes to bring resources into a clean, deployable state.

Core Features & Use Cases

  • Local structural validation with percli lint to catch syntax and schema errors before deployment.
  • Online validation against a Perses server to verify plugin schemas, datasource existence, and variable resolution.
  • Batch validation across directories to scale for large repos and CI pipelines.
  • Guidance for diagnosing and iterating on fixes with a repeatable lint-fix-revalidate loop.

Quick Start

Validate a resource file by running percli lint -f <file> to see issues and suggested fixes

Frequently Asked Questions about perses-lint

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

FAQPage Schema
How do I validate Perses dashboard configurations before deployment?▼

You can validate Perses dashboard configurations by running percli lint on JSON or YAML files to catch syntax and schema errors locally before deployment.

Can I verify datasource existence and variable resolution against a live Perses server?▼

Yes, online validation against a Perses server verifies plugin schemas, datasource existence, and variable resolution across your resource files.

What is the best way to lint multiple Perses resource files in CI pipelines?▼

Batch validation across directories scales for large repos and CI pipelines by running percli lint to surface structural issues across all files.

How does the fix-and-revalidate loop work for Perses lint errors?▼

The fix-and-revalidate loop surfaces all lint errors, provides actionable fixes for structural issues, and re-runs percli lint to confirm resources are deployable.

Do I need a Perses server connection to lint dashboard variables and datasources?▼

No, local structural validation with percli lint catches syntax and schema errors without a server, though online validation adds datasource existence checks.

Why does my Perses dashboard fail to load due to plugin schema errors?▼

Perses dashboards fail to load when plugin schema validation fails, which percli lint detects by checking structural correctness of dashboards, datasources, and variables.