Oracle Taleo
v1.0.0Oracle Taleo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Oracle Taleo data.
⭐ 0· 49·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the SKILL.md: it instructs the agent to use the Membrane CLI to connect to Oracle Taleo, discover actions, run actions, or proxy raw API requests. No unrelated credentials, binaries, or config paths are required.
Instruction Scope
Instructions stay within the stated integration task (install CLI, login via Membrane, create/connect to a connector, run actions, proxy requests). Important privacy/security note: proxying requests through Membrane sends request/response data and uses Membrane-managed credentials/server-side auth — users should understand that Taleo data and auth are handled by Membrane's service.
Install Mechanism
There is no automated install spec in the skill bundle; the SKILL.md instructs users to run `npm install -g @membranehq/cli`. This is a public npm package (traceable) but installing a global npm CLI executes third-party code on the host — a normal but non-zero risk; verify the package and trust the maintainer before installing on sensitive systems.
Credentials
The skill declares no required environment variables or credentials and explicitly instructs users to rely on Membrane-managed connections rather than local API keys. The only required account is a Membrane account and browser-based login, which is proportional to the integration.
Persistence & Privilege
Skill is instruction-only, no install artifacts in the bundle, and always:false. It does not request persistent or elevated platform privileges beyond allowing the agent to invoke it when called (default behavior).
Assessment
This skill appears coherent: it delegates auth and proxying to the Membrane service and uses the Membrane CLI (npm). Before installing or using it: (1) verify you trust @membranehq/cli and the Membrane service (review their package page, repo, and privacy/security docs); (2) understand that API requests and Taleo data will flow through Membrane's servers and that Membrane will manage credentials on your behalf; (3) avoid installing the global CLI on sensitive production hosts without review; (4) if you need tighter control, prefer creating limited-scope connections in Membrane or review the CLI source code and Membrane's data handling policies. If any of these are unacceptable, do not install or use the connector.Like a lobster shell, security has layers — review code before you run it.
latestvk975hhg83r91062nq6kffdmssd84dgew
License
MIT-0
Free to use, modify, and redistribute. No attribution required.