CtrlK
BlogDocsLog inGet started
Tessl Logo

docs-sync

Keep ioredis documentation synchronized with code behavior. Use when an agent changes public APIs, options, Redis command support, examples, generated typings, connection behavior, Cluster/Sentinel behavior, Pub/Sub, pipelines, transactions, scan streams, reconnect behavior, TypeScript usage, or release-facing behavior that may require README or docs updates.

70

Quality

85%

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

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.

A well-structured, actionable instruction-only skill with concrete commands, file paths, a clear workflow, and a properly signaled one-level-deep reference. Adding an explicit validate-and-retry loop and trimming surface-list redundancy would push it to the top tier.

Suggestions

Add an explicit feedback loop in step 5 ('if validation fails, fix the issue and re-run the check until it passes') to reach the top workflow-clarity anchor.

De-duplicate the documentation-surface listings between the workflow, the decision checklist, and the bundled checklist to tighten conciseness.

Consider a short 'References' section naming references/doc-coverage-checklist.md so the pointer is discoverable alongside the workflow rather than only in the intro sentence.

DimensionReasoningScore

Conciseness

Efficient and free of concept padding, assuming Claude's competence; minor redundancy between the workflow's documentation-surface list, the decision checklist, and the bundled checklist keeps it just short of fully lean.

4 / 5

Actionability

Provides concrete file paths and executable commands (npm run docs, node bin/index.js, tsd, npm run format-check), but the bulk is decision guidance ('update X when Y') rather than copy-paste procedures, leaving minor gaps.

4 / 5

Workflow Clarity

A clear five-step sequence with a dedicated verify step and a decision checklist, but validation lacks an explicit fix-and-retry feedback loop, so it sits below the top anchor.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview that signals a single one-level-deep reference ('also read references/doc-coverage-checklist.md'), which exists as a real bundled file; navigation is easy and content is appropriately split.

5 / 5

Total

17

/

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 strong, third-person description that clearly states what the skill does and when to use it, with comprehensive and domain-specific triggers. Slight room to add user-natural synonyms or file extensions for trigger terms.

DimensionReasoningScore

Specificity

Names the domain ('Keep ioredis documentation synchronized with code behavior') and enumerates many concrete surfaces—public APIs, options, Redis command support, examples, generated typings, Cluster/Sentinel, Pub/Sub, pipelines, transactions, scan streams, reconnect, TypeScript usage—giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (keep docs synchronized with code behavior) and 'when' ('Use when an agent changes ... release-facing behavior that may require README or docs updates') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural trigger terms for the domain ('Redis command support', 'Pub/Sub', 'pipelines', 'transactions', 'TypeScript usage'), but it leans on technical jargon and omits synonyms or file/extension variants, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (ioredis documentation sync) with distinct, domain-specific 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
redis/ioredis
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.