Name: keen
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

keen

Keen integration. Manage data, records, and automate workflows. Use when the user wants to interact with Keen data.

Quality

72%

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/keen/SKILL.md

Quality

Content

82%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 a strong, executable integration guide with concrete commands and a well-checkpointed connection workflow, slightly held back by minor padding in the intro and reference-style content inlined rather than split out.

Suggestions

Trim or relocate the opening "Keen is a customer analytics platform..." sentence to remove concept explanation Claude already knows.

Fix step numbering so the referenced "Step 2" is explicitly labeled and the action discovery/run flow is sequenced consistently with the connection steps.

Move the proxy flags table and detailed clientAction field schema into a separate reference file (e.g. REFERENCE.md) referenced one level deep to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands with minimal padding; the only mild over-explanation is the opening "Keen is a customer analytics platform..." sentence, which could be trimmed but is brief, fitting the efficient-with-minor-trimmable-instances anchor rather than the fully lean level 5.	4 / 5
Actionability	Every section provides copy-paste-ready, executable bash commands (install, login, connection ensure, action list/run, request) with concrete flags and JSON output guidance, covering the common cases comprehensively.	5 / 5
Workflow Clarity	The connection flow is explicitly sequenced with state-based checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED) and a poll->act->re-poll feedback loop; held below 5 because step numbering is inconsistent (a "1b" and a referenced "Step 2" that is not labeled) and action search/run are unnumbered.	4 / 5
Progressive Disclosure	The content is well-organized into clearly headed sections and is self-contained with no bundle files needed; below 5 because the body exceeds 50 lines and inlines reference-like material (the proxy flags table and the detailed clientAction field schema) that could live in a separate reference file.	4 / 5
	Total	17 / 20 Passed

Description

62%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 correctly answers both what and when in third person, but relies on generic action verbs ("manage data, records") and a single trigger phrase rather than concrete Keen-specific capabilities and varied trigger terms.

Suggestions

Replace generic verbs with concrete Keen capabilities, e.g. "Query event datasets, build analysis queries, and manage Keen projects and dashboards".

Broaden the trigger clause with natural variations: "Use when the user wants to query Keen events, run analyses, or manage Keen projects/dashboards."

Add file-format or noun triggers users actually say (events, datasets, queries) to improve distinctiveness and trigger coverage.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Keen domain plus a few actions, but the actions are generic ("manage data", "records") rather than concrete capabilities, matching the 1-2 concrete actions anchor; not a 4 because the listed actions lack specificity and coverage is thin.	3 / 5
Completeness	Both "what" ("Keen integration. Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with Keen data") are present, but the when clause is general rather than tied to concrete trigger phrases, so it sits below the explicit-trigger level 5.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Keen data" offers the natural trigger phrase "Keen data" but misses common variations or synonyms (e.g. analytics, events, dashboards, projects), fitting the some-relevant-keywords-but-missing-variations anchor.	3 / 5
Distinctiveness Conflict Risk	"Keen integration" names a specific app niche with minimal conflict risk, though the generic "manage data, records, automate workflows" framing leaves minor overlap with broad data skills; mostly distinct.	4 / 5
	Total	14 / 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/keen/SKILL.md
Commit: f484c82

Reviewed: 5 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.