CtrlK
BlogDocsLog inGet started
Tessl Logo

customerio-performance-tuning

Optimize Customer.io API performance for high throughput. Use when improving response times, implementing connection pooling, batching, caching, or regional routing. Trigger: "customer.io performance", "optimize customer.io", "customer.io latency", "customer.io connection pooling".

67

Quality

82%

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

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill delivers highly actionable, executable code across five well-ordered techniques, but it reads as a monolithic inline implementation: bundle reference files exist yet are never cited, the LRU cache is reimplemented inline, and batch/destructive workflows lack explicit validation checkpoints.

Suggestions

Link the existing references/implementation-guide.md and references/implementation.md from the body (e.g. under an Advanced section) and move the long per-step implementations there so SKILL.md stays a concise overview.

Add explicit validation/verification checkpoints to the batch workflow — e.g. verify the buffer drained on shutdown and confirm measured latency against the Performance Targets table before declaring success.

Drop or compress the hand-rolled LRUCache class (or move it to a reference); Claude can supply a standard LRU, so the inline implementation adds tokens without adding unique knowledge.

DimensionReasoningScore

Conciseness

The body is mostly efficient executable TypeScript, but the full hand-rolled LRUCache implementation and several restating comments (e.g. "No await — returns immediately") are content Claude could produce itself and could be tightened.

2 / 3

Actionability

Every step ships complete, executable TypeScript (pooled agent, dedup cache, batch processor, fire-and-forget, regional routing) with real config values, making it copy-paste ready.

3 / 3

Workflow Clarity

Steps 1–5 are clearly sequenced and an error-handling table exists, but the batch processor and other operations lack explicit validation/verification checkpoints (e.g. confirm-flush-before-shutdown, latency-baseline verification), which caps batch-operation workflows at 2.

2 / 3

Progressive Disclosure

Sections are organized, but the bundled references/implementation-guide.md and references/implementation.md are never linked from the body, and the full per-step implementations live inline rather than being split out — structure exists but references are unsignaled and content that should be separate is inline.

2 / 3

Total

9

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 strong, third-person description that names concrete techniques, provides explicit "Use when" guidance, and lists natural trigger phrases. It is concise and clearly differentiated within the Customer.io niche.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "implementing connection pooling, batching, caching, or regional routing" plus "improving response times" — matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers what ("Optimize Customer.io API performance for high throughput" with the technique list) and when ("Use when improving response times..." plus an explicit Trigger clause), satisfying both halves.

3 / 3

Trigger Term Quality

Trigger clause gives natural phrases users would say — "customer.io performance", "optimize customer.io", "customer.io latency", "customer.io connection pooling" — with good coverage of variations.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to Customer.io API performance tuning with Customer.io-prefixed triggers, giving it a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-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.