Name: nextcloud
Rating: 60 (1 reviews)
Author: membranedev

nextcloud

Nextcloud integration. Manage Users, Groups, Files, Folders, Calendars, Contacts and more. Use when the user wants to interact with Nextcloud data.

Quality

70%

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/nextcloud/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 a solid, actionable integration guide with a well-validated connection workflow and concrete commands throughout. It loses points mainly to mild verbosity (background on Nextcloud and Membrane) and some redundancy between the action-discovery sections.

Suggestions

Trim the introductory "Nextcloud is a self-hosted file sync and collaboration platform..." paragraph and the "so you can focus on the integration logic" clause, which explain concepts Claude already knows.

Consolidate the redundant "Searching for actions" and "Popular actions" sections into one discovery block to remove the repeated `action list` command.

Add a short validation note for action results (e.g. check the `output`/`error` fields before reporting success) to strengthen the workflow checkpoints for potentially destructive Nextcloud operations.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes unnecessary explanation Claude likely already knows (e.g. "Nextcloud is a self-hosted file sync and collaboration platform...") and mild fluff like "so you can focus on the integration logic rather than auth plumbing."	3 / 5
Actionability	Provides copy-paste-ready commands for the common cases (install, login, connection ensure, action list/run, request proxy) plus a flags table; minor gaps remain since placeholders like <actionId> and CONNECTION_ID are not concretely instantiated.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-after-action feedback loop; minor validation gaps exist around verifying action-run results before proceeding.	4 / 5
Progressive Disclosure	Single well-organized file with clear section headers serving as navigation and no nested references; slightly short of 5 because the "Popular actions" section duplicates the earlier "Searching for actions" command and the proxy flags table could live in a reference.	4 / 5
	Total	15 / 20 Passed

Description

73%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 well-structured with an explicit what-and-when pairing and a distinct, low-conflict niche. Its main weakness is the generic "Manage" verb, which lists objects rather than concrete actions, leaving specificity slightly short of the top anchor.

Suggestions

Replace the generic "Manage" verb with a few concrete actions (e.g., "create and delete users, share files and folders, sync calendars and contacts") to lift specificity.

Tighten the trigger clause to mirror natural phrasing, e.g. "Use when the user wants to manage Nextcloud users, files, shares, calendars, or contacts."

Consider trimming "and more" — it adds little specificity and slightly dilutes the concrete entity list.

Dimension	Reasoning	Score
Specificity	Names the domain and lists many specific managed entities ("Users, Groups, Files, Folders, Calendars, Contacts") but uses a single generic verb ("Manage") rather than multiple distinct concrete actions, so coverage of actions is not comprehensive.	3 / 5
Completeness	Explicitly states both what ("Manage Users, Groups, Files, Folders, Calendars, Contacts and more") and when ("Use when the user wants to interact with Nextcloud data"), matching the anchor where both are present but the trigger could be more specific.	4 / 5
Trigger Term Quality	Includes natural terms ("Users, Groups, Files, Folders, Calendars, Contacts") and an explicit "Use when the user wants to interact with Nextcloud data" clause; keyword coverage is good though "interact with ... data" is slightly generic.	4 / 5
Distinctiveness Conflict Risk	Nextcloud is a clear, named niche with distinct triggers and a specific data model, giving minimal overlap risk with other skills.	5 / 5
	Total	16 / 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/nextcloud/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.