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

arangodb

ArangoDB integration. Manage data, records, and automate workflows. Use when the user wants to interact with ArangoDB 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/arangodb/SKILL.md

Quality

Content

63%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 body is actionable and gives a clear connection workflow with state-based checkpoints, but it spends tokens explaining ArangoDB basics Claude already knows and inlines reference-style material rather than splitting it out. No bundle files exist, so progressive disclosure relies on the single in-body structure.

Suggestions

Remove the introductory explanation of what ArangoDB is and the product overview bullets; Claude already knows this — lead directly with how to use the skill.

Extract the proxy flag reference table and the clientAction schema field listing into a separate REFERENCE.md (or shorten to the essential flags), since no bundle files currently exist.

Add an explicit verification step after running actions against the database (e.g. checking the response `output`/`error` fields) to strengthen the workflow's feedback loop for a database-operation skill.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with command examples, but it explains concepts Claude already knows (a multi-paragraph overview of what ArangoDB is) and includes redundant discover/search instructions that could be tightened.	3 / 5
Actionability	It provides concrete, copy-pasteable CLI commands for install, auth, connection, searching and running actions, plus a flag reference table, with only minor gaps (e.g. actionId placeholders are unexplained).	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based branching (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-then-check loop, though it lacks explicit verification after action runs for a database skill.	4 / 5
Progressive Disclosure	There is section-based structure and no external bundle files are present, but the 'Popular actions'/'Running actions'/'Proxy' sections inline what reads like API-reference material (flag tables, schema field lists) that could be split into separate reference files.	3 / 5
	Total	14 / 20 Passed

Description

57%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 is third person and includes an explicit 'Use when' trigger, satisfying the completeness floor, but its verbs are generic ('Manage data, records') rather than concrete ArangoDB operations. Tightening the actions to specific capabilities (AQL queries, collections, graphs) would lift specificity and trigger quality.

Suggestions

Replace generic verbs ('Manage data, records, automate workflows') with concrete ArangoDB actions such as 'Run AQL queries, manage collections, documents, and graphs'.

Expand the 'when' trigger with natural phrasing users actually say, e.g. 'Use when the user mentions ArangoDB, AQL queries, or wants to query/manage ArangoDB collections or graphs'.

Add common synonyms/aliases (AQL, collections, documents, graph data) to broaden natural trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (ArangoDB) and a couple of generic verbs ('Manage data, records, and automate workflows') but the actions are minimal and non-specific rather than concrete operations like 'run AQL queries' or 'create collections'.	2 / 5
Completeness	It has both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' clause ('Use when the user wants to interact with ArangoDB data'), though the 'when' could be more specific with concrete triggers.	4 / 5
Trigger Term Quality	'ArangoDB data' and 'interact with ArangoDB data' give a relevant keyword but miss natural synonyms or file/extension-style variations users would say, so coverage is partial.	3 / 5
Distinctiveness Conflict Risk	'ArangoDB' is a specific named product giving it a clear niche and minimal conflict risk, though the generic 'data'/'records' phrasing leaves minor overlap with general database skills.	4 / 5
	Total	13 / 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/arangodb/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.