LOLSkillsby
Back to scanner
LOLSKILLS-SCAN / AGENT SKILL

A second look.
Before the install.

Your agent just found a new skill.
Give it the habit of checking first.

Add LOLSkills to Claude Code or Codex. Inspect the exact GitHub version, surface suspicious signals, and pause before bringing it into your workflow.

Add to your agent View on GitHub
No API keyAI off by defaultApache 2.0 helper
lolskills-scanWORKFLOW PREVIEW
YOU → YOUR AGENT

“Check this skill before
installing it.”

  1. Pin the sourceOne repository. One commit. One skill.
  2. Inspect the bundleInstructions, scripts, and related files.
  3. Review before installingFindings or gaps? The workflow pauses.
Evidence before trust.THEN → INSTALL
Inspectable source Checks an exact commit Pauses on incomplete checks
01 / MAKE IT PART OF YOUR WORKFLOW

Small skill.
Better install habits.

Choose your agent and clone the skill into its personal skills folder. The helper uses the hosted LOLSkills scanner; nothing to build or deploy.

Full setup guide on GitHub
Download release ZIP

Read it before you run it.

Inspect SKILL.md and the helper on GitHub. Cloning the repo does not execute it. If you already have it installed, review changes before updating.

TERMINAL · macOS / Linux / WSL
mkdir -p ~/.claude/skills
git clone https://github.com/magicsword-io/lolskills-scan.git ~/.claude/skills/lolskills-scan

Requires Git and Node.js 22+. No npm install or API key needed.

VERIFY THE HELPERnode ~/.claude/skills/lolskills-scan/scripts/check-skill.mjs --help

This prints usage without starting a scan. Restart your agent to load the skill.

THEN ASK CLAUDE CODE

/lolskills-scan Check this GitHub skill before installing it: <skill URL>

02 / KNOW WHAT HAPPENS NEXT

A check with a clear next step.

NO FINDINGS · EXIT 0

Continue at the checked version.

All required checks completed without signals. Your agent can continue the installation you authorized, using that exact commit and skill path.

REVIEW NEEDED · EXIT 2

Pause. Look at the evidence.

Rule signals, correlated findings, or concerning advisory AI results pause installation for review. Signals alone do not prove maliciousness.

INCOMPLETE · EXIT 3

No result is never a green light.

Missing coverage, service limits, or a timeout keep the workflow paused. Incomplete checks cannot clear an install.

A scan is evidence about one version, not a guarantee of safety.Changed files or a new commit need a new check.

How scanning works