Teamioo
Analysis
This Teamioo skill is coherent for an integration, but it relies on an unpinned external CLI, persistent account credentials, and broad raw API access to workforce data.
Findings (7)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
`npx @membranehq/cli@latest request CONNECTION_ID /path/to/endpoint` ... `HTTP method (GET, POST, PUT, PATCH, DELETE)` ... `You can also pass a full URL instead of a relative path — Membrane will use it as-is.`
The skill exposes broad raw API/proxy capability, including mutating methods and full URLs, without clear approval, scope, or containment limits.
`This skill uses the Membrane CLI (`npx @membranehq/cli@latest`) to interact with Teamioo.`
The skill depends on an unpinned `@latest` npm package fetched at runtime, creating a supply-chain and version-drift risk.
`npx @membranehq/cli@latest login --tenant`
The instruction-only skill tells the agent to run an external CLI via `npx`; this is purpose-aligned but still executes local code.
`schedule employees, track attendance, and manage time off` ... `HTTP method (GET, POST, PUT, PATCH, DELETE)`
The skill can act on operational HR/workforce systems using mutating methods, but does not define containment, dry-run, confirmation, or rollback practices.
`credentials are stored in ~/.membrane/credentials.json` ... `Membrane manages the full Auth lifecycle server-side with no local secrets.`
The instructions make a reassuring 'no local secrets' claim that conflicts with the earlier statement that credentials are stored locally.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
`Requires network access and a valid Membrane account` ... `After login, credentials are stored in ~/.membrane/credentials.json and reused for all future commands.`
The skill requires delegated account access and persistent local credentials, despite the registry declaring no primary credential requirement.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
`send requests directly to the Teamioo API through Membrane's proxy` ... `injects the correct authentication headers` ... `You can also pass a full URL instead of a relative path — Membrane will use it as-is.`
The Membrane proxy/gateway handles authentication and will accept full URLs, but the artifact does not clearly bound origin or data-routing rules for those requests.
