CtrlK
BlogDocsLog inGet started
Tessl Logo

frontend-to-backend-requirements

Document frontend data needs for backend developers. Use when frontend needs to communicate API requirements to backend, or user says 'backend requirements', 'what data do I need', 'API requirements', or is describing data needs for a UI.

Install with Tessl CLI

npx tessl i github:softaworks/agent-toolkit --skill frontend-to-backend-requirements
What are skills?

83

Does it follow best practices?

Agent success when using this skill

Validation for skill structure

SKILL.md
Review
Evals

Evaluation results

100%

55%

Notification Center Requirements

Backend requirements document structure and workflow

Criteria
Without context
With context

Correct output path

40%

100%

Title format

0%

100%

Context section

50%

100%

Screen subsections

57%

100%

Data display described

100%

100%

Actions described

100%

100%

States covered

100%

100%

Uncertainties section

25%

100%

Questions for Backend

62%

100%

Discussion Log present

0%

100%

No endpoint specs

0%

100%

No field names

0%

100%

Context-rich data descriptions

40%

100%

Without context: $0.2861 · 1m 27s · 12 turns · 12 in / 4,570 out tokens

With context: $0.2650 · 1m 24s · 12 turns · 12 in / 3,585 out tokens

98%

-2%

Incorporating Backend Feedback into Requirements

Updating requirements after backend feedback

Criteria
Without context
With context

Correct output path

100%

100%

Discussion Log populated

100%

100%

Decisions recorded

100%

100%

Uncertainties resolved

100%

100%

Requirements adjusted

100%

100%

Original structure preserved

100%

100%

No implementation details added

100%

100%

Source of truth note

100%

100%

Remaining questions flagged

100%

100%

Pushback invitation present

100%

33%

Without context: $0.2008 · 56s · 8 turns · 9 in / 3,083 out tokens

With context: $0.2993 · 1m 17s · 13 turns · 13 in / 3,549 out tokens

100%

70%

Order History Requirements

Data relationships and pushback invitation

Criteria
Without context
With context

Correct output path

28%

100%

Relationship descriptions

20%

100%

No nesting assumptions

30%

100%

No field names

0%

100%

Context for data items

50%

100%

Pushback invitation phrases

0%

100%

Open questions phrasing

50%

100%

Business rules section

0%

100%

Edge case states

87%

100%

Uncertainties checklist

14%

100%

No endpoint specs

100%

100%

Without context: $0.2907 · 1m 47s · 10 turns · 10 in / 5,920 out tokens

With context: $0.2895 · 1m 29s · 14 turns · 12 in / 3,938 out tokens

Evaluated
Agent
Claude Code

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.