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

tubular

Tubular integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tubular 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/tubular/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 skill body is a strong, executable integration guide with copy-paste commands, a clearly sequenced connection workflow with state-based checkpoints, and clean single-file organization.

Dimension	Reasoning	Score
Conciseness	The body is command-focused and largely lean, with only minor over-explanation (the opening paragraph describing what Tubular is and who uses it) that could be trimmed, fitting 'efficient; minor instances of over-explanation'.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (npm install, membrane login, connection ensure, action list/run with JSON input, request with a full flag table), covering the common cases, matching the top anchor.	5 / 5
Workflow Clarity	The install→authenticate→connect→poll→search→run sequence is clearly ordered with explicit state checkpoints (READY/CLIENT_ACTION_REQUIRED/BUILDING) and a polling feedback loop, though action-result and destructive-proxy verification are less explicit, fitting 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references and a logical overview-to-detail flow; the single-file content is appropriately structured with only minor organization gaps, matching the 'good structure; most content appropriately placed' anchor.	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 successfully pairs a stated purpose with an explicit trigger clause and anchors the skill to a distinct named platform, but it relies on generic action language and limited trigger-term coverage.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Tubular-specific actions (e.g., 'Pull video and audience analytics, list creators, fetch comment metrics') to lift specificity.

Expand the 'Use when' clause with natural user phrasings and synonyms (e.g., 'Use when the user wants to query Tubular video metrics, audience data, or creator stats') to improve trigger-term quality.

Mention the platform's domain (social media / video analytics) in the description so it is distinguishable from generic data-management skills.

Dimension	Reasoning	Score
Specificity	Names the Tubular domain but the actions ('Manage data, records, and automate workflows') are generic rather than concrete operations, fitting the 'names domain but actions are minimal or generic' anchor.	2 / 5
Completeness	Provides both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Tubular data'), though the 'when' could be more specific, matching the 'has both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	Includes relevant keywords ('Tubular', 'data', 'records', 'workflows') and a 'Use when' trigger, but lacks common synonyms or variations a user might naturally say, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the specific named platform Tubular gives it a clear niche with minimal conflict risk, but the generic action verbs ('manage data') leave minor overlap risk, fitting 'mostly distinct; minor overlap risk'.	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/tubular/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.