Ritekit
v1.0.2Ritekit integration. Manage Hashtags, Images, Texts. Use when the user wants to interact with Ritekit data.
⭐ 0· 118·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 (Ritekit integration) match the instructions: the SKILL.md consistently instructs use of Membrane CLI to connect to Ritekit, list actions, run actions, and proxy requests. Requested capabilities (network access, Membrane account) are expected and proportional.
Instruction Scope
Runtime instructions are narrowly scoped to using the Membrane CLI (login, create connection, list/run actions, proxy requests). The SKILL.md does not ask the agent to read unrelated system files or environment variables, nor to transmit data to unexpected endpoints beyond Membrane/Ritekit.
Install Mechanism
The skill is instruction-only (no install spec), but the document tells users to run `npm install -g @membranehq/cli` (or use npx). Installing a global npm package runs third-party code on the host — this is common for CLIs but worth verifying the package/source and preferring npx or local installs where appropriate.
Credentials
The skill declares no required env vars or credentials. It explains that Membrane handles auth and advises not to collect API keys locally — this is proportionate. Be aware that Membrane (the service/operator) will hold the Ritekit credentials once you connect.
Persistence & Privilege
The skill does not request always: true and makes no requests to modify other skills or system-wide agent settings. Normal autonomous invocation is allowed by platform defaults but the skill itself shows no persistent or elevated privileges.
Assessment
This skill appears to be what it says: it uses the Membrane CLI to manage Ritekit integrations and does not request unrelated credentials. Before using it: (1) verify the @membranehq/cli package and publisher (or use `npx` to avoid a global install), (2) understand that you will log in to Membrane and Membrane will store/manage the Ritekit credentials (trust in that service matters), and (3) run installs in an environment you control (or sandbox) if you want to limit risk from installing third-party CLIs.Like a lobster shell, security has layers — review code before you run it.
latestvk97dj7metk0m0vf0pbakawhrrh842jnj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.