Name: howuku
Rating: 65.60000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

howuku

Howuku integration. Manage Organizations, Users, Goals, Filters. Use when the user wants to interact with Howuku data.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/howuku/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete, executable membrane commands and well-organized sections, but it opens with conceptual padding Claude could infer and lacks explicit validation/error-recovery checkpoints in its workflow for potentially destructive proxy and action-run operations.

Suggestions

Cut the introductory paragraph explaining what Howuku is and who uses it, and tighten or remove the Overview entity list that duplicates the popular-actions table, to improve token efficiency.

Add explicit validation checkpoints to the workflow (e.g., verify the connection succeeded after `membrane connect`, confirm auth completed before running actions, check the action's inputSchema before invoking) with fix-and-retry guidance.

Move the full action catalog and detailed proxy options into a separate reference file (e.g., REFERENCE.md) linked from the body to apply progressive disclosure more cleanly.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and tables, but the opening paragraph explaining what Howuku is and who uses it, plus the somewhat redundant Overview entity list, are unnecessary explanations Claude could infer.	3 / 5
Actionability	Fully executable, copy-paste-ready membrane commands cover the common cases (install, login, connect, list, search, action run with JSON input, proxy) alongside a flags table and a popular-actions key table.	5 / 5
Workflow Clarity	A clear ordered sequence (install -> login -> connect -> discover -> run -> proxy) is present, but explicit validation checkpoints and error-recovery feedback loops are missing, and proxy/action-run can be destructive so workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	Well-organized self-contained file with clear section headers and no nested references; minor gap is that bulk material (full action catalog, proxy details) is inlined rather than split into one-level-deep reference files, and the file is too long for the under-50-line exception.	4 / 5
	Total	15 / 20 Passed

Description

90%Weight 40%Scale 1-5

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 cleanly covers both what and when with an explicit 'Use when' clause and a branded, distinct trigger, but its trigger language is thin (mostly just the product name) and its actions are a single generic verb spread across entities rather than distinct operations.

Suggestions

Replace the uniform verb 'Manage' with distinct concrete actions (e.g., 'List, create, and update Organizations, Users, Goals, and Filters') to lift specificity toward 5.

Expand the 'when' clause with concrete trigger phrases users would actually say, e.g., 'Use when the user mentions Howuku analytics, funnels, session recordings, heatmaps, or surveys'.

Add common synonyms or product-adjacent terms (analytics, A/B tests, personalization) so the trigger matches more natural user phrasings.

Dimension	Reasoning	Score
Specificity	Names the Howuku domain and four concrete management targets (Organizations, Users, Goals, Filters), but the single generic verb 'Manage' applied uniformly rather than distinct operations keeps it just below comprehensive.	4 / 5
Completeness	Both 'what' (Manage Organizations, Users, Goals, Filters) and 'when' (an explicit 'Use when...' clause) are present, but the 'when' is generic ('interact with Howuku data') rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	Natural keywords are essentially limited to the brand name 'Howuku' and 'Howuku data', with no synonyms, file extensions, or common phrasing variations beyond the product name.	3 / 5
Distinctiveness Conflict Risk	The branded 'Howuku' noun gives it a clear niche with minimal conflict risk, but the generic 'Manage ... data' framing and thin trigger language leave minor overlap risk with other analytics CRUD integrations.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/howuku/SKILL.md
Commit: f484c82

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.