CtrlK
BlogDocsLog inGet started
Tessl Logo

boost-asio-pro

Use when writing or reviewing asynchronous C++ networking code with Boost.Asio or standalone Asio — TCP/UDP servers and clients, SSL/TLS, timers, strands, io_context, co_spawn, awaitable, async_read/async_write, asio::spawn, yield_context, or pre-C++20 completion-handler callbacks.

77

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

The canonical home for this skill is boost-asio-pro in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 tightly engineered body: non-obvious version floors, copy-paste build configuration, and the Asio gotchas that actually bite (strand semantics, buffer lifetimes, executor types), all sequenced with a closing validation checklist. The only weak spot is a handful of editorial phrases that add voice but not information.

Suggestions

Tighten the editorial asides in Step 3 (e.g. 'This is the single most common wrong answer about Asio', 'Reach for one of these and the build breaks on older distros') to pure statements of fact to reclaim tokens.

Consider moving the Boost.Asio vs standalone Asio comparison table and shim into references/build.md or a dedicated references/shim.md, keeping the body focused on the decision flow and gotchas.

DimensionReasoningScore

Conciseness

Dense and high-signal throughout — it assumes C++/Asio competence and skips basic explanations — but carries a few editorial sentences ('the single most common wrong answer about Asio', 'the build breaks on older distros') that could be trimmed; sits above the 3 anchor (some unnecessary explanation) but not fully at the 5 anchor (every token earns its place).

4 / 5

Actionability

Fully executable guidance: exact version-floor tables (Boost ≥ 1.77 / 1.79 / 1.85), copy-paste CMake flags (-fcoroutines, BOOST_ERROR_CODE_HEADER_ONLY), a ready-to-use dual-mode shim code block, and concrete per-API fixes (as_tuple(use_awaitable), take async_accept(make_strand(...)) by value).

5 / 5

Workflow Clarity

Clear sequence (Step 1 pick style → Step 2 floors → Step 3 rules → Anti-Patterns) capped by an explicit 'Before you call it done' checklist and a build-it feedback loop ('It compiles. Build it — most mistakes are compile-time'), giving validation checkpoints and an error-recovery loop.

5 / 5

Progressive Disclosure

SKILL.md is a lean overview that splits per-style depth into one-level-deep, clearly signaled reference files (coroutines.md, pre-cpp20.md, classic-boost.md, ssl.md, build.md — all verified to exist), with worked examples linked to an external repo; navigation is easy.

5 / 5

Total

19

/

20

Passed

Description

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

An exemplary description: it states a concrete capability, opens with an explicit 'Use when' trigger, and packs in the precise API vocabulary a practitioner would actually invoke. It is distinctive and conflict-resistant with no fluff.

DimensionReasoningScore

Specificity

Names concrete actions ('writing or reviewing asynchronous C++ networking code') and comprehensively enumerates specific capabilities — TCP/UDP servers and clients, SSL/TLS, timers, strands, io_context, co_spawn, awaitable, async_read/async_write, asio::spawn, yield_context, and pre-C++20 callbacks.

5 / 5

Completeness

Explicitly answers both what (writing/reviewing async C++ networking code across the listed features) and when ('Use when writing or reviewing asynchronous C++ networking code with Boost.Asio or standalone Asio — ...') with concrete trigger phrases, matching the 5-anchor example form.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms ('Boost.Asio' / 'standalone Asio') plus the exact API names Asio developers actually say (io_context, co_spawn, awaitable, async_read/async_write, yield_context); the lead phrase 'writing or reviewing asynchronous C++ networking code' is the natural trigger.

5 / 5

Distinctiveness Conflict Risk

A clear niche (Asio async C++ networking) with highly specific triggers like co_spawn, awaitable, and yield_context that are unique to this library, giving minimal overlap risk with other skills.

5 / 5

Total

20

/

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
alirezarezvani/claude-skills
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.