Name: botanalytics
Rating: 59.2 (1 reviews)
Author: membranedev

botanalytics

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

Quality

68%

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

Quality

Content

75%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, actionable CLI integration guide with executable commands, a clear connection workflow, and explicit state-polling validation. Its main weaknesses are an unnecessary marketing intro and inconsistent step numbering that slightly muddies the workflow.

Suggestions

Trim the opening overview paragraph and other explanatory prose ('This is the fastest way to get a connection...') to assume Claude's competence and save tokens.

Fix the step numbering: label a clear '1. Connect' / '2. Wait for ready' / '3. Search and run actions' sequence so the dangling '1b' and unreferenced 'Step 2' resolve.

Consider moving the proxy flag table and clientAction state reference into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but opens with marketing-style background ('a platform for understanding and improving chatbot performance... used by developers and product managers') and several explanatory prose blocks Claude does not need, so it could be tightened.	3 / 5
Actionability	It provides copy-paste-ready, executable commands throughout (install, login, connection ensure, action list/run, request) plus a complete proxy flag table, covering the common cases concretely.	5 / 5
Workflow Clarity	The install → auth → connect → poll → search → run sequence is clear with explicit state-based validation checkpoints and a re-poll feedback loop, but the step numbering is inconsistent (a '1b' with no '1a', and a referenced 'Step 2' that is not labeled as a section), introducing minor gaps.	4 / 5
Progressive Disclosure	The content is well-organized into clearly headed sections with no nested references, but it is a single 145-line monolithic file with no bundle files or one-level-deep references for the longer reference material (e.g. the proxy flags, clientAction states), so it stops short of ideal content splitting.	4 / 5
	Total	16 / 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 is functional, naming the Botanalytics domain and including an explicit 'Use when' trigger, which satisfies the core what/when requirements. It is held back from higher scores by generic action verbs and a thin set of natural trigger phrases.

Suggestions

Replace generic verbs with concrete Botanalytics actions, e.g. 'Pull metric reports, filter by date range or bot, and invite team members' to raise specificity.

Add natural user phrasings and synonyms to the trigger clause, e.g. 'Use when the user mentions chatbot analytics, bot metrics, user retention, or wants to pull Botanalytics reports.'

Tie the 'Use when' clause to the actual Botanalytics concepts (metrics, reports, team members) so it is less likely to overlap with generic data skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Botanalytics integration') and lists 2-3 actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete, so it does not reach the 'several specific actions' bar of a 4.	3 / 5
Completeness	It answers both 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Botanalytics data'), but the 'when' clause is somewhat generic rather than packed with concrete trigger phrases, keeping it below a 5.	4 / 5
Trigger Term Quality	It surfaces relevant keywords ('Botanalytics', 'data', 'records', 'workflows', 'interact with Botanalytics data') but misses common natural variations a user might say, such as 'chatbot analytics', 'bot metrics', or 'bot performance'.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Botanalytics' gives it a clear niche with low conflict risk, but the generic 'manage data, records, and automate workflows' phrasing could overlap with broad data-management skills, so it is not maximally 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/botanalytics/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.