Name: teamwork-crm
Rating: 60.8 (1 reviews)
Author: membranedev

teamwork-crm

Teamwork CRM integration. Manage Deals, Persons, Organizations, Leads, Projects, Activities and more. Use when the user wants to interact with Teamwork CRM data.

Quality

71%

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

A highly actionable, well-structured CLI integration guide with concrete commands, a clear connection workflow, and explicit state-handling feedback loops. Its weaknesses are an unnecessary introductory explanation of what a CRM is, placeholder-only examples, and missing verification steps for write operations.

Suggestions

Cut the introductory paragraph explaining what Teamwork CRM / a CRM is, and remove filler lines like "Use action names and parameters as needed." to tighten token efficiency.

Add a verification step after create/update actions (e.g., re-fetch the created deal with get-deal to confirm) so write workflows have an explicit validation checkpoint.

Move the 30-item entity list and the 20-row popular-actions table into a references file (e.g., references/actions.md) and link to it, leaving SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The intro paragraph explaining what a CRM is and who uses it ("Teamwork CRM is a customer relationship management platform...used by sales teams and business owners to track leads...") is padding Claude does not need, alongside filler like "Use action names and parameters as needed."; this matches the anchor for mostly efficient content with some unnecessary explanation, and is not a 4 due to these noticeable padding instances.	3 / 5
Actionability	Concrete, executable commands appear throughout (npm install, membrane login, connection ensure, action list/run, request) plus a 20-row actions table, giving mostly executable guidance; it is not a 5 because examples rely on unfilled placeholders (<actionId>, CONNECTION_ID, <code>) with no single end-to-end worked example.	4 / 5
Workflow Clarity	A clear sequence (install, authenticate, connect, poll until READY, search, run) includes explicit checkpoints and a feedback loop for CLIENT_ACTION_REQUIRED; it is not a 5 because create/update write operations lack verification steps, leaving minor validation gaps.	4 / 5
Progressive Disclosure	The body is well-organized into clearly headed sections and is self-contained with no nested references, matching the anchor for good structure with most content appropriately placed; it is not a 5 because the sizable inline entity list (30 bullets) and 20-row actions table could live in a reference file and there are no file-based references at all.	4 / 5
	Total	15 / 20 Passed

Description

75%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, well-structured description that names the specific product and enumerates concrete CRM entities with an explicit use-when trigger. Its main limitation is the generic verb "Manage" and a "when" clause that lacks richer trigger phrases and common synonyms.

Suggestions

Replace the generic verb "Manage" with distinct concrete actions (e.g., "Create, update, and retrieve Deals, Persons, Organizations, Leads...") to raise specificity.

Expand the "Use when" clause with concrete trigger phrases and synonyms (e.g., "Use when the user wants to manage Teamwork CRM deals, leads, contacts, or companies").

Dimension	Reasoning	Score
Specificity	"Manage Deals, Persons, Organizations, Leads, Projects, Activities and more" lists several concrete CRM entities, matching the anchor for several specific items with minor gaps (the "and more" hedge); it is not a 5 because the single verb "Manage" is generic rather than enumerating distinct actions.	4 / 5
Completeness	It provides a clear "what" (the managed entities) and an explicit "when" ("Use when the user wants to interact with Teamwork CRM data"), satisfying the anchor for both present with room to improve; it is not a 5 because the "when" clause is generic ("interact with...data") rather than rich concrete trigger phrases.	4 / 5
Trigger Term Quality	"Teamwork CRM", "Deals", "Leads", "Persons", and "Organizations" are natural terms users would say, giving good keyword coverage; it falls short of 5 because common synonyms like "contacts" and "companies" are absent.	4 / 5
Distinctiveness Conflict Risk	Naming the specific product "Teamwork CRM" establishes a clear niche with mostly distinct triggers, but the generic CRM entity terms (deals, leads) carry minor overlap risk with other CRM skills, keeping it at 4 rather than 5.	4 / 5
	Total	16 / 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-crm/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.