Name: algomo
Rating: 63.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

algomo

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

Quality

75%

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/algomo/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 body is a well-structured, highly actionable integration guide built around concrete Membrane CLI commands. Its gaps are the absence of validation checkpoints in workflows that can execute destructive operations and a little introductory padding.

Suggestions

Add explicit validation checkpoints to the connection and action-execution workflows (e.g., verify the connection id was returned and the action ran without error before proceeding).

Trim the opening marketing paragraph about Algomo's audience and the 'auth plumbing' aside to reduce token overhead.

Introduce a brief feedback loop for proxy/action errors (e.g., inspect the JSON output, retry on auth-refresh) since destructive methods are supported.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command-driven guidance, with only minor padding such as the opening marketing sentence ('helps businesses manage and automate interactions... streamline communication workflows') and 'so you can focus on the integration logic rather than auth plumbing', placing it above the mostly-efficient anchor 3 but short of the fully-lean anchor 5.	4 / 5
Actionability	Provides copy-paste-ready executable commands throughout (npm install, membrane login/search/connect/action list/action run/request) plus a flag table for proxying, matching the 'fully executable, copy-paste ready, covers common cases' anchor.	5 / 5
Workflow Clarity	The install->login->connect->search->run sequence is clearly ordered with numbered steps, but there are no validation/verification checkpoints, and the proxy path explicitly enables destructive HTTP methods (PUT/PATCH/DELETE), so the missing-feedback-loop cap holds it at 3 rather than 4.	3 / 5
Progressive Disclosure	Content is well organized into clear single-level sections (Overview, Working with Algomo, Popular actions, Best practices) with no nested references and appropriately self-contained for this scope, sitting between the well-structured anchor 4 and the multi-reference anchor 5 which does not apply given no bundle files exist.	4 / 5
	Total	16 / 20 Passed

Description

73%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 cleanly states what the skill does and when to use it, anchored by a distinctive brand name that prevents conflict. Its main weakness is generic action verbs and a single, non-enumerated trigger phrase.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Algomo actions such as 'get bot responses, search actions, and proxy API requests'.

Expand the 'Use when...' clause with concrete trigger scenarios (e.g., 'Use when the user wants to send Algomo chatbot responses or query Algomo data via Membrane').

Add natural synonyms/variants (e.g., 'Algomo chatbot', 'Algomo API') to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the Algomo domain plus a few actions ('Manage data, records, and automate workflows'), but the verbs are generic and coverage is not comprehensive, matching the 'names domain and 1-2 concrete actions' anchor rather than the richer action list at 4.	3 / 5
Completeness	Explicitly answers both what ('Algomo integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with Algomo data.'), but the 'when' clause is a single generic trigger rather than the enumerated concrete trigger phrases required for a 5.	4 / 5
Trigger Term Quality	Includes natural terms tied to the product ('Algomo', 'Algomo integration', 'interact with Algomo data') with good coverage for a niche SaaS, sitting above the single-keyword anchor 3 and just below the comprehensive-synonym anchor 5.	4 / 5
Distinctiveness Conflict Risk	The proper-noun brand 'Algomo' creates a clear, distinct niche with minimal conflict risk against other skills, matching the 'clear niche with distinct triggers' 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/algomo/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.