Name: workamajig
Rating: 53.6 (1 reviews)
Author: membranedev

workamajig

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

Quality

60%

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

Quality

Content

60%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 skill delivers executable CLI guidance and a clear connection workflow, but it is dragged down by a massive inline entity catalog that violates progressive disclosure and adds token bloat.

Suggestions

Move the full entity-type list into a references/entities.md file and keep only a short representative sample in SKILL.md with a pointer.

Add an explicit error-recovery checkpoint for the connection flow (e.g. on CONFIGURATION_ERROR: read the error field, remediate, re-run ensure).

Replace CONNECTION_ID placeholders with a note on where the value comes from so commands are fully runnable.

Dimension	Reasoning	Score
Conciseness	The prose instructions are reasonably tight, but the ~170-line bulleted enumeration of every Workamajig entity type (Project through Zip Code) is padding that Claude does not need pre-loaded.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection ensure, action list/run, and proxy requests with a flags table, with only minor placeholders like CONNECTION_ID.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based branching (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and an explicit polling loop with --wait, though it lacks a formal validate-fix-retry feedback loop.	4 / 5
Progressive Disclosure	No bundle files exist and all content is inlined; the large entity-type catalog clearly belongs in a separate reference file but is dumped directly into SKILL.md, burying the actionable content.	2 / 5
	Total	13 / 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 is distinct and includes both a 'what' and an explicit 'Use when' trigger, but its action verbs are generic ('manage', 'automate') and the keyword coverage is thin beyond the app name.

Suggestions

Replace generic verbs with concrete Workamajig capabilities, e.g. 'Create projects and invoices, track time and expenses, manage client billing'.

Expand the 'Use when' clause with natural trigger phrases such as 'Use when the user wants to create projects, log time, or generate invoices in Workamajig'.

Add common synonyms or feature names (CRM, purchase orders, retainers) so users searching by feature find this skill.

Dimension	Reasoning	Score
Specificity	The description names the Workamajig domain but its actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete capabilities like creating invoices or tracking time.	2 / 5
Completeness	It explicitly states both what it does ('Manage data, records, and automate workflows') and when to use it ('Use when the user wants to interact with Workamajig data'), though the 'when' could name more concrete trigger phrases.	4 / 5
Trigger Term Quality	The domain term 'Workamajig' is the natural user trigger, but the only supporting keyword is 'data'; common variations or synonyms the user might say are missing.	3 / 5
Distinctiveness Conflict Risk	Naming the specific application Workamajig gives it a clear niche with distinct triggers and minimal risk of conflicting with 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/workamajig/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.