Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/zernie/vigiles --skill audit-feedback-loop- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads audit-feedback-loop automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Scan the current repository and score its feedback loop maturity for AI-assisted development.
Instructions
Analyze this repository and score its feedback loop maturity using the levels below. Check for each signal, then output a summary report.
Maturity Levels
Level 0 — Vibes No CI config, no linter rules, no CLAUDE.md. The AI agent is flying blind.
Level 1 — Guardrails Has CI + standard linters, but no custom rules. The agent gets basic feedback but can't learn project-specific conventions.
Level 2 — Architecture as Code Has custom lint rules, CLAUDE.md rules have enforcement annotations. The agent gets rich, project-specific feedback.
Level 3 — The Organism Has CI + custom rules + screenshot/visual tests + observability + scheduled agent tasks. The entire development loop is instrumented.
Signals to Check
Scan the repository for the following and note which exist:
- CI Configuration: Look for
.github/workflows/,.circleci/,Jenkinsfile,.gitlab-ci.yml,bitbucket-pipelines.yml,.travis.yml, etc. - Linter Config (language-aware):
- JS/TS:
eslint.config.*,.eslintrc*,biome.json,.prettierrc*,deno.json - Python:
pyproject.toml(look for[tool.ruff],[tool.pylint],[tool.flake8]),setup.cfg,.flake8,ruff.toml - Rust:
clippy.toml,.clippy.toml,rustfmt.toml - Go:
.golangci.yml,.golangci.yaml - Ruby:
.rubocop.yml - Java/Kotlin:
checkstyle.xml,pmd.xml,detekt.yml
- JS/TS:
- Custom Lint Rules: Look for custom plugins, rule directories, or inline rule definitions in linter configs
- JS/TS:
eslint-plugin-*,eslint-rules/directories - Python: custom Ruff/Pylint plugins, AST-based checks
- Rust: custom Clippy lints
- Go: custom analyzers
- JS/TS:
- CLAUDE.md: Check if
CLAUDE.mdexists at the repo root - CLAUDE.md Enforcement: Check if using vigiles v2 specs (
CLAUDE.md.spec.tsexists) or v1 annotations (**Enforced by:**in CLAUDE.md). v2 specs = higher maturity. - Type-Safe Specs: Check for
CLAUDE.md.spec.tsor*.spec.tsfiles — indicates typed spec compilation via vigiles v2 - Generated Types: Check for
.vigiles/generated.d.ts— indicates linter rules are type-checked at authoring time - Screenshot/Visual Tests: Look for Playwright (
playwright.config.*), Cypress (cypress.config.*), Chromatic, Percy, BackstopJS configs - Observability: Search for imports/usage of
@sentry/,dd-trace,@datadog/,newrelic,@opentelemetry/,sentry_sdk,structlog,tracing(Rust),opentelemetryin source files - Scheduled Agent Tasks: Look for cron patterns in CI configs,
.github/workflows/withschedule:triggers, or references to scheduled Claude Code tasks
Output Format
## Feedback Loop Audit
**Repository:** <repo name>
**Primary language(s):** <detected languages>
**Score: Level X — <Name>**
### Signals Found
- [x] CI Configuration: <details>
- [ ] Custom Lint Rules: not found
- [x] CLAUDE.md: found, 5 enforced / 2 guidance / 1 missing
...
### Recommendations
1. <Most impactful next step to level up>
2. <Second recommendation>
3. <Third recommendation>
### How to Level Up
<Specific, actionable advice for reaching the next maturity level>
Be specific about file paths and what you found. Give actionable recommendations tailored to the project's language and toolchain.
FAQ
What does the audit-feedback-loop skill do?
Scan the current repo and score its feedback loop maturity for AI-assisted development
How do I install audit-feedback-loop?
Run npx skills add https://github.com/zernie/vigiles --skill audit-feedback-loop in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/audit-feedback-loop/ (personal) or .claude/skills/audit-feedback-loop/ (project).
Which AI agents can use audit-feedback-loop?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is audit-feedback-loop safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains audit-feedback-loop?
It is published by zernie in zernie/vigiles. It has 435 recorded installs.
More from zernie/vigiles
edit-spec
zernie/vigiles
Edit a vigiles .spec.ts to change a compiled instruction file (CLAUDE.md / AGENTS.md) — add, modify, or remove a rule, section, command, or file pointer (including a request to add a "key file" — the keyFiles field is deprecated). Use whenever you need to change a CLAUDE.md/AGENTS.md that carries a vigiles hash (edit the spec, never the artifact), including adding a new enforce()/check()/guidance() rule.
strengthen
zernie/vigiles
Upgrade a vigiles spec's guidance() rules to enforce() — scan the guidance rules in a CLAUDE.md/AGENTS.md spec and find existing linter rules (ESLint, Ruff, Clippy, Pylint, RuboCop, Stylelint) that back them. Use when asked to strengthen, harden, or make vigiles rules enforceable; NOT for general linting or fixing lint errors.
test-harness
zernie/vigiles
Install vigiles and test a Claude Code harness — hooks, skills, agents, settings, CLAUDE.md — by picking the right tier (unit / deterministic / eval) and writing a test that passes. Use to check that a hook fires or blocks, that a skill triggers, that injected context lands; or to observe a run — which tools it called, whether it stayed inside its declared allowed-tools, what files and side effects it produced, how to intercept a call without executing it.
linter-docs
zernie/vigiles
Deep linter reference for authoring or debugging a vigiles enforce() rule — plugin tables, AST selectors, type-aware rules, auto-fix, and edge cases for ESLint, Ruff, Pylint, RuboCop, Stylelint, and Clippy. Use when you need the exact rule name or config for a specific linter, not for running a linter. (JVM/Go linters — detekt, ktlint, Checkstyle, golangci-lint — and Cedar have no deep-dive file yet; their reference lives in docs/linter-support.md.)
adopt-spec
zernie/vigiles
Adopt a typed .spec.ts for an existing hand-written CLAUDE.md — start from the file you already have, non-destructively
debug-my-harness
zernie/vigiles
Diagnose why an agent harness misbehaved by reading the local flight-recorder ledger (.vigiles/runs.jsonl) — which skills fired or got hijacked, which hooks blocked or wrongly allowed, which subagent tool-contract violations happened, and how a skill's trigger rate moved. Use when asked why a skill stopped firing, why a hook didn't block, why the wrong skill ran, or to debug/investigate what the harness actually did. NOT for writing new rules (use strengthen) or editing the spec (use edit-spec).
Popular security skills
azure-compliance
microsoft/azure-skills
Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized reprooutputs/ files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
seo-audit
coreyhaines31/marketingskills
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
firebase-security-rules-auditor
firebase/agent-skills
Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege escalation, role bypasses, create vs update inconsistencies, resource exhaustion, type safety, size limits, and hasOnly ownership checks. Use when auditing/reviewing rules, running red-team rule assessments, or scoring against auditor checklists. Don't use for Firebase CLI (login, deploy), Auth, Crashlytics, Remote Config, or database queries.
audit
pbakaus/impeccable
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
competitors
coreyhaines31/marketingskills
When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'competitor teardown,' 'audit our competitor pages,' 'are our comparison pages out of date,' or 'competitive asset audit.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For auditing existing claims (not researching competitors from scratch, which is competitor-profiling; not technical SEO on these pages, which is seo-audit), use the asset audit here. For internal battle cards and sales-specific competitor docs, see sales-enablement.