Name: lakefs
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

lakefs

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

Quality

65%

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/lakefs/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 strong, command-driven integration guide with a clear connection workflow, polling feedback loops, and error handling. Its weak spots are conceptual padding in the intro, placeholder-dependent examples, and inconsistent step numbering.

Suggestions

Cut the opening 'LakeFS is an open-source platform...' paragraph and the Membrane concept prose; assume Claude knows the domain and keep only operational guidance.

Fix the step numbering: label '1a' for connection ensure and add an explicit 'Step 2' anchor so 'skip to Step 2' resolves, or restructure as a single numbered list.

Make 'Popular actions' actually list common LakeFS actions (e.g. list commits, create branch, upload object) instead of restating the discovery command.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph explains what LakeFS is ('LakeFS is an open-source platform that adds Git-like version control...') and adds conceptual padding about Membrane that Claude does not need, fitting the 'mostly efficient but includes some unnecessary explanation' anchor rather than the lean anchor of 4.	3 / 5
Actionability	It provides many concrete, executable commands (install, login, connection ensure, action list/run, request proxy) with a flag table, but relies on placeholders like CONNECTION_ID, <actionId>, and <id> and the 'Popular actions' section only repeats the discovery command rather than listing real actions, leaving minor gaps below the fully copy-paste anchor of 5.	4 / 5
Workflow Clarity	The connect-then-poll-then-act sequence is clear with feedback loops (poll until READY, re-poll after clientAction) and error handling for CONFIGURATION_ERROR/SETUP_FAILED, but the numbering is inconsistent ('1b' with no 1a, a dangling 'skip to Step 2' reference with no labeled Step 2), which keeps it below the explicit-checklist anchor of 5.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections with no nested references and no bundle files, but at ~158 lines all material is inlined and some content (the proxy flag table, the clientAction state-machine details) could live in a separate reference, fitting the 'good structure, minor organization gaps' anchor rather than the ideally-split anchor of 5.	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 clearly names the LakeFS niche and includes an explicit 'Use when' trigger, satisfying both what and when. Its main weakness is generic, non-concrete action language and limited trigger-term variation.

Suggestions

Replace generic verbs with concrete LakeFS operations, e.g. 'Branch, commit, tag, and revert data lakes; manage objects and refs.'

Expand trigger terms with natural user phrasings such as 'versioned data lake', 'data lake branching', or 'lakefs repository/branch'.

Tighten the 'when' clause to name concrete scenarios, e.g. 'Use when the user wants to version, branch, or commit changes to data in LakeFS.'

Dimension	Reasoning	Score
Specificity	Names the domain (LakeFS) and a few actions ('Manage data, records, and automate workflows'), but the actions are generic categories rather than concrete operations, so it sits between the minimal/generic anchor (2) and the comprehensive anchor (4).	3 / 5
Completeness	It has both a 'what' ('LakeFS integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with LakeFS data.'), but the 'what' is generic and the 'when' could be more specific, so it does not reach the fully concrete anchor of 5.	4 / 5
Trigger Term Quality	'LakeFS' and 'interact with LakeFS data' give some natural trigger terms, but common variations or synonyms a user might say are missing, matching the 'some relevant keywords but missing variations' anchor rather than the comprehensive coverage of 4.	3 / 5
Distinctiveness Conflict Risk	'LakeFS' is a specific platform niche with a distinct trigger, giving low conflict risk, but the generic action verbs ('manage data, records, automate workflows') leave minor overlap risk with adjacent data skills, keeping it below the clear-niche anchor of 5.	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/lakefs/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.