Dnsfilter
v1.0.0DNSFilter integration. Manage data, records, and automate workflows. Use when the user wants to interact with DNSFilter data.
⭐ 0· 59·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 and description match the runtime instructions: the skill is an integration that uses the Membrane CLI to interact with DNSFilter. The only external dependency it mentions is a Membrane account/CLI, which is consistent with the described capability.
Instruction Scope
SKILL.md contains only step-by-step CLI guidance: install membrane CLI (or use npx), login, create/connect a DNSFilter connection, list and run actions, or proxy requests. It does not instruct reading unrelated files, asking for local API keys, or exfiltrating data outside the Membrane proxy flow.
Install Mechanism
This is an instruction-only skill (no install spec). It recommends installing a public npm package (@membranehq/cli) globally or using npx. Installing third-party npm packages is normal for this use case but carries the usual supply-chain risks; the skill itself does not perform any automatic installs or download arbitrary archives.
Credentials
The skill declares no required environment variables or credentials. The SKILL.md explicitly advises not to ask users for API keys and relies on Membrane to manage credentials server-side, which is consistent and proportionate.
Persistence & Privilege
always is false, there is no install script or files written by the skill, and no instructions to modify other skills or global agent settings. The skill does not request elevated or persistent privileges.
Assessment
This skill is internally consistent but relies on a third party (Membrane) and a public npm package. Before installing or using it: (1) Review Membrane's privacy, terms, and security posture—Membrane will handle and store DNSFilter credentials and can access DNSFilter data on your behalf. (2) Inspect the @membranehq/cli package source and publisher on GitHub/NPM or prefer using npx to avoid a global install. (3) Limit connection scope in DNSFilter (use least privilege) and prefer testing with a non-production tenant/account first. (4) If you have supply-chain concerns, run the CLI in an isolated environment (container/VM) or review the package release history and maintainers. (5) Do not provide unrelated credentials; the skill does not require additional env vars.Like a lobster shell, security has layers — review code before you run it.
latestvk97bydatyzhjmyvwvg0wzrgwdd849pq0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.