← Back to Skills Marketplace
136
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install normieclaw-security-team
Description
Automates daily security, platform, and memory audits of your OpenClaw environment, alerting only on critical risks requiring immediate action.
Usage Guidance
Summary & next steps before installing/running:
- Expect writes: despite README claims of "read-only by design," the setup steps create security-team/state.json, an audit-history dir, and copy the skill's scripts/config into your workspace. If you prefer no persistent footprint, do not run the setup; instead run the scripts from the skill directory manually.
- Inspect and test scripts locally first: open scripts/security-scan.sh and scripts/platform-health.sh and search for the 'find_skill_root' function and other top-of-file logic. In the provided files there are garbled lines in the skill-root detection (malformed quoting); fix or validate these before executing. Run scripts in a safe environment (non-production VM or container) first.
- Validate network behavior: the scripts will make outbound requests to whatever domains you add to config/domains and will call npm (which may contact registries) and openssl/curl. Ensure you only configure intended endpoints. The skill does not declare any telemetry endpoints, but you should monitor outbound connections during a first run.
- Review permissions and state files: the setup changes file permissions and creates a state directory with audit history. If you are comfortable with that persistence, proceed; otherwise run scans ad-hoc and avoid running the setup copy steps.
- Check large-repo and git-history impact: git history scanning and npm audits can be expensive on large repos. Limit scan_directories in config/security-config.json to avoid unintended heavy scans.
- If you want stronger assurance, run the scripts through static linters (shellcheck) and execute them step-by-step with 'set -x' in an isolated environment to see what they do before letting an agent run them autonomously.
If you want, I can point out the exact lines with malformed quoting in the scripts and suggest a corrected snippet to safely detect the skill root.
Capability Analysis
Type: OpenClaw Skill
Name: normieclaw-security-team
Version: 1.0.3
The 'Security Team' skill bundle is a comprehensive security and health monitoring tool designed for the OpenClaw environment. It includes well-structured Bash scripts (security-scan.sh and platform-health.sh) that perform legitimate auditing tasks such as secret detection, npm vulnerability checks, and service uptime monitoring. The skill demonstrates high security awareness by including explicit prompt-injection defenses in SKILL.md, enforcing strict file permissions (chmod 600/700) for its data directory, and implementing mandatory redaction of discovered secrets to prevent accidental exposure in chat logs.
Capability Assessment
Purpose & Capability
Skill name/description and the included scripts align: it is a local security/platform/memory auditor that reads code, git history, runs npm audit, curl, openssl, and reports findings. However the README and SECURITY.md assert "read-only by design," while SETUP-PROMPT.md explicitly instructs the agent to create directories, initialize security-team/state.json, and copy scripts/config into the user's workspace. That is a real behavior mismatch (observational vs writes to workspace) and should be expected by the user.
Instruction Scope
SKILL.md and SETUP-PROMPT instruct the agent to run search tools (rg/grep), git log -p across history, npm audit, curl to configured domains, and to copy files into config/ and scripts/ in the user's workspace. Those actions are consistent with the auditor purpose, but they access broad textual data (source code, git history, config files) and create persistent state. The skill's own prompt-injection defense text is present; a pre-scan pattern flagged 'ignore-previous-instructions' (this appears to be part of the defense text, not active injection). The agent will also be asked to run shipped scripts — those scripts contain some garbled/malformed lines in their skill-root detection functions which could cause failures or unexpected behavior; this reduces trust and increases risk. Overall instructions are fairly prescriptive (calls out exact commands) rather than vague, which is good, but the discrepancy between 'read-only' claims and explicit instructions to write files is a notable scope creep.
Install Mechanism
There is no automatic install spec — the skill is instruction-plus-scripts only. That is lower-risk than arbitrary network installs. The provided scripts are executed locally; nothing in the manifest pulls in external archives or remote installers.
Credentials
The skill declares no required environment variables or external credentials. It asks the user to configure scan directories, domains, and local services via config/security-config.json. The operations (git, npm audit, curl) don't require the skill to be given unrelated credentials. This is proportionate to the stated purpose.
Persistence & Privilege
always:false and no special platform privileges. However the setup instructions intentionally create persistent state (security-team/state.json, audit-history/) and copy scripts into the workspace, and they instruct chmod 700/600 on created files. That is expected for a local auditor but is a persistent footprint — the user should be aware the skill will write state files and scripts into their workspace.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install normieclaw-security-team - After installation, invoke the skill by name or use
/normieclaw-security-team - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.3
v1.0.3: Security fixes: confined scripts to skill directory, removed filesystem traversal from setup
v1.0.2
v1.0.2: MIT license, cleaned descriptions, removed cross-sell
v1.0.0
Initial publish from NormieClaw.ai
Metadata
Frequently Asked Questions
What is Security Team?
Automates daily security, platform, and memory audits of your OpenClaw environment, alerting only on critical risks requiring immediate action. It is an AI Agent Skill for Claude Code / OpenClaw, with 136 downloads so far.
How do I install Security Team?
Run "/install normieclaw-security-team" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Security Team free?
Yes, Security Team is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Security Team support?
Security Team is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Security Team?
It is built and maintained by Nollio (@nollio); the current version is v1.0.3.
More Skills