axiom-analyze-triage

Use when the user wants to triage a CORPUS of production crashes/hangs from an aggregator (Sentry, App Store Connect) — grouped, counted issues — rather than a single crash file.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

88%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 highly actionable, well-sequenced corpus-triage workflow with strong validation guardrails for a batch operation. The only real cost is the length of the inlined safety-note blocks, which is deliberate but still token-heavy.

Suggestions

The three inlined standing-note blocks are byte-identical to production-triage.md by assertion; if any harness ships axiom-shipping, consider a one-level reference plus a terse inline fallback rather than full verbatim copies to recover tokens.

The anr_suspension standing note packs several distinct arguments (watchdog signature, SwiftUI App.$main, MetricKit discrimination) into one paragraph; splitting into bullet points would aid scanning without losing content.

Progressive disclosure could reach 5 by extracting the per-provider fetch/normalize detail (Sentry steps 1-5, ASC steps 1-3) into a referenced file once a local bundle is permitted.

Dimension	Reasoning	Score
Conciseness	Dense and assumes Claude's competence (no generic explanations of crashes/Sentry), but the three inlined standing-note blocks — especially the long anr_suspension note — are verbose even though their inlining is explicitly justified for safety.	4 / 5
Actionability	Copy-paste-ready throughout: exact endpoints with query params, the `xcsym triage --latest-version ...` command, JSONL output path, and the TriageResult JSON fields to parse.	5 / 5
Workflow Clarity	A six-step sequence with explicit validation checkpoints (limit=1 scope probe with 401/403 handling, pagination-until-exhausted, errors[] reported to the user) and error feedback loops for a batch operation.	5 / 5
Progressive Disclosure	Well-signaled one-level-deep cross-skill references (production-triage.md, xcsym-ref.md, hang-diagnostics.md); no local bundle files exist, and a substantial block of inlined standing-note content could otherwise live in a separate file.	4 / 5
	Total	18 / 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, trigger-rich description that cleanly scopes a corpus-level triage skill against the single-crash-file alternative. Minor headroom only in synonym coverage and listing the downstream actions.

Dimension	Reasoning	Score
Specificity	Names the domain (corpus triage) and concrete actions — 'triage a CORPUS of production crashes/hangs', 'grouped, counted issues' from named aggregators — but stops short of listing the full set of operations the body performs.	4 / 5
Completeness	Explicit 'Use when the user wants to triage...' gives a concrete trigger, and the what (corpus triage of grouped/counted crashes/hangs from an aggregator) is clearly stated, with a negation boundary ('rather than a single crash file').	5 / 5
Trigger Term Quality	Strong natural terms users would say ('triage', 'production crashes/hangs', 'Sentry', 'App Store Connect'); a few common synonyms (e.g. 'production issues', 'rollout') are absent.	4 / 5
Distinctiveness Conflict Risk	Clear niche (corpus-level triage from aggregators) explicitly distinguished from the single-file crash-analyzer case, minimizing wrong-skill triggering.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: CharlesWiltgen/Axiom
Path: axiom-codex/skills/axiom-analyze-triage/SKILL.md
Commit: 9cbcd2d

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.