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.

66

Quality

78%

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

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 high-quality, actionable audit skill: concrete grep patterns, copy-paste fixes, explicit verification checkpoints, and a well-structured phased workflow. The only gap is that a long monolithic body could split some reference material into a separate file.

DimensionReasoningScore

Conciseness

The body is long but dense — runnable grep patterns, fix code, and information-rich tables — with only minor explanatory labels ('NSLayoutManager — TextKit 1 layout manager (legacy)') that could be trimmed; it does not pad with concepts Claude already knows.

4 / 5

Actionability

Copy-paste-ready Swift fix blocks for every pattern plus exact grep regexes and concrete verification steps cover the common cases fully and are directly executable.

5 / 5

Workflow Clarity

Five phases are clearly sequenced with an explicit validation checkpoint ('use Read to verify the surrounding context before reporting'), a Phase 1 output gate ('Present this map before proceeding'), output-limit handling, and a False Positives checklist; this read-only audit is not destructive so the validation cap does not apply.

5 / 5

Progressive Disclosure

No bundle directories exist; the body is well-organized into sections and the Related section gives clear one-level-deep cross-skill pointers, but the ~310-line monolith could move the pattern catalog or cross-auditor overlap tables into a reference file.

4 / 5

Total

18

/

20

Passed

Description

68%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 is a strong, explicit trigger clause with a clear TextKit niche and low conflict risk, but it is trigger-only: it never states what the skill actually does. Adding a concrete action verb would lift both specificity and completeness.

Suggestions

Lead with the action, e.g. 'Detects TextKit anti-patterns and missing Writing Tools support in UITextView/NSTextView code. Use when the user mentions TextKit review, text layout issues, Writing Tools integration, or UITextView/NSTextView code review.'

Add a natural synonym and extension such as '.swift files' or 'NSTextLayoutManager' to round out trigger-term coverage.

Make the 'what' explicit (audits for TextKit 1 fallback, deprecated glyph APIs, missing Writing Tools wiring) so both what and when are concretely answered.

DimensionReasoningScore

Specificity

The description names the domain (TextKit, Writing Tools, UITextView/NSTextView) but states no concrete actions beyond the generic word 'review' — it lists triggers, not what the skill does (e.g. detect anti-patterns, audit fallback risks).

2 / 5

Completeness

An explicit and detailed 'Use when...' clause answers 'when' clearly, and 'code review'/'TextKit review' weakly implies the 'what', but the what-action is not stated explicitly (no 'detects', 'audits', 'reports').

4 / 5

Trigger Term Quality

Natural user-facing terms ('TextKit review', 'text layout issues', 'Writing Tools integration', 'UITextView/NSTextView code review') with concrete class names, but missing synonyms and file extensions like .swift or NSTextLayoutManager.

4 / 5

Distinctiveness Conflict Risk

A clear niche (TextKit 1/2, Writing Tools, UITextView/NSTextView) with distinct, specific triggers and minimal risk of firing for unrelated skills.

5 / 5

Total

15

/

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.

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.