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

Blog Docs Log in Get started

intuiface

Intuiface integration. Manage Experiences. Use when the user wants to interact with Intuiface 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/intuiface/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 executable commands and a clear stateful workflow including polling/feedback loops, though it carries some marketing-style over-explanation and slightly inconsistent step numbering. Structure is good but could split dense reference material into separate files.

Suggestions

Trim the introductory marketing paragraph ('no-code platform... used by businesses in various industries...') and the 'so you can focus on the integration logic rather than auth plumbing' aside to improve conciseness.

Fix step numbering: label the connection-setup step as '1a', the wait step as '1b', and add an explicit 'Step 2: Searching for / running actions' header that the 'Skip to Step 2' references point to.

Consider moving the clientAction state detail and the popular-actions/proxy flag tables into a referenced reference file so SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes padded/marketing-style explanation Claude does not need ('Intuiface is a no-code platform... used by businesses in various industries to build and deploy interactive displays, kiosks...') and editorializing ('so you can focus on the integration logic rather than auth plumbing'); a 4 would require trimming these without losing clarity.	3 / 5
Actionability	It provides copy-paste-ready, executable commands throughout (npm install, membrane login, connection ensure, action run with --input JSON, request with flags) plus a popular-actions table with concrete keys and a proxy-flags table, covering the common cases fully as in the top anchor.	5 / 5
Workflow Clarity	The install -> login -> connection ensure -> poll-until-ready -> search -> run sequence is clear with an explicit state-handling feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED and 'poll again after the user completes the action'); not a 5 because step numbering is inconsistent (a '1b' with no '1a', and a 'Step 2' referenced but not labeled as a header), leaving minor navigation gaps.	4 / 5
Progressive Disclosure	Content is organized into clear, well-signaled sections (Overview, Working with Intuiface, Popular actions, Proxy, Best practices) with no bundle files present so everything is appropriately inline; not a 5 because the long clientAction detail and popular-actions/proxy tables could be split into referenced files for a cleaner overview, though the current structure is reasonable.	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 is well-structured with both a 'what' and an explicit 'Use when...' trigger tied to a distinctive niche, but it is thin on specific capabilities and natural trigger variations. Expanding the action list and trigger terms would lift it toward the top anchors.

Suggestions

Add 2-3 concrete actions to the description (e.g. 'Deploy Experiences, list Players, send trigger messages') to raise specificity.

Broaden the 'Use when...' clause with concrete trigger nouns users would say, such as 'Intuiface Experiences, Players, or web trigger messages'.

Mention key synonyms/extensions (e.g. 'Intuiface Cloud, Players') to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	It names the domain ('Intuiface integration') and one concrete action ('Manage Experiences'), but offers only that single generic action and no further concrete operations, matching the 1-2-actions-but-not-comprehensive anchor; a 4 would require several specific listed actions.	3 / 5
Completeness	It states both a 'what' ('Intuiface integration. Manage Experiences.') and an explicit 'when' ('Use when the user wants to interact with Intuiface data'), but the trigger clause is single and could be more specific with concrete trigger phrases; not a 5 because the 'when' lacks multiple concrete triggers as in the top anchor.	4 / 5
Trigger Term Quality	It surfaces the relevant keyword 'Intuiface' and the phrase 'interact with Intuiface data', but misses common natural variations, synonyms, or concrete nouns a user might say (e.g. 'Experiences', 'Players', 'deploy'), paralleling the 'Works with PDF files' anchor; a 4 would need broader natural-term coverage.	3 / 5
Distinctiveness Conflict Risk	The 'Intuiface' niche is specific and the trigger is tied to Intuiface data, giving low conflict risk with other skills; not a 5 because 'interact with Intuiface data' is somewhat broad within the niche and could overlap with generic data-handling skills if Intuiface were not named.	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/intuiface/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.