status
Show MemPalace status — room counts, storage usage, and palace health.
60
70%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.codex-plugin/skills/status/SKILL.mdQuality
Discovery
67%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 concise and specific about what it does within the MemPalace domain, listing three concrete metrics it reports. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know when to select this skill. The trigger terms are domain-specific and may not match how users naturally phrase requests.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user asks about MemPalace status, storage, room counts, or wants to check palace health.'
Include natural language trigger variations users might say, such as 'how much space is used', 'show stats', 'memory palace overview', or 'check palace status'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'room counts', 'storage usage', and 'palace health'. These are distinct, measurable outputs rather than vague language. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (show status with room counts, storage usage, palace health), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes domain-specific terms like 'MemPalace', 'room counts', 'storage usage', and 'palace health', but these are specialized jargon. Missing common user-facing trigger terms like 'status', 'dashboard', 'how much space', or 'memory palace stats' that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the domain-specific 'MemPalace' terminology and the specific combination of room counts, storage usage, and palace health. Unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an ultra-minimal skill that delegates all real logic to the `mempalace instructions status` command. While admirably concise, it sacrifices actionability by providing zero information about expected outputs, possible errors, or what the returned instructions might entail. It functions more as a command alias than a teaching document.
Suggestions
Add a brief description of what output to expect from the status command (e.g., room counts, storage metrics) so Claude can interpret and relay results without blindly following opaque instructions.
Include at least one example of typical output or a note on common error conditions to make the skill self-contained and actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean — just a heading, a one-line instruction, and a single command. No unnecessary explanation of what MemPalace is or how status works. Every token earns its place. | 3 / 3 |
Actionability | It provides a concrete command to run, but the actual guidance is fully deferred to the runtime output ('follow the returned instructions step by step'). Claude doesn't know what those instructions will be, so the skill itself gives no concrete details about what to do, what output to expect, or how to interpret results. | 2 / 3 |
Workflow Clarity | For a simple status-check skill, the single step is clear, but the instruction to 'follow the returned instructions step by step' implies a multi-step process without specifying what those steps are or providing any validation checkpoints. The workflow is essentially opaque. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines with no need for external references, the content is appropriately minimal and well-organized with a clear heading and action. | 3 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Repository
- milla-jovovich/mempalace
- Commit
db1fbe8
- 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.