Name: chartiq
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

chartiq

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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/chartiq/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.

The body is a well-structured, actionable guide with concrete Membrane CLI commands and a clear connection state machine. Its main weaknesses are moderate verbosity in the prose framing and the absence of explicit validation/error-recovery steps for action runs and proxy requests.

Suggestions

Trim editorial padding ('so you can focus on the integration logic rather than auth plumbing', 'Use action names and parameters as needed', the ungrammatical Agent Types sentence) to assume Claude's competence.

Add a validation/feedback loop for action runs and proxy requests, e.g. how to interpret error responses and when to retry or fall back to the proxy.

Consolidate the overlapping 'Searching for actions' and 'Popular actions' sections to remove the duplicated invocation examples.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but contains padding — the 'so you can focus on the integration logic rather than auth plumbing' editorializing, the repeated Membrane-benefit prose, 'Use action names and parameters as needed' filler, and the ungrammatical Agent Types sentence — fitting the score-3 anchor of mostly efficient with some unnecessary explanation.	3 / 5
Actionability	It provides concrete executable commands throughout (membrane login, connection ensure, action run, request) with real flags and JSON examples, matching score 4 of mostly executable guidance with only minor gaps such as no worked output-parsing example.	4 / 5
Workflow Clarity	The connection flow has a clear sequence with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and explicit polling, matching score 4's clear sequence with most checkpoints present, though the action-run and proxy sections lack explicit error-recovery feedback loops.	4 / 5
Progressive Disclosure	No external bundle files exist; all content lives in SKILL.md but it is reasonably scoped and organized under clear section headers with no nested references, matching score 4 of good structure with minor organization gaps (some sections like 'Popular actions' overlap with 'Searching for actions').	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.

The description clearly establishes a distinct ChartIQ niche with both what and when clauses, but its action verbs ('Manage data, records') are generic and its trigger language ('interact with ChartIQ data') is narrow. Tightening the actions to concrete ChartIQ capabilities and broadening the triggers would raise it.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete ChartIQ capabilities, e.g. 'Fetch chart data, manage studies and drawing tools, and automate ChartIQ workflows.'

Broaden the trigger clause to mirror natural user phrasing, e.g. 'Use when the user wants to work with ChartIQ charts, financial data, studies, or trading visualizations.'

Name the specific ChartIQ concepts users mention (charts, studies, drawing tools) so the trigger captures more variations.

Dimension	Reasoning	Score
Specificity	It names the ChartIQ domain and lists actions ('Manage data, records, and automate workflows'), but 'data, records' are generic nouns rather than concrete capabilities like 'fetch chart data' or 'create studies', matching the score-3 anchor of naming the domain with only vague actions.	3 / 5
Completeness	It states both what it does ('Manage data, records, and automate workflows') and when to use it ('Use when the user wants to interact with ChartIQ data'), matching score 4 where both what and when are present but the when could be more specific — it does not mention financial charts, trading, or specific ChartIQ features.	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with ChartIQ data' includes the brand term 'ChartIQ data' but uses the generic verb 'interact' and lacks synonyms or file extensions, fitting the score-3 anchor of some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	'ChartIQ integration' is a clear, named niche with distinct triggers ('ChartIQ data') and minimal overlap risk with other skills, matching the score-5 anchor for a clear niche with minimal conflict risk.	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/chartiq/SKILL.md
Commit: f484c82

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