Name: workiom
Rating: 60 (1 reviews)
Author: membranedev

workiom

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

Quality

70%

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/workiom/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.

A highly actionable, well-sequenced integration guide with executable commands and good feedback loops during connection setup. It loses points mainly on a padded introductory paragraph and inlining reference material that could live in separate files.

Suggestions

Remove the introductory paragraph describing what Workiom is and the filler line 'Use action names and parameters as needed.' to tighten token use.

Add an explicit validation/check step before running destructive or batch actions (e.g., preview the action and confirm with the user before execution).

Move the proxy request flag table and action inputSchema/outputSchema detail into a separate reference file linked from the body.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but the opening paragraph explaining what Workiom is ('no-code work management platform... used by businesses of all sizes') and filler like 'Use action names and parameters as needed' are unnecessary padding Claude does not need.	3 / 5
Actionability	Copy-paste-ready commands throughout (membrane login, connection ensure, action list/run, request) with flags and JSON usage explained, covering the common cases fully.	5 / 5
Workflow Clarity	There is a clear install → authenticate → connect → poll-for-ready → search → run sequence with explicit state-based feedback loops (poll again until READY, handle CLIENT_ACTION_REQUIRED). Minor validation gaps exist for destructive action runs and proxy requests, which lack explicit pre-flight validation.	4 / 5
Progressive Disclosure	Well-organized into Overview, Working with Workiom, Popular actions, and Best practices sections with clear navigation. Some content like the full proxy-flag table and action schema details is inlined where a separate reference file could carry it, leaving minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

66%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.

A concise, third-person description that answers both what and when for a clearly distinct product. It is held back from the top tier by generic action language and a single, non-varied trigger phrase.

Suggestions

Replace generic 'Manage data, records' with concrete capabilities (e.g., 'Create and update list items, manage attachments, query records').

Expand the trigger clause with natural variations: 'Use when the user wants to interact with Workiom data, manage Workiom lists or records, or automate Workiom workflows.'

Dimension	Reasoning	Score
Specificity	Names the Workiom domain and a couple of actions ('Manage data, records, and automate workflows'), but 'manage data, records' is generic rather than enumerating concrete capabilities, matching the '1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Workiom data'), but the 'when' clause is somewhat generic rather than listing concrete trigger phrases, so it sits just below the 5 anchor.	4 / 5
Trigger Term Quality	The single trigger phrase 'when the user wants to interact with Workiom data' is natural but lacks synonyms or variations users might say, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The named product 'Workiom' creates a clear niche with distinct, product-specific triggers and minimal conflict risk with other skills.	5 / 5
	Total	15 / 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/workiom/SKILL.md
Commit: f484c82

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