prisma-config
v1.0.1Generate Prisma Access configurations for Strata Cloud Manager (SCM). Use when creating security policies, NAT rules, decryption policies, URL filtering prof...
⭐ 0· 20·0 current·0 all-time
byH@CKMEN@leesandao
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description state the skill generates Prisma Access/SCM configurations; the SKILL.md provides detailed guidance and output formatting for SCM API-compatible JSON. There are no unrelated environment variables, binaries, or installs requested.
Instruction Scope
Instructions are narrowly scoped: produce SCM API-compatible JSON payloads, endpoint paths, folder/query parameters, and follow Palo Alto best practices. The SKILL.md does not instruct reading local files, harvesting environment variables, or posting data to third-party endpoints. Note: it mandates producing API-ready payloads which an agent or user could then POST—review outputs before applying to production.
Install Mechanism
No install spec and no code files: this is instruction-only, so nothing is written to disk or fetched at install time.
Credentials
The skill requests no environment variables or credentials, which is proportionate for a generator-only skill. Practical use (actually pushing configs to SCM) will require separate Prisma/SCM credentials, but the skill does not request or attempt to access them.
Persistence & Privilege
always is false and there are no persistent installs or modifications to agent/system configuration. The skill does not request elevated privileges or config paths belonging to other skills.
Assessment
This skill appears to only generate SCM API-compatible JSON payloads and does not itself request credentials or perform installs. Before using: 1) Review generated JSON carefully and test in a staging environment before applying to production. 2) Provide SCM credentials to your agent only through secure, least-privileged tokens and only when necessary. 3) Be cautious if you configure an autonomous agent to both generate and POST these payloads — verify the agent's destination and authorization to avoid accidental misconfiguration. 4) If you expect the skill to actually call the API, confirm how credentials will be supplied and whether any network/call behavior is handled outside this instruction file.Like a lobster shell, security has layers — review code before you run it.
latestvk97aajnzkyxn5xtnjdxe7z69hn84mtqv
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🛡️ Clawdis