Content
68%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A reasonably well-structured skill that provides concrete CLI commands for AI file metadata stamping and auditing. Its main weakness is the lack of an explicit end-to-end workflow with validation checkpoints (e.g., stamp → verify → audit), which is important for metadata operations that affect compliance. The skill also undersells its claimed breadth (20+ formats, detailed compliance) without pointing to deeper documentation.
Suggestions
Add an explicit numbered workflow with a validation step: e.g., 1. Stamp the file, 2. Read/inspect to verify metadata was applied, 3. Audit for compliance — with example output showing expected results.
Include sample command output for at least `akf read` or `akf inspect` so Claude knows what to expect and can verify success.
Reference or link to format-specific guidance for the 20+ supported formats (DOCX, PDF, images, code) — even a brief table of format → embedding notes would improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally lean and efficient. The opening analogy ('Every photo has EXIF. Every song has ID3.') is a minor indulgence but adds context quickly. The evidence examples list is slightly verbose but still useful. Overall respects Claude's intelligence. | 4 / 5 |
Actionability | Provides concrete, copy-paste CLI commands for stamping, reading, inspecting, and auditing. However, it lacks a complete workflow example showing end-to-end usage (e.g., stamp then verify), and there's no example output shown for any command, which leaves minor gaps. | 4 / 5 |
Workflow Clarity | The sections imply a sequence (create/modify → stamp, before modifying → read, then audit), but there's no explicit numbered workflow tying these together. For a tool that modifies file metadata, there's no validation step to confirm the stamp was applied correctly (e.g., stamp then read to verify). Missing verification caps this at 3. | 3 / 5 |
Progressive Disclosure | For a relatively short skill with no bundle files, the content is well-organized into clear sections (when to use, after creating, before modifying, compliance, classification, install, links). External links are provided for deeper exploration. Minor gap: no references to separate docs for advanced features like format-specific embedding details for 20+ formats mentioned in the description. | 4 / 5 |
Total | 15 / 20 Passed |