Name: chartmogul
Rating: 61.6 (1 reviews)
Author: membranedev

chartmogul

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

Quality

72%

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/chartmogul/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 lean, highly actionable, and well-organized with concrete commands and a clear connection-state workflow. Minor improvements would tighten the intro, resolve the dangling 'Step 2' reference, and move bulk reference material into a separate file.

Suggestions

Define or remove the dangling 'Step 2' reference so the connection workflow has an unambiguous next step.

Move the full popular-actions table and proxy flag reference into a separate references file, keeping the overview concise.

Trim the definitional opening paragraph about MRR/churn since Claude already knows these subscription-analytics concepts.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with copy-paste commands and minimal concept explanation; only minor padding like the definitional intro paragraph and a few prose asides could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands across install, auth, connection, action search/run, and proxy flows, plus a flags table and a popular-actions catalog covering common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state-based checkpoints and a poll-again feedback loop; minor gaps include a dangling 'Step 2' reference and no final verification step.	4 / 5
Progressive Disclosure	Well-sectioned self-contained document with clear headers and no broken references; the inlined full action table and proxy flags are reference-like material that could be split out for a leaner overview.	4 / 5
	Total	17 / 20 Passed

Description

62%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 cleanly states what the skill does and when to use it, with an explicit 'Use when' trigger and product-specific scoping. It is held back by generic action verbs and a narrow set of trigger phrases lacking synonyms.

Suggestions

Replace generic verbs ('Manage data, records') with specific concrete actions like 'list and update customers, plans, invoices, and subscription metrics'.

Expand the trigger clause with natural synonyms users would say, e.g. 'Use when the user wants to query Chartmogul subscription analytics, MRR, churn, customers, or invoices'.

Add file-extension or entity keywords (customers, plans, invoices, MRR) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the Chartmogul domain and a few actions ('Manage data, records, and automate workflows') but the actions are generic and not comprehensively specific.	3 / 5
Completeness	Provides both a 'what' (manage data, records, automate workflows) and an explicit 'when' clause, though the trigger is somewhat generic rather than concrete phrases.	4 / 5
Trigger Term Quality	Includes a natural trigger phrase ('Use when the user wants to interact with Chartmogul data') but offers only one phrasing with no synonyms or variations like 'subscription analytics' or 'MRR'.	3 / 5
Distinctiveness Conflict Risk	Tied to the named product Chartmogul, making it largely distinct with only minor overlap risk against general data skills.	4 / 5
	Total	14 / 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/chartmogul/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.