Name: team-up
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

team-up

Team Up integration. Manage Organizations. Use when the user wants to interact with Team Up data.

Quality

62%

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/team-up/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.

The body is a well-structured, mostly executable CLI integration guide with a clear connection workflow and state-driven feedback loops. Its weaknesses are mild redundancy, a small amount of marketing prose, and a "Popular actions" section that does not list actions.

Suggestions

Trim marketing prose (e.g. "so you can focus on the integration logic rather than auth plumbing") and consolidate the duplicated action-list instructions into one section.

Either populate "Popular actions" with actual example Team Up actions or rename the section to avoid the unfulfilled promise.

Resolve the dangling "skip to Step 2" reference by either labeling the next step as Step 2 or rewording to "skip to Searching for actions."

Dimension	Reasoning	Score
Conciseness	Mostly command-focused and efficient, but it includes unnecessary prose ("so you can focus on the integration logic rather than auth plumbing," "burn less tokens") and repeats the action-list command in both "Searching for actions" and "Popular actions," fitting the mostly-efficient-with-some-to-tighten anchor.	3 / 5
Actionability	Commands like `membrane connection ensure "https://www.teamup.com/" --json` and `membrane action run <actionId> --connectionId=CONNECTION_ID --input '...'` are concrete and copy-paste ready, but the "Popular actions" heading promises actions yet only re-states the discovery command, a minor coverage gap.	4 / 5
Workflow Clarity	The install -> login -> connection ensure -> poll-for-ready -> search -> run sequence is clear with explicit state checkpoints and a feedback loop (poll again after CLIENT_ACTION_REQUIRED), but the dangling "skip to Step 2" reference is a minor gap.	4 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well-organized with clear section headers covering install, auth, connection, actions, proxy, and best practices; minor redundancy between the two action sections keeps it just below the top anchor.	4 / 5
	Total	15 / 20 Passed

Description

57%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 names the domain and includes an explicit Use-when trigger, but it is thin on concrete capabilities and trigger synonyms. It is distinct because of the named product but not comprehensive.

Suggestions

Replace the single generic verb "Manage Organizations" with several concrete actions the skill performs (e.g. view schedules, create shifts, manage team members).

Add natural trigger variations users might say, such as "Team Up schedules," "shift management," or "Teamup."

Dimension	Reasoning	Score
Specificity	Quotes "Team Up integration. Manage Organizations." name the domain but the only action, "Manage Organizations," is a single generic verb, matching the anchor whose actions are minimal or generic.	2 / 5
Completeness	It states a what ("Manage Organizations") and an explicit when ("Use when the user wants to interact with Team Up data"), so both are present; the when could be more specific, matching the anchor where 'when' could be more explicit.	4 / 5
Trigger Term Quality	The product name "Team Up" and the phrase "interact with Team Up data" give a relevant natural keyword, but common variations or synonyms are missing, fitting the anchor with some relevant keywords but missing variations.	3 / 5
Distinctiveness Conflict Risk	The specific app name "Team Up" carves a clear niche with distinct triggers and minimal conflict risk, though the generic "interact with data" phrasing leaves minor overlap risk with other Membrane app integrations.	4 / 5
	Total	13 / 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/team-up/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.