Name: assembled
Rating: 60 (1 reviews)
Author: membranedev

assembled

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

Quality

70%

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

Quality

Content

81%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 a strong, executable guide with concrete CLI commands, a clear connection-to-action workflow, and explicit state-polling checkpoints. Its main weakness is slight repetition around authentication handling and the absence of a destructive-operation validation gate.

Suggestions

Add an explicit validation/verification checkpoint before destructive or batch actions (e.g. confirm a connection id and dry-run output before running mutating actions), since the workflow_clarity cap for unvalidated destructive operations is 3.

Consolidate the repeated "Membrane handles auth automatically" statements into one place to tighten token efficiency.

Consider splitting the proxy flag reference and popular-actions list into a separate reference file to move from good to clear one-level-deep progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, using lean command blocks and a tight best-practices list, with only minor over-explanation (e.g. restating that Membrane handles auth in several places); it does not pad with concepts Claude already knows.	4 / 5
Actionability	It provides copy-paste-ready, executable commands throughout (install, login, connection ensure/get with --wait, action list/run with --input, request with a full flag table), covering the common cases concretely.	5 / 5
Workflow Clarity	There is a clear sequence (install -> login -> connection ensure -> wait/poll for READY -> search actions -> run) with explicit state-branching and polling checkpoints; it stops just short of a full validate/feedback loop checklist, fitting the level-4 anchor.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections with inline command reference kept brief and a flag table for the proxy; no bundle files exist, so structure is appropriate, though the API/action reference could optionally be split out, leaving minor organization gaps.	4 / 5
	Total	17 / 20 Passed

Description

60%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 includes both a capability statement and an explicit "Use when" trigger clause, and it is anchored to a distinct branded product. Its main weakness is generic action verbs and limited natural-language trigger coverage that undersells the platform's actual capabilities.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Assembled capabilities such as forecasting, scheduling agents, and monitoring support performance.

Expand the trigger clause with natural phrases users would say, e.g. "Use when the user wants to forecast staffing, schedule agents, or view support performance in Assembled."

Add synonyms and product-specific terms (schedules, shifts, agent productivity) so the description surfaces for the ways users actually phrase requests.

Dimension	Reasoning	Score
Specificity	Quotes "Manage data, records, and automate workflows" name the domain and a couple concrete actions (manage, automate), but the actions are generic and not a comprehensive list; matches the anchor that names the domain with 1-2 concrete actions.	3 / 5
Completeness	It states both a clear "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Assembled data"); the "when" is present but somewhat generic rather than tied to concrete trigger phrases, fitting the level-4 anchor.	4 / 5
Trigger Term Quality	Trigger phrasing "interact with Assembled data" plus "data, records, workflows" gives some relevant keywords, but it misses common natural variations users would say (e.g. "schedules", "forecasting", "agents", "support staffing") and file/format extensions.	3 / 5
Distinctiveness Conflict Risk	The branded name "Assembled" plus the explicit "Use when... to interact with Assembled data" gives it a clear niche distinct from other skills with only minor overlap risk from generic terms like "data" and "records".	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/assembled/SKILL.md
Commit: f484c82

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