CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

add-agent-playbooks

Add Redis Iris Agent Playbooks to an existing agent. Use when approved answers or repeatable procedures live in prompts, document retrieval, or a semantic response cache. Connect or provision a Playbook, publish FAQs and Skills, and verify the first application turn with optional review proposals.

Quality

92%

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

92%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.

An exemplary orchestration-style SKILL.md: lean, sequentially clear with explicit validation and feedback loops, and a well-structured one-level-deep reference bundle where every cited file and anchor exists. The body intentionally delegates executable detail to its references, which is appropriate progressive disclosure and only mildly limits standalone actionability.

DimensionReasoningScore

Conciseness

The ~45-line body is dense with task- and product-specific information — a decision table, terse per-step directives, and an constraints list — with no explanation of concepts Claude already knows and no padding. It assumes competence ("Inspect installed package source when documentation does not match the installed API") and every sentence carries non-obvious information, matching the lean score-5 anchor rather than the minor-trimming of score 4.

5 / 5

Actionability

Concrete, executable elements are present: the command pattern "iris agent-playbooks <command> --help", the hard rule "Every `iris` command uses root options `--json --no-input`", specific directives ("Register disclosure tools with both the model and executor", "Keep runtime `.env` credentials separate from `.env.content`"), and purposeful pointers to per-step reference files. It stops short of a 5 because the body itself contains no copy-paste-ready code or command for the integration step — the executable detail is delegated to references — leaving minor gaps if the body is read alone.

4 / 5

Workflow Clarity

Six numbered phases (Orient → Prerequisites → Publish → Integrate → Verify → Hand off) give a clear sequence with explicit checkpoints: "Confirm its serving version before wiring the agent", and in section 5 a full feedback loop — "inspect the content keys/versions and procedure loads, check a paraphrase and missing-content behavior, fix observed gaps, and rerun". Destructive cleanup is guarded ("run affected application checks on the final integration"), matching the score-5 anchor with validation steps and error-recovery loops.

5 / 5

Progressive Disclosure

The body is a concise overview in which every one of the six bundle files in references/ is cited with its purpose (e.g., "Follow [provisioning](references/provisioning.md) for the short prerequisite check"), conditional paths are clearly signaled ("For a semantic response cache, read [cache migration](references/response-cache.md) before..."), both anchor links resolve to real headers (## Handoff, ## Maintain the content), and references are one level deep with no nested chains. This matches the score-5 anchor of a clear overview with well-signaled one-level-deep references.

5 / 5

Total

19

/

20

Passed

Description

87%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: it states concrete capabilities in third-person/imperative voice and includes an explicit, well-phrased "Use when" trigger clause tied to a distinct product niche. The only room for improvement is broader synonym coverage in the trigger terms and slightly fuller capability coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Connect or provision a Playbook", "publish FAQs and Skills", "verify the first application turn", "with optional review proposals" — which goes beyond the 1–2 actions of a score-3 anchor. It falls short of the comprehensive coverage of a 5 because supporting capabilities covered in the body (e.g., content migration from prompts/docs, cleanup of the replaced retrieval/cache path) are only implied by "Add ... to an existing agent".

4 / 5

Completeness

Both halves are explicit: the "what" is "Add Redis Iris Agent Playbooks to an existing agent. Connect or provision a Playbook, publish FAQs and Skills, and verify the first application turn with optional review proposals", and the "when" is a literal "Use when" clause with concrete trigger conditions. This matches the score-5 anchor (clear what AND when with concrete trigger phrases); score 4's "'when' could be more explicit" does not apply since the trigger clause is fully explicit.

5 / 5

Trigger Term Quality

"Use when approved answers or repeatable procedures live in prompts, document retrieval, or a semantic response cache" supplies natural phrases users with this need would say, plus product-specific terms ("FAQs", "semantic response cache"). It sits at 4 rather than 5 because common synonyms and variations are missing — e.g., "canned responses", "RAG", "grounded answers", "response caching" — that a user might naturally use instead.

4 / 5

Distinctiveness Conflict Risk

"Redis Iris Agent Playbooks" names a specific product niche, and the triggers (approved answers, repeatable procedures, semantic response cache) are distinctive to this use case, giving minimal overlap risk with generic document or caching skills. The score-4 anchor ("minor overlap risk with closely related skills") is a worse fit since the product qualifier sharply disambiguates it.

5 / 5

Total

18

/

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

redis/agent-skills

Path

plugins/redis-development/skills/add-agent-playbooks/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.