Name: teamgantt
Rating: 60 (1 reviews)
Author: membranedev

teamgantt

TeamGantt integration. Manage data, records, and automate workflows. Use when the user wants to interact with TeamGantt data.

Quality

70%

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

Quality

Content

82%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 lean, highly actionable CLI integration guide with strong executable examples and a well-sequenced, validated connection workflow. Its main weakness is the absence of verification steps around running actions and proxy requests.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands throughout, though the opening "TeamGantt is a project management software..." orientation and the repeated `action list` invocation across "Searching for actions" and "Popular actions" are minor trim opportunities, matching anchor 4.	4 / 5
Actionability	It provides copy-paste-ready executable commands (`membrane action run <actionId> --connectionId=... --input '{...}' --json`, `membrane request CONNECTION_ID /path`) plus a full proxy flag table, covering the common cases per anchor 5.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit checkpoints and a feedback loop (poll BUILDING, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after action), but running actions and proxy requests lack result verification, so it sits at anchor 4 rather than 5.	4 / 5
Progressive Disclosure	Content is organized into clear, well-signaled sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references; it stays at anchor 4 since some detail (e.g. the long connection-state handling) could be split into a reference file.	4 / 5
	Total	17 / 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 correctly includes an explicit 'Use when' trigger and leverages a distinctive product name, but its capability phrasing is generic and it lacks natural synonyms users might say. It is functional but could be sharpened with concrete actions and broader trigger terms.

Suggestions

Replace generic verbs with concrete capabilities, e.g. "Create and manage projects, tasks, dependencies, and baselines in TeamGantt Gantt charts."

Add natural trigger synonyms beyond the product name, e.g. "Use when the user wants to manage Gantt charts, project timelines, tasks, or resources in TeamGantt."

Tie the 'when' clause to the entity list already documented in the body (projects, tasks, resources) so the description previews real capability.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the TeamGantt domain but the actions are generic ("manage", "automate") rather than concrete capabilities like creating tasks or editing Gantt charts, matching anchor 2.	2 / 5
Completeness	It has an explicit "Use when the user wants to interact with TeamGantt data" trigger and a stated "what" ("Manage data, records, and automate workflows"), satisfying both; the "what" is generic so it sits at anchor 4 rather than 5.	4 / 5
Trigger Term Quality	"TeamGantt" is a relevant keyword a user would say, but the description misses common variations and synonyms (Gantt charts, project timelines, tasks, resources), so it has some keywords with gaps per anchor 3.	3 / 5
Distinctiveness Conflict Risk	TeamGantt is a named proprietary product giving a clear niche with minimal conflict risk, but the thin trigger surface (only "TeamGantt") keeps it at anchor 4 rather than the comprehensive-trigger anchor 5.	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/teamgantt/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.