status
Display the current state of the FPF knowledge base
56
47%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/fpf/skills/status/SKILL.mdQuality
Discovery
17%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 is too terse and lacks both explicit trigger guidance and natural user-facing keywords. While it references a specific domain (FPF knowledge base), it fails to explain what the 'current state' includes or when Claude should select this skill. It would benefit significantly from concrete action details and a 'Use when...' clause.
Suggestions
Add a 'Use when...' clause specifying triggers, e.g., 'Use when the user asks to see, list, or check the status of the FPF knowledge base.'
Include natural trigger terms users might say, such as 'show', 'list', 'status', 'view', 'knowledge base contents', or 'FPF entries'.
Elaborate on what 'current state' means with concrete details, e.g., 'Lists all entries, categories, and metadata in the FPF knowledge base, showing counts and last-updated timestamps.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names a specific domain ('FPF knowledge base') and one action ('Display the current state'), but does not list multiple concrete actions or elaborate on what 'current state' entails. | 2 / 3 |
Completeness | It partially answers 'what' (display current state) but provides no 'when' clause or explicit trigger guidance, which caps this at a maximum of 2, and the 'what' itself is weak, so it scores 1. | 1 / 3 |
Trigger Term Quality | 'FPF knowledge base' is domain-specific jargon that users may not naturally say. There are no common variations or natural trigger terms like 'show', 'list', 'status', or 'summary' included. | 1 / 3 |
Distinctiveness Conflict Risk | 'FPF knowledge base' is a fairly specific domain reference that reduces conflict with generic skills, but the action 'display current state' is vague enough to overlap with any status/dashboard-type skill. | 2 / 3 |
Total | 6 / 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 solid, actionable skill for a status-check operation with clear directory paths, well-defined phase detection logic, and concrete output formats. Its main weakness is moderate verbosity from having both a full format template and a separate example output that partially overlap. The content is well-structured within the file but could benefit from slightly tighter presentation.
Suggestions
Consolidate the Status Report Format section and Example Output into a single annotated example to reduce redundancy and save tokens.
Consider extracting the phase detection logic table and evidence freshness rules into a referenced file if this skill is part of a larger FPF bundle.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy—two example outputs (the full format template and the simplified example) overlap significantly. The phase detection table and evidence freshness logic are useful but the overall document could be tightened by consolidating the format template and example. | 2 / 3 |
Actionability | The skill provides concrete directory paths to check, specific file locations, a clear output format with markdown tables, explicit phase detection logic with conditions mapped to phases, and precise evidence freshness classification rules with date comparisons. Everything is specific and directly executable. | 3 / 3 |
Workflow Clarity | The 5-step action sequence is clearly numbered and unambiguous. The phase detection table provides explicit conditions and next steps. The evidence freshness check has a clear 3-step process with classification criteria. For a read-only status check operation, validation/feedback loops are not critical, and the workflow is well-sequenced. | 3 / 3 |
Progressive Disclosure | The content is reasonably well-structured with clear sections (Action, Format, Phase Detection, Evidence Freshness, Example), but it's somewhat long for a single file with no bundle references. The detailed status report format template and the example output could potentially be split into a reference file, and the phase detection logic table could be a separate reference. | 2 / 3 |
Total | 10 / 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
- NeoLabHQ/context-engineering-kit
- Commit
dedca19
- 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.