Name: flexie
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

flexie

Flexie integration. Manage Organizations, Pipelines, Users, Filters. Use when the user wants to interact with Flexie data.

Quality

61%

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/flexie/SKILL.md

Quality

Content

50%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 highly actionable, executable Membrane CLI commands with a clear connection-state workflow, but it is weighed down by a large padded entity list, inlined reference content that belongs in separate files, and missing validation guidance for destructive operations.

Suggestions

Remove or relocate the ~130-line Flexie Overview entity list; if kept, move it to a references file and replace the inline wall with a one-line pointer, since it adds token cost without actionable detail.

Add an explicit validation/confirmation checkpoint before destructive actions (e.g. verify the record exists via get-* and confirm the ID before running delete-* commands) to lift workflow clarity above the destructive-operation cap.

Move the 20-row popular actions table into a separate reference file and link to it from the body to improve progressive disclosure and reduce inline reference bulk.

Dimension	Reasoning	Score
Conciseness	The ~130-line "Flexie Overview" bulleted entity list (Contact through Smart Assistant) ending with "Use action names and parameters as needed" is a heavily padded section that conveys little actionable information, making the body noticeably verbose.	2 / 5
Actionability	Concrete copy-paste-ready `membrane` CLI commands cover install, auth, connection, action search/run, and proxy, with only minor gaps such as the literal "QUERY" intent placeholder and the action-key vs. actionId mismatch in the popular actions table.	4 / 5
Workflow Clarity	The connection flow has explicit state-checking checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-after-action feedback loop, but the skill supports destructive delete actions (delete-account, delete-contact, etc.) with no validation or confirmation guidance, capping this at 3.	3 / 5
Progressive Disclosure	Section headers provide some structure, but large reference blocks (the entity list and the 20-row popular actions table) are inlined rather than split into separate files, and no bundle references are signaled.	3 / 5
	Total	12 / 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 "Use when" trigger and a distinctive brand anchor, but its action vocabulary is generic ("Manage") and the trigger clause is broad rather than enumerating concrete user phrases.

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Pipelines, Users, Filters" names the Flexie domain and four concrete entities, but relies on a single generic verb ("Manage") rather than distinct actions, so it is not comprehensive like the score-4 anchor.	3 / 5
Completeness	It states a clear "what" ("Manage Organizations, Pipelines, Users, Filters") and an explicit "Use when the user wants to interact with Flexie data" trigger, but the "when" clause is generic rather than enumerating concrete triggers, matching the score-4 anchor.	4 / 5
Trigger Term Quality	The brand "Flexie" appears twice and is paired with natural entity nouns (Organizations, Pipelines, Users, Filters), giving good keyword coverage, though a few common variations (e.g. contacts, deals, leads) are missing.	4 / 5
Distinctiveness Conflict Risk	The unique product brand "Flexie" combined with "interact with Flexie data" carves a clear niche with minimal conflict risk against 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/flexie/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.