One operator, five workflows that replace a patchwork of tools.
Forces AI agents to enumerate five specific failure scenarios before generating any output — at least one must be unique to the current task — then declare the single most likely failure and its mitigation, so every plan accounts for what could go wrong before committing to what might go right.
A scan tells you what is wrong. This tells you what to do. Same engine as the ADA Website Risk Scanner — 14 WCAG 2.2 AA check families. But instead of a defect list, you get a work plan: findings grouped into batches, ordered by exposure reduced per hour of developer time, each with before/after code, effort estimate, required skill, and a verification step. Three phases. Quick wins first. A project manager can assign it as-is.
Paste scattered incident notes, handoff messages, timeline, and impact details, and get a factual postmortem draft: a timestamped timeline, an evidence ledger, and a bounded causal read — so you can decide what happened, what is still unknown, and which follow-ups to assign first, without inventing a root cause.
Created from 10+ years of manufacturing and industrial automation experience across food packaging, planter-part manufacturing, and Tier 1 automotive environments, with Ignition used in production-facing work over that span. The skill packages practical SCADA judgment around maintainable expressions, operator-safe behavior, troubleshooting habits, and realistic Designer/Gateway validation workflows.
Created from 10+ years of manufacturing and industrial automation experience across food packaging, planter-part manufacturing, and Tier 1 automotive environments, with Ignition used in production-facing work over that span. The skill packages practical SCADA judgment around maintainable expressions, operator-safe behavior, troubleshooting habits, and realistic Designer/Gateway validation workflows.
Find live creator and editorial topics from a global Radar, then turn one into an evidence-backed brief with research questions, must_verify, avoid_claims, and visual requirements.
Before you write code, kill the causes of rework. A phase-gate skill that runs a pre-implementation diagnosis (clarify requirements, success criteria, non-goals, hidden risks) and sets up the dev environment (toolchain check, repo init, dependency/secret/config templates, DB/API contract, folder layout). Each gate must pass before moving on. Delivers a diagnosis report, a stack-selection doc, and a ready-to-build foundation to hand off to implementation.
Stress-test any plan, PRD or decision: find the 3-5 assumptions that would kill it, with kill criteria and the cheapest test for each. Or turn a fuzzy idea into a discovery brief with opportunities, options, experiments and metrics.