recon-common-pitfalls — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited recon-common-pitfalls (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.
Aggregated pitfalls migrated from the legacy patterns/ JSON store. Each section is one pitfall; the planner should treat them as independent checks.
ID: grep-substring-match Severity: MEDIUM
Issue.
grep 'web1' also matches web10, web11, web100 in CSV lookups
Planner action.
Always use grep -w for hostname lookups in CSV files
Reviewer check.
Check all grep calls against CSV for whole-word matching
ID: idrac-ssh-hang Severity: HIGH
Issue.
SSH without ConnectTimeout blocks indefinitely when an iDRAC is unreachable, stalling the batch loop
Planner action.
Always include -o ConnectTimeout=5 in SSH commands to iDRAC
Reviewer check.
Verify all SSH calls in loops have a connect timeout set
ID: unlabeled-batch-output Severity: LOW
Issue.
Running commands across hosts without echoing the hostname makes output impossible to correlate
Planner action.
Always echo hostname before command output in batch loops
Reviewer check.
Check that all batch loops label their output with the current host
ID: cpld-firmware-not-in-ome Severity: HIGH
Issue.
Dell OpenManage Enterprise does not support CPLD (Complex Programmable Logic Device) firmware updates. CPLD sits BELOW the iDRAC -- it controls power sequencing, signal routing, and interface logic at the board level. Updating CPLD reboots the iDRAC itself since iDRAC depends on CPLD for its own power sequencing. Symptoms of outdated CPLD include intermittent power issues, unexplained fan behavior, and board-level glitches that don't appear in standard logs. Must use custom tooling or manual DUP methods. High resistance to running the update because: loss of out-of-band access during update, risk of physical truck roll if it fails.
Planner action.
When diagnosing unexplained hardware behavior (power, fans, board-level), consider CPLD firmware as a root cause. Use the custom CPLD update tool, not OME.
Reviewer check.
Verify CPLD firmware version is checked during hardware troubleshooting. Confirm OME is not being relied on for CPLD updates.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.