Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable hunt skill with concrete UDM queries, clear MCP tool invocations, and a well-sequenced multi-step workflow with appropriate escalation paths. Its main weakness is that it's somewhat long for a single SKILL.md file—the query library and key indicators table add bulk that could be externalized. The placeholder documentation table is a nice touch for customization clarity.
Suggestions
Consider moving the detailed UDM query library to a separate reference file (e.g., LATERAL_MOVEMENT_QUERIES.md) and keeping only 1-2 example queries inline to improve progressive disclosure.
Remove the Key Indicators table at the end since it largely duplicates information already conveyed by the queries themselves, improving conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and avoids explaining basic concepts, but includes some redundancy (e.g., the Key Indicators table at the end largely repeats what's already clear from the queries, and the placeholder table could be more compact). Overall reasonably lean but could be tightened. | 2 / 3 |
Actionability | Provides fully concrete UDM queries that are copy-paste ready, specific MCP tool calls with parameters, and clear instructions for each step. The placeholder table explicitly documents what needs customization, and the queries are executable rather than pseudocode. | 3 / 3 |
Workflow Clarity | The 8-step workflow is clearly sequenced with logical progression from research → query development → execution → correlation → analysis → enrichment → documentation. It includes validation through network correlation (Step 4), enrichment feedback loops (Step 6), explicit escalation paths for confirmed findings, and requires documenting negative results. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and tables, but it's a fairly long monolithic document (~130 lines of content). The references to other skills/commands (e.g., `/enrich-ioc`, `/find-relevant-case`, `case_event_timeline_and_process_analysis`) are well-signaled, but the inline query library could potentially be split into a separate reference file for better organization. | 2 / 3 |
Total | 10 / 12 Passed |