presence
Online status, activity tracking, and multi-device sync
65
51%
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 ./src/skills/bundled/presence/SKILL.mdQuality
Discovery
22%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 description is a weak noun-phrase list that fails to explain what actions the skill performs or when Claude should select it. It lacks concrete verbs, explicit trigger guidance, and sufficient detail to distinguish it from other potentially similar skills. The description would benefit significantly from restructuring into action-oriented language with clear use-case triggers.
Suggestions
Rewrite using action verbs in third person (e.g., 'Tracks user online/offline status, monitors activity across sessions, synchronizes state between multiple devices').
Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user asks about presence status, last active time, syncing data across devices, or real-time availability').
Include specific file types, APIs, or contexts this skill applies to (e.g., 'for chat applications', 'WebSocket connections', 'user presence indicators') to reduce conflict with other tracking or sync skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language ('online status', 'activity tracking', 'multi-device sync') without specifying concrete actions Claude would perform. No verbs describe what the skill actually does. | 1 / 3 |
Completeness | The description only vaguely hints at 'what' through noun phrases and completely lacks any 'when' guidance. There is no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords like 'online status', 'activity tracking', and 'multi-device sync' that users might mention, but lacks common variations and natural phrasing users would actually say (e.g., 'presence', 'last seen', 'sync across devices'). | 2 / 3 |
Distinctiveness Conflict Risk | The terms are somewhat specific to presence/sync functionality, but 'activity tracking' is generic and could overlap with analytics, logging, or monitoring skills. The lack of specificity increases conflict risk. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
79%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 API reference with excellent actionability - all code examples are executable and concrete. The content is appropriately concise without explaining obvious concepts. Main weaknesses are the lack of error handling guidance and the monolithic structure for what's labeled a 'complete reference'.
Suggestions
Add error handling examples showing what happens when presence operations fail (e.g., Redis connection issues, sync failures) and how to recover
Consider splitting into SKILL.md (overview + quick start) and REFERENCE.md (detailed API) for better progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting API methods directly with executable code examples. No unnecessary explanations of what presence/status means or how libraries work in general. | 3 / 3 |
Actionability | Fully executable TypeScript code examples throughout, with clear method signatures, parameters, and return values. Chat commands are copy-paste ready with concrete syntax. | 3 / 3 |
Workflow Clarity | This is primarily an API reference rather than a multi-step workflow skill. While individual operations are clear, there's no guidance on error handling, validation, or what to do when sync fails or status updates don't propagate. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a logical flow from commands to API to best practices. However, for a 'Complete API Reference' this is quite long inline content that could benefit from splitting detailed API docs into separate files. | 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 | |
- Repository
- alsk1992/CloddsBot
- Commit
2a8c94e
- 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.