prd-archive
Archive completed or cancelled PRDs
69
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear, narrow use case (archiving PRDs) which makes it distinctive, but it's too terse to be effective. It lacks explicit trigger guidance and doesn't explain what archiving involves or when Claude should invoke this skill over others.
Suggestions
Add a 'Use when...' clause specifying triggers like 'when user wants to archive, close, or move completed/cancelled PRDs'
Expand the action description to clarify what archiving entails (e.g., 'moves to archive folder, updates status, notifies stakeholders')
Include term variations like 'product requirements document', 'close PRD', 'finish PRD' to improve trigger matching
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names a specific domain (PRDs) and one action (archive), but lacks detail on what archiving entails or additional capabilities. | 2 / 3 |
Completeness | Only describes what (archive PRDs) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'PRDs', 'completed', 'cancelled', and 'archive' which are relevant terms, but misses common variations like 'product requirements document', 'close PRD', or 'move to archive'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche focused on PRD archival with clear status triggers (completed/cancelled); unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent actionability and workflow clarity - the execution instructions are clear, sequential, and include proper validation checkpoints. The main weaknesses are moderate verbosity (especially in output examples) and keeping all content inline rather than using progressive disclosure to reference files for templates and detailed examples.
Suggestions
Move the Archive Summary File template and detailed Output Format example to separate reference files (e.g., ARCHIVE-TEMPLATES.md) and link to them
Trim the output format section to show a minimal example, with full verbose output in a reference file
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some redundancy - the output format section is quite verbose with example output that could be trimmed, and the archive summary file example adds bulk that could be referenced externally. | 2 / 3 |
Actionability | Provides concrete, executable guidance with specific YAML metadata formats, exact directory structures, clear command examples, and step-by-step execution instructions that Claude can follow directly. | 3 / 3 |
Workflow Clarity | Clear 9-step sequence with explicit validation checkpoints (status checking, confirmation prompts for non-standard states), conditional branching for different scenarios, and comprehensive error handling section. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is inline in one file. The archive summary template and detailed output format could be split into separate reference files to reduce the main skill's length. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.