CtrlK
BlogDocsLog inGet started
Tessl Logo

wasm-constraints

WASM build constraints for the crates/xberg-wasm crate — the wasm-target feature set, no-tokio sync-only internal APIs, the mandatory SyncExtractor trait for WASM-compatible extractors, the 2 MB HTML size limit, size-optimized build config (opt-level="z"), and the async-wrapper/sync-internal API pattern. Load when building for wasm32, adding or modifying a WASM-compatible extractor, or debugging WASM build/runtime failures.

67

Quality

80%

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

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 well-structured, mostly actionable reference for WASM build constraints with concrete code examples. Its main weaknesses are the lack of explicit build/size-validation checkpoints and a redundant recap section.

Suggestions

Add an explicit validation step for the build, e.g. 'cargo build --target wasm32-unknown-unknown' and a check that the resulting .wasm stays under the jsDelivr 50 MB cap, to give the workflow a real checkpoint.

Remove or fold the 'Critical Rules' recap into the earlier sections to avoid duplicating the constraints and save tokens.

Tighten the code examples so they are copy-paste ready — define or pass in 'mime_type' and replace placeholder bodies like '/* sync implementation */' with minimal real logic or a clear 'implement sync extraction here' note.

DimensionReasoningScore

Conciseness

Mostly lean with useful context (e.g., the tree-sitter/jsDelivr 50 MB rationale), but the trailing 'Critical Rules' section largely recapitulates the constraints already detailed above and could be trimmed.

4 / 5

Actionability

Provides concrete code blocks (SyncExtractor impl, MAX_HTML_SIZE const, build config, wasm_bindgen function), but examples contain placeholders like '/* sync implementation */' and an undefined 'mime_type' variable, so they are not fully copy-paste ready.

4 / 5

Workflow Clarity

Presents a clear checklist of constraints ('No tokio', 'Implement SyncExtractor', 'HTML limited to 2MB', etc.) but includes no validation/verification checkpoints for a build process with strict size limits, which caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Well-organized with clear section headers (Overview, Feature Flags, Critical Constraints, Build Config, API Pattern, Critical Rules) and no external bundle files; slightly over the 50-line simple-skill threshold with a minor redundancy in the recap section.

4 / 5

Total

15

/

20

Passed

Description

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

A highly specific, well-triggered description that clearly states both what the skill covers and when to load it. Only minor gap is the lack of common WASM synonyms/file extensions among the trigger terms.

DimensionReasoningScore

Specificity

Enumerates multiple concrete items — 'the wasm-target feature set, no-tokio sync-only internal APIs, the mandatory SyncExtractor trait... the 2 MB HTML size limit, size-optimized build config (opt-level="z"), and the async-wrapper/sync-internal API pattern' — giving comprehensive, non-vague coverage.

5 / 5

Completeness

Explicitly answers both what ('WASM build constraints for the crates/xberg-wasm crate — ...') and when ('Load when building for wasm32, adding or modifying a WASM-compatible extractor, or debugging WASM build/runtime failures.') with concrete trigger phrases.

5 / 5

Trigger Term Quality

'Load when building for wasm32, adding or modifying a WASM-compatible extractor, or debugging WASM build/runtime failures' gives good natural keyword coverage, but misses common synonyms like 'WebAssembly', '.wasm', or 'wasm-pack'.

4 / 5

Distinctiveness Conflict Risk

Targets a very specific niche (the xberg-wasm crate, wasm32 target, SyncExtractor trait) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

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
xberg-io/xberg
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.