CtrlK
BlogDocsLog inGet started
Tessl Logo

marin-software

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

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/marin-software/SKILL.md
SKILL.md
Quality
Evals
Security

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 a clean, executable integration guide that avoids teaching concepts Claude already knows and sequences the connection workflow with explicit state-branching and polling. Its main gaps are minor verbosity and the under-developed overview action list that names entities without describing them.

DimensionReasoningScore

Conciseness

The body is mostly lean command snippets and a flag table with no basic-concept lecturing; a few phrases like "so you can focus on the integration logic rather than auth plumbing" could be trimmed.

4 / 5

Actionability

It provides concrete, copy-paste-ready commands for install, login, connection ensure, action list/run, and proxy requests with a clear options table, with only minor placeholder gaps (CONNECTION_ID, <actionId>).

4 / 5

Workflow Clarity

The connection flow is clearly sequenced (ensure -> poll --wait -> branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with explicit feedback loops for re-polling and error inspection, though not every branch has a validation checklist.

4 / 5

Progressive Disclosure

Content is well organized into headed sections within a single file, and since no bundle files exist there is nothing to split out; structure is good with only minor organization gaps in the overview action list.

4 / 5

Total

16

/

20

Passed

Description

57%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 correctly pairs a "what" with an explicit "Use when" trigger and is anchored to a named product, giving it low conflict risk. Its weakness is generic, non-concrete action language ("manage", "automate") and limited trigger-term variety.

Suggestions

Replace generic verbs with concrete capabilities, e.g. "Create and update campaigns, pull performance reports, and manage ad spend" instead of "Manage data, records, and automate workflows".

Add natural trigger terms and synonyms users would say, such as "ad campaigns", "advertising spend", "search/social/e-commerce ads", or "Marin reports".

Tighten the "Use when" clause to name the specific scenarios, e.g. "Use when the user wants to query or manage Marin advertising campaigns, reports, or ad spend."

DimensionReasoningScore

Specificity

The phrase "Manage data, records, and automate workflows" names the domain but the actions are generic ("manage", "automate") rather than concrete, matching the anchor where actions are minimal or generic.

2 / 5

Completeness

It states a clear "what" (manage data, records, automate workflows) and an explicit "Use when the user wants to interact with Marin Software data" clause, though the "when" could be more specific.

4 / 5

Trigger Term Quality

"Marin Software" and "interact with Marin Software data" provide the relevant product keyword but miss natural synonyms and variations a user might say.

3 / 5

Distinctiveness Conflict Risk

The named product "Marin Software" gives it a clear niche with minimal overlap risk against other skills, though the generic action verbs leave slight residual ambiguity.

4 / 5

Total

13

/

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.