Name: marketo
Rating: 60.8 (1 reviews)
Author: membranedev

marketo

Marketo integration. Manage Leads, Persons, Organizations, Activities, Notes, Files and more. Use when the user wants to interact with Marketo data.

Quality

71%

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/marketo/SKILL.md

Quality

Content

68%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, built around concrete Membrane CLI commands and a well-organized section structure. Its weaknesses are an unnecessary introductory explanation of what Marketo is and a lack of validation/confirmation guidance for the destructive batch lead operations it exposes.

Suggestions

Remove or trim the opening paragraph explaining what Marketo is, since Claude already knows this; lead directly with the operational overview.

Add a validation/confirmation checkpoint before destructive batch actions (e.g., "Before running delete-leads or remove-leads-from-list, confirm the lead IDs and count with the user; these are irreversible and capped at 300 per request").

Consider moving the detailed connection-state handling and the full popular-actions catalog into a one-level-deep reference file, keeping SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The bulk is lean, command-driven content, but the opening paragraph ("Marketo is a marketing automation platform that helps businesses manage and automate their marketing campaigns...") explains a concept Claude already knows, and phrases like "so you can focus on the integration logic rather than auth plumbing" add mild padding, placing it at the mostly-efficient-with-some-unnecessary-explanation anchor.	3 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands for every common case (install, login, connection ensure, polling, action list/run, proxy) plus a flags table and a popular-actions table with keys, fully covering the executable surface.	5 / 5
Workflow Clarity	The connection flow has an explicit sequence with state checks and feedback loops (poll until READY, re-poll after CLIENT_ACTION_REQUIRED), but the skill exposes destructive/batch operations ("Delete Leads", "Remove Leads from List", max 300 per request) with no validation or confirmation step before execution, which caps this dimension at 3.	3 / 5
Progressive Disclosure	No bundle files exist; content lives in a single SKILL.md with clear, well-ordered section headers, giving good structure and easy navigation, though at ~150 lines some detail (e.g., the connection-state handling, full actions list) could be split into one-level-deep reference files, leaving a minor organization gap below the 5 anchor.	4 / 5
	Total	15 / 20 Passed

Description

73%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 explicitly covers both what the skill does and when to use it, anchored by the distinctive Marketo brand. Its main weakness is reliance on the generic verb "Manage" and the vague "and more" rather than concrete action verbs, and a trigger clause that could name more specific Marketo concepts.

Suggestions

Replace the generic "Manage ... and more" with concrete action verbs (e.g., "Create and update leads, trigger campaigns, manage static lists, sync activities").

Expand the "Use when..." clause with concrete trigger phrases (e.g., "Use when the user mentions Marketo leads, campaigns, programs, or static lists").

Add file extensions or synonyms where relevant (e.g., reference "smart campaigns" and "static lists" to match user vocabulary).

Dimension	Reasoning	Score
Specificity	It names the domain ("Marketo integration") and a list of concrete entities ("Leads, Persons, Organizations, Activities, Notes, Files"), but the only action verb is the generic "Manage" plus the vague catch-all "and more", so it falls between the generic-action anchor (2) and the specific-actions anchor (4).	3 / 5
Completeness	Both "what" ("Manage Leads, Persons, Organizations...") and "when" ("Use when the user wants to interact with Marketo data") are explicitly present, but the "when" trigger is fairly generic rather than listing concrete trigger phrases, so it does not reach the explicit-trigger anchor (5).	4 / 5
Trigger Term Quality	"Marketo" and "Leads" are natural terms users say, and the explicit "Use when the user wants to interact with Marketo data" clause gives good coverage, though common Marketo terms like "campaigns", "programs", and "email" are missing.	4 / 5
Distinctiveness Conflict Risk	"Marketo" is a specific branded platform with a distinct trigger ("interact with Marketo data"), giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	16 / 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/marketo/SKILL.md
Commit: f484c82

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