Name: section
Rating: 52.8 (1 reviews)
Author: membranedev

section

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

Quality

59%

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/section/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 content delivers concrete, runnable Membrane CLI commands and a workable connection workflow, but is held back by inconsistent step numbering, absent verification for proxy/destructive operations, and minor verbosity including a stray non-instructional line. Tightening the workflow sequencing and adding an output-verification checkpoint would move it toward the top anchors.

Suggestions

Fix the inconsistent step numbering (the flow references "Step 2" and "1b" without a clear Step 1) so the connect → ready → search → run sequence is unambiguous.

Add an explicit validation/verification step after proxy and action-run operations (e.g., check the response `output`/status field before proceeding) to satisfy the feedback-loop expectation for potentially destructive API calls.

Remove the stray line "I don't have enough information to do that. I need a description of the app." and trim narration like "This is the fastest way to get a connection" to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands, but includes unnecessary narration ("This is the fastest way to get a connection", restated credential-handling) and a stray unhelpful line ("I don't have enough information to do that"), fitting anchor 3's "mostly efficient but some unnecessary explanation" rather than the lean anchor 4.	3 / 5
Actionability	Concrete, executable `membrane` commands with flags are provided throughout (connection, polling, action list/run, proxy), with only minor gaps like unfilled `<actionId>` and `<id>` placeholders, matching anchor 4 rather than the fully copy-paste-ready anchor 5.	4 / 5
Workflow Clarity	A connect → poll → search → run/proxy sequence exists with state checks and a CLIENT_ACTION_REQUIRED feedback loop, but the numbering is inconsistent (jumps to "Step 2" and "1b") and destructive/proxy operations lack an explicit verification step, capping it at anchor 3.	3 / 5
Progressive Disclosure	The single-file body is well-sectioned (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no bundle files to over-reference, fitting anchor 4's "good structure, most content appropriately placed" rather than anchor 5's idealized one-level-deep reference split.	4 / 5
	Total	14 / 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 correctly pairs a what-statement with a Use-when clause, but its capabilities are generic and the trigger vocabulary is thin. Strengthening it with concrete actions and richer Section-specific trigger terms would lift it from mid-range toward the top anchors.

Suggestions

Replace generic verbs with concrete Section capabilities (e.g., "query Section observability data, manage deployments, view request logs") to raise specificity.

Expand trigger terms with natural phrases users would say (e.g., "Section app", "Section dashboard", monitoring/alerting synonyms) beyond the single "Section data" trigger.

Tighten the when-clause to name concrete scenarios (e.g., "Use when the user asks about Section app performance or wants to automate Section workflows") rather than the generic "interact with Section data".

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain but the actions are generic; no concrete capabilities are listed, matching anchor 2 rather than the 1-2 concrete actions required for anchor 3.	2 / 5
Completeness	It states both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Section data"), but the trigger is somewhat generic, matching anchor 4 rather than the fully concrete anchor 5.	4 / 5
Trigger Term Quality	Only "Section" and generic "data, records, workflows" appear; a relevant keyword exists but common variations or synonyms are missing, fitting anchor 3 over anchor 2 (which needs only generic terms) and below 4 (which needs fuller coverage).	3 / 5
Distinctiveness Conflict Risk	The named "Section" niche is mostly distinct with only minor overlap risk from the broad "data/records/workflows" phrasing, fitting anchor 4 rather than the clearly-distinct anchor 5.	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/section/SKILL.md
Commit: f484c82

Reviewed: 4 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.