Name: chatbase
Rating: 60.8 (1 reviews)
Author: membranedev

chatbase

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

Quality

71%

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/chatbase/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 content is highly actionable with concrete CLI commands and a well-structured connection workflow including state-based checkpoints. Minor improvements are tightening the intro prose, fixing the dangling 'Step 2' reference, and optionally splitting the flag table into a reference file.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command examples and a flag table, but the intro paragraph explaining what Chatbase is and phrases like 'so you can focus on the integration logic rather than auth plumbing' over-explain slightly, fitting the score-4 anchor of efficient with minor trimmable instances.	4 / 5
Actionability	Copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) with concrete flags and a JSON-input example cover the common cases, matching the fully-executable score-5 anchor.	5 / 5
Workflow Clarity	The connection flow is a clear sequence with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, but 'Step 2' is referenced without a corresponding labeled section, leaving a minor gap below the score-5 anchor.	4 / 5
Progressive Disclosure	No bundle files exist and the content is a single well-organized file with clear section headers and no nested references; it sits at score 4 rather than 5 because the body exceeds ~50 lines and could offload the proxy-flag table or clientAction detail to a reference.	4 / 5
	Total	17 / 20 Passed

Description

61%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 has an explicit trigger clause and a clearly distinct Chatbase niche, but its capability list is generic ('manage data, records, automate workflows') rather than concrete. Strengthening the action verbs and adding natural trigger synonyms would raise specificity and trigger-term quality.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Chatbase actions such as 'manage chatbots, send messages, and view analytics'.

Add natural trigger synonyms to the 'Use when' clause, e.g. 'Use when the user wants to manage Chatbase chatbots, messages, analytics, or API keys'.

Keep the explicit third-person 'Use when...' trigger but tie it to the specific resources listed in the body (Chatbots, Messages, Analytics, API Keys).

Dimension	Reasoning	Score
Specificity	The description names the Chatbase domain but the actions ('Manage data, records, and automate workflows') are generic and not concrete Chatbase-specific operations, matching the anchor for named domain with minimal/generic actions rather than the 1-3 concrete actions at score 3.	2 / 5
Completeness	Both a 'what' (Chatbase integration, manage data/records, automate workflows) and an explicit 'Use when...' trigger clause are present; it is not a 5 because the 'what' actions remain vague rather than concrete.	4 / 5
Trigger Term Quality	'Chatbase' and 'Chatbase data' are relevant natural keywords, but common variations, synonyms, or file extensions are missing, fitting the score-3 anchor of some relevant keywords without common variations.	3 / 5
Distinctiveness Conflict Risk	'Chatbase' is a distinct named product with a clear niche trigger ('interact with Chatbase data'), giving minimal overlap risk with other skills.	5 / 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/chatbase/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.