Attendance Giriton
v1.0.0Attendance GIRITON integration. Manage data, records, and automate workflows. Use when the user wants to interact with Attendance GIRITON data.
⭐ 0· 54·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, the instructions, and required tooling all focus on using the Membrane CLI to integrate with Attendance GIRITON. The requested actions (connect, action run, proxy requests) are coherent with an integration skill.
Instruction Scope
Instructions are limited to installing and using the Membrane CLI and performing actions/proxied requests via Membrane. This is in-scope for the stated purpose. Note: using the proxy means requests and authentication flows go through Membrane's service (so Membrane will see proxied requests and hold the connection credentials).
Install Mechanism
No automated install spec in the skill metadata (instruction-only). The README instructs the user to run `npm install -g @membranehq/cli` — a standard public npm package install. This is expected for a CLI-based integration but depends on trusting the @membranehq/cli package from the npm registry.
Credentials
The skill does not request environment variables or secret keys. It requires a Membrane account and browser-based authentication, which is proportional. Keep in mind granting Membrane access to your Attendance GIRITON account is necessary for the integration to work.
Persistence & Privilege
The skill is not always-on, does not request to modify other skills or system settings, and is user-invocable only. There is no build-time or runtime persistence requested by the skill itself.
Assessment
This skill is an instructions-only integration that relies on the Membrane service and its CLI. Before installing or using it: (1) Verify you trust Membrane (@membranehq/cli on npm and getmembrane.com) because requests and authentication will be proxied through their service and they will hold the connection credentials; (2) Install the CLI manually (npm global install) only if you are comfortable installing public npm packages; (3) In headless or automated environments, follow the documented login flow carefully — do not paste secrets into unrelated prompts; (4) If you need stricter control over data flow or credentials, consider using a direct API integration with credentials you control rather than the proxy. Overall the skill's requirements and instructions match its stated purpose.Like a lobster shell, security has layers — review code before you run it.
latestvk977qcshty7ddw410txn6y7ev984bq2d
License
MIT-0
Free to use, modify, and redistribute. No attribution required.