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

Blog Docs Log in Get started

float

Float integration. Manage Projects. Use when the user wants to interact with Float 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/float/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 delivers concrete, executable Membrane CLI guidance organized into a clear sequenced workflow with explicit state-based feedback loops, weakened mainly by a padded intro and broken step numbering.

Suggestions

Remove or tighten the opening marketing paragraph and the awkward "Those will be used to adjust tooling..." sentence so the body assumes Claude's competence.

Fix the step numbering: the text references "Step 2" and "1b" without a labeled Step 1a or Step 2 header, which muddies the connection workflow sequence.

Add an explicit pre-flight validation/checkpoint note before destructive actions (delete-person, update-*) in the Running actions section.

Dimension	Reasoning	Score
Conciseness	The opening marketing paragraph ("Float is a resource management and project planning tool... visualize team workload") and awkward filler ("Those will be used to adjust tooling to be used best with your harness") explain concepts Claude already knows and could be trimmed, though most of the CLI operational detail earns its place.	3 / 5
Actionability	Concrete copy-paste commands appear throughout (install, login, connection ensure, action list/run with --input JSON, proxy request) plus a flags table; minor gaps remain from placeholders and the all-"No description" actions table.	4 / 5
Workflow Clarity	A clear sequenced workflow runs from install through authenticate, connect, poll the state machine (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR with feedback loops), search, run, and proxy fallback; minor gaps come from broken step numbering (references to an unlabeled "Step 2") and no validation checkpoints for destructive create/update/delete actions.	4 / 5
Progressive Disclosure	The single file is well-organized with clear section headers and no nested references, though the large inline Popular actions and flags tables could arguably live in a reference file; as a self-contained skill the structure is good with minor organization gaps.	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 answers both what and when and names a distinct app, but it is thin on concrete actions and natural trigger terms, leaving it generic within the project-management space.

Suggestions

Add more concrete actions beyond "Manage Projects" (e.g., schedule tasks, track time, manage clients, log time off) to raise specificity.

Expand the "Use when" clause with concrete trigger phrases users would actually say (e.g., "when the user wants to manage Float projects, schedule tasks, track time, or view team workload").

Dimension	Reasoning	Score
Specificity	"Float integration. Manage Projects." names the domain and one concrete action, matching the anchor for naming a domain plus 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	Both the what ("Float integration. Manage Projects.") and the when ("Use when the user wants to interact with Float data") are present, though the trigger guidance is generic rather than concrete.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Float data" offers a relevant natural phrase but misses common variations or synonyms (projects, time tracking, schedules, resource planning).	3 / 5
Distinctiveness Conflict Risk	Naming the specific product Float gives it a clear niche with only minor overlap risk against other project-management tools.	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/float/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.