← Back to Skills Marketplace
mengbin92

Skill Linter

by mengbin92 · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
117
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install skill-linter-checker
Description
Analyze and validate SKILL.md files for best practices, common issues, and improvement suggestions. Use when reviewing a Skill, creating a new Skill, or when...
Usage Guidance
This skill appears coherent and focused: it lints SKILL.md files, needs no credentials, and includes a straightforward Python script that reads the file you provide and prints a report. Before installing or granting file access, consider: 1) only run it against SKILL.md files (or review the script) because it will read any path you pass it; 2) if you don't want the skill to modify files, remove or avoid granting the 'Write'/'Edit' allowed-tools or ensure it runs in read-only mode; 3) if you need higher assurance, review the included skill_linter.py locally to confirm there are no network calls or surprising behavior and run it on a sample SKILL.md first.
Capability Assessment
Purpose & Capability
Name/description, the SKILL.md runtime instructions, and the provided Python linter are all aligned: they parse YAML frontmatter and check the markdown body for best practices. The skill requests no unrelated binaries, env vars, or config paths. Note: the included script accepts an arbitrary filepath argument and will read whatever file path it is given — functionally consistent with a linter but means the script can read any file you pass to it.
Instruction Scope
SKILL.md instructs the agent to load and analyze a SKILL.md file and produce a structured report — the linter code implements exactly that. The top frontmatter includes allowed-tools: Read, Edit, Write, which is reasonable if the skill will propose or apply edits, but it also expands the agent's ability to read/write files. The code itself does not access network endpoints or other system state beyond reading the supplied file path.
Install Mechanism
No install spec is present (instruction-only usage). A Python file is included but there is no automatic install/download or archive extraction. This is low risk: nothing is fetched from external URLs and no installers run.
Credentials
The skill requires no environment variables, credentials, or config paths. The absence of secrets or unrelated env requests is proportionate to a documentation/linting tool.
Persistence & Privilege
always:false and user-invocable:true (defaults) — no persistent/always-on privilege requested. The skill does not attempt to modify other skills or system-wide agent settings. The only potential privilege is file read/write if the agent is granted allowed-tools permissions.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install skill-linter-checker
  3. After installation, invoke the skill by name or use /skill-linter-checker
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Analyze and validate SKILL.md files for best practices
Metadata
Slug skill-linter-checker
Version 1.0.0
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 1
Frequently Asked Questions

What is Skill Linter?

Analyze and validate SKILL.md files for best practices, common issues, and improvement suggestions. Use when reviewing a Skill, creating a new Skill, or when... It is an AI Agent Skill for Claude Code / OpenClaw, with 117 downloads so far.

How do I install Skill Linter?

Run "/install skill-linter-checker" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Skill Linter free?

Yes, Skill Linter is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Skill Linter support?

Skill Linter is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Skill Linter?

It is built and maintained by mengbin92 (@mengbin92); the current version is v1.0.0.

💬 Comments