CtrlK
BlogDocsLog inGet started
Tessl Logo

marketing-master-io

Marketing Master IO integration. Manage Leads, Persons, Organizations, Deals, Projects, Activities and more. Use when the user wants to interact with Marketing Master IO data.

58

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/marketing-master-io/SKILL.md
SKILL.md
Quality
Evals
Security

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 CLI commands and a solid validation feedback loop for connection setup. Its main weakness is mild verbosity in the overview and a few redundant or thinly-developed sections rather than any structural defect.

Suggestions

Cut the opening product-description paragraph and rhetorical asides; assume Claude knows what a SaaS marketing platform is.

Resolve the dangling "skip to Step 2" reference by adding an explicit numbered top-level sequence (1. Install, 2. Authenticate, 3. Connect, 4. Discover actions, 5. Run).

Merge the thin "Popular actions" section into "Searching for actions" or populate it with actual example action names and intents.

DimensionReasoningScore

Conciseness

The opening product-overview paragraph ("SaaS platform designed to help marketing teams...") and asides like "so you can focus on the integration logic rather than auth plumbing" are unnecessary explanation that could be trimmed, despite otherwise efficient command examples.

3 / 5

Actionability

Provides concrete, mostly copy-paste-ready commands for install, login, connection, action search/run, and proxy with a flag table; minor gaps are the unresolved placeholders (CONNECTION_ID, <actionId>) and a thin "Popular actions" section.

4 / 5

Workflow Clarity

The connection flow has explicit state-based validation and a poll/retry feedback loop (READY, BUILDING, CLIENT_ACTION_REQUIRED, error states), but the dangling "skip to Step 2" reference and lack of an overall numbered sequence leave minor gaps.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections with no nested references and no bundle files needed; minor gaps are the redundant "Popular actions" section overlapping "Searching for actions" and content (proxy flag table, best practices) that could be split out.

4 / 5

Total

15

/

20

Passed

Description

67%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 both capability and a Use-when trigger tied to a specific product, but relies on one generic verb and a single trigger phrase rather than varied natural keywords. It is solid and distinct, just not maximally specific or trigger-rich.

Suggestions

Replace the single verb "Manage" with a few distinct concrete actions (e.g., create, update, search, sync) applied to the listed entities to lift specificity.

Expand the when-clause with concrete trigger phrases users would say, e.g., "Use when the user wants to manage leads, track deals, or sync Marketing Master IO contacts."

Add common synonyms or related terms (CRM, contacts, campaigns, deals pipeline) to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

"Manage Leads, Persons, Organizations, Deals, Projects, Activities and more" names several specific entities with comprehensive coverage, though the single generic verb "Manage" keeps it just below a 5.

4 / 5

Completeness

It answers both what ("Manage Leads, Persons, Organizations...") and when ("Use when the user wants to interact with Marketing Master IO data"), but the when-clause is generic rather than enumerating concrete triggers.

4 / 5

Trigger Term Quality

The only natural trigger is the product name "Marketing Master IO" plus generic "interact with ... data"; common variations, synonyms, or related phrases users might say are missing.

3 / 5

Distinctiveness Conflict Risk

Tying the skill to the named product "Marketing Master IO" gives it a clear niche with minimal conflict risk, though the broad "interact with ... data" phrasing leaves minor overlap with generic CRM/data skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.