Neckr0ik Security Fixer

ReviewAudited by ClawScan on May 10, 2026.

Overview

This appears to be a security auto-fixer, but it has unclear execution dependencies while giving the tool authority to automatically rewrite skill files.

Review the full source and verify the exact scanner/fixer executable before installing or running it. Start with dry-run mode, keep backups or version control, avoid `--auto` until you trust the diffs, and treat any reports as potentially containing real secrets.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

The tool may fail, or it may resolve and run an unreviewed local or installed module/command before changing skill code.

Why it was flagged

The main fixer depends on an `audit` module, but the provided manifest does not include `audit.py` and the metadata/install information declares no dependency or required scanner binary. For a tool that rewrites skill source files, this missing dependency/provenance path is material.

Skill content
from audit import audit_skill, Vulnerability, Severity
Recommendation

Only run the fixer if the scanner/fixer dependency is included or pinned in a clear install spec. Prefer invoking reviewed source directly, and verify which executable/module is actually being used.

What this means

Running automatic mode can change or break a skill's code if the generated fix is wrong or too broad.

Why it was flagged

The documented workflow supports automatic application of fixes without prompting. This is purpose-aligned and disclosed, but it is still high-impact because it can rewrite source files.

Skill content
neckr0ik-security-fixer fix /path/to/skill --auto
Recommendation

Use `--dry-run`, keep backups/version control, and review diffs before using `--auto` on important skills.

What this means

A local report or shared output could expose secrets that were present in the original code.

Why it was flagged

Because the skill targets hardcoded secrets, reports or console output containing original vulnerable code may include real tokens or passwords from the scanned project.

Skill content
Outputs a detailed fix report with:
  - Original vulnerable code
Recommendation

Do not share generated reports without redacting secrets, and rotate any credentials that were hardcoded in source files.