ot-ics

Use for authorized OT/ICS security assessment covering Purdue model zoning, PLC/SCADA exposure, industrial protocol discovery, and safe passive-first evaluation.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, lean OT/ICS assessment workflow with strong safety validation and clear progressive disclosure. The only gap is the absence of concrete executable command examples for the named tools.

Suggestions

Add 1-2 copy-paste command examples for the key tools (e.g., a rate-limited Nmap NSE scan against an authorized segment, or a tshark filter for Modbus/TCP 502) to lift actionability to fully executable.

Optionally surface the common protocol-port table (Modbus 502, S7comm 102, EtherNet/IP 44818, DNP3 20000) from the reference file into the body's Phase 1/2 checklists so it is visible at first load.

Dimension	Reasoning	Score
Conciseness	Lean checklist/table format with no padding or explanation of concepts Claude already knows (no definition of PLC, Modbus, etc.); every line carries directive value.	5 / 5
Actionability	Concrete guidance with named tools (Wireshark, Nmap NSE, binwalk/Ghidra), specific protocol ports, and per-phase checklists, but lacks copy-paste command syntax for the tools cited.	4 / 5
Workflow Clarity	Clear four-phase sequence with explicit safety validation gates (passive-first default, ready_for_act before writes, MUST NOT rules), stop-on-anomaly feedback, and a completion self-check checklist.	5 / 5
Progressive Disclosure	Well-sectioned overview with a clearly signaled, verified one-level-deep reference (references/ot-safe-assessment.md) and appropriately split safety-checklist content; easy to navigate.	5 / 5
	Total	19 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A tight, domain-specific description that explicitly pairs a 'Use for' trigger with concrete OT/ICS capabilities. Minor keyword synonyms could be added, but it is distinctive and complete.

Dimension	Reasoning	Score
Specificity	Names the OT/ICS domain plus several concrete assessment areas — 'Purdue model zoning, PLC/SCADA exposure, industrial protocol discovery, and safe passive-first evaluation' — but stops short of comprehensive coverage of all OT assessment actions (e.g., firmware, reporting).	4 / 5
Completeness	An explicit 'Use for ...' trigger clause supplies the 'when', and the enumerated assessment scope supplies the 'what', both with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Includes natural terms a user would say ('OT/ICS security assessment', 'PLC/SCADA', 'industrial protocol', 'Purdue model') with good coverage, though some common synonyms (DCS, SCADA standalone, Modbus/DNP3) are absent.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (authorized OT/ICS assessment, Purdue zoning, industrial protocols) with triggers unlikely to fire for unrelated skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: zhaoxuya520/reverse-skill
Path: skills/ot-ics/SKILL.md
Commit: 3ae5c59

Reviewed: ~2 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.