CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

redis-cache-manager

Ativado ao implementar cache distribuído no Redis, manipulação de cache-aside, definição de chaves (Key Management) e invalidação de cache na camada de Application e Infraestrutura do .NET 8.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/dotnet-clean-arch/skills/redis-cache-manager/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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-only skill: concrete API-level guidance, explicit cache-aside and invalidation sequences, and an error-recovery fallback pattern, organized in clean sections with no unnecessary references. The main improvement opportunities are a minimal executable code example and a validation checkpoint on the invalidation path.

Suggestions

Add a minimal C# snippet showing the cache-aside flow with IDistributedCache (GetStringAsync / SetStringAsync / RemoveAsync) so the read and invalidation paths are copy-paste ready.

Add a verification step after invalidation (e.g., confirm key removal or handle RemoveAsync failure inside the try-catch fallback) to close the validation gap in the write path.

DimensionReasoningScore

Conciseness

Lean, rule-based bullets that assume Claude's competence — no padding explaining what Redis, cache-aside or TTL are. Minor trimmable instances: the meta intro paragraph and the Clean Architecture rationale sentence keep it below anchor 5.

4 / 5

Actionability

Concrete, specific guidance throughout: 'IDistributedCache'/'ICacheService', 'System.Text.Json', the key format 'nomedoapp:contexto:identificador' with real examples ('machinereturn:maquinas:MQ-9988'), 'RemoveAsync', 'DistributedCacheEntryOptions', 'AbsoluteExpirationRelativeToNow', 'SlidingExpiration', 'LogWarning' and PostgreSQL fallback. Not 5 because no code snippet makes the guidance copy-paste ready and some method-level details are implied rather than stated.

4 / 5

Workflow Clarity

The cache-aside flow is explicitly sequenced (read Redis → hit: return / miss: query PostgreSQL → save → return), write-path invalidation is ordered, and try-catch → 'LogWarning' → silent DB fallback forms an explicit error-recovery loop. Not 5 because no validation checkpoint confirms invalidation succeeded or that fallback data is consistent.

4 / 5

Progressive Disclosure

A self-contained ~54-line skill with no bundle files (references/, scripts/, assets/ absent); content is appropriately all-inline for this size, organized under clear section headers with no nested or buried references. Per the rubric's simple-skill guidance, well-organized sections alone warrant 5.

5 / 5

Total

17

/

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 has a strong, explicit trigger clause with specific capability areas and good natural keywords, and it occupies a distinct niche. Its main weakness is completeness: it only states when the skill activates, never what the skill provides or does.

Suggestions

Add an explicit 'what' statement before the trigger clause (e.g., 'Orienta a implementação de cache distribuído com Redis no .NET 8: padrão cache-aside, gestão de chaves, invalidação e TTL. Ativado quando...') so the description answers both what and when.

Include additional natural trigger terms users would say, such as 'IDistributedCache', 'StackExchange.Redis', 'TTL/expiração' and 'performance', to broaden trigger coverage.

Mention the resilience/fallback capability (cache unavailability must not break the API) to close the gap between description and body scope.

DimensionReasoningScore

Specificity

Lists several concrete capability areas ('implementar cache distribuído no Redis', 'manipulação de cache-aside', 'definição de chaves (Key Management)', 'invalidação de cache') with a named domain (.NET 8, Application/Infra layers). Falls short of 5 because TTL and resilience/fallback, which the body covers, are not mentioned.

4 / 5

Completeness

The 'when' is explicit and detailed ('Ativado ao implementar...'), but the description never states what the skill does — it is entirely one trigger clause. This sits above anchor 2's bare 'Use when...' (the enumerated topics imply scope) but lacks the distinct 'what' that anchor 4 requires.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'cache distribuído', 'Redis', 'cache-aside', 'invalidação de cache', '.NET 8' — terms a user would plausibly say. Not 5 because common variations like 'IDistributedCache', 'StackExchange.Redis', 'TTL' and 'performance' are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche — Redis distributed caching in .NET 8 layered architecture — with distinct, specific triggers ('cache-aside', 'Key Management', 'invalidação de cache'); minimal conflict risk with unrelated skills.

5 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

JoseMD12/testing-tessl

Path

plugins/dotnet-clean-arch/skills/redis-cache-manager/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.