Name: kanbanflow
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

kanbanflow

KanbanFlow integration. Manage Boards, Users, Tags. Use when the user wants to interact with KanbanFlow data.

Quality

67%

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

Quality

Content

61%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 actionable and well-structured with concrete Membrane CLI commands covering the common cases. It loses points for an unnecessary marketing intro, redundant command repetition, and the absence of validation checkpoints for potentially destructive actions.

Suggestions

Remove or trim the introductory paragraph describing what KanbanFlow is and who uses it; Claude does not need the marketing context.

Deduplicate the `action list` command that appears in both "Searching for actions" and "Popular actions".

Add an explicit verification step before running mutating actions (e.g. confirm the discovered ACTION_ID and inspect its inputSchema before `action run`).

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command-focused content, but the marketing-style intro ("KanbanFlow is a web-based project management application... used by project managers, software developers...") explains context Claude does not need, and the action-list command is repeated across "Searching for actions" and "Popular actions".	3 / 5
Actionability	It provides concrete, copy-paste-ready `npx @membranehq/cli@latest` commands for login, connect, list, run, and proxy with a flags table; minor gaps remain since run examples use unfilled placeholders (CONNECTION_ID, ACTION_ID, "key": "value").	4 / 5
Workflow Clarity	The sequence (login → connect → discover actions → run/proxy) is clear, but there are no explicit validation or verification checkpoints, and actions that modify KanbanFlow data can be destructive, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is organized into well-labeled sections (setup, connecting, searching, running, proxy, best practices) with easy navigation; it stays just short of a 5 due to redundancy and length over 50 lines.	4 / 5
	Total	14 / 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 cleanly answers both what and when for a specific named product, with good trigger keywords and low conflict risk. Its main weakness is the generic verb "Manage" rather than concrete actions.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "Create, update, and query Boards, Users, and Tags."

Expand the "Use when" clause with concrete trigger phrases such as "when the user mentions KanbanFlow boards, tasks, tags, or columns."

Dimension	Reasoning	Score
Specificity	"Manage Boards, Users, Tags" names the domain plus several concrete entities, but the single verb "Manage" is generic rather than enumerating specific actions, matching the anchor that lists domain and a few concrete actions without being comprehensive.	3 / 5
Completeness	It states both what ("KanbanFlow integration. Manage Boards, Users, Tags.") and when ("Use when the user wants to interact with KanbanFlow data."), but the "when" clause is somewhat generic and could list more concrete trigger phrases, so it is below the fully explicit anchor 5.	4 / 5
Trigger Term Quality	"KanbanFlow", "Boards", "Users", "Tags", and "interact with KanbanFlow data" give good keyword coverage a user would naturally say, though a few natural variations (tasks, columns, kanban board) are missing.	4 / 5
Distinctiveness Conflict Risk	Naming the specific product "KanbanFlow" with entity-specific triggers gives a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: membranedev/application-skills
Path: skills/kanbanflow/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.