No user-submitted related servers found.
Scored across 50 tools
Many tools have distinct purposes, but several overlap: the six catalogue loaders (load_classifications, load_approaches, load_principles, load_techniques, load_standards, load_rules) duplicate the generic sumo_qa_load_catalogue_entry, and multiple QA-workflow skills (preparing_for_work vs creating_test_plan vs strategising) have nuanced boundaries. The central routers using_sumo_qa and sumo_qa_deciding_approach reduce misselection, but tool selection can still be confusing without following the prescribed flow.
Most tools share the sumo_qa_ prefix and snake_case, but the set mixes imperative action names (load_classifications, scan_repo, format_risk_ledger) with gerund-based skill names (measuring_coverage, reviewing_before_merge, closing_qa_gaps). One tool (using_sumo_qa) lacks the prefix entirely. The pattern is readable but not uniform.
50 tools is far beyond the typical 3–15 range and burdens tool selection, even with the mentioned active tool profile and capability groups. The domain is broad, but the surface feels inflated and risks overwhelming an agent.
The suite covers a wide QA lifecycle: repo mapping, diff impact analysis, knowledge pack ingestion, test data catalogue, external skill management, risk ledger, reports, and rollout orchestration. Minor gaps exist (e.g., no delete for ingested knowledge packs, limited update paths for some artifacts), but core workflows are well covered.