Create API handoff documentation for frontend developers. Use when backend work is complete and needs to be documented for frontend integration, or user says 'create handoff', 'document API', 'frontend handoff', or 'API documentation'.
81
83%
Does it follow best practices?
Impact
63%
0.87xAverage score across 3 eval scenarios
Passed
No known issues
Output file path and no-chat mode
Correct directory prefix
0%
0%
Feature-named subfolder
20%
0%
Correct filename
100%
0%
No extra chat output
100%
100%
work-log path reference
100%
100%
Handoff file exists
0%
0%
Business Context present
0%
0%
All three endpoints documented
100%
0%
Auth documented per endpoint
60%
0%
Business rules surfaced
100%
0%
No backend internals
100%
0%
Error responses documented
100%
0%
Simple API shortcut vs full template
Correct file path
0%
100%
Shortcut: no Business Logic section
100%
0%
Shortcut: no Integration Notes
100%
0%
Shortcut: no Validation Rules
100%
0%
Endpoint method and path
100%
100%
Example response JSON
100%
100%
404 error case
100%
100%
Auth documented as public
100%
100%
Price field precision
100%
100%
summary.txt path reference
100%
100%
No backend class names
100%
100%
Full template sections and versioning
Versioned filename
0%
100%
Correct directory
100%
100%
TypeScript interface present
100%
100%
Enums table format
50%
100%
Display labels in table
100%
100%
Integration Notes: recommended flow
75%
100%
Integration Notes: optimistic UI
0%
100%
Integration Notes: caching
62%
100%
Integration Notes: real-time
75%
100%
Business logic surfaced
100%
100%
change-notes.md path reference
100%
100%
No backend internals
100%
100%
3027f20
Table of Contents
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.