CtrlK
BlogDocsLog inGet started
Tessl Logo

redis-insight-plugin

Use when creating, modifying, debugging, deploying, or testing Redis Insight Workbench visualization plugins, plugin manifests, package.json visualizations, activationMethod functions, redisinsight-plugin-sdk usage, Parcel/Vite plugin builds, iframe rendering, Redis command parsing, Docker RedisInsight deployment, /api/plugins verification, or Playwright plugin validation.

72

Quality

89%

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

88%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-architected skill body with executable commands, a phased development workflow, explicit verification checkpoints, and a clean reference index. The main gaps are minor redundancy between the DO NOT/Checklist sections and inline rules, and broken references to a non-existent templates/ directory.

Suggestions

Add the missing templates/ directory (with external-styles.scss) or remove the two templates/ references on lines 138 and 148 to fix the broken bundle links.

Consolidate the DO NOT list and Final Checklist so each rule lives in one canonical place, cross-referencing instead of restating to reduce token duplication.

Consider moving the long Repo Code Conventions block (which repeats sibling-skill styleguides) into a reference file, keeping the body as a brief pointer to reduce inline bulk.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence and avoids concept over-explanation; however the DO NOT list and Final Checklist restate rules already covered inline, which is duplicative though useful as quick reference, leaving minor trims available rather than full leanness.

4 / 5

Actionability

Provides copy-paste-ready commands (npm run build, test -f dist/index.js, grep -c process.env, curl /api/plugins, cp -R dist) and concrete code (export default { renderMyView }), with specific field lists and file paths covering the common build/verify/deploy cases.

5 / 5

Workflow Clarity

A clearly sequenced phased workflow (Phase 1/2/3) with explicit validation checkpoints in Build and Verify (process.env count must be 0, test -f checks), a Review Hardening adversarial loop, and a deploy-then-verify curl step with a Final Checklist feedback structure.

5 / 5

Progressive Disclosure

Strong one-level-deep structure with a Reference Index table ('Load When') and 12 real reference files, but the body references templates/external-styles.scss and the templates/ directory (lines 138, 148) which do not exist in the bundle, a notable organization gap.

4 / 5

Total

18

/

20

Passed

Description

91%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 dense, trigger-rich description that precisely scopes a narrow plugin-development niche and supplies abundant natural keywords. The only weakness is that the capability ('what') is interwoven with the 'Use when' clause instead of being stated as a clean standalone sentence.

Suggestions

Lead with a short capability statement (e.g. 'Build, deploy, and validate Redis Insight Workbench visualization plugins.') before the 'Use when...' clause so the 'what' reads as a standalone sentence.

Keep the 'Use when...' list but consider trimming a few overlapping triggers (e.g. 'package.json visualizations' and 'plugin manifests') to reduce length without losing coverage.

DimensionReasoningScore

Specificity

Enumerates many concrete actions (creating, modifying, debugging, deploying, testing) bound to specific objects (plugin manifests, package.json visualizations, activationMethod functions, Parcel/Vite builds), giving comprehensive concrete coverage rather than vague abstraction.

5 / 5

Completeness

An explicit 'Use when...' clause answers 'when' with concrete triggers, and action verbs convey 'what', but the 'what' is folded into the trigger list rather than leading as a standalone capability statement as the score-5 anchor does.

4 / 5

Trigger Term Quality

Covers natural user vocabulary with synonyms and specific tokens ('Redis Insight Workbench visualization plugins', 'plugin manifests', 'Docker RedisInsight deployment', '/api/plugins verification', 'Playwright'), matching the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

Scoped to the narrow niche of Redis Insight Workbench visualization plugins with distinct, product-specific triggers, leaving minimal overlap risk with other skills.

5 / 5

Total

19

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing, 11 suspicious

Warning

Total

15

/

16

Passed

Repository
redis/RedisInsight
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.