Name: spaycial
Rating: 51.2 (1 reviews)
Author: membranedev

spaycial

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

Quality

56%

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

Quality

Content

56%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 Membrane CLI workflow is executable and well-sequenced with good connection-state validation, but the skill is dominated by a massive inlined, largely generic entity/action list that wastes tokens and should live in a separate reference file. No bundle files are used, so progressive disclosure is flat.

Suggestions

Move the 390-item entity/action list into a references/ file (e.g., references/entities.md) and replace it in SKILL.md with a one-line pointer, recovering token budget and improving navigation.

Prune generic items unrelated to Spaycial (e.g., 'Universe', 'Wisdom', 'Hire', 'Zoom In', 'Pan') so the list reflects real Spaycial API entities only.

Add one concrete end-to-end Spaycial example (e.g., searching and running an action with real parameters and expected output) and an action-run error-handling/validation checkpoint.

Dimension	Reasoning	Score
Conciseness	Roughly 390 inlined bullet items (e.g., 'Universe', 'Wisdom', 'Hire', 'Zoom In') form a heavily padded, largely undifferentiated list, while the CLI sections are reasonably efficient; overall this is noticeably verbose with a major padded section.	2 / 5
Actionability	Concrete executable commands are given throughout ('npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://www.spaycial.com/" --json', 'membrane action run <actionId> --connectionId=CONNECTION_ID --json') plus a proxy flag table, with only minor gaps from placeholders and the non-actionable entity list.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state checkpoints and a poll/re-poll feedback loop (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but running actions lacks error-handling guidance, leaving a minor validation gap.	4 / 5
Progressive Disclosure	There are clear section headers and no nested references, but the ~390-item entity glossary is content that clearly belongs in a separate reference file and is inlined, and no bundle/reference files exist to offload it.	3 / 5
	Total	13 / 20 Passed

Description

57%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 successfully pairs a what with an explicit 'Use when' trigger tied to a named app, but its capability verbs are generic ('manage') and it offers only a single narrow trigger phrase. Voice is correctly third person.

Suggestions

Replace generic verbs with concrete Spaycial actions (e.g., 'search spatial records, create and assign tasks, automate workflows') to lift specificity.

Broaden the trigger with natural synonyms users would say, e.g., 'Use when the user wants to query, update, or automate Spaycial records, tasks, or spatial data.'

Tie each listed capability to the Spaycial domain to reduce overlap with generic data-management skills.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the Spaycial domain but uses generic verbs ('manage') rather than concrete actions, matching the anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	It states a what ('Manage data, records, and automate workflows') and an explicit when ('Use when the user wants to interact with Spaycial data'), but the when is a single narrow trigger that could be more specific, matching 'Has both what and when; when could be more explicit or specific'.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with Spaycial data' provides the natural phrase 'Spaycial data' plus 'records' and 'workflows', but misses common synonyms or variations, fitting 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	Tying the trigger to the named SaaS 'Spaycial' gives a clear niche with minimal conflict risk, but the generic 'manage data, records' action wording leaves minor overlap risk with related data/CRM skills, fitting 'Mostly distinct; minor overlap risk'.	4 / 5
	Total	13 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (535 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: membranedev/application-skills
Path: skills/spaycial/SKILL.md
Commit: f484c82

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