library-investigator

Name: library-investigator
Availability: InStock
Author: LazyIsEfficient

Probe Claude library files against RULESET.md and report violation counts.

15|3|Updated Apr 9, 2026

Search Tags:#automation #verification #compliance #evidence #library-audit #rule-set

Ready to run

npx skills add https://github.com/LazyIsEfficient/agentic-os --skill library-investigator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: library-investigator
Source: https://github.com/LazyIsEfficient/agentic-os/tree/main/.claude/skills/library-investigator
Command: npx skills add https://github.com/LazyIsEfficient/agentic-os --skill library-investigator

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Forensic auditing of Claude Code libraries against RULESET.md to produce objective counts and evidence without applying quality judgments.

Core Features & Use Cases

Enumerates and probes files across .claude/skills//SKILL.md, .claude/agents/.md, .claude/commands/.md, and .claude/workflows/.js using mechanically-checkable rules.
Returns a counts-first report with per-file evidence in CONFORMS / VIOLATES / UNVERIFIABLE / N-A taxonomy, deferring judgments to the library-review process.
Provides an investigation artifact template for structured, auditable governance.

Quick Start

Run the library-investigator probe to generate a counts-first report of RULESET.md compliance for the repository's Claude assets (skills, agents, commands, and workflows).

Frequently Asked Questions about library-investigator

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

FAQPage Schema

How do I audit Claude Code libraries for rule-based compliance violations?▼

To audit Claude Code libraries for compliance, probe files across .claude/skills, agents, commands, and workflows against RULESET.md to emit plain counts and detailed evidence. This generates a counts-first report using CONFORMS, VIOLATES, UNVERIFIABLE, and N-A taxonomy without applying quality judgments.

What is the best way to verify evidence of rule violations in Claude assets?▼

The best way to verify rule violations in Claude assets is running a forensic audit that probes .claude files against mechanically-checkable rules. It returns objective per-file evidence and uniform tabular output, deferring quality judgments to the library-review process.

How do I generate a compliance report for skills, agents, commands, and workflows?▼

Generate a compliance report for skills, agents, commands, and workflows by enumerating and probing files against RULESET.md. The audit produces a counts-first artifact using a CONFORMS or VIOLATES taxonomy to provide structured, auditable governance evidence.

Can I check .claude workflow files for rule compliance without subjective quality judgments?▼

Yes, you can check .claude workflow files for rule compliance objectively by probing them against RULESET.md. The audit emits plain counts and detailed evidence without applying quality judgments, deferring all subjective assessments to the library-review process.

When do I need a forensic audit of my Claude Code library?▼

You need a forensic audit of your Claude Code library when you require objective counts and supporting evidence of rule-based violations across .claude assets. It provides an investigation artifact template for structured, auditable governance without subjective quality judgments.

Why does my library audit report show UNVERIFIABLE status for some files?▼

Your library audit report shows UNVERIFIABLE status when the probe cannot mechanically confirm or deny a rule from RULESET.md for specific .claude files. This plain count taxonomy ensures objective reporting by separating unverifiable cases from clear CONFORMS or VIOLATES results.