huckleberry
Track baby sleep, feeding, diapers, and growth via Huckleberry app API. Use for logging baby activities through natural language.
51
58%
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 ./public/skills/aaronn/openclaw-huckleberry-skill/SKILL.mdQuality
Discovery
75%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 functional and covers the basics well, with a clear 'what' and 'when' clause and a distinctive niche tied to the Huckleberry API. Its main weaknesses are moderate specificity in the actions listed and limited trigger term coverage, missing common natural language variations users might use when requesting baby activity logging.
Suggestions
Expand trigger terms to include natural variations like 'nap', 'bottle', 'breastfeed', 'nursing', 'diaper change', 'weight tracking', 'baby tracker'.
Add more specific concrete actions such as 'log naps and nighttime sleep', 'record bottle or breastfeeding sessions', 'track diaper changes and baby weight/height'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (baby tracking) and lists several actions (sleep, feeding, diapers, growth), but doesn't elaborate on specific concrete operations like 'log a nap', 'record bottle feeding amount', or 'track diaper changes with timestamps'. | 2 / 3 |
Completeness | Clearly answers both what ('Track baby sleep, feeding, diapers, and growth via Huckleberry app API') and when ('Use for logging baby activities through natural language'), providing an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes some natural keywords like 'baby sleep', 'feeding', 'diapers', 'growth', and 'Huckleberry', but misses common variations users might say such as 'nap', 'bottle', 'breastfeed', 'nursing', 'diaper change', 'weight', 'baby tracker', or 'log a feed'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Huckleberry app API' and the specific baby-tracking domain creates a very clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at actionability with comprehensive, executable CLI commands and a useful natural language mapping table. However, it is significantly too long and verbose, including medical guides and explanations Claude doesn't need, and fails to split content across files despite its length. The workflow could benefit from explicit validation steps (e.g., confirming entries were logged successfully).
Suggestions
Remove the color guide and consistency guide entirely — Claude already knows this medical information and can provide it contextually if asked.
Split the complete parameter reference tables into a separate REFERENCE.md file, keeping only the most common commands in the main SKILL.md.
Add a verification step after logging entries: e.g., 'After logging, run `history --date today` to confirm the entry appears correctly.'
Consolidate the duplicated notes information (the '--notes' section at the bottom repeats what's already in the parameter tables) and remove the credits/dates footer.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is excessively verbose at ~250+ lines. The color guide and consistency guide explain medical knowledge Claude already has. The troubleshooting section is generic. The credits, dates, and repeated notes about '--notes' parameter availability are redundant. The complete parameter reference tables duplicate information already shown in the CLI usage examples. | 1 / 3 |
Actionability | Every command is fully executable with exact CLI syntax, specific parameter values, and copy-paste ready examples. The natural language mapping table provides clear input-to-command translations, and parameter tables include all required values and defaults. | 3 / 3 |
Workflow Clarity | The timer-based workflows (sleep-start → sleep-complete, feed-start → feed-switch → feed-complete) are implicitly sequenced but lack explicit validation checkpoints. There's no guidance on verifying entries were successfully logged (e.g., checking history after logging), and the 'Timer already active' troubleshooting note suggests error states that should have been addressed in the workflow with a check-before-start step. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files despite being long enough to warrant splitting. The parameter reference, color/consistency guides, troubleshooting, and technical notes could all be separate files. The notes section at the bottom feels like an afterthought appended without reorganizing the document. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Repository
- Demerzels-lab/elsamultiskillagent
- Commit
f45fcb5
- 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.