Name: mapulus
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

mapulus

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

Quality

68%

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/mapulus/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 concrete, copy-paste CLI commands and a well-sequenced connection workflow that includes state-based validation checkpoints. Its main weaknesses are mild conceptual over-explanation, a redundant "Popular actions" section, and slightly broken step references ("Skip to Step 2").

Suggestions

Trim the conceptual intro paragraph ("Think of it as a platform for creating interactive maps and performing spatial analysis") and the chatty Membrane commentary to assume Claude's competence and lift conciseness.

Merge the "Popular actions" section into "Searching for actions" to remove the duplicated `action list` guidance, or differentiate them clearly with a concrete catalog of named actions.

Fix the workflow labeling so "Skip to Step 2" resolves to an explicitly numbered Step 2 section, and label 1a/1b consistently to make the connection sequence fully unambiguous.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes unnecessary explanation ("Think of it as a platform for creating interactive maps...") and redundancy between the "Searching for actions" and "Popular actions" sections, fitting "mostly efficient but includes some unnecessary explanation"; not a 4 because the conceptual intro and duplicated action-listing guidance are clearly trimmable.	3 / 5
Actionability	Provides copy-paste-ready commands for every common case (install, login, connection ensure/get, action list, action run, request proxy) plus a flag table, matching "fully executable; copy-paste ready commands covering common cases"; placeholders like CONNECTION_ID are appropriate and do not reduce executability.	5 / 5
Workflow Clarity	The connection setup has a clear sequence with validation checkpoints (polling state, branching on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after user action), fitting "clear sequence with most checkpoints present"; not a 5 because "Skip to Step 2" references a Step 2 that is not clearly labeled and step numbering is incomplete.	4 / 5
Progressive Disclosure	Content is well-organized into clearly signaled sections (Overview, Working with Mapulus, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references; fitting "good structure; most content appropriately placed; minor organization gaps"; not a 5 because the file is ~140 lines (above the simple-skill threshold) with some inlined redundancy rather than a lean overview.	4 / 5
	Total	16 / 20 Passed

Description

62%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 pairs a what with an explicit use-when trigger and leverages a distinctive product name, but the capability list is thin (only "Manage Organizations") and the keyword coverage lacks synonyms. It is solid but not comprehensive.

Suggestions

Expand the "what" beyond "Manage Organizations" to enumerate the concrete capabilities the skill exposes (e.g., create/manage maps, layers, features, styles) so specificity and completeness reach the top anchor.

Add natural trigger synonyms and entity terms users would say (e.g., "maps", "spatial data", "layers", "locations") to improve trigger-term quality and distinctiveness.

Keep the third-person "Use when the user wants to interact with Mapulus data" form but make the "when" clause list the concrete data types or tasks to sharpen the trigger.

Dimension	Reasoning	Score
Specificity	Names the domain ("Mapulus integration") and one concrete action ("Manage Organizations"), matching the anchor for 1-2 concrete actions without comprehensive coverage; it is not a 2 because "Manage Organizations" is a specific action rather than purely generic, and not a 4 because no further actions are listed.	3 / 5
Completeness	Provides both a "what" ("Mapulus integration. Manage Organizations.") and an explicit "when" ("Use when the user wants to interact with Mapulus data"), matching the anchor where both are present but the "what" could be more specific; not a 5 because the "what" is vague and lists only one action.	4 / 5
Trigger Term Quality	Includes relevant keywords ("Mapulus", "Organizations", "Mapulus data") but lacks synonyms or common variations users might say, fitting the "some relevant keywords but missing variations" anchor; it is above 2 because Mapulus is a natural product term, but below 4 due to thin keyword coverage.	3 / 5
Distinctiveness Conflict Risk	The product-specific "Mapulus" trigger gives it a clear niche with minimal conflict risk, but "Manage Organizations" is a generic action that could overlap with other org-management skills, fitting "mostly distinct; minor overlap risk"; not a 5 because of that generic action phrasing.	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/mapulus/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.