Name: nozbe-teams
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

nozbe-teams

Nozbe Teams integration. Manage Users, Organizations. Use when the user wants to interact with Nozbe Teams data.

Quality

66%

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/nozbe-teams/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 well-structured, highly actionable integration guide with executable commands and a state-driven connection workflow, held back by some background padding, a duplicated action-list example, and an unlabeled "Step 2" reference.

Suggestions

Remove the opening "Nozbe Teams is a project management..." paragraph and the filler line "Use action names and parameters as needed." — Claude already knows this.

Merge the duplicated "Searching for actions" and "Popular actions" sections into one, since both demonstrate `action list --intent=QUERY`.

Replace the dangling "skip to Step 2" references with explicit step labels (e.g. "### Step 1: Connect", "### Step 2: Discover and run actions") or remove them.

Dimension	Reasoning	Score
Conciseness	Mostly efficient operational command blocks, but it includes unnecessary context Claude already knows (the opening "Nozbe Teams is a project management..." paragraph), filler like "Use action names and parameters as needed.", and a duplicated action-list example across "Searching for actions" and "Popular actions."	3 / 5
Actionability	Concrete, copy-paste-ready commands cover install, auth, connection, action search/run, and proxy with a flags table; minor gaps are the placeholder CONNECTION_ID never shown resolved and the redundant action-list example.	4 / 5
Workflow Clarity	There is a clear install → auth → connect → poll sequence with state-driven branching (READY/BUILDING/CLIENT_ACTION_REQUIRED) and feedback loops (re-poll after user action, check error field), but it references an undefined "Step 2" without a matching labeled step, a minor sequencing gap.	4 / 5
Progressive Disclosure	No bundle files exist, so the skill is self-contained; it is well-organized with a clear header hierarchy and no nested/broken references, though the inline connection-state machine and proxy flags table could live in separate reference files for a skill over 50 lines.	4 / 5
	Total	15 / 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.

A solid description that pairs a named-product niche with an explicit "Use when" clause, but the capability list is thin and the trigger phrasing is generic rather than enumerating the task/project terms users would naturally say.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "Create, update, and query Users, Organizations, Projects, and Tasks."

Expand the trigger clause to list natural terms: "Use when the user wants to manage Nozbe Teams tasks, projects, comments, or team data."

Mention the other core entities (Task, Comment, Project, Context, Category) that the body exposes so the description reflects full coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ("Nozbe Teams integration") and two entity-level actions ("Manage Users, Organizations"), but "Manage" is generic and only two of the available entities are named, leaving coverage incomplete.	3 / 5
Completeness	Both "what" ("Nozbe Teams integration. Manage Users, Organizations.") and an explicit "when" ("Use when the user wants to interact with Nozbe Teams data.") are present, though the "when" clause is somewhat generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	The product name "Nozbe Teams" is a strong natural keyword and a "Use when..." trigger is present, but it omits common variations users would say (tasks, projects, comments) and relies on the generic phrase "interact with Nozbe Teams data."	3 / 5
Distinctiveness Conflict Risk	The named product "Nozbe Teams" gives it a clear niche with distinct triggers 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/nozbe-teams/SKILL.md
Commit: f484c82

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