latency-critical-systems

Use for latency-sensitive systems such as realtime dashboards, market data, streaming agents, execution gateways, queues, caches, or HFT-like infrastructure where freshness and p95 latency matter. Use when p95 latency or data freshness matters — realtime dashboards, market data, streaming agents, queues, or caches.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/latency-critical-systems/SKILL.md

Quality

Content

86%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 tight, well-structured instruction skill that assumes Claude's competence and provides concrete metrics, a hot-path template, a sequenced optimization order, and explicit verification/guardrail checkpoints without padding.

Dimension	Reasoning	Score
Conciseness	Lean and token-efficient throughout: it never explains concepts Claude already knows (what p95, a cache, or a queue is) and every line is actionable guidance that earns its place.	5 / 5
Actionability	Concrete and specific guidance — a hot-path template, a numbered optimization order, and named verification readbacks (HTTP timing, provider freshness timestamp, orderbook age, VWAP assumptions) — though a few items like 'Move compute closer to the data or the user' are principles rather than executable steps, keeping it just below 5.	4 / 5
Workflow Clarity	A clear sequenced process (track metrics -> map hot path -> measure segments -> optimize in order -> verify) with an explicit verification gate ('before calling the path ready') and approval-gate guardrails; not a strict validate-fix-retry loop, so it sits at 4 rather than 5.	4 / 5
Progressive Disclosure	A single self-contained file with clean, well-labeled section headers and no nested or buried references; no external bundle files are needed or present, so navigation is trivial.	5 / 5
	Total	18 / 20 Passed

Description

70%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 trigger-rich and domain-specific with excellent 'when' guidance, but it leans on enumerating target systems rather than naming the concrete actions the skill performs, leaving the 'what' implicit.

Suggestions

Add an explicit action clause naming what the skill does (e.g., 'Measures, maps, and optimizes hot-path latency for ...') so the capability is stated, not just the trigger.

Include colloquial trigger synonyms users naturally say ('fast', 'slow', 'real-time', 'low-latency') alongside the technical terms.

Avoid duplicating the trigger list in two near-identical sentences; consolidate into one tight 'what + when' statement.

Dimension	Reasoning	Score
Specificity	It enumerates concrete target systems ("realtime dashboards, market data, streaming agents, execution gateways, queues, caches, or HFT-like infrastructure") but never states a concrete action verb for what the skill does, so it sits at the domain-named-but-actions-minimal anchor rather than 4.	3 / 5
Completeness	The 'when' is explicit and even repeated ("Use for ...", "Use when p95 latency or data freshness matters"), and the 'what' is implied via the target-system list, but the capability itself is never explicitly named as an action, keeping it below 5.	4 / 5
Trigger Term Quality	Strong natural keyword coverage ("realtime dashboards", "market data", "streaming agents", "queues", "caches", "p95 latency", "freshness") with synonyms, though colloquial variants like "fast", "slow", or "real-time" are missing.	4 / 5
Distinctiveness Conflict Risk	The latency-critical / HFT / execution-gateway niche is clearly distinct with specific triggers, but there is minor overlap risk with general performance- or monitoring-oriented skills.	4 / 5
	Total	15 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/latency-critical-systems/SKILL.md
Commit: 06c5e11

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.