Name: anodot
Rating: 52.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

anodot

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

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

56%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 provides strong, executable CLI guidance with a clear connection-state workflow, but it is bloated by a ~180-line account list and a concept-explaining intro. Moving or trimming the account list would materially improve conciseness and progressive disclosure.

Suggestions

Remove or relocate the ~180-line bullet list of "X Accounts" into a separate reference file (e.g. references/accounts.md) and link to it, keeping only the core Anodot resource types in the overview.

Trim the opening paragraph that explains what Anodot is; Claude can infer this — lead instead with what the skill does.

De-duplicate the action-discovery instructions, which appear in both "Searching for actions" and "Popular actions".

Dimension	Reasoning	Score
Conciseness	The ~180-line bullet list of "X Accounts" entries is heavy padding that does not earn its token cost, and the intro paragraph explains what Anodot is — a concept Claude can infer. This is noticeably verbose with padded sections (anchor 2); it stops short of anchor 1 only because the core CLI sections themselves are reasonably tight.	2 / 5
Actionability	Concrete, copy-paste-ready commands appear throughout (npm install, membrane login, connection ensure, action run, request) plus a flags table for proxy options. It is mostly executable guidance with minor gaps such as placeholder CONNECTION_ID/actionId values, fitting anchor 4 rather than the fully-covered anchor 5.	4 / 5
Workflow Clarity	The flow install → authenticate → connect → search → run is clearly sequenced with explicit state-polling checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) acting as feedback loops. It has most checkpoints present with minor gaps (e.g. the duplicated "Popular actions" discovery block), matching anchor 4.	4 / 5
Progressive Disclosure	Section headers organize the body, but the large inlined account list is content that clearly belongs in a separate file or should be trimmed, and no bundle files or external references exist. This fits anchor 3 (some structure, content that should be separate is inline) rather than anchor 4's well-split organization.	3 / 5
	Total	13 / 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 answers both what and when and is anchored to a distinct named product, but its actions and trigger terms are generic. Tightening the action list and adding concrete trigger phrases would raise completeness and trigger quality.

Suggestions

Replace generic verbs ("Manage data, records, automate workflows") with concrete Anodot-specific actions such as "query metrics", "create alerts", or "inspect anomaly detection segments".

Expand the "Use when" clause with concrete trigger phrases users would actually say, e.g. "Use when the user wants to query Anodot metrics, view dashboards, or manage alerts."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Anodot domain plus a few actions, but the actions are generic rather than concrete, matching the anchor for domain + 1-2 non-comprehensive actions. It is above the minimal/generic anchor (2) because multiple actions are named, but below anchor 4 since none are specific.	3 / 5
Completeness	It answers "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with Anodot data"), but the "when" clause is somewhat generic and could be more explicit. This matches anchor 4 (both present, when could be more specific) rather than anchor 5's concrete trigger phrases.	4 / 5
Trigger Term Quality	The terms "Anodot", "data", "records", and "workflows" are relevant but the trigger phrase "interact with Anodot data" is narrow and misses common synonyms or variations a user might say. It fits the anchor for some relevant keywords with missing variations, and is not strong enough for anchor 4's good coverage.	3 / 5
Distinctiveness Conflict Risk	"Anodot" is a named product, giving the skill a clear niche with low conflict risk, though the generic "interact with data" trigger leaves minor overlap risk. It is mostly distinct (anchor 4) but not quite anchor 5's fully distinct triggers.	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/anodot/SKILL.md
Commit: f484c82

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