CtrlK
BlogDocsLog inGet started
Tessl Logo

oracle-cloud-hcm

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

56

Quality

63%

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-cloud-hcm/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 a well-structured, actionable CLI integration guide with strong connection-state handling, but it is held back by a redundant section, an over-explanatory intro, placeholder-only examples, and missing validation for destructive proxy operations.

Suggestions

Remove the redundant "Popular actions" section (it duplicates the "Searching for actions" command) and trim the opening HCM-definition paragraph.

Add a concrete worked example of a real HCM action, e.g. `membrane action run <workerListActionId> --connectionId=... --input '{"limit": 50}' --json`.

Add a validation/checkpoint step before destructive proxy requests (e.g. confirm method and path, or dry-run a GET first), and fix the dangling "Step 2" reference by labeling the connection steps.

DimensionReasoningScore

Conciseness

The body is mostly efficient commands, but the opening paragraph explains what Oracle Cloud HCM is (concept Claude already knows) and the "Popular actions" section redundantly re-states the `membrane action list` command already shown under "Searching for actions", fitting the 'mostly efficient but includes some unnecessary explanation' anchor.

3 / 5

Actionability

It provides copy-paste-ready CLI commands (install, login, connection ensure, action list/run, request) plus a flags table, but examples use only generic placeholders (CONNECTION_ID, <actionId>, QUERY) with no concrete HCM action example, matching the 'mostly executable guidance with minor gaps' anchor rather than fully covering common cases.

4 / 5

Workflow Clarity

The connection flow has clear state feedback loops (poll until READY, retry after CLIENT_ACTION_REQUIRED), but the action-run and proxy flows (proxy supports destructive DELETE) lack validation checkpoints, and the body references a "Step 2" that has no matching labeled step, so it sits at the 'steps listed but validation gaps' anchor.

3 / 5

Progressive Disclosure

No bundle files exist; the skill is a single file with clear section headers (Overview, Authentication, Connecting, Searching, Running actions, Proxy requests, Best practices) and easy navigation, with no nested references — good structure with only minor organization gaps such as the redundant Popular actions section.

4 / 5

Total

14

/

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 is well-formed with an explicit trigger clause and a highly distinct product niche, but its action list is generic and it lacks the natural synonyms (HR, payroll, talent) users would actually say. It is solid but not comprehensive.

Suggestions

Replace generic verbs with HCM-specific actions, e.g. "Manage workers, absence records, talent profiles, and payroll data."

Add natural trigger synonyms users would say, e.g. "Use when the user wants to work with Oracle Cloud HCM, HR records, payroll, or workforce data."

Broaden the 'when' clause beyond just 'interact with data' to cover read, create, update, and automate scenarios.

DimensionReasoningScore

Specificity

The description names the domain and two-to-three actions ("Manage data, records, and automate workflows"), but those actions are generic rather than HCM-specific (no payroll, talent, or workforce operations), matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor.

3 / 5

Completeness

Both a clear "what" ("Manage data, records, and automate workflows") and an explicit "Use when the user wants to interact with Oracle Cloud HCM data" trigger are present, but the "when" is narrow and could be more specific, matching the 'has both what and when; when could be more explicit' anchor rather than the comprehensive 5.

4 / 5

Trigger Term Quality

"Oracle Cloud HCM" is repeated and "interact with Oracle Cloud HCM data" is a usable trigger, but common synonyms users would say (HR, human capital management, payroll, talent, workforce) are missing, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

"Oracle Cloud HCM" is a specific named enterprise product with a distinct trigger, giving it a clear niche and minimal conflict risk with other skills.

5 / 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.