ips-cleanup — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited ips-cleanup (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Find what's broken or dead in an IP-Symcon system and resolve it: surface the instances in an error state and the dead/orphaned objects, then fix what's safely fixable and remove what's truly dead — without trading old errors for new orphans. Read-only review by default; every write goes through a plan you approve first.
REQUIRED BACKGROUND: the ipsymcon skill — same MCP, same plan-before-you-touch rule, the ips_call gateway and type-specific deletes. This is cleanup-specific orchestration on top.
"The logs are always red" is usually a handful of broken instances spamming errors, not a hopeless mess — but removing a broken instance naively orphans everything connected to it. A device connects to its gateway via ConnectionID, not as a tree-child — so a children+links check reports "0 dependencies" and is dangerously wrong. (Verified live: a Hue bridge showed 0 children / 0 links, yet had 4 lamps connected via ConnectionID.) This skill always checks three vectors before deleting, and removes bottom-up.
This is Phase 0 of a migration: clean the source first, so a greenfield migrate (ips-migration skill) carries a healthy system across instead of re-implementing the cruft. Also useful standalone as a periodic health check.
1 Review (read-only) → 2 Triage (you decide) → 3 Safe removal (plan-first)
↘ 4 Fix (apply safe, flag creds) → 5 VerifyStep-by-step, the ready-to-run scan scripts and the delete-order rules: references/workflow.md.
ConnectionID. Skipping ConnectionID is exactly how you create new red while removing old red.
parents; IPS_DeleteVariable/Category/Script/Event/Instance/Link — there is no generic delete.
human**. Apply only what's safe on your own (re-apply config, IPS_ApplyChanges, reconnect).
IPS_ENABLE_WRITE); an IPS backup is the safety net, the plan is the guardrail.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.