Name: appbaseio
Rating: 53.6 (1 reviews)
Author: membranedev

appbaseio

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

Quality

60%

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

Quality

Content

57%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.

A command-heavy, reasonably executable CLI-wrapper guide with a strong connection-state workflow, weakened by inline content that belongs in reference files and by missing validation before destructive proxy operations.

Suggestions

Add an explicit validation/verification checkpoint before running destructive proxy requests (e.g. confirm method and target, or dry-run GET before mutating DELETE/PUT) to lift workflow_clarity above the destructive-op cap.

Move the nested Appbase.io feature tree and the proxy-flags table into reference files (e.g. references/features.md, references/proxy.md) and link to them from the body to improve progressive disclosure.

Trim explanatory prose such as 'so you can focus on the integration logic rather than auth plumbing' and the broad feature listing to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is largely command- and table-driven, but the nested feature tree ('Search Relevance', 'Analytics', 'AI Insights' ... 'Help/Documentation/Support') and prose like 'so you can focus on the integration logic rather than auth plumbing' add padding Claude does not need.	3 / 5
Actionability	Concrete copy-paste-ready commands cover the common cases (install, login, connection ensure, action list/run, proxy flags table), with only minor gaps such as placeholder substitution (CONNECTION_ID, actionId) and no worked end-to-end example.	4 / 5
Workflow Clarity	There is a clear install→login→connect→poll sequence with an explicit READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR feedback loop, but the proxy path enables destructive DELETE/PUT with no pre-operation validation, capping the score at 3 per the destructive-operation rule.	3 / 5
Progressive Disclosure	No bundle files exist and the entire ~168-line guide is inline with sections; the feature tree and proxy-flag table are content that could live in separate reference files, and no one-level-deep references are signaled.	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.

A clear, brand-scoped description that answers both what and when with executable-leaning language, held back by generic action wording and a thin set of trigger synonyms.

Suggestions

Add concrete trigger synonyms and surface terms (e.g. ReactiveSearch, search relevance, analytics, query rules) to the 'Use when...' clause to raise trigger_term_quality and completeness.

Replace generic verbs ('Manage data, records, and automate workflows') with more specific capabilities (e.g. 'search, index, and curate records; configure synonyms and query rules') to lift specificity.

Dimension	Reasoning	Score
Specificity	'Manage data, records, and automate workflows' names the domain plus two action clusters, matching the '1-2 concrete actions but not comprehensive' anchor; the actions remain generic rather than several specific ones, so it does not reach 4.	3 / 5
Completeness	It states both the what ('Appbase.io integration. Manage data, records, and automate workflows') and the when ('Use when the user wants to interact with Appbase.io data'), but the when-clause is a single scoped phrase rather than rich concrete triggers, so it does not reach 5.	4 / 5
Trigger Term Quality	'Appbase.io' and 'data' are relevant keywords but common variations or synonyms (e.g. ReactiveSearch, search) are missing, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The explicit 'Appbase.io' brand tie-in gives a clear niche with minimal conflict, but the generic action vocabulary ('manage data, records, automate workflows') carries minor overlap risk with general data/search skills, keeping it just below 5.	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/appbaseio/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.