stickies
Manage stickies as markdown files — create new, read, list, or delete. Use when the user mentions "sticky", "stickies", or wants to take a quick note or save a reminder.
79
100%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that concisely covers all key dimensions. It specifies concrete actions, provides explicit trigger guidance with natural user terms, and occupies a distinct niche. The description follows the recommended pattern closely and uses third person voice appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'create new, read, list, or delete' stickies as markdown files. Clear and actionable. | 3 / 3 |
Completeness | Clearly answers both what ('Manage stickies as markdown files — create new, read, list, or delete') and when ('Use when the user mentions "sticky", "stickies", or wants to take a quick note or save a reminder'). | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'sticky', 'stickies', 'quick note', 'save a reminder'. Good coverage of how users would naturally phrase requests. | 3 / 3 |
Distinctiveness Conflict Risk | The 'stickies' concept is a clear niche distinct from general note-taking or document management skills. The specific trigger terms 'sticky' and 'stickies' reduce conflict risk significantly. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%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-crafted skill that is concise, actionable, and clearly structured. It provides concrete examples for filenames, frontmatter, and table output while keeping instructions tight. The edge case handling (no matches, multiple matches) across Read and Delete actions demonstrates thoughtful workflow design.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what markdown files are, what stickies conceptually are, or how file systems work. Every section serves a clear purpose and there's no padding or unnecessary explanation. | 3 / 3 |
Actionability | Each action has concrete, numbered steps with specific instructions. The filename format, frontmatter template, and table output format are all explicitly defined with copy-paste ready examples. Claude knows exactly what to produce. | 3 / 3 |
Workflow Clarity | Each action is a clearly sequenced multi-step workflow with appropriate handling for edge cases (no matches, multiple matches). The delete action explicitly states not to ask for confirmation. The routing logic (match action → follow steps → handle edge cases) is unambiguous. | 3 / 3 |
Progressive Disclosure | For a skill of this size and complexity, the content is well-organized with clear sections (Actions, Sticky format) and doesn't need external references. The structure uses headers and subsections effectively for easy navigation without being monolithic. | 3 / 3 |
Total | 12 / 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 | |
- Repository
- shillem/cc-marketplace
- Commit
2384118
- 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.