agent-definition-auditor
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Security
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: agent-definition-auditor
description: Audit and score an agent-definition markdown such as `AGENTS.md`, `CLAUDE.md`, `SKILL.md`, `SOUL…
category: security
runtime: no special runtime
---
# agent-definition-auditor output preview
## PART A: Task fit
- Use case: Audit and score an agent-definition markdown such as `AGENTS.md`, `CLAUDE.md`, `SKILL.md`, `SOUL.md`, `.cursorrules`, or a system prompt using a cold-reader rubric for clarity, consistency, context independence, and operating-model fit. Use when the user asks to review, score, critique, or audit an agent instruction file. Not for evaluating agent outputs, code quality, or rewriting the file itself. Use when this capability is needed..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When to use / When not to use / Non-negotiables” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Audit and score an agent-definition markdown such as `AGENTS.md`, `CLAUDE.md`, `SKILL.md`, `SOUL.md`, `.cursorrules`, or a system prompt using a cold-reader rubric for clarity, consistency, context independence, and operating-model fit. Use when the user asks to review, score, critique, or audit an agent instruction file. Not for evaluating agent outputs, code quality, or rewriting the file itself. Use when this capability is needed.”.
- **02** When the source has headings, the agent prioritizes “When to use / When not to use / Non-negotiables” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “When to use / When not to use / Non-negotiables”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: agent-definition-auditor
description: Audit and score an agent-definition markdown such as `AGENTS.md`, `CLAUDE.md`, `SKILL.md`, `SOUL…
category: security
source: tomevault-io/skills-registry
---
# agent-definition-auditor
## When to use
- Audit and score an agent-definition markdown such as `AGENTS.md`, `CLAUDE.md`, `SKILL.md`, `SOUL.md`, `.cursorrules`…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “When to use / When not to use / Non-negotiables” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "agent-definition-auditor" {
input -> user goal + target files + boundaries + acceptance criteria
context -> When to use / When not to use / Non-negotiables
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Agent Definition Auditor
Use this skill when the job is auditing one agent-definition file, not rewriting it.
When to use
- The user wants to audit or score an
AGENTS.md,CLAUDE.md,SKILL.md,SOUL.md,.cursorrules, system prompt, or other agent-definition markdown. - The user wants a cold-reader review of agent-contract quality.
- The user wants a deploy / revise / do-not-ship judgment with concrete findings and fastest improvements.
- The user wants a reusable rubric-based critique of an agent instruction file rather than an output benchmark.
When not to use
- The user wants to write, rewrite, or refactor the agent file rather than score it.
- The user wants to evaluate agent outputs, benchmark runtime behavior, or compare model responses rather than audit the instruction artifact itself.
- The job is code review, product-doc review, or general technical writing feedback unrelated to an agent-definition file.
- No target artifact or pasted instruction text is available.
Non-negotiables
- Default to a single-artifact, read-only cold read.
- Judge the document as an operational contract, not as domain strategy or business policy.
- Distinguish precise layered contracts from phantom context.
- Apply the scoring model, hard caps, and report shape from the reference prompt literally.
- Cite line numbers when available; otherwise cite exact headings or short anchors.
- Do not widen to repo-wide inspection unless the user explicitly asks for multi-file or repo-context evaluation.
- Do not rewrite the file unless the user explicitly asks for fixes after the audit.
First move
- Resolve one target artifact path or pasted instruction text.
- Read
references/agent-definition-judge-prompt.md. - Read the full target artifact once before scoring.
- If the user also wants revisions, finish the audit first unless they explicitly want authoring instead of judging.
Workflow
- Confirm the artifact class and whether the input is a full file or an excerpt.
- Stay on the single document by default.
- Inventory the artifact's hard rules:
- mission and scope
- output rules
- tool rules
- approval and escalation rules
- failure handling
- external dependencies
- Apply the reference prompt's scoring model and hard caps.
- Return the exact report sections required by the reference prompt.
- If the user then wants fixes, use the audit as the basis for the follow-up instead of recomputing the diagnosis from scratch.
Output expectations
- Return the exact top-level sections from the reference prompt.
- Include overall and uncapped score, verdict, confidence, cap logic, findings, strengths, fastest score gains, and limits.
- Keep findings ordered by severity and tied to concrete evidence from the artifact.
Reference map
references/agent-definition-judge-prompt.md- full judging prompt, scoring model, hard caps, report contract, and examples
Source: aelaguiz/arch_skill — distributed by TomeVault.
Decide Fit First
AGENTS.md,CLAUDE.md,SKILL.md,SOUL.md,.cursorrules, or a syste…Design Intent
How To Use It
Boundaries And Review