update-solution-analyzer

MANDATORY guidelines for ANY edit to ANY file under Tools/Solutions Analyzer/ — including the mapper (map_solutions_connectors_tables.py), doc generator (generate_connector_docs.py), interactive docs (generate_interactive_docs.py), ASIM browser, collect_table_info, collect_asim_fields, upload_to_kusto, compare_runs, solution_analyzer_overrides.csv, filter_field_resolution.yaml, or any other script/config in that folder. Use when: editing/modifying/refactoring/fixing/renaming/tweaking ANY logic in those files, even one-line fixes such as renaming a classification, escaping a character, adjusting a regex, adding an override row, suppressing a false positive, or changing a constant. Covers: keeping script-docs in sync, README Version History changelog rules (required for feature/behavior changes; optional for small bug fixes), CSV output sync with upload_to_kusto.py, static/interactive index synchronization, and markdown/HTML entity page synchronization.

Quality

93%

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

87%

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

The body is a concise, actionable instruction set organized into clear synchronization concerns, with exact file paths and concrete rules. Its only weakness is workflow clarity: the sync-heavy, parallel-output tasks lack explicit validation/verification checkpoints to confirm both code paths stayed aligned after an edit.

Suggestions

Add an explicit verification step after sync-prone edits (e.g., 'After changing index logic, regenerate both static and interactive indexes and diff the outputs to confirm both reflect the change').

Include a short per-change checklist that names each artifact pair to re-check (script-doc vs per-CSV page, static index vs interactive index, markdown vs HTML entity page) so nothing is missed.

For changelog-eligible changes, add a checkpoint confirming the Version History entry was actually added before considering the edit complete.

Dimension	Reasoning	Score
Conciseness	The body is lean and instruction-oriented, using bullets and bold emphasis with no explanation of concepts Claude already knows; every section earns its place and avoids the padding seen in the lower anchors.	3 / 3
Actionability	Guidance names exact paths and identifiers ("edit the per-CSV page in `script-docs/csv/<csv-name>.md`", "Update `upload_to_kusto.py` → `SOLUTION_ANALYZER_FILES` list"); as an instruction-only skill, concrete actionable guidance substitutes for code per the scoring notes, so it is not the incomplete-pseudocode anchor at 2.	3 / 3
Workflow Clarity	Sections are logically ordered (review first, then doc/changelog/CSV/sync updates), but there are no explicit validation checkpoints or feedback loops confirming the parallel static/interactive and markdown/HTML outputs are actually in sync after edits, matching the 'steps present but checkpoints implicit' anchor rather than the explicit-validation anchor at 3.	2 / 3
Progressive Disclosure	No bundle files exist, so content is self-contained and organized into clear, well-signaled sections with no nested references; per the scoring notes a small single-purpose skill with no external references and good organization scores 3, and this does not fall to the disorganized/wall-of-text anchor at 2.	3 / 3
	Total	11 / 12 Passed

Description

100%

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

The description is specific, trigger-rich, and tightly scoped to the Solutions Analyzer folder, clearly answering both what it covers and when to use it. It uses third-person directive voice with explicit 'Use when' guidance and no first/second-person phrasing.

Dimension	Reasoning	Score
Specificity	Enumerates many concrete actions and named files ("editing/modifying/refactoring/fixing/renaming/tweaking", "renaming a classification, escaping a character, adjusting a regex, adding an override row"), matching the 'multiple specific concrete actions' anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	It clearly states both what (guidelines for edits to Solutions Analyzer files) and when (the explicit "Use when:" trigger), satisfying the highest anchor with explicit triggers rather than the implied-only anchor at 2.	3 / 3
Trigger Term Quality	The explicit "Use when: editing/modifying/refactoring/fixing/renaming/tweaking ANY logic" clause provides natural terms a user would actually say, with good coverage of common variations; not the partial-coverage anchor at 2.	3 / 3
Distinctiveness Conflict Risk	Scoping to "Tools/Solutions Analyzer/" with named scripts and configs (map_solutions_connectors_tables.py, upload_to_kusto, etc.) carves a clear niche unlikely to trigger for other skills, matching the distinct-triggers anchor.	3 / 3
	Total	12 / 12 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: Azure/Azure-Sentinel
Path: .github/skills/update-solution-analyzer/SKILL.md
Commit: fd26ba7

Reviewed: 3 days 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.