← ClaudeAtlas

target-auditlisted

Audit every agnostic-ai target against current vendor docs, report evidence-backed drift, and surface project capability changes. Use for the recurring adapter truth check or when a tool ships a new surface.
Chemaclass/agnostic-ai · ★ 16 · AI & Automation · score 75
Install: claude install-skill Chemaclass/agnostic-ai
<!-- Generated by agnostic-ai. Do not edit this file directly; edit specs under .agnostic-ai/ and run `agnostic-ai sync`. --> # target-audit Answers two questions: **do these tools still read what agnostic-ai emits, and what newly documented project capabilities deserve a product decision?** Adapters encode a snapshot of every vendor's config format. Those vendors ship often. Drift is silent. A moved skills directory keeps syncing cleanly, keeps `sync --check` green, and stops reaching the tool. This skill finds that drift on a schedule instead of via a user bug report. ## Arguments - no args: audit every registered target **and file an issue per confirmed finding**. Filing is the default, not an opt-in. - `claude zed kilo`: audit only those - `--no-file-issues`: stop at the report. Use it for a scratch run you do not intend to act on. - `--fix`: file issues, then open a PR per fix bucket. Never merges. - `--compare-models <model>`: run a bounded challenger pass with the requested model over breaking findings, spec candidates, and conflicting evidence. The audit still completes if that model is unavailable. **Why filing is the default.** It used to be opt-in, and two consecutive runs proved that wrong. The 2026-08-19 run found 52 findings and filed none. The 2026-08-27 run found 54 and filed none until a human asked, by which point it was re-verifying the previous run's backlog instead of auditing. The report lands in gitignored `local/`, so a run that does not