Name: totango
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

totango

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

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/totango/SKILL.md

Quality

Content

61%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 highly actionable with concrete Membrane CLI commands and a real connection-readiness feedback loop, but suffers from incoherent step numbering (a never-defined 'Step 2', an orphaned '1b'), redundant action-discovery sections, and a padded Totango intro.

Suggestions

Fix the step numbering: define a 'Step 1 / Step 2' sequence (or remove the 'skip to Step 2' and '1b' labels) so references resolve.

Remove the redundant 'Popular actions' discovery command that duplicates 'Searching for actions', or merge them into one section.

Trim the Totango marketing intro paragraph and add a brief verification step after `membrane action run` (e.g. check the `output` field for errors).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete command blocks, but includes padding such as the Totango marketing intro ('helps businesses proactively manage...') and a repeated action-list command across 'Searching for actions' and 'Popular actions', fitting 'mostly efficient but could be tightened'.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands (install, login, connection ensure, action run, request) and a detailed proxy-options table, but the dangling 'skip to Step 2' reference to a non-existent section is a minor gap keeping it below fully executable.	4 / 5
Workflow Clarity	A sequence exists with one genuine feedback loop (poll --wait for READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but the step numbering is incoherent (a '1b' with no 1a, repeated 'Step 2' references that never resolve) and there is no validation after running actions, matching 'sequence present but checkpoints missing'.	3 / 5
Progressive Disclosure	Content is organized into clear sections (Install, Authentication, Connecting, Searching, Popular actions, Best practices) with no external bundle files to reference; minor redundancy between the action-search and popular-actions sections keeps it just below optimal.	4 / 5
	Total	14 / 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 is third-person, explicit about when to trigger, and clearly niched to Totango, but its capability list is generic ('manage data, records, automate workflows') rather than naming concrete Totango operations.

Suggestions

Replace generic verbs with concrete Totango operations, e.g. 'Manage accounts and users, query customer health, and automate success workflows'.

Add natural trigger variations such as 'customer success', 'account health', or 'at-risk accounts' alongside 'Totango data'.

Tighten the 'what' so it signals specific record types (accounts, users) rather than 'data, records'.

Dimension	Reasoning	Score
Specificity	Names the domain (Totango) and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Totango operations (e.g. accounts, users, health scores), matching the '1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Totango data') are present; the 'what' is generic, so it sits at the 'both present, when could be more specific' level rather than a 5.	4 / 5
Trigger Term Quality	The phrase 'Use when the user wants to interact with Totango data' surfaces the relevant keyword 'Totango', but offers no synonyms or natural variations beyond the proper noun, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Totango is a specific named platform with a clear niche and an explicit Totango-data trigger, giving it distinct triggers and minimal conflict 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/totango/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.