CtrlK
BlogDocsLog inGet started
Tessl Logo

kvdb

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

56

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/kvdb/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 clear connection workflow, but it omits validation/verification before destructive data operations and lacks a fully worked end-to-end example.

Suggestions

Add a validation/verification checkpoint before destructive or batch operations (e.g., read-back a key after a write, or confirm a key exists before DELETE) so the data workflow clears the destructive-operations cap.

Include one fully worked end-to-end example with concrete values (a real connection id, a specific action, and sample JSON output) to turn placeholders into copy-paste-ready guidance.

Trim prose like "Use action names and parameters as needed." and the agent-types sentence to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is dominated by concrete, copy-pasteable commands with only light explanatory prose (e.g., "This is the fastest way to get a connection..." and the agent-types aside), so it is efficient with minor trimmable over-explanation rather than lean throughout.

4 / 5

Actionability

It gives executable commands for install, login, connection ensure, action list/run, and proxy with a full flag table, but relies on unfilled placeholders (<actionId>, CONNECTION_ID) and lacks a worked end-to-end example with real values and parsed output.

4 / 5

Workflow Clarity

Sequencing and the connection-state polling feedback loop (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) are clear, but KVdb is a database where destructive/batch writes and DELETEs occur via action run and proxy with no verification step before acting, capping workflow clarity at 3 per the destructive-operations rule.

3 / 5

Progressive Disclosure

No bundle files exist and the skill is a single well-organized SKILL.md with clearly headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) and no nested references, giving good structure and easy navigation without a true overview-to-detail split.

4 / 5

Total

15

/

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.

The description covers what and when adequately with a clear, distinct KVdb trigger, but relies on generic action verbs and a single trigger phrase rather than concrete capabilities and varied keywords.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete KVdb operations such as store, retrieve, list, and delete key-value pairs.

Broaden the trigger with natural synonyms, e.g. "Use when the user wants to store, read, or update data in KVdb or mentions a key-value bucket."

Mention the key-value/bucket concept so the "what" is more specific and less interchangeable with other database skills.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the KVdb domain plus several actions, but the verbs are generic rather than concrete (no store/retrieve/delete specifics), placing it just above the minimal anchor-2 example.

3 / 5

Completeness

It provides both a "what" ("KVdb integration. Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with KVdb data"), but the trigger is single-scoped and the "what" is not comprehensive, so it stops short of a 5.

4 / 5

Trigger Term Quality

The phrase "interact with KVdb data" surfaces the keyword "KVdb" a user would naturally say, but offers no synonyms or variations beyond repeating the product name, matching the anchor-3 example "Works with PDF files".

3 / 5

Distinctiveness Conflict Risk

KVdb is a uniquely named service with a distinct trigger ("interact with KVdb data"), giving low conflict risk, but the generic action phrasing keeps it from a clean 5.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.