Name: workboard
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

workboard

Workboard integration. Manage Organizations. Use when the user wants to interact with Workboard 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/workboard/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 complete, copy-paste CLI commands and a strong state-based connection workflow including feedback loops, though it carries some unnecessary Workboard/marketing exposition and the step numbering is slightly confusing.

Suggestions

Trim the opening Workboard platform explainer and the Membrane marketing phrasing to assume Claude's competence and save tokens.

Clarify the workflow step numbering — the "skip to Step 2" and "1b" labels reference steps that are not formally enumerated; use a consistent ordered list.

Add a brief validation/verification note for mutating actions (update-metric, create-goal, update-user, create-user) so the workflow confirms the change took effect.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI guidance, but the opening Workboard explainer ("Workboard is a strategy and results management platform... typically used by executives, managers, and teams in large enterprises") and minor marketing phrasing ("so you can focus on the integration logic rather than auth plumbing", "burn less tokens") are over-explanation that could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready commands for the full common path — install, login (interactive and headless), connection ensure, polling, action list, action run with JSON input, and proxy requests — plus a concrete actions table and a flags table covering the common cases.	5 / 5
Workflow Clarity	The connection setup has a clear state-based feedback loop (BUILDING/READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR with explicit next actions and re-polling), but step references like "skip to Step 2" and "1b" are confusingly labeled, and there is no validation checkpoint after running mutating actions like update-metric or create-goal.	4 / 5
Progressive Disclosure	The file is well-organized into clear sections and points to the official docs URL, and it is appropriately self-contained for a CLI skill, but at ~158 lines with a large inline popular-actions table it exceeds the simple-skill threshold and has no further reference split.	4 / 5
	Total	16 / 20 Passed

Description

61%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 has an explicit "Use when" trigger and is clearly anchored to the distinct Workboard product, but it is thin on concrete capabilities and trigger-term breadth, mentioning only "Manage Organizations" while the skill covers OKRs, goals, metrics, tasks, meetings, and users.

Suggestions

Replace the generic "Manage Organizations" with concrete actions the skill performs, e.g. "List and update goals, metrics, and users; create goals and users."

Broaden trigger terms to include natural Workboard vocabulary users would say: OKRs, goals, metrics, tasks, meetings, and key results.

Make the "when" clause more specific, e.g. "Use when the user wants to read or update Workboard OKRs, goals, metrics, users, or meetings."

Dimension	Reasoning	Score
Specificity	"Workboard integration" and "Manage Organizations" name the domain and only one generic action, with no concrete operations like listing goals, updating metrics, or creating users that the skill actually performs.	2 / 5
Completeness	It has both a (vague) "what" ("Manage Organizations") and an explicit "Use when the user wants to interact with Workboard data" trigger, but the "what" is not comprehensive and the "when" lacks concrete trigger phrases beyond "Workboard data".	4 / 5
Trigger Term Quality	"Workboard" is a natural keyword users would say and "interact with Workboard data" is reasonable, but it omits common Workboard-specific terms users would mention like OKRs, goals, metrics, tasks, or meetings.	3 / 5
Distinctiveness Conflict Risk	"Workboard" is a specific named product and the trigger is product-bound ("interact with Workboard data"), giving it a clear niche with minimal conflict risk against other skills.	5 / 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/workboard/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.