Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Audit locally installed agent skills for security/policy issues using the SkillLens CLI (`skilllens scan`, `skilllens config`). Use when asked to scan a skills directory (Codex/Claude) and produce a risk-focused audit report based on each skill's `SKILL.md` and bundled resources.
Audit locally installed agent skills for security/policy issues using the SkillLens CLI (`skilllens scan`, `skilllens config`). Use when asked to scan a skills directory (Codex/Claude) and produce a risk-focused audit report based on each skill's `SKILL.md` and bundled resources.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
One-off run: npx skilllens scan (or pnpm dlx skilllens scan) Global install: pnpm add -g skilllens
Run skilllens config to see configured scan roots and auditor CLI availability. Run skilllens scan to scan configured roots, or skilllens scan <path> to scan a specific directory. Re-run with --verbose to see raw auditor output and --force to ignore cached results.
Define scope Prefer a concrete target path (example: ~/.codex/skills) unless the user explicitly wants all configured roots. If auditing a repo checkout containing skills, scan the parent folder that contains skill directories (example: skilllens scan ./skills). Inventory skills with SkillLens Run skilllens scan [path] [--auditor claude|codex]. Treat missing auditor CLIs or skipped statuses as “manual review required”, not “safe”. Prioritize review order Review any unsafe or suspicious verdicts first. Next, review skills that request broad permissions (filesystem/network), run shell commands, or reference external downloads. Manually review each skill’s contents Read the skill’s SKILL.md and any referenced scripts/, references/, and assets/. Do not execute bundled scripts by default; inspect first. Evaluate risks (focus on realistic abuse) Exfiltration: sending file contents, env vars, tokens, SSH keys, browser data, or configs to remote endpoints. Execution: instructions to run arbitrary shell commands, curl | bash, eval, or to fetch-and-execute code. Persistence: modifying shell profiles, launch agents, cron, editor configs, or skill install locations. Privilege/approval bypass: instructions to ignore system policies, disable safety checks, or request escalated permissions unnecessarily. Prompt injection: attempts to override higher-priority instructions (“ignore previous”, “always comply”, “never mention…”). Overbroad triggers: vague descriptions that cause the skill to trigger on unrelated tasks. Produce a report For each skill, include: name, path, verdict (safe/suspicious/unsafe), risk (0–100), and bullet issues with concrete evidence (quote or filename). Recommend fixes that reduce blast radius: narrow scope, remove dangerous defaults, add explicit confirmation gates, and document required permissions.
Scan configured roots: skilllens scan Scan a specific folder: skilllens scan ~/.codex/skills Force a re-audit and show raw output: skilllens scan ~/.codex/skills --force --verbose
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.