Awesome Support

v1.0.0

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

0· 47·0 current·0 all-time
byMembrane Dev@membranedev
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
Name/description, instructions, and required capabilities align: the skill describes an Awesome Support integration and instructs the user/agent to use the Membrane CLI and a Membrane account to create connections and run actions.
Instruction Scope
SKILL.md only instructs installing and using the Membrane CLI, creating connections, listing actions, running actions, and proxying API requests through Membrane. It does not instruct reading unrelated files, exfiltrating environment variables, or modifying unrelated system state.
Install Mechanism
The only install instruction is 'npm install -g @membranehq/cli' (a public npm package). This is proportionate to the stated purpose; no arbitrary downloads or extracts are recommended.
Credentials
The skill requests no environment variables or credentials in the metadata. It requires a Membrane account (handled via browser-based login) which is appropriate for a connector-style integration; the SKILL.md explicitly warns not to ask users for API keys.
Persistence & Privilege
The skill is not always-enabled and is user-invocable. It does not request persistent system privileges or modify other skills' configurations.
Assessment
This skill is coherent and uses the Membrane CLI to handle auth and proxies to Awesome Support. Before installing or running commands: (1) verify you trust the @membranehq/cli package and the Membrane service (check npm/GitHub and the vendor privacy/security practices), (2) be aware installing a global npm package will place code on your system, (3) the skill will perform network requests via Membrane and can act on resources you authorize in the connector—use least privilege when authorizing, and (4) review any commands the agent proposes to run in your environment (especially npm installs or commands that open browser auth flows) before approving them.

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

latestvk9780jrbnqgn1hxa1dza85hgrh84fpw9

License

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

Comments