CtrlK
BlogDocsLog inGet started
Tessl Logo

oracle-marketing-cloud

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

59

Quality

68%

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/oracle-marketing-cloud/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 content is an efficient, actionable Membrane CLI guide with a clear connection state workflow and good sectioning. Its main gaps are inconsistent step numbering and some bulk inline reference material that could be offloaded.

Suggestions

Fix the workflow numbering: label the explicit 'Step 1'/'Step 2' sections that 'skip to Step 2' refers to, and reconcile the lone '1b.' header.

Provide one fully-worked end-to-end example with concrete values (a real connection id, action id, and intent) so the placeholders are unambiguous.

Move the full clientAction type taxonomy and proxy flag table into a dedicated reference file, keeping SKILL.md a concise overview.

DimensionReasoningScore

Conciseness

The body is largely tight CLI commands and flag tables, with only minor motivational prose ('so you can focus on the integration logic rather than auth plumbing') that could be trimmed.

4 / 5

Actionability

Concrete copy-paste commands cover the common cases (login, connection ensure, action list/run, request proxy), but placeholders like <actionId>, CONNECTION_ID, and QUERY are never shown with concrete worked values.

4 / 5

Workflow Clarity

The connection state machine is well-sequenced with polling and re-check checkpoints, but numbering is inconsistent ('skip to Step 2' with no labeled Step 2, and a stray '1b.' header without a '1a.').

4 / 5

Progressive Disclosure

A single well-organized SKILL.md with clear sections and no deep/nested references, though the full clientAction taxonomy and proxy flag table are bulk inline content, and 'Popular actions' overlaps with the searching/running sections.

4 / 5

Total

16

/

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 answers both what and when and anchors on a distinctive platform name, but its actions are generic and its trigger phrasing offers no synonyms or natural variations. Tightening the action list and adding common user phrases would lift it.

Suggestions

Replace generic verbs with Eloqua-specific actions, e.g. 'Send emails, manage contacts and groups, and search records' to match the body's actual operations.

Add natural trigger synonyms a user would say, e.g. 'Use when the user mentions Eloqua, marketing campaigns, lead generation, or email automation.'

DimensionReasoningScore

Specificity

Names the domain (Oracle Marketing Cloud) and a few actions ('Manage data, records, and automate workflows'), but the verbs are generic rather than the platform's specific capabilities (campaigns, leads, contacts, email sends) shown in the body.

3 / 5

Completeness

Both a clear 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Oracle Marketing Cloud data') are present, though the trigger clause is generic.

4 / 5

Trigger Term Quality

The trigger relies on the single proper noun 'Oracle Marketing Cloud' with no synonyms (Eloqua, marketing campaigns, lead generation) or natural phrasings users would actually say.

3 / 5

Distinctiveness Conflict Risk

The platform name is a distinct trigger with minimal conflict risk, but the generic action verbs ('manage data, automate workflows') could overlap with a general CRM/marketing skill.

4 / 5

Total

14

/

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.