Techwolf

v1.0.2

TechWolf integration. Manage data, records, and automate workflows. Use when the user wants to interact with TechWolf data.

0· 97·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description say 'TechWolf integration' and the SKILL.md consistently instructs using Membrane to connect to TechWolf. Required capabilities (installing and using @membranehq/cli, running membrane commands) match the described purpose; there are no unrelated credential or binary requirements.
Instruction Scope
Runtime instructions are limited to installing the Membrane CLI, logging in via browser, creating/listing connections, running actions, and proxying requests through Membrane. The instructions do not ask the agent to read arbitrary local files, harvest environment variables, or transmit data to unexpected endpoints beyond Membrane/TechWolf.
Install Mechanism
The skill has no registry install spec (instruction-only) but tells the user to run `npm install -g @membranehq/cli`. That is a reasonable, proportional step for this integration, but global npm installs modify the system (PATH, global node_modules). Users should verify the package and publisher on npm before installing.
Credentials
The skill declares no required environment variables or credentials and explicitly advises using Membrane to avoid local API keys. This is proportionate: authentication is delegated to the Membrane service rather than the skill requesting secrets.
Persistence & Privilege
The skill does not request always:true, does not claim to modify other skills or system-wide settings, and does not require config path access. It does not request elevated or persistent privileges beyond normal CLI usage.
Assessment
This skill is instruction-only and appears coherent, but before installing the Membrane CLI: 1) verify the @membranehq/cli package and publisher on npm (or the project's GitHub) to ensure you're installing the expected software; 2) be aware a global npm install writes files and updates PATH on your machine; 3) understand that Membrane acts as a proxy — TechWolf API requests and any transferred data go through Membrane's service, so confirm this data-handling aligns with your privacy and corporate policies; 4) if you need to run this in CI/headless environments, follow the documented headless login flow and ensure no secrets are printed or stored insecurely.

Like a lobster shell, security has layers — review code before you run it.

latestvk977j85yp2nwqypx1q9f6b2n85842rdr

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments