common-feedback-reporter
Pre-write skill violation audit. Checks planned code against loaded skill anti-patterns before any file write. Use when writing Flutter/Dart code, editing SKILL.md files, or generating any code where project skills are active. Load as composite alongside other skills. When a violation is detected and Auto-fixed: YES, also load +common/common-learning-log to record the mistake. (triggers: skill violation, pre-write audit, audit violations, SKILL.md, **/*.dart, **/*.ts, **/*.tsx, +common/common-learning-log)
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong, well-crafted skill description that clearly communicates its purpose (pre-write audit of code against skill anti-patterns), specifies when to use it (Flutter/Dart, SKILL.md editing, active project skills), and includes explicit trigger terms. The description also provides useful operational guidance about composite loading and conditional learning log integration, making it highly actionable for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists multiple specific concrete actions: 'Checks planned code against loaded skill anti-patterns before any file write', mentions specific file types (Flutter/Dart, SKILL.md, *.dart, *.ts, *.tsx), and describes the auto-fix workflow with learning log integration. | 3 / 3 |
Completeness | Clearly answers both 'what' (checks planned code against skill anti-patterns before file writes) and 'when' (when writing Flutter/Dart code, editing SKILL.md files, or generating code where project skills are active). Also includes conditional behavior guidance about loading the learning log. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger terms in parentheses covering natural keywords: 'skill violation', 'pre-write audit', 'audit violations', 'SKILL.md', and glob patterns for relevant file types. These are terms a user or system would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | This skill occupies a very clear niche — pre-write violation auditing against skill anti-patterns. The concept of auditing code against SKILL.md anti-patterns before writing is highly distinctive and unlikely to conflict with general coding or linting skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent meta-skill that efficiently teaches Claude to audit its own code against loaded skill anti-patterns before file writes. It excels in all dimensions: concise without sacrificing clarity, fully actionable with concrete formats and examples, clearly sequenced with validation checkpoints, and well-organized with appropriate progressive disclosure. The anti-patterns section is a particularly strong addition that prevents common failure modes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. Every section serves a purpose — no unnecessary explanations of what skills are, what file writes are, or other concepts Claude already knows. The flow diagram, table, and anti-patterns are all tightly written. | 3 / 3 |
Actionability | The skill provides a concrete, step-by-step detection flow, a specific violation report format with all required fields, a root cause classification table, and concrete examples (Flutter color, React class component, SKILL.md line count). The instructions are unambiguous and directly executable. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced: check extension → identify skills → audit anti-patterns → report or proceed. It includes explicit decision points (YES/NO branches), a pre-completion validation checkpoint ('Did I write code? Did I audit skills?'), and the anti-patterns section acts as a guardrail against skipping steps. | 3 / 3 |
Progressive Disclosure | The skill is well-structured with clear sections (Checkpoint, Detection Flow, Examples, Violation Report Format, Root Cause Guide, Anti-Patterns). It references a deeper examples file via '[More examples →](references/violation-examples.md)' — one level deep, clearly signaled. The main content stays concise as an overview. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
19a1140
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.