Network Security Skills
v1.0.0Generates comprehensive skill assessments and personalized learning roadmaps for network and security professionals.
⭐ 0· 41·0 current·0 all-time
byToolWeb@krishnakumarmahadevan-cmd
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 (skill assessment and learning roadmaps for network/security) align with the provided SKILL.md and openapi.json: endpoints and request/response schemas are exactly what you'd expect for an assessment-generation API. There are no unrelated required binaries, env vars, or config paths.
Instruction Scope
SKILL.md contains API usage, sample requests/responses, and endpoint documentation only. It does not instruct the agent to read local files, environment variables, or system configuration, nor to transmit data to unexpected endpoints. Lab scenarios are described at a high level (e.g., 'Configure Cisco ASA Firewall Rules') but do not contain device credentials or commands to run on local systems.
Install Mechanism
This is an instruction-only skill with no install spec and no code files to execute. Nothing will be downloaded or written to disk by an installation step in the skill itself.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. That matches the described API documentation and is proportionate to its stated function.
Persistence & Privilege
The skill does not request always:true and is user-invocable with normal autonomous invocation allowed by platform policy. It does not ask to modify other skills or system-wide settings.
Assessment
This skill appears internally consistent and low-risk: it’s just documentation (an OpenAPI spec and usage notes) for an assessment-generation API and requests no credentials or installs. However, provenance is unknown (no homepage, unknown source), so if you plan to rely on it in a corporate environment: (1) prefer skills from a known/trusted publisher; (2) avoid including sensitive or proprietary data in sample requests sent to external services; (3) review any generated lab instructions before executing them on live network equipment (they may suggest configuration steps that should be validated in a sandbox); and (4) if you need an actual running service, ensure you deploy a vetted implementation rather than relying on an untrusted third-party endpoint.Like a lobster shell, security has layers — review code before you run it.
latestvk973yh2evaxkzm97xbm7b0ezb983y5ct
License
MIT-0
Free to use, modify, and redistribute. No attribution required.