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

gloww

Gloww integration. Manage Organizations, Pipelines, Users, Filters, Files, Notes. Use when the user wants to interact with Gloww 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/gloww/SKILL.md

Quality

Content

65%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 concrete, copy-paste-ready Membrane CLI commands, but it leans on a padded conceptual intro and a long inline entity list. Workflow sequencing is clear but lacks validation checkpoints, and all reference material is inlined with no separate files.

Suggestions

Remove or trim the conceptual intro paragraph about what Gloww is — it does not help execute the skill and inflates the token budget.

Move the 40+ item entity list and the proxy flag-options table into a separate reference file, keeping only the essentials inline with a clearly signaled link.

Add an explicit validation checkpoint to the workflow, e.g., run `test-connection` after creating a connection and verify action output before proceeding to batch or mutating runs.

Dimension	Reasoning	Score
Conciseness	The operational sections are tight and command-driven, but the conceptual intro paragraph ('Gloww is a social media platform...') and a 40+ item inline entity list are padding that does not aid execution.	3 / 5
Actionability	Provides copy-paste-ready CLI commands across the full path (install, login, connect, search, run, proxy) with real flags and a flag-options table, covering the common cases concretely.	5 / 5
Workflow Clarity	The install→login→connect→discover→run→proxy sequence is ordered, but there are no validation checkpoints (e.g., test-connection before running actions), so the destructive/external-mutating cap at 3 applies.	3 / 5
Progressive Disclosure	Sections are well-organized with clear headers, but there are no reference files at all and bulk material (the 40-item entity list, the full flag-options table) is inlined rather than split out.	3 / 5
	Total	14 / 20 Passed

Description

78%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 states what Gloww entities it manages and when to use the skill, with a distinct brand-named trigger. Its main weakness is a generic 'Manage' verb and a slightly generic 'when' clause that could name concrete trigger phrases.

Suggestions

Replace the repeated generic verb 'Manage' with distinct concrete actions per entity (e.g., 'Create and list Pipelines, invite Users, apply Filters, upload Files').

Expand the 'when' trigger with concrete phrases users would say, e.g., 'Use when the user wants to list Gloww pipelines, invite users, or query Gloww data.'

Add natural synonyms or relevant file extensions alongside 'Gloww' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names six concrete resource areas ('Manage Organizations, Pipelines, Users, Filters, Files, Notes'), but repeats a single generic verb 'Manage' rather than enumerating distinct actions, so it falls short of comprehensive coverage.	4 / 5
Completeness	Provides both a clear 'what' (manage these Gloww entities) and an explicit 'when' ('Use when the user wants to interact with Gloww data'), though the 'when' is generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	Has an explicit natural trigger clause ('Use when the user wants to interact with Gloww data') built on the brand name, but lacks synonyms or file extensions beyond the brand and generic 'data'.	4 / 5
Distinctiveness Conflict Risk	Names a specific brand ('Gloww') with a distinct entity list and an explicit Gloww-only trigger, giving it a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	17 / 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/gloww/SKILL.md
Commit: f484c82

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