Name: assembla
Rating: 60.8 (1 reviews)
Author: membranedev

assembla

Assembla integration. Manage Organizations, Leads, Deals, Pipelines, Users, Goals and more. Use when the user wants to interact with Assembla data.

Quality

71%

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

Quality

Content

75%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 highly actionable with a clear, validated connection workflow and copy-paste commands, but it trades conciseness and file-based disclosure for inlined prose and reference tables. Moving the action catalog and proxy flags into reference files and trimming the introductory paragraph would lift the weaker dimensions.

Suggestions

Trim the opening 'Assembla is a project management...' paragraph to one line or remove it; Claude does not need a product backgrounder to use the CLI.

Extract the Popular actions table and the proxy request flags table into a reference file (e.g. references/actions.md) and link to it from SKILL.md to improve progressive disclosure.

Move the detailed clientAction state-handling prose into a separate connection reference, keeping only the READY/BUILDING short path inline.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and a useful action table, but the opening 'Assembla is a project management...' paragraph and a few prose explanations could be tightened; fits score 3 rather than 4.	3 / 5
Actionability	Provides copy-paste-ready membrane CLI commands, a full popular-actions table with keys, and a proxy flags table covering the common cases, matching the score-5 anchor.	5 / 5
Workflow Clarity	The connection sequence is explicit with state-based branching (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a polling feedback loop, providing clear validation checkpoints and error recovery matching score 5.	5 / 5
Progressive Disclosure	Content is well-sectioned but entirely inlined in a ~195-line SKILL.md with no bundle files; the full action table and proxy reference could live in separate files, so it sits at score 3 rather than 4.	3 / 5
	Total	16 / 20 Passed

Description

68%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 clearly names a distinct niche (Assembla) and provides an explicit 'Use when' trigger, but its trigger-term breadth is limited and the 'when' clause is somewhat generic. It is solid and functional but not maximally rich in natural-language triggers.

Dimension	Reasoning	Score
Specificity	Lists several concrete managed domains ('Organizations, Leads, Deals, Pipelines, Users, Goals') but the single generic verb 'Manage' plus 'and more' leaves minor coverage gaps, fitting the score-4 anchor rather than 5.	4 / 5
Completeness	Both 'what' (Assembla integration managing named entities) and 'when' ('Use when the user wants to interact with Assembla data') are present and explicit, but the 'when' clause is less concrete/rich than the score-5 example, so 4 fits better than 5.	4 / 5
Trigger Term Quality	'Assembla' and 'interact with Assembla data' provide relevant keywords, but natural-term coverage is thin with no synonyms or common variations beyond the product name, matching score 3 rather than 4.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Assembla' with product-scoped triggers carves a clear niche with minimal overlap risk against other skills, matching the score-5 anchor.	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/assembla/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.