CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

axiom-audit-siri-ai

Use when the user mentions Siri AI readiness, tool intents, or App Skills.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./axiom-codex/skills/axiom-audit-siri-ai/SKILL.md
SKILL.md
Quality
Evals
Security

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.

This is an exceptionally strong instruction-only skill body: every phase is sequenced with explicit read-before-report validation, the grep patterns and commands are copy-paste ready, and the 20 anti-patterns each carry measured specifics, exceptions, and concrete fixes rather than generic advice. The main improvements are removing the duplicated false-positive list (inline exceptions vs. the closing "False Positives" section) and considering whether the pattern catalog belongs in a reference file to keep the main body lean.

DimensionReasoningScore

Conciseness

The body is dense with measured, non-obvious facts ("measured on Xcode 27.3", "in testing on one app and device") and wastes no tokens explaining concepts Claude already knows. It stays at 4 rather than 5 because the false-positive exceptions (`.system.searchInApp`, `@Dependency(default:)`, schema-entity plain `var`s, stored `UUID` ids) are stated twice — inline in Phase 2 patterns and again in the "False Positives" section — and the four near-identical Invocation Examples could be cut to one.

4 / 5

Actionability

The skill provides copy-paste-ready Grep regexes ("`import\s+AppIntents`", "`@AppIntent\(\s*\[?\.tool`"), an exact verification command ("`xcrun sirimetadataanalyzer <App.app> --format json`"), per-pattern severity/confidence labels with concrete fixes ("`some IntentResult & ReturnsValue<T>`", "throw `AppIntentError.UserActionRequired.signin`"), and a complete output template. This fully matches anchor 5 ("Fully executable; copy-paste ready code or commands; specific examples cover the common cases").

5 / 5

Workflow Clarity

Five explicitly sequenced phases each define their outputs, with validation checkpoints throughout: "Confirm every candidate finding by reading the surrounding code before reporting it", "Each finding needs a file:line you read", "report 'bundle membership unverified' instead of a finding", plus a terminal verify chain (build → sirimetadataanalyzer → SiriEvaluations → device) and overflow rules for >50/>100 findings. This matches anchor 5 ("Clear sequence with explicit validation steps; feedback loops for error recovery"); it is a read-only audit, so the destructive-operation cap does not apply.

5 / 5

Progressive Disclosure

No bundle files exist, and the body is well-organized with clear section headers and a "Related" section that cleanly signals one-level-deep external pointers ("`axiom-integration (skills/app-intents.md)`", "`security-privacy-scanner` agent"). It stays at 4 rather than 5 because the ~140-line, 20-pattern catalog is fully inlined — the body is the complete detailed material rather than an overview pointing to reference files, which the rubric's rationale favors splitting.

4 / 5

Total

18

/

20

Passed

Description

43%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.

The description has a clear, distinctive trigger clause aimed at the right audience, but it is only half a description: it says when to use the skill without ever saying what the skill does (source-level auditing of App Intents and App Skills for Siri AI usability, with a readiness score). Adding one sentence of concrete capabilities and the missing "App Intents" trigger term would raise both specificity and completeness substantially.

Suggestions

State the 'what' explicitly, e.g.: "Audits App Intents code and App Skills for Siri AI (27.3) usability — whether Siri can find, choose, fill, and run the app's actions — and reports a readiness score with fixes. Use when the user mentions Siri AI readiness, tool intents, App Intents, or App Skills."

Add the missing natural trigger variations the audience would say: "App Intents", "skillsbundle"/".skillsbundle", and "Siri never calls my tool", which the body's own Invocation Examples show users actually typing.

Keep the third-person, verb-led style ("Audits…", "Reviews…") while expanding, so the added capabilities read as concrete actions rather than filler.

DimensionReasoningScore

Specificity

The description names a specific domain ("Siri AI readiness, tool intents, or App Skills") but lists no actions at all — it never says the skill audits, reviews, or scores anything. This matches anchor 2 ("Names the domain but actions are minimal or generic"); it is not 1 because the domain terms are concrete rather than abstract, and not 3 because even one concrete action is absent.

2 / 5

Completeness

The "when" is explicit ("Use when the user mentions…") but the "what" is entirely missing — the description never states what the skill does. This is exactly anchor 2 ("only 'when' is present without 'what'"); anchor 3 is ruled out because it requires a clear 'what', and anchor 1 is ruled out because the 'when' clause is present and specific.

2 / 5

Trigger Term Quality

"Siri AI readiness", "tool intents", and "App Skills" are phrases the target developer audience would naturally say, but common variations are missing — most notably "App Intents" itself, the skill's primary subject, plus "skillsbundle", "Shortcuts", and "Siri". This fits anchor 3 ("Some relevant keywords but missing common variations or synonyms"), falling short of anchor 4's "Good keyword coverage".

3 / 5

Distinctiveness Conflict Risk

"Siri AI readiness, tool intents, or App Skills" carves out a clear niche with distinct triggers and minimal conflict risk with other skills. This matches anchor 5 ("Clear niche with distinct triggers; minimal conflict risk") rather than 4, since the terms are highly unlikely to fire for an unrelated skill.

5 / 5

Total

12

/

20

Passed

Validation

100%

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

CharlesWiltgen/Axiom

Path

axiom-codex/skills/axiom-audit-siri-ai/SKILL.md

Reviewed

Table of Contents

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.