Skip to content
SkillModel-led1,032 tokens in use

impl-validator

A critical reviewer subagent that checks whether files or output match their stated goal and returns PASS, WARN or FAIL for each check.

3,792 stars on the repository MIT LicenseAr9av/obsidian-wiki · skills/impl-validator
pip install obsidian-wiki
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing impl-validator costs

37tokens idle
1,032tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetectedwrites filesdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter8/15
  • Structure22/25
  • Examples15/15
  • Output15/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity100
  • Maintenance100
  • Community60
  • Maturity28
  • Momentum40

impl-validator gives an agent an independent second opinion on work that was just done. It receives a goal, a list of artifacts and a list of checks, reads each artifact, and rates every check as PASS, WARN or FAIL with a one-line note.

Another skill can spawn it as a subagent with a structured check block, or you can call it directly and describe what was just done. The report ends with an overall verdict and the specific issues to fix.

What You Get

  • A structured report with a table of checks and a result for each
  • An overall PASS, WARN or FAIL verdict
  • A list of specific issues to fix, with file paths and lines where they apply
  • Convention checks for skills, wiki pages, shell scripts and plist files

Common Use Cases

  • Verify that a generated skill file has the required frontmatter
  • Check a maintenance job’s state files after it runs
  • Catch placeholder text left in generated output
  • Get a second opinion on an implementation before showing it to a user

What Makes It Unique

It has a clear scope: it checks an implementation against its stated goal and leaves out style preferences, performance and the merits of the goal itself. Other skills in the same repository, such as daily-update and memory-bridge, call it as a subagent and apply its findings before reporting.

Under The Hood

The skill is instructions for the agent, with no scripts. In subagent mode it parses the check block it was given. It then reads the listed artifacts and returns a report as text. In user mode it asks one clarifying question if the goal is unclear and offers to fix issues after a FAIL. The skill text does not tell the agent to run commands, call web services or write files itself.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers