Name: boost
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

boost

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

Quality

62%

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

Quality

Content

67%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 executable guidance and a clearly sequenced connection workflow with real validation checkpoints, organized into clean sections. Its main weakness is conciseness — marketing-style overview prose and some redundant explanation pad the otherwise command-focused content.

Suggestions

Remove the introductory paragraph explaining what Boost is and who uses it; Claude does not need the platform's marketing context.

Trim explanatory prose around connection states where the state names are largely self-explanatory, keeping only the required-action guidance.

The 'Official docs' link points to Microsoft Semantic Kernel (https://learn.microsoft.com/en-us/semantic-kernel/), which is unrelated to Boost — replace it with the correct Boost documentation URL or remove it.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but includes unnecessary prose Claude doesn't need ('Boost is a social media management platform... used by small businesses and creators', 'so you can focus on the integration logic rather than auth plumbing'), matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request) with a flag table and a JSON-input example, fitting 'mostly executable guidance; concrete code or commands with minor gaps'; placeholders like CONNECTION_ID keep it just short of copy-paste-complete.	4 / 5
Workflow Clarity	The install → login → connection ensure → poll-for-ready → search → run sequence is clear with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a feedback loop (poll again after the user acts), matching 'clear sequence with most checkpoints present'; the inconsistent step labels ('Step 2' vs '1b') are a minor gap.	4 / 5
Progressive Disclosure	With no bundle files present, all content is inline but well sectioned (Overview, Working with Boost, install/auth/connecting/searching/proxy/best practices), matching 'good structure; most content appropriately placed'; the connection state-machine detail and proxy flag table could arguably live in separate reference files.	4 / 5
	Total	15 / 20 Passed

Description

57%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 pairs a what/when structure with an explicit 'Use when' trigger, but its capability list is vague and generic rather than naming Boost's concrete features. Trigger-term coverage is adequate but not comprehensive.

Suggestions

Replace the generic verbs with concrete Boost capabilities, e.g. 'Schedule posts, track analytics, manage workspaces and members, and view notifications.'

Add natural trigger terms users would actually say, such as 'social media posts, scheduling, analytics, or Boost campaigns'.

Tighten the 'when' clause to reference specific Boost entities (campaigns, posts, workspaces) to further reduce overlap with generic data skills.

Dimension	Reasoning	Score
Specificity	The description names the domain (Boost) but its actions are generic — 'Manage data, records, and automate workflows' are abstract verbs rather than concrete capabilities like scheduling posts or tracking analytics, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states both what ('Boost integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with Boost data.'), satisfying both halves; the 'when' is explicit but the 'what' is generic, so it lands at 'has both what and when; when could be more specific' rather than a 5.	4 / 5
Trigger Term Quality	It surfaces relevant keywords ('Boost data', 'records', 'workflows') and an explicit trigger phrase ('Use when the user wants to interact with Boost data'), but lacks common variations and synonyms users would naturally say, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The named platform 'Boost' gives it a clear, distinct niche with minimal conflict risk, matching 'mostly distinct; minor overlap risk with closely related skills'; generic verbs keep it just short of a 5.	4 / 5
	Total	13 / 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/boost/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.