Name: oracle-eloqua
Rating: 60 (1 reviews)
Author: membranedev

oracle-eloqua

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

Quality

70%

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

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 delivers highly actionable, executable CLI commands and a clear connect-and-run workflow with state-based checkpoints, held back only by minor verbosity in the intro and loose step numbering.

Suggestions

Tighten or remove the introductory paragraph defining Oracle Eloqua and the duplicated `membrane action list` example to reduce token overhead.

Replace the informal 'Step 2' / '1b' references with explicit numbered steps (1. Connect, 2. Discover and run actions) so the workflow sequence is unambiguous.

Consider moving the proxy-options flag table and the detailed clientAction state reference into a separate reference file so the main flow stays scannable.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven, but the three-sentence intro paragraph explaining what Oracle Eloqua is and the duplicated `membrane action list` command (lines 105-106 and 115) are unnecessary padding that could be trimmed, matching the 'mostly efficient with some unnecessary explanation' anchor.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run with --json, proxy flags) and a concrete proxy-options table covering the common cases, matching the 'fully executable, copy-paste ready, covers common cases' anchor.	5 / 5
Workflow Clarity	Sequences a clear install→authenticate→connect→poll→search→run workflow with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, but step labels are informal ('Step 2' referenced without a clear Step 1/2 header, a lone '1b' subsection), matching the 'clear sequence with most checkpoints present, minor gaps' anchor.	4 / 5
Progressive Disclosure	The single SKILL.md is organized into well-labeled sections (Overview, Working with Eloqua, Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references, but all content is inlined in one file with no external references, matching the 'good structure, most content appropriately placed, minor organization gaps' anchor.	4 / 5
	Total	16 / 20 Passed

Description

66%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 covers the required 'what' and 'when' and is anchored to a distinctive named product, but its action vocabulary is generic and its trigger terms lack the natural variations a user would actually say.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Eloqua capabilities such as 'create and send email campaigns, manage contacts and segments, and score leads'.

Expand the 'Use when...' trigger with natural phrases users say, e.g. 'Use when the user wants to manage Eloqua campaigns, contacts, forms, segments, or lead scoring.'

Reference the specific Eloqua objects surfaced in the body (Campaign, Contact, Form, Segment, Email) to strengthen specificity and trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Oracle Eloqua integration') and a couple of actions ('Manage data, records', 'automate workflows'), but the actions are generic rather than several concrete capabilities, matching the anchor for naming the domain with 1-2 non-comprehensive actions.	3 / 5
Completeness	Explicitly answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Oracle Eloqua data'), fitting the anchor for having both with the 'when' somewhat generic; not a 5 because the trigger phrases are not concrete.	4 / 5
Trigger Term Quality	Includes the product keyword 'Oracle Eloqua' and a 'Use when...' trigger, but the trigger phrase ('interact with Oracle Eloqua data') is generic and misses natural variations users would say (campaigns, leads, emails, segments), matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Ties triggers to the named product 'Oracle Eloqua', giving it a clear niche with minimal conflict risk against other skills, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	15 / 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/oracle-eloqua/SKILL.md
Commit: f484c82

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