Skip to content
cccskills
FreePublished on GitHub

library-investigator

Use when forensically auditing a Claude Code skill/agent/command/workflow library against RULESET.md by a fixed mechanical protocol — probing every file against the mechanically-checkable rules and reporting CONFORMS / VIOLATES / UNVERIFIABLE / N-A counts with quoted evidence. It casts NO judgment and emits NO pass/fail verdict; counts are the headline. Triggers on "investigate the library", "audit against RULESET", "find every violation", "forensic library audit", "evidence-only check". Not for routing/quality/single-responsibility judgment — use skill-library-review. Not the full sharded sweep — use the audit-library command.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (5)

  • SKILL.md5.5 KB
  • assets/investigation-report-template.md2.7 KB
  • references/probe-table.md5.7 KB
  • references/verdict-taxonomy.md2.6 KB
  • scripts/library_probe.sh12.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Library Investigator

You are a truthseeker, not a referee. You probe files against the mechanically-checkable rules of RULESET.md and report facts plus evidence. You never grade quality, never weigh routing, never emit pass / fail / hold or any overall verdict. The headline is COUNTS.

Core rules

  1. No judgment. Quality, routing, and single-responsibility are out of jurisdiction — they are N-A, deferred to skill-library-review. Never guess at a judgment rule.
  2. No softening. Well-written prose that breaks a rule is still VIOLATES. Polish is non-evidence.
  3. Costume check. Self-describing phrases ("comprehensive", "follows best practices") trigger mandatory verification of the rule they imply.
  4. Probe, don't infer. A claim of CONFORMS or VIOLATES rests on probe output, not on reading "how the file feels." When a probe cannot complete, the verdict is UNVERIFIABLE.

Protocol

Fixed seven steps. Probe contract: references/probe-table.md.

  1. Inventory — enumerate the files under audit across all four surfaces. Report the count.
  2. Map — for each file, list which rules apply to its surface (see probe table's Applies-to column).
  3. Probe — resolve the probe script (see findings-ledger references/install-paths.md), then run bash "$PROBE" [REPO_ROOT]. It emits one STATUS<TAB>TIER<TAB>RULE<TAB>FILE<TAB>DETAIL row per (file, rule) check and runs scripts/validate.sh for the Tier-0 line.
  4. Classify — tag each row CONFORMS / VIOLATES / UNVERIFIABLE / N-A per references/verdict-taxonomy.md.
  5. Tier-tag — label each VIOLATES with its tier as a FACT (a property of the check), framed as a ratchet candidate for validate.sh. Never say "this blocks."
  6. Self-consistency — confirm every probed file appears in the output. Rows can exceed (files × applicable rules) because R5/R33 emit one row per runnable/README; reconcile that surplus rather than expecting an exact product. Flag any missing file as UNVERIFIABLE.
  7. Report — fill assets/investigation-report-template.md: counts headline first, per-VIOLATES evidence rows, then the defer-list. No verdict line.

Jurisdiction split

  • Mechanical (investigator owns): R9, R12/R32-desc, R13, R32-body, R33, R5. Probed directly by the script.
  • Tier-0 (defer to validate.sh): R6, R7, R8, R31, dangling-refs. The script runs validate.sh and reports its exit; do not re-implement.
  • Judgment (N-A, defer to skill-library-review): R11, R15–R17, R22, routing specificity, single-responsibility.

Output contract

Counts first: CONFORMS n / VIOLATES n / UNVERIFIABLE n / N-A n over N files × M rules. Then per-VIOLATES rows with the exact probe command and quoted failing output. Then the defer-list. Never an overall verdict.

Tier discipline

Tier definitions: review-tiers (.claude/rules/review-tiers.md). Each VIOLATES states its tier as a fact about the check, not a gate.

References

Related

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when adversarially reviewing a document that makes formal or technical claims — math derivations, physics papers, statistical analyses, benchmark reports, whitepapers. Inventories every equation and quantitative claim, verifies each AS NAMED in the text (never a paraphrase or a neighboring statement), and classifies VERIFIED / REFUTED / UNVERIFIABLE / VACUOUS. Triggers on "check this paper", "verify these claims", "is this derivation right", "review this proof", "audit this benchmark", "does the math hold up". For source-code review see code-review-and-quality; for skill/agent library audits see skill-library-review; for content quality scoring see content-ops (marketing pack: `--with-marketing`).

The English summary is being prepared. Showing the original description.

LazyIsEfficient/agentic-os17Updated Oct 23, 2026

Run Karpathy-style autoresearch optimization on any content. Generates 50+ variants, scores with a 5-expert simulated panel, evolves winners through multiple rounds, outputs optimized version + full experiment log. Use when optimizing landing pages, email sequences, ad copy, headlines, form pages, CTA text, or any conversion-focused content. Triggers on "optimize this page", "run autoresearch", "score these variants", "A/B test this copy".

The English summary is being prepared. Showing the original description.

LazyIsEfficient/agentic-os17Updated Oct 23, 2026

Tests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data via Chrome DevTools MCP.

The English summary is being prepared. Showing the original description.

LazyIsEfficient/agentic-os17Updated Oct 23, 2026

Conducts multi-axis code review across correctness, readability, architecture, security, and performance. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Triggers on "review my PR", "review this diff", "code review", "review this changeset", "is this ready to merge", "pre-merge review".

The English summary is being prepared. Showing the original description.

LazyIsEfficient/agentic-os17Updated Oct 23, 2026

Estimate the full development cost of an existing codebase from lines of code, architectural complexity, and team-composition overhead. Use for 'how much would this cost to build', 'what did this codebase cost', development-cost or build-cost estimates, calendar-time estimates, and Claude/AI ROI on a delivered codebase. Estimates by measured LOC and complexity, not by ticket volume.

The English summary is being prepared. Showing the original description.

LazyIsEfficient/agentic-os17Updated Oct 23, 2026

Auto-assembles a domain-specific expert panel (7–10 experts), scores any content or strategy artifact against a typed rubric, and iterates until the aggregate hits 90+ (max 3 rounds). Use as a quality gate on copy, email sequences, landing-page drafts, strategy docs, charts, titles, or recruiting evaluations — or when another skill needs a final review gate on its output. Triggers on "expert panel this", "score this", "rate these variants", "quality check this", "panel review", "expert score", "evaluate this copy/strategy/page". For variant generation and multi-round conversion optimization see autoresearch; for live-URL CRO auditing see conversion-ops; for the scripted content-production pipeline see content-pipeline.

The English summary is being prepared. Showing the original description.

LazyIsEfficient/agentic-os17Updated Oct 23, 2026

See all skills by LazyIsEfficient

Report a problem with this skill