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

Blog Docs Log in Get started

appwrite

Appwrite integration. Manage Accounts, Projects. Use when the user wants to interact with Appwrite 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

75%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 highly actionable with concrete, executable Membrane CLI commands and a well-validated connection workflow, but it carries avoidable padding (an Appwrite definition paragraph, an entity overview, and a 'No description' action table) that hurts token efficiency. Organization is good though it leans on inline content that could be externalized.

Suggestions

Remove the opening definitional paragraph ('Appwrite is an open-source, self-hosted platform...') and the Appwrite Overview entity tree — Claude already knows what Appwrite is.

Drop or replace the 'Popular actions' table whose every row says 'No description'; either populate real descriptions or point to `membrane action list --intent` discovery instead.

Add a brief validation note in 'Running actions' for destructive operations (e.g. confirm before create/delete, check the `output`/error field before proceeding).

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands, but includes unnecessary explanation (the opening paragraph defining Appwrite, the Appwrite Overview entity tree) and a 20-row 'Popular actions' table where every entry reads 'No description', which is padding noise.	3 / 5
Actionability	Provides copy-paste-ready, fully executable commands covering the common cases — install CLI, login (incl. headless completion), connection ensure/wait, action list, action run with --input JSON, and request proxy — each with concrete flags documented in tables.	5 / 5
Workflow Clarity	Clear sequenced workflow (install → auth → connect → search → run) with explicit validation checkpoints and a feedback loop for connection state (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but the 'Running actions' step lacks result validation for potentially destructive actions like create/delete.	4 / 5
Progressive Disclosure	Single well-organized SKILL.md with clear section headers and no nested references; however the large inline 'Popular actions' table and CLI flag reference could be split into a separate reference file for a cleaner overview.	4 / 5
	Total	16 / 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 is third-person, includes an explicit 'Use when...' trigger, and names a clear niche (Appwrite), but its action list is narrow and generic ('Manage Accounts, Projects') and it omits many natural trigger terms. It sits solidly above the vague baselines but below the comprehensive exemplars.

Suggestions

Broaden the action list to match Appwrite's actual surface, e.g. 'Manage Accounts, Databases, Collections, Documents, Storage, Functions, Users, and Teams.'

Add natural trigger synonyms users would say, e.g. 'Use when the user wants to manage Appwrite databases, collections, documents, buckets, files, or users.'

Replace the generic verb 'Manage' with more specific concrete verbs (create, list, query) to lift specificity.

Dimension	Reasoning	Score
Specificity	Quotes 'Manage Accounts, Projects' which names the Appwrite domain plus two concrete-ish actions, but 'Manage' is generic and coverage is not comprehensive (no mention of Databases, Storage, Functions, Users, Teams).	3 / 5
Completeness	Provides a clear 'what' ('Appwrite integration. Manage Accounts, Projects.') and an explicit 'when' ('Use when the user wants to interact with Appwrite data.'), though the 'when' trigger could be more specific.	4 / 5
Trigger Term Quality	Includes 'Appwrite', 'Accounts', 'Projects', and 'Appwrite data' as relevant keywords, but misses common natural variations and synonyms a user might say (e.g. collections, documents, buckets, functions, users).	3 / 5
Distinctiveness Conflict Risk	'Appwrite integration' is a clear, distinct niche with the Appwrite trigger term minimizing conflict risk, though 'Manage Accounts, Projects' has minor overlap with generic account/project management skills.	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/appwrite/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.