Validate agent handoff packets and resume readiness using schema, freshness, and replay checks. Use when tasks pause/resume across sessions, agents, or humans — including when a user wants to continue where they left off, hand off to another agent, resume a previous task, or pick up an interrupted workflow.
90
90%
Does it follow best practices?
Impact
92%
1.21xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly articulates specific capabilities (handoff packet validation with schema, freshness, and replay checks), provides comprehensive trigger guidance with natural user language, and occupies a distinct niche. The description is concise yet thorough, uses proper third-person voice, and includes both the 'what' and 'when' components effectively.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'validate agent handoff packets', 'resume readiness', 'schema checks', 'freshness checks', 'replay checks', and 'prompt-injection guardrails'. These are concrete, well-defined operations. | 3 / 3 |
Completeness | Clearly answers both 'what' (validate handoff packets using schema, freshness, and replay checks with prompt-injection guardrails) and 'when' (explicit 'Use when...' clause covering multiple trigger scenarios like pausing/resuming, handing off, continuing interrupted workflows). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'pause/resume across sessions', 'continue where they left off', 'hand off to another agent', 'resume a previous task', 'pick up an interrupted workflow'. These are phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche — agent handoff validation with schema/freshness/replay checks is a very specific domain unlikely to overlap with other skills. The combination of handoff packets, cross-session resumption, and prompt-injection guardrails creates a clear, unique identity. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill with strong actionability and workflow clarity. It provides concrete schemas, executable code, clear validation steps with classification tiers, and thoughtful security guardrails for untrusted content. Minor improvements could be made in conciseness (tightening some explanatory text) and progressive disclosure (splitting detailed examples into a reference file).
Suggestions
Tighten the resume_token interpretation section — the bullet list repeats concepts that are already clear from the validation workflow section.
Consider moving the detailed valid/invalid examples and output format examples to a separate EXAMPLES.md file, keeping only the schema and workflow in the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some redundancy — the invalid example section and the resume_token interpretation section could be tighter. The two full output examples are somewhat verbose but serve a useful purpose. Overall mostly lean with minor padding. | 2 / 3 |
Actionability | Provides a concrete JSON schema, executable Python code for freshness checking, specific validation criteria for resume_token, clear classification logic, and copy-paste-ready output format examples. Fully actionable. | 3 / 3 |
Workflow Clarity | Clear sequential workflow with explicit validation checkpoints (schema check → freshness check → resume_token validation → replay check → classification). Includes explicit failure classification tiers and recovery steps. The guardrails section adds appropriate safety constraints for destructive/risky operations. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections and headers, but everything is inline in a single file. The output examples and guardrails sections could potentially be split out for a skill of this length (~100 lines). However, the content is organized logically and navigable. | 2 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents