Name: teamwork-desk
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

teamwork-desk

Teamwork Desk integration. Manage Organizations. Use when the user wants to interact with Teamwork Desk data.

Quality

61%

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

Quality

Content

57%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 actionable with executable Membrane CLI commands and a clear connection workflow, but it is padded with unnecessary explanation, inlines reference content that belongs in separate files, and lacks validation steps for destructive ticket/customer operations. Splitting the action reference out and adding verification guidance would improve it.

Suggestions

Add validation/verification guidance for destructive and batch actions (e.g., verify a ticket exists and confirm before delete, check the result after update).

Move the Popular actions table and proxy flags into a separate reference file and link to it from SKILL.md to improve progressive disclosure.

Trim the explanatory intro paragraph and filler phrases ('so you can focus on the integration logic rather than auth plumbing') to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the opening paragraph explaining what Teamwork Desk is and filler lines like 'so you can focus on the integration logic rather than auth plumbing' could be trimmed, fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands for install, login, connection, action search/run, and proxy with a flags table, but examples rely on placeholders (CONNECTION_ID, <actionId>) and lack a complete end-to-end real example, leaving minor gaps.	4 / 5
Workflow Clarity	The connection flow is well-sequenced with polling and CLIENT_ACTION_REQUIRED feedback loops, but destructive actions (delete/update ticket) have no validation or verification steps, so the destructive-ops cap holds it at 3.	3 / 5
Progressive Disclosure	Sections are well-organized with clear headers, but the 20-row Popular actions table and proxy flags table are reference-style content inlined in SKILL.md with no external reference files, fitting 'content that should be separate is inline'.	3 / 5
	Total	13 / 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.

The description answers both what and when and is highly distinct because it names a specific product, but its action coverage is thin and it lacks natural trigger synonyms users would actually say. Tightening the action list and adding common terms like 'helpdesk' or 'support tickets' would raise it.

Suggestions

Expand 'Manage Organizations' to list 2-3 concrete actions actually supported (e.g., 'manage tickets, customers, and inboxes').

Add natural trigger synonyms users would say, such as 'helpdesk tickets', 'support tickets', or 'customer inquiries'.

Broaden the 'Use when' clause with concrete trigger phrases rather than the single generic 'interact with Teamwork Desk data'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Teamwork Desk integration') and one concrete action ('Manage Organizations'), matching the '1-2 concrete actions but not comprehensive' anchor; it is not a 2 because a specific action is named, and not a 4 because coverage is thin and 'Manage' is generic.	3 / 5
Completeness	Both 'what' ('Teamwork Desk integration. Manage Organizations.') and 'when' ('Use when the user wants to interact with Teamwork Desk data.') are present, but the trigger clause is single and generic rather than listing concrete trigger phrases, so it falls short of a 5.	4 / 5
Trigger Term Quality	Contains the relevant product keyword 'Teamwork Desk' (repeated) but misses common natural variations a user would say like 'helpdesk', 'support tickets', or 'customer inquiries', fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Targets a specific named product ('Teamwork Desk') with a distinct trigger, giving it a clear niche and minimal overlap 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/teamwork-desk/SKILL.md
Commit: f484c82

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