Name: workast
Rating: 55.2 (1 reviews)
Author: membranedev

workast

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

Quality

62%

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

Quality

Content

67%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 a well-organized, action-oriented guide to driving Workast through the Membrane CLI, with strong executable commands and an explicit connection-readiness feedback loop. Its weaknesses are an unnecessary introductory description of what Workast is and a missing 'Step 2' anchor that the flow references.

Suggestions

Remove or trim the opening paragraph explaining what Workast is and the Slack/Teams context — Claude does not need this background.

Define or relabel the 'Step 2' the text repeatedly points to (e.g. 'Step 2: Search for actions') so the cross-references resolve.

Move the verbose clientAction state breakdown and the proxy flag table into a reference file, keeping SKILL.md a lean overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI documentation, but the opening paragraph explaining what Workast is ('built directly within Slack and Microsoft Teams... primarily used by small to medium-sized teams') and filler like 'Use action names and parameters as needed.' add unnecessary padding.	3 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request) plus a thorough flag table, with only minor gaps where placeholders like CONNECTION_ID and actionId must be resolved by the reader.	4 / 5
Workflow Clarity	The install → login → connect → poll → search → run sequence is clear, and the connection-state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED) gives an explicit poll-and-retry feedback loop; the main gap is the dangling 'skip to Step 2' reference that is never labeled.	4 / 5
Progressive Disclosure	No bundle files exist, and the body is organized into clear labeled sections (Overview, Authentication, Connecting, Searching, Running actions, Proxy, Best practices); it is well-structured for a single file, though the detailed clientAction state breakdown and proxy flag table could justify separate reference files.	4 / 5
	Total	15 / 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 correctly includes an explicit 'Use when' trigger and anchors on the distinct Workast brand, but the capability list is vague fluff ('manage data, records, and automate workflows') rather than concrete Workast features. Tightening the 'what' to mention tasks, projects, meetings, and spaces would lift specificity and completeness.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Workast capabilities such as 'manage tasks, projects, spaces, meetings, and subtasks'.

Expand the trigger to mention natural user phrasings like 'Workast tasks', 'Workast projects', or 'tasks in Slack/Teams'.

Tie the 'Use when' clause to specific intents, e.g. 'Use when the user wants to create or track Workast tasks, manage projects, or automate Workast workflows.'

Dimension	Reasoning	Score
Specificity	The description names the domain ('Workast integration') but its actions are minimal and generic — 'Manage data, records, and automate workflows' uses vague abstract terms rather than concrete capabilities like tasks, projects, or meetings.	2 / 5
Completeness	Both 'what' ('Workast integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with Workast data.') are present, though both could be more specific and concrete.	4 / 5
Trigger Term Quality	'Workast' and 'interact with Workast data' are relevant keywords a user might say, but coverage is thin with no synonyms or natural variations beyond the brand name.	3 / 5
Distinctiveness Conflict Risk	The Workast brand name gives it a clear niche unlikely to trigger for unrelated skills, but the generic 'manage data, records' phrasing leaves minor overlap risk with other project-management integrations.	4 / 5
	Total	13 / 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/workast/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.