CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-audit-textkit

Use when the user mentions TextKit review, text layout issues, Writing Tools integration, or UITextView/NSTextView code review.

64

Quality

75%

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-textkit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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 audit prompt with concrete grep patterns, executable fixes, and explicit verification checkpoints. Its main weaknesses are length/redundancy across the pattern, completeness, and compound tables, and the absence of any progressive disclosure into bundle reference files.

Suggestions

Deduplicate the Phase 2 / Phase 3 / Phase 4 tables: Phase 3 and Phase 4 largely restate Pattern 1-6 findings, so collapse them into cross-references or a single compound-severity table to recover token budget.

Move the per-pattern Swift fix snippets and the Phase 5 health-scoring rubric into a reference file (e.g. references/textkit-fixes.md) and link to it from SKILL.md, so the main file stays an overview.

Create the referenced skills/textkit-ref.md as an actual bundle file (or drop the external axiom-uikit pointer) so the 'Related' references resolve within the skill bundle.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no basic TextKit explanations) and is densely actionable, but at ~310 lines it repeats the same findings across the Phase 2 patterns, the Phase 3 question table, and the Phase 4 compound table, so it could be tightened.

2 / 3

Actionability

Every phase gives concrete, copy-paste-ready Grep patterns and executable Swift fix examples (e.g. the NSTextRange conversion guard and the textLayoutManager fallback), matching the fully-executable anchor.

3 / 3

Workflow Clarity

Phases 1-5 are explicitly sequenced with validation checkpoints ('use Read to verify the surrounding context before reporting', 'Require evidence from the Phase 1 map — don't speculate') and a false-positive guardrail, matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

No bundle files exist and all detail (full pattern catalog, fix code, health-scoring rubric) lives inline in a single 310-line file; the only references point to other skills (axiom-uikit, sibling auditors), not to one-level-deep references within this skill's own bundle.

2 / 3

Total

10

/

12

Passed

Description

72%

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 focused, distinctive trigger description with strong natural keywords, but it is essentially a 'when' clause: it never states what the skill actually does (auditing/detecting TextKit issues), leaving the capability implicit.

Suggestions

Lead with an explicit capability statement before the trigger, e.g. 'Detects TextKit anti-patterns and missing patterns that cause silent TextKit 1 fallback, Writing Tools loss, and complex-script layout breakage. Use when...'.

Vary the action verbs beyond 'review' to surface concrete actions (detect, audit, flag, recommend fixes) so specificity reaches the score-3 anchor.

Keep the existing trigger-term list intact — it is the strongest part of the description.

DimensionReasoningScore

Specificity

The description names the TextKit domain and several concrete review targets ('text layout issues, Writing Tools integration, or UITextView/NSTextView code review'), but the only action verb is 'review' repeated, so it does not list multiple distinct concrete actions like the score-3 anchor.

2 / 3

Completeness

The 'when' is explicit ('Use when the user mentions...') but the 'what' (detecting TextKit anti-patterns and missing patterns) is only implied through the trigger terms rather than stated as a capability, so it does not clearly answer both what and when.

2 / 3

Trigger Term Quality

It covers natural developer terms a user would actually say — 'TextKit', 'text layout issues', 'Writing Tools', 'UITextView/NSTextView', 'code review' — matching the good-coverage anchor.

3 / 3

Distinctiveness Conflict Risk

The TextKit/UITextView/NSTextView/Writing Tools niche is narrow and specific, with triggers unlikely to fire for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

10

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
CharlesWiltgen/Axiom
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.