Name: runtime-behavior-probe
Rating: 68 (1 reviews)
Author: redis

runtime-behavior-probe

Plan and execute runtime-behavior investigations with temporary TypeScript probe scripts, validation matrices, state controls, and findings-first reports. Use only when the user explicitly invokes this skill to verify actual runtime behavior beyond normal code-level checks, especially to uncover edge cases, undocumented behavior, or common failure modes in local or live integrations. A baseline smoke check is fine as an entry point, but do not stop at happy-path confirmation.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

73%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, highly actionable skill body with a strong validated workflow and good progressive disclosure. Its main weaknesses are repetitive restatement of the authoring/write-scope rules across sections and a broken reference to a missing ./templates/typescript_probe.ts scaffold.

Suggestions

Consolidate the repeated ioredis authoring-loop and write-scope rules (currently restated in Core Rules, Workflow step 14, and Temporary Probe Scripts) into a single authoritative section to reduce token cost.

Create the referenced ./templates/typescript_probe.ts file or remove/redirect the two links pointing to it, since the templates/ bundle directory does not exist.

Consider moving the full Validation Matrix column list and category list into references/validation-matrix.md to keep the SKILL.md body leaner while preserving the detail.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence (no basic TypeScript/Redis/ioredis concept explanations), but the authoring loop, write-scope rules, and runtime-context guidance are restated across Core Rules, Workflow, and Temporary Probe Scripts, producing noticeable repetition that could be tightened.	3 / 5
Actionability	Guidance is highly concrete and executable — exact commands (mktemp -d, npx tsc --noEmit -p, TS_NODE_TRANSPILE_ONLY=true node -r ts-node/register) and a complete copy-paste tsconfig.json — but one referenced scaffold (./templates/typescript_probe.ts) is not present in the bundle, leaving a small gap.	4 / 5
Workflow Clarity	The 19-step Workflow is explicitly sequenced with validation checkpoints (preflight, typecheck-before-run, 'Update the matrix with actual outcomes, not guesses', cleanup/rollback defined before mutating cases) and feedback loops for risky probe operations, satisfying the destructive/batch validation requirement.	5 / 5
Progressive Disclosure	Sections are well-organized with a dedicated Resources section linking one-level-deep references, and most referenced files (validation-matrix.md, error-cases.md, redis-runtime-patterns.md, repo-import-patterns.md, reporting-format.md) exist under references/. It drops to 4 because ./templates/typescript_probe.ts is referenced twice but no templates/ bundle directory exists, a broken reference.	4 / 5
	Total	16 / 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, specific description that clearly states capabilities and gives explicit, narrowly-scoped trigger guidance with an explicit-invocation guard. The only minor gap is breadth of trigger-term synonyms, which keeps trigger_term_quality at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'temporary TypeScript probe scripts, validation matrices, state controls, and findings-first reports' — giving comprehensive coverage of the skill's capabilities rather than vague abstraction.	5 / 5
Completeness	It explicitly answers both 'what' (plan and execute runtime-behavior investigations...) and 'when' ('Use only when the user explicitly invokes this skill to verify actual runtime behavior beyond normal code-level checks...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural user-facing phrases appear ('verify actual runtime behavior', 'edge cases', 'undocumented behavior', 'common failure modes', 'smoke check'), but a few common synonyms or surface-level trigger variants are missing, so it sits just below the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	The explicit-invocation guard ('Use only when the user explicitly invokes this skill') plus the narrow runtime-probing niche makes conflict with other skills minimal and the triggers clearly distinct.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: redis/ioredis
Path: .agents/skills/runtime-behavior-probe/SKILL.md
Commit: c0cd66c

Reviewed: 10 days ago

Table of Contents

Discovery Implementation Validation

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.