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

thoughtspot

ThoughtSpot integration. Manage data, records, and automate workflows. Use when the user wants to interact with ThoughtSpot 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

75%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 copy-paste CLI commands and a well-structured connection workflow including validation checkpoints. It loses points on marketing-style padding and confusing section numbering that could be tightened.

Suggestions

Remove the marketing sentence about 'Business analysts, executives... without relying on traditional BI tools' and other product-pitch framing that Claude does not need.

Fix the workflow numbering: label the initial connection step as '1a' (or renumber sequentially) and explicitly mark the 'Step 2' (searching/running actions) anchor that the connection section references.

Deduplicate the 'action list' command shown in both 'Searching for actions' and 'Popular actions', keeping a single canonical example.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and command-focused, but includes marketing padding ('Business analysts, executives... without relying on traditional BI tools') and a redundant second 'action list' example that could be trimmed.	3 / 5
Actionability	Copy-paste-ready commands cover the common cases end-to-end (install, login, connection ensure, action list/run, request) and the proxy flags table gives complete executable options.	5 / 5
Workflow Clarity	The connection state machine is clearly sequenced with checkpoints (poll --wait, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after user action), but section labels are confusing ('1b' with no '1a', an unlabeled 'Step 2').	4 / 5
Progressive Disclosure	A self-contained guide with well-organized headers and no nested references; over the 50-line simple-skill threshold, and some inline detail (clientAction state handling, the proxy flags table) could be split into reference files.	4 / 5
	Total	16 / 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 clear and distinct thanks to the named proprietary app, with both a 'what' and an explicit 'Use when' clause. It is held back by somewhat generic action verbs and limited natural trigger-term coverage beyond the product name.

Suggestions

Replace generic verbs with concrete ThoughtSpot actions, e.g. 'Search data, manage Liveboards and Worksheets, run and automate workflows.'

Expand the 'Use when' clause with natural trigger phrases users would say, e.g. 'Use when the user wants to search ThoughtSpot data, view or build Liveboards, or automate ThoughtSpot workflows.'

Dimension	Reasoning	Score
Specificity	Names the ThoughtSpot domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete; not the several specific actions needed for a 4.	3 / 5
Completeness	Both 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with ThoughtSpot data') are present, though the trigger phrasing is less concrete than the 5-anchor example.	4 / 5
Trigger Term Quality	The natural term 'ThoughtSpot' is present, but supporting terms ('data', 'records') are generic and common synonyms or scenario phrases users would say are missing.	3 / 5
Distinctiveness Conflict Risk	Naming a proprietary app (ThoughtSpot) creates a clear niche with distinct triggers and minimal risk of firing for unrelated 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/thoughtspot/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.