Deactivate DuploCloud context and clear credentials
55
62%
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 ./skills/deactivate/SKILL.mdQuality
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 is very terse and narrowly scoped. While it benefits from referencing a specific product (DuploCloud) which makes it distinctive, it lacks a 'Use when...' clause and misses common user-facing trigger terms like 'logout', 'disconnect', or 'sign out'. The brevity hurts both completeness and trigger term coverage.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to log out of DuploCloud, disconnect, or reset their DuploCloud session.'
Include natural trigger term variations such as 'logout', 'sign out', 'disconnect', 'remove DuploCloud credentials', or 'end DuploCloud session'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names a specific domain (DuploCloud) and two actions (deactivate context, clear credentials), but doesn't elaborate on what those actions entail or list additional related capabilities. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also minimal, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes 'DuploCloud', 'deactivate', 'context', and 'credentials' which are relevant keywords, but misses common user variations like 'logout', 'disconnect', 'sign out', 'remove credentials', or 'reset session'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'DuploCloud' as a specific product name with 'deactivate context' and 'clear credentials' creates a very clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
85%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, concise skill for a simple deactivation task. It correctly includes a user confirmation before destructive file operations and provides helpful context in the Notes section. The main weakness is that the deletion steps describe actions rather than providing executable commands.
Suggestions
Replace descriptive deletion steps with executable shell commands (e.g., `rm -f ~/.duplocloud/.auth` and `rm -f .duplocloud/state.json`) to improve actionability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. Every line serves a purpose—confirmation prompt, file deletions, and post-action confirmation. No unnecessary explanations of what DuploCloud is or how credentials work. | 3 / 3 |
Actionability | The steps are clear but lack executable commands. Instead of specifying 'Delete ~/.duplocloud/.auth', it could provide the actual shell commands (e.g., `rm ~/.duplocloud/.auth`). The guidance is concrete but not fully copy-paste ready. | 2 / 3 |
Workflow Clarity | For this simple, destructive operation, the workflow is well-sequenced: confirm with user first, then perform deletions, then confirm completion. The user confirmation step serves as a validation checkpoint before the destructive action. | 3 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with clear sections (Steps, Notes). No external references are needed, and the cross-reference to `/duplo:activate_project` is appropriate. | 3 / 3 |
Total | 11 / 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 | |
0b53740
Table of Contents
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.