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

Blog Docs Log in Get started

plance

Plance integration. Manage data, records, and automate workflows. Use when the user wants to interact with Plance 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/plance/SKILL.md

Quality

Content

76%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 skill body is highly actionable with executable commands and a clear connection-state workflow, but it lacks verification steps after data-mutating actions and proxy requests, which caps workflow clarity despite otherwise strong sequencing.

Suggestions

Add a verification step after `membrane action run` and proxy requests, e.g. inspect the `output` field, check status codes, and confirm the record was created/updated before reporting success.

Merge or clearly differentiate the "Searching for actions" and "Popular actions" sections to remove redundant discovery instructions.

Trim the "Think of it as a simpler alternative to Jira or Asana" framing to keep the overview lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and minimal concept re-teaching; only minor padding remains, such as the Jira/Asana comparison and slight redundancy between "Searching for actions" and "Popular actions".	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, action discovery, action execution, and proxy requests, plus a flag table covering the common cases.	5 / 5
Workflow Clarity	The connection flow is well-sequenced with state checks and a poll-again feedback loop, but running actions and proxy requests can mutate Plance data with no verification step afterward, which caps this dimension at 3 per the destructive/batch-operation rule.	3 / 5
Progressive Disclosure	Content is a single well-organized SKILL.md with clear section headers and no nested references, appropriate for a skill with no bundle files; minor organization gaps come from overlapping "Searching for actions" and "Popular actions" sections.	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 distinct named app, but its capability list is generic ("manage data, records, automate workflows") rather than concrete Plance actions, and natural trigger terms beyond "interact with Plance data" are thin.

Suggestions

Replace the generic action list with concrete Plance capabilities, e.g. "Create and track tasks, manage projects and workspaces, and search records."

Broaden trigger terms to natural user phrasing such as tasks, projects, to-dos, or Plance records, not just "interact with Plance data".

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain and a few actions, but the actions are generic rather than concrete (e.g., no mention of creating tasks, managing projects, or specific record operations).	2 / 5
Completeness	It states both what the skill does ("Manage data, records, and automate workflows") and when to use it ("Use when the user wants to interact with Plance data"), though the when-clause is fairly generic.	4 / 5
Trigger Term Quality	"interact with Plance data" and the "Plance" keyword are relevant, but common natural variations and synonyms (tasks, projects, Plance records) are missing.	3 / 5
Distinctiveness Conflict Risk	The named "Plance" app gives it a clear, distinct niche with minimal conflict risk, though the generic "manage data, records" framing leaves minor overlap with other data-management skills.	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/plance/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.