Oracle Field Service
v1.0.2Oracle Field Service integration. Manage data, records, and automate workflows. Use when the user wants to interact with Oracle Field Service data.
⭐ 0· 85·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
The name/description (Oracle Field Service integration) matches the runtime instructions: the SKILL.md shows how to use the Membrane CLI to create connections, list/run actions, and proxy requests to Oracle Field Service. There are no unrelated requirements (no unexpected cloud credentials, unrelated binaries, or config paths).
Instruction Scope
All instructions stay within the stated scope: installing/using the Membrane CLI, authenticating via browser or headless flow, discovering and running actions, and proxying API calls through Membrane. The SKILL.md does not instruct reading arbitrary files, harvesting environment variables, or sending data to third-party endpoints beyond Membrane/Oracle.
Install Mechanism
This is an instruction-only skill (no install spec), but the guide tells users to run `npm install -g @membranehq/cli` (and suggests `npx` for some commands). Global npm installs are common but carry moderate risk—verify the package source (npm listing/GitHub repo) before installing and prefer `npx` or a contained environment if you are cautious.
Credentials
The skill declares no required environment variables or primary credential. It explicitly recommends letting Membrane handle credentials rather than asking for API keys locally, which is proportionate for a connector integration.
Persistence & Privilege
No elevated persistence requested: always=false, user-invocable=true, no config paths or system-wide changes are described in the SKILL.md. The skill does not request permanent system-level presence or to modify other skills' configs.
Assessment
This skill appears coherent and uses the Membrane CLI to manage Oracle Field Service connections. Before installing: 1) Verify the @membranehq/cli package and its GitHub repository to ensure you trust the publisher; 2) Prefer `npx` or install in an isolated environment (container/VM) if you want to avoid a global npm install; 3) Do not share direct Oracle API keys—follow the guide to create a Membrane connection so credentials are managed server-side; 4) Confirm your organization is comfortable routing Oracle Field Service API calls through Membrane (review their privacy/security docs). If you need higher assurance, ask the skill author for the exact npm package version and verify its integrity on npm/GitHub before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk971w517afty25jgxk4sn041hn842fp1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.