Name: questdb
Rating: 59.2 (1 reviews)
Author: membranedev

questdb

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

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/questdb/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 is actionable and well-structured with a clear connection workflow and concrete CLI commands throughout. Its main weaknesses are an unnecessary introductory explainer about QuestDB itself and minor redundancy between the actions sections.

Suggestions

Cut or drastically shorten the opening paragraph explaining what QuestDB is and who uses it; Claude already knows this and it adds token cost.

Standardize on one invocation form (either `membrane` or `npx @membranehq/cli`) to avoid confusing mixed usage in examples.

Add an explicit verification step after running actions (e.g. inspect the `output` field / confirm row count) and merge 'Popular actions' with 'Searching for actions' to remove redundancy.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explains what QuestDB is and who uses it ('QuestDB is an open-source time-series database designed for high-performance data ingestion... used by developers...'), restating concepts Claude already knows; the rest is reasonably efficient but that padding is more than minor.	3 / 5
Actionability	Provides concrete, copy-paste-ready `membrane` commands (login, connection ensure, action list/run, request) with flags, a JSON-input example, and an options table, with only minor gaps such as the mixed `membrane` vs `npx @membranehq/cli` invocation style.	4 / 5
Workflow Clarity	The connection flow is a clear sequenced process with explicit state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a polling feedback loop, but running actions lacks an explicit verify-the-result step.	4 / 5
Progressive Disclosure	Single well-organized file with clear section headers and no nested references; structure is good, though the 'Popular actions' section partly duplicates 'Searching for actions' and no detail is split into separate files.	4 / 5
	Total	15 / 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 covers both capability and trigger guidance with an explicit 'Use when' clause and a distinct product name. Its main weakness is generic action verbs ('manage', 'automate workflows') that undersell the concrete time-series/querying capabilities.

Suggestions

Replace generic verbs with concrete QuestDB-specific actions, e.g. 'Query time-series data with SQL, ingest records, and inspect table schemas.'

Add natural synonyms users say, such as 'time-series data', 'SQL queries', or 'QuestDB tables', to broaden trigger coverage.

Tighten the 'when' clause to reference the triggering nouns (e.g. 'Use when the user wants to query or ingest time-series data in QuestDB.').

Dimension	Reasoning	Score
Specificity	Names the QuestDB domain plus three actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete operations like querying time-series data or ingesting records, so it sits at the lower edge of 'names domain and 1-2 actions'.	3 / 5
Completeness	Explicitly answers both what ('QuestDB integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with QuestDB data.'), with the 'when' concrete but slightly generic.	4 / 5
Trigger Term Quality	Includes natural trigger terms ('QuestDB', 'data', 'records') and an explicit 'Use when the user wants to interact with QuestDB data' phrase, though it omits common synonyms like time-series, query, or SQL.	4 / 5
Distinctiveness Conflict Risk	The specific named product 'QuestDB' gives it a clear niche and low conflict risk, though the generic 'manage data, records' phrasing leaves minor overlap with other database skills.	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/questdb/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.