CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

recommendation-system

Deploy production recommendation systems with feature stores, caching, A/B testing. Use for personalization APIs, low latency serving, or encountering cache invalidation, experiment tracking, quality monitoring issues.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/recommendation-system/skills/recommendation-system/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 delivers highly actionable, largely executable guidance with a clear getting-started workflow and a well-signaled reference layer. Its main weakness is redundancy — duplicated classes and monitoring examples, plus implementation detail inlined in SKILL.md that duplicates the reference files — which costs token efficiency and dilutes the overview role.

Suggestions

Deduplicate repeated code: keep one FeatureStore definition and one Prometheus monitoring example, and cut the second occurrences in Known Issue #6 and Common Patterns.

Move the full class implementations (RecommendationService, TieredCache, sample-size calculation) into references/production-architecture.md and references/ab-testing-framework.md, leaving only minimal illustrative snippets in SKILL.md.

Fix the non-executable details in snippets: replace the wildcard redis delete with a SCAN+delete pattern, and define or import fetch_from_db, time, and logger where they are used.

DimensionReasoningScore

Conciseness

The body is code-dense rather than explanatory, but it is noticeably redundant: FeatureStore is defined twice (Core Components and Known Issue #6), Prometheus monitoring appears twice (Issue #5 and Common Patterns), and full inline implementations duplicate content already placed in references/production-architecture.md. Mostly efficient but could be tightened considerably.

3 / 5

Actionability

The Quick Start is copy-paste runnable end-to-end (install, docker, app.py, uvicorn, curl) and the snippets are near-executable. Minor gaps remain: redis delete with a wildcard key ("recs:{user_id}:*") does not actually glob-delete in Redis, and fetch_from_db, time, and logger are used but undefined.

4 / 5

Workflow Clarity

The Quick Start is a clearly numbered 5-step sequence that ends with an explicit verification step (curl test), and the Known Issues sections follow a consistent Problem→Solution structure. It falls short of 5 because no explicit error-recovery or feedback loops are described beyond the single curl check.

4 / 5

Progressive Disclosure

A dedicated "When to Load References" section clearly signals each of the four reference files (all present, one level deep) with per-file purposes. Minor gap: fully inline class implementations and the sample-size calculation belong in the reference files rather than the overview, keeping it below the anchor-5 'appropriately split' bar.

4 / 5

Total

15

/

20

Passed

Description

83%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 strong description that clearly states concrete capabilities and pairs them with an explicit, natural-language trigger clause. Its only weaknesses are minor: a few missing synonyms in the trigger terms and slight overlap risk from generic caching/experimentation phrases.

DimensionReasoningScore

Specificity

"Deploy production recommendation systems with feature stores, caching, A/B testing" lists several concrete capabilities, but coverage has minor gaps — serving, monitoring, and metric operations appear only implicitly through the trigger clause rather than as enumerated actions.

4 / 5

Completeness

It explicitly answers both what ("Deploy production recommendation systems with feature stores, caching, A/B testing") and when ("Use for personalization APIs, low latency serving, or encountering cache invalidation, experiment tracking, quality monitoring issues") with concrete trigger phrases, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Natural phrases users would say include "personalization APIs", "low latency serving", "cache invalidation", "experiment tracking", and "quality monitoring", but common synonyms like "recommender", "recsys", or "recommendation engine" are missing.

4 / 5

Distinctiveness Conflict Risk

The recommendation-system niche is distinct, but broad triggers like "cache invalidation" and "experiment tracking" could also fire for general caching or experimentation skills, giving minor overlap risk.

4 / 5

Total

17

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

secondsky/claude-skills

Path

plugins/recommendation-system/skills/recommendation-system/SKILL.md

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.