Name: minio
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

minio

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

Quality

66%

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/minio/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 commands and a reasonably clear workflow including connection-readiness checkpoints. Its main weaknesses are conceptual padding in the intro/overview and a couple of minor workflow-labeling gaps.

Suggestions

Trim or remove the opening 'MinIO is a high-performance...' paragraph and the MinIO Overview concept list; assume Claude knows what MinIO and buckets/objects are.

Fix the broken 'Step 2' reference by labeling the Searching/Running actions sections as Step 2, or remove the cross-references.

Add a brief verify step after running actions (e.g. check the `output`/error fields) to close the workflow loop for batch or state-changing operations.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command examples, but it opens by explaining what MinIO is ('high-performance, distributed object storage system... compatible with Amazon S3') and lists basic concepts (Bucket, Object, Policy, User, Group) that Claude already knows. This matches anchor 3 rather than the trimmed anchor 4.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run with --input, request proxy) plus a concrete flag table, covering the common cases. This matches anchor 5.	5 / 5
Workflow Clarity	There is a clear install→auth→connect→poll-until-READY→search→run sequence with a readiness checkpoint and error-state handling (BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR). Minor gaps — a 'Step 2' is referenced but never labeled, and there is no explicit verify-after-run loop — keep it at anchor 4 rather than 5.	4 / 5
Progressive Disclosure	No bundle files exist, so the skill is a single well-sectioned SKILL.md with no nested references and easy navigation. At ~140 lines with the proxy-flag table and best-practices inlined, it fits anchor 4 rather than the lean, reference-split anchor 5.	4 / 5
	Total	16 / 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 answers both 'what' and 'when' and is anchored to a clear product niche, but the capability verbs are generic and the trigger terms lack synonyms or extensions. It is competent but not maximally specific or comprehensive.

Suggestions

Replace generic verbs with concrete MinIO actions, e.g. 'Create and manage buckets, upload and download objects, configure access policies, and manage users and service accounts.'

Broaden trigger terms to include natural variations users say, such as 'S3-compatible storage', 'object storage', 'buckets', or '.minio'.

Tighten the 'when' clause to concrete triggers, e.g. 'Use when the user wants to manage MinIO/S3-compatible object storage, buckets, or objects.'

Dimension	Reasoning	Score
Specificity	It names the MinIO domain but the actions ('Manage data, records, and automate workflows') are generic and abstract rather than concrete operations. It does not reach anchor 3 because no genuinely concrete action (like 'extract' or 'create buckets') is stated.	2 / 5
Completeness	Both halves are present: 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with MinIO data'). The 'when' is explicit but generic, matching anchor 4 rather than the concrete-trigger anchor 5.	4 / 5
Trigger Term Quality	'MinIO' and 'MinIO data' are relevant keywords a user would say, but common variations, synonyms, or related terms are missing. It sits above anchor 2 (more than one generic keyword) but below anchor 4 (no broader natural-term coverage).	3 / 5
Distinctiveness Conflict Risk	The MinIO-specific trigger gives it a clear niche with minimal conflict risk, but the generic 'what' wording leaves minor overlap with general storage/data skills. This fits anchor 4 rather than the fully-distinct anchor 5.	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/minio/SKILL.md
Commit: f484c82

Reviewed: 6 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.