Oracle Cloud Hcm
v1.0.0Oracle Cloud HCM integration. Manage data, records, and automate workflows. Use when the user wants to interact with Oracle Cloud HCM data.
⭐ 0· 14·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description announce an Oracle Cloud HCM integration and the SKILL.md exclusively documents using the Membrane CLI to connect, discover, and call HCM APIs — this matches the stated purpose and nothing unrelated is requested.
Instruction Scope
Runtime instructions only cover installing and using the Membrane CLI, logging in, creating connections, running actions, and proxying API requests. There are no instructions to read unrelated files, harvest environment secrets, or contact endpoints outside the described Membrane proxy flow.
Install Mechanism
The skill is instruction-only (no automatic install). It tells the user to run `npm install -g @membranehq/cli`, which is a typical distribution method but does require installing a global npm package — users should verify the package and its publisher before installing.
Credentials
The skill declares no required env vars or credentials and explicitly advises letting Membrane manage auth server-side. There are no requests for unrelated API keys or secrets.
Persistence & Privilege
The skill is not always-enabled and is user-invocable. It can be invoked autonomously (platform default), but there are no additional persistence or cross-skill configuration changes requested.
Assessment
This skill appears coherent and uses the Membrane CLI to handle Oracle Cloud HCM access. Before using: (1) verify the @membranehq/cli package and the referenced repository (check the npm package page and GitHub source) to ensure you trust the publisher; (2) be aware you will grant Membrane access to HCM data during connection/auth flows — confirm this meets your privacy/compliance needs for HR data; (3) prefer installing the CLI in a controlled environment (non-root or container) and review any auth browser flows and audit logs; and (4) do not share unrelated credentials — the skill explicitly warns not to ask users for API keys.Like a lobster shell, security has layers — review code before you run it.
latestvk97fdrn59q9279qjz45g1bdb9d84ezeg
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
