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

boostai

Boost.ai integration. Manage data, records, and automate workflows. Use when the user wants to interact with Boost.ai 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/boostai/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 delivers strong, copy-paste-ready executable guidance and a well-validated connection workflow with state-based feedback loops. Its weaknesses are conciseness (a marketing intro, a generic concept tree, and an empty 'Popular actions' section) and minor workflow gaps such as an orphaned 'Step 2' reference and missing action-run error handling.

Suggestions

Cut the marketing-style opening paragraph and the generic chatbot concept tree (Intent/Entity/Flow/Variable) since Claude already knows these concepts, keeping only Boost.ai-specific structure.

Replace the empty 'Popular actions' section with a few concrete example actions (e.g. a sample intent report or transcript query) or remove it to avoid restating the search command.

Fix the orphaned 'Step 2' reference (label the next section 'Step 2: Search for actions' or reword) and add brief error-handling guidance for failed action runs (check the response error field and retry).

Dimension	Reasoning	Score
Conciseness	Mostly efficient commands, but the marketing-style intro paragraph ('used by enterprises looking to improve efficiency...'), the generic chatbot concept tree (Intent/Entity/Flow/Variable that Claude already knows), and the empty 'Popular actions' section that only restates a search command are unnecessary padding, matching 'mostly efficient but includes some unnecessary explanation'; not a 4 because the padding is more than minor.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands across the common cases (install, login, connection ensure/get with --wait, action list/run, request) plus a flags table and output-field notes, matching the 'fully executable; copy-paste ready; covers common cases' anchor.	5 / 5
Workflow Clarity	The connection workflow has explicit state-based validation and feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED polling and retry), but there are minor gaps: an orphaned 'skip to Step 2' with no labeled Step 2, and no error-handling guidance for action-run failures, fitting 'clear sequence with most checkpoints; minor validation gaps' rather than the 5 anchor.	4 / 5
Progressive Disclosure	No bundle files exist; the ~150-line body is well-sectioned with clear headers and a single one-level external doc link with no nested references, but minor organization gaps (the empty/redundant 'Popular actions' section and a trimmable overview tree) keep it at 'good structure; minor gaps' rather than the cleanly-split 5 anchor.	4 / 5
	Total	16 / 20 Passed

Description

70%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 states both what the skill does and when to use it with a Boost.ai-specific trigger, but its action verbs are generic ('manage', 'automate workflows') and the trigger is a single condition without synonyms or variations. It is distinct thanks to the named platform but loses specificity from the generic vocabulary.

Suggestions

Replace generic verbs with concrete Boost.ai actions (e.g., 'List and run Boost.ai intents, entities, and flows; pull intent and engagement reports') to lift specificity toward a 5.

Expand the 'Use when...' clause with concrete trigger phrases and synonyms, e.g. 'Use when the user wants to manage Boost.ai chatbots, intents, flows, or reports, or interact with Boost.ai data.'

Add common user phrasings or file/term variants (chatbot, intent, flow, transcript) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the Boost.ai domain plus a couple of actions ('Manage data, records, and automate workflows'), but the verbs are generic ('manage', 'automate') rather than concrete, matching the '1-2 concrete actions, not comprehensive' anchor; not a 2 because multiple actions are explicitly listed.	3 / 5
Completeness	Both the 'what' (Boost.ai integration; manage data, records, automate workflows) and an explicit 'Use when...' trigger are present, but the 'when' is a single generic condition rather than multiple concrete trigger phrases, so it sits at 'both present; when could be more explicit' rather than the 5 anchor.	4 / 5
Trigger Term Quality	Includes relevant keywords (Boost.ai, data, records, workflows) and a natural trigger phrase ('Use when the user wants to interact with Boost.ai data'), but lacks synonyms and variations, fitting 'good keyword coverage; a few natural terms missing' rather than the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	Tied to a named platform (Boost.ai) with a specific trigger ('interact with Boost.ai data') giving low conflict risk, but the generic 'manage data, records' verbs create minor overlap with general data-management skills, fitting 'mostly distinct; minor overlap' rather than the clear-niche 5 anchor.	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/boostai/SKILL.md
Commit: f484c82

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