Name: teamwave
Rating: 60.8 (1 reviews)
Author: membranedev

teamwave

TeamWave integration. Manage Organizations, Pipelines, Users, Filters. Use when the user wants to interact with TeamWave 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/teamwave/SKILL.md

Quality

Content

76%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 highly actionable with concrete, copy-paste commands and a clean section structure, but it lacks validation checkpoints for its destructive proxy operations and carries minor redundancy and trimmable prose.

Suggestions

Add validation steps to the workflow, e.g., after `membrane connect` confirm the connection appears in `membrane connection list`, and before destructive proxy calls inspect the action output or confirm with the user.

Remove the duplicated action-discovery command in "Popular actions" since it restates the "Searching for actions" section, or collapse the two into one.

Trim the background paragraph about what TeamWave is and the "so you can focus on the integration logic" aside to save tokens.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands, code blocks, and a flags table, with only minor trimmable prose such as the introductory "TeamWave is an integrated platform..." paragraph and the "so you can focus on the integration logic" aside, matching the efficient-with-minor-over-explanation anchor.	4 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, search, connect, action list/run, request) plus a concrete flags table, fully executable and covering the common cases, matching the top anchor.	5 / 5
Workflow Clarity	The install → login → connect → discover → run sequence is present, but there are no validation checkpoints (e.g., confirm the connection succeeded, inspect action output before running, verify results), and the proxy path permits destructive POST/PUT/PATCH/DELETE calls without verification, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	The body is well organized into clearly labeled sections with no nested references and no bundle files, but at over 50 lines some inline material (the full proxy flags table, the repeated action-discovery command) could live in a separate reference, fitting the good-structure-with-minor-gaps anchor.	4 / 5
	Total	16 / 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 cleanly answers both what and when and is anchored to a distinct product, but its action verb is generic and its entity list omits the natural synonyms users would actually say. It is solid but not comprehensive.

Suggestions

Replace the generic verb "Manage" with concrete actions (e.g., "Create, list, and update Deals, Contacts, Projects, and Tasks") to lift specificity.

Add natural trigger terms and synonyms users would say, such as CRM, contacts, deals, projects, or sales pipeline, not just "TeamWave data".

Align the entity list with the skill body (Deals, Contacts, Tasks, Events, Projects, Products, Users) so the description reflects actual capabilities.

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Pipelines, Users, Filters" names the domain and several entities, but the single generic verb "Manage" leaves the concrete actions underspecified, matching the anchor that lists domain plus a few concrete actions without comprehensive coverage.	3 / 5
Completeness	It states both what ("Manage Organizations, Pipelines, Users, Filters") and when ("Use when the user wants to interact with TeamWave data"), but the trigger clause is generic rather than concrete, matching the anchor where both are present but when could be more specific.	4 / 5
Trigger Term Quality	The product name "TeamWave" and the entity names (Organizations, Pipelines, Users, Filters) give some relevant keywords, but it omits common natural synonyms a user would say (CRM, contacts, deals, projects), fitting the anchor with relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	"TeamWave integration" names a specific product niche with a distinct trigger term, giving it minimal conflict risk with other skills, matching the clear-niche anchor.	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/teamwave/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.