Name: mindspun
Rating: 56.8 (1 reviews)
Author: membranedev

mindspun

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

Quality

65%

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

Quality

Content

68%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 content is highly actionable with copy-paste CLI commands and a solid connection-state feedback loop, but it carries a marketing-fluff intro and lacks validation steps around the data operations themselves. Adding verification guidance before destructive action runs and trimming padding would lift the weaker dimensions.

Suggestions

Add a validation/verification checkpoint before and after running actions that modify records or automate workflows (e.g. dry-run, confirm scope, inspect output before proceeding) to satisfy the destructive/batch workflow cap.

Remove the marketing-style intro paragraph and the vague 'When to use which actions' filler; let the concrete commands and section headers carry the explanation.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient concrete CLI commands, but the marketing-style intro ('It's used by businesses and developers to build conversational interfaces for customer support, lead generation, and internal knowledge bases') and filler like 'When to use which actions: Use action names and parameters as needed' could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready commands throughout — install, login, connection ensure/get, action list/run with JSON input, and the proxy request with a full flags table — covering the common cases fully.	5 / 5
Workflow Clarity	The connection flow is well sequenced with a state-machine feedback loop (READY / CLIENT_ACTION_REQUIRED with re-polling / CONFIGURATION_ERROR), but running actions that manage records and automate workflows has no validation or verification checkpoint, so the destructive/batch cap applies.	3 / 5
Progressive Disclosure	No bundle files exist, but the single body is well organized into clear headed sections (Install, Authentication, Connecting, Searching, Running actions, Proxy, Best practices); the proxy flags table and clientAction details are reasonable to keep inline, with only minor organization gaps.	4 / 5
	Total	15 / 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 answers both what and when with an explicit 'Use when' clause and a distinctive brand trigger, but its action list is generic and it misses natural synonyms a user would actually say. Tightening the capabilities to concrete platform features and adding terms like chatbot/assistant would raise it.

Suggestions

Replace generic actions ('Manage data, records') with concrete Mindspun capabilities such as creating projects, assistants, messages, and files to improve specificity.

Add natural trigger terms users would say — e.g. 'chatbot', 'virtual assistant', 'assistant messages', or 'Mindspun files' — alongside the brand name.

Dimension	Reasoning	Score
Specificity	It names the domain (Mindspun) and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete platform capabilities, so it is not comprehensive.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Mindspun data') are present, though the 'when' clause could be more specific about the scenarios.	4 / 5
Trigger Term Quality	The trigger relies on the brand name 'Mindspun' and 'Mindspun data', which is a relevant keyword, but it omits natural variations users might say such as chatbot, assistant, message, or file.	3 / 5
Distinctiveness Conflict Risk	The unique brand trigger 'Mindspun' makes it mostly distinct with minimal conflict risk, but the generic 'manage data, records' phrasing leaves minor overlap with other data-management skills.	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/mindspun/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.