CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-networking

Use when implementing or debugging ANY network connection, API call, or socket. Covers URLSession, Network.framework, NetworkConnection, connection diagnostics.

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude-plugin/plugins/axiom/skills/axiom-networking/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a well-organized networking router with concrete pointers and a clear decision sequence, but it loses conciseness by restating the same file references across four sections. Progressive disclosure is structurally sound yet weakened by missing bundle files and redundancy.

Suggestions

Consolidate the file-to-symptom mapping into the Quick Reference table alone, and have the Decision Tree and Example Invocations reference back to it rather than re-listing every path.

Ship the referenced bundle files (skills/networking-discipline.md, skills/network-framework-ref.md, skills/networking-diag.md, skills/networking-legacy.md, skills/networking-migration.md) in the bundle, or replace the paths with descriptions of where to find them.

Trim the AXIOM_AUDITOR inline block and the Anti-Rationalization table to the essentials; the router already conveys the same routing intent.

DimensionReasoningScore

Conciseness

The body is mostly efficient but repeats the same handful of file paths (e.g. skills/networking-discipline.md) across the Quick Reference table, Decision Tree, Critical Patterns, and Example Invocations sections, which could be consolidated.

3 / 5

Actionability

As a router skill it gives concrete, executable pointers — specific file paths, agent names, and slash commands (/axiom:audit networking) — with minor gaps where the dot decision tree duplicates the numbered list.

4 / 5

Workflow Clarity

A clear numbered routing sequence (1–10) plus a decision tree guides the user to the right file; no validation checkpoints are needed for a read-only router, so the simple-skill guidance applies.

4 / 5

Progressive Disclosure

Structure is good: an overview with well-signaled, one-level-deep references organized in a table and bold labels; however the referenced bundle files (skills/*.md) are not present in the bundle, and references are repeated across multiple sections rather than cleanly consolidated.

4 / 5

Total

15

/

20

Passed

Description

75%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 strong: it pairs an explicit 'Use when' trigger with a concrete framework scope, hitting both what and when clearly. It is concise and distinct, with only minor gaps in action specificity and synonym coverage.

DimensionReasoningScore

Specificity

Names the networking domain and several concrete actions ("implementing or debugging ANY network connection, API call, or socket") plus specific frameworks (URLSession, Network.framework, NetworkConnection), with minor coverage gaps rather than a fully exhaustive action list.

4 / 5

Completeness

Explicitly answers both what ("Covers URLSession, Network.framework, NetworkConnection, connection diagnostics") and when ("Use when implementing or debugging ANY network connection, API call, or socket"), with the 'when' concrete but the 'what' framed as a framework list rather than action list.

4 / 5

Trigger Term Quality

Includes natural terms users would say ("network connection", "API call", "socket", "connection diagnostics") alongside framework names; a few common synonyms or variations are missing, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The Apple-platform framework specifics (URLSession, Network.framework, NetworkConnection) carve a clear niche with minimal conflict risk, though the broad "ANY network connection" phrasing leaves minor overlap with general networking skills.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

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.