Name: loomio
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

loomio

Loomio integration. Manage Organizations. Use when the user wants to interact with Loomio data.

Quality

62%

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

Quality

Content

63%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 delivers strong executable command coverage and a clear connection workflow with a built-in polling feedback loop, but it is held back by minor prose padding and a monolithic structure that inlines reference material rather than splitting it out. Trimming the intro and extracting the state-machine/proxy reference into separate files would lift the weakest dimensions.

Suggestions

Cut the opening paragraph ("Loomio is a collaborative decision-making platform...") and Membrane marketing prose; Claude can infer what Loomio is from the API docs link.

Move the detailed connection state-machine reference and the proxy options table into a separate reference file (e.g., references/connections.md) and link to it one level deep.

Resolve the dangling "Step 2" / "1b" references by adding explicit labeled Step 1 and Step 2 headings to the connecting workflow.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight command examples, but the opening paragraph explaining what Loomio is and the Membrane marketing prose ("so you can focus on the integration logic rather than auth plumbing") are unnecessary padding that could be trimmed.	3 / 5
Actionability	Copy-paste-ready commands cover install, login, connection ensure/get, action list/run, and proxy requests, plus a concrete options table; the "Popular actions" section redundantly repeats the action list command, leaving a minor gap.	4 / 5
Workflow Clarity	The install→auth→connect→poll→search→run sequence is clear with a connection state-machine feedback loop, but the dangling "skip to Step 2" and "1b" references lack labeled Step 1/Step 2 headings.	4 / 5
Progressive Disclosure	Section headers are well organized, but at over 50 lines the body is monolithic — reference-y content (connection state machine, proxy options table, entity overview, best practices) is inlined with no one-level-deep reference files.	3 / 5
	Total	14 / 20 Passed

Description

61%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 an explicit "Use when..." trigger and a distinct product name, but the capability statement is thin — only one generic action is named. Expanding the action list and adding natural trigger synonyms would raise specificity and trigger-term quality.

Suggestions

Replace the generic "Manage Organizations" with 2-3 concrete actions that reflect Loomio's surface area (e.g., "Manage discussions, polls, and threads across Loomio organizations").

Add natural trigger synonyms users would actually say, such as "Loomio discussions", "Loomio polls", or "Loomio threads", to broaden keyword coverage.

Tighten the "what" clause so the capability is stated as concretely as the "when" clause already is.

Dimension	Reasoning	Score
Specificity	Names the Loomio domain but offers only one generic action ("Manage Organizations"), fitting the "minimal or generic actions" anchor rather than the 1-2 concrete actions required for a 3.	2 / 5
Completeness	Both a "what" ("Loomio integration. Manage Organizations.") and an explicit "when" ("Use when the user wants to interact with Loomio data.") are present, but the "what" is vague enough to fall short of a 5.	4 / 5
Trigger Term Quality	Relevant keywords ("Loomio", "Organizations", "Loomio data") appear, but common natural variations users would say (discussions, polls, threads, decisions) are missing.	3 / 5
Distinctiveness Conflict Risk	"Loomio" is a unique product name used as the explicit trigger, giving the skill a clear niche with minimal risk of triggering for the wrong skill.	5 / 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/loomio/SKILL.md
Commit: f484c82

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