Name: influxdb-cloud
Rating: 52.8 (1 reviews)
Author: membranedev

influxdb-cloud

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

Quality

59%

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/influxdb-cloud/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.

The skill is action-dense with solid executable commands and a clear connection state machine, but it is padded with InfluxDB background and empty overview bullets, lacks validation feedback for action/proxy execution, and is monolithic with no reference files.

Suggestions

Trim the InfluxDB explainer and the empty-bullet Overview list; assume Claude knows what a time series database is.

Add an explicit validation/verify step after running actions or proxy requests (e.g., check the response status and confirm the expected output before proceeding) to satisfy the batch/destructive-operation feedback-loop requirement.

Move the full clientAction spec and proxy flag table into a separate reference file and link to it one level deep to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but it includes unnecessary explanation Claude already knows ("InfluxDB Cloud is a time series database as a service...used by developers and organizations...") plus a low-value empty-bullet Overview list and promotional phrasing, fitting the mostly-efficient-with-some-unnecessary-explanation anchor.	3 / 5
Actionability	Concrete, copy-paste-ready commands with flags and --json examples are provided throughout (install, login, connection ensure, action run, proxy), with only minor gaps such as unresolved CONNECTION_ID placeholders and a thin Popular actions section.	4 / 5
Workflow Clarity	The connection workflow is well sequenced with a state machine and polling checkpoints, but running actions and proxy requests (potentially destructive/batch operations) lack any validate/verify feedback loop, which caps workflow clarity per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist, so everything lives in one SKILL.md; section headers give it some structure, but content that could be split out (full clientAction spec, proxy flag table) is inlined with no one-level-deep references, fitting the some-structure-but-could-be-better-organized anchor.	3 / 5
	Total	13 / 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 answers both what and when with an explicit trigger tied to a distinct niche, but its capabilities are phrased generically and it lacks natural synonyms a user would actually say.

Suggestions

Replace generic verbs with concrete InfluxDB actions, e.g. "Query and write time series data to buckets, manage organizations and tasks."

Add natural trigger synonyms users say, such as "time series data", "metrics", or "Flux queries".

Keep the existing "Use when..." trigger but expand the "what" to list 2-3 specific capabilities for higher specificity.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain but the actions are minimal and generic rather than concrete (e.g., no mention of querying, writing, or buckets), fitting the anchor between 2 and 3 but closer to a generic-action anchor.	2 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with InfluxDB Cloud data") are present, with the when being clear though the what is somewhat generic.	4 / 5
Trigger Term Quality	"InfluxDB Cloud" and "interact with InfluxDB Cloud data" provide a relevant natural keyword, but common synonyms users would say (time series, metrics, Flux, .influx) are missing, so it sits at the some-relevant-keywords anchor.	3 / 5
Distinctiveness Conflict Risk	"InfluxDB Cloud integration" carves out a clear, specific niche with a distinct product-name trigger and 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/influxdb-cloud/SKILL.md
Commit: f484c82

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