skill-audit

Lints SKILL.md files and scripts for credentials, broken references, and convention violations.

Updated May 28, 2026
One-click install
npx skills add https://github.com/cpanse/skills --skill skill-audit-cpanse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-audit
Source: https://github.com/cpanse/skills/tree/main/meta-skills/skills/skill-audit
Command: npx skills add https://github.com/cpanse/skills --skill skill-audit-cpanse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Maintaining a marketplace of agent skills manually leads to leaked credentials, broken reference links, personal paths, and version drift that reviewers catch inconsistently. This Skill runs a deterministic, LLM-free linter that mechanically detects these issues before they reach production. ## Core Features & Use Cases - Deterministic rule engine: Eleven regex- and structure-based rules across P0/P1/P2 severities covering plaintext credentials, broken references, unsafe gStore writes, personal paths, hardcoded Slurm nodelists, API inconsistencies, and version drift. - CI and pre-commit integration: JSON output mode, severity thresholds, and exit codes (0/1/2) designed for GitLab CI pipelines and git pre-commit hooks. - Flexible scoping: Audit the whole marketplace, a single plugin, a single skill, or run one rule in isolation. - Use Case: Before merging a new bioinformatics skill, run the audit with --threshold P1 to fail the pipeline if the contributor committed a MySQL password or a /home/<username>/ path. ## Quick Start Run the audit script on the marketplace to list all P0 and P1 findings before committing my skill changes.

Frequently Asked Questions about skill-audit

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

FAQPage Schema
How do I lint agent skills for leaked credentials before committing?

Run scripts/audit.py from the marketplace root; the no_plaintext_credentials rule detects mysql -p passwords, hardcoded password assignments, API keys, and Bearer tokens. Use --threshold P0 in a pre-commit hook to block commits containing secrets.

How to integrate a skill linter into GitLab CI?

Add a test stage job using a python:3.11-slim image that runs audit.py with --threshold P1 and allow_failure: false. The script exits with code 1 when findings meet the threshold, failing the pipeline on P0 and P1 issues.

Does the skill audit tool require external Python packages?

No, audit.py uses only the Python standard library with no external dependencies and no network access. It runs on any Python 3 installation, making it safe for CI environments and offline clusters.

What are the limitations of regex-based skill linting?

Regex rules cannot catch semantic issues like citation accuracy, scientific correctness, logic errors, or general API drift beyond hardcoded cases. Those require the companion multi-LLM review approach; the linter is the fast mechanical first pass.

Why does the linter report false positives on placeholder hostnames?

Rules filter common placeholder shapes like fgcz-r-NNN, <username>, and ${VAR} to keep false positives low. When a true false positive appears, the fix is refining the rule regex in audit.py rather than adding per-file ignores.