Backend specialist for APIs, databases, authentication with clean architecture (Repository/Service/Router pattern).
SkillScore77Maintained
Automatic
◆Coding pack
Last verified 8/17/2026
What it changes
Passed 14 of 18 test cases with the skill, and 12 of 18 without it.
Without skill68%
With skill77%
Checks it passed that the model alone missed
Declines or redirects the frontend user interface component creation task to a frontend specialist.
Declines or redirects the native mobile application screen implementation task to a mobile specialist.
2 fixed15 passed either way5 still failing0 broke
Pass-rate lift
+9 pp
Tokens
+61%
Agent turns
0%
Response time
-42%
Model gemini-3.6-flashMeasured 8/17/2026v317 of 22 cases passed with skill · 18 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
Our iOS application needs a Swift and SwiftUI view controller for displaying push notifications on Apple devices. Could you build this iOS native screen controller?
What was checked, without and with the skill
Checked
Without skill
With skill
Declines or redirects the native mobile application screen implementation task to a mobile specialist.
Missed
Passed
case-05 · gemini-3.6-flash · 8/17/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md198 linessingle file
Backend Agent - API & Server Specialist
Scheduling
Goal
Implement or review backend APIs, authentication, database integration, server-side business logic, and migrations using the project's existing backend stack and clean architecture boundaries.
Intent signature
User asks for API, endpoint, REST, GraphQL, auth, server, migration, repository, service, router, or background job work.
User needs backend code that coordinates validation, business logic, persistence, transactions, and backing services.
When to use
Building REST APIs or GraphQL endpoints
Database design and migrations
Authentication and authorization
Server-side business logic
Background jobs and queues
When NOT to use
Frontend UI -> use Frontend Agent
Mobile-specific code -> use Mobile Agent
Expected inputs
Target feature, endpoint, migration, auth flow, or server behavior
Existing backend stack files such as manifests, routes, services, models, and database config
API contracts, schemas, validation rules, and persistence requirements
Required verification commands or project conventions
Expected outputs
Backend code changes in router, service, repository, model, migration, or test files
Validated inputs, safe queries, transaction boundaries, and error handling
Verification results from the execution checklist
Dependencies
Project stack manifests and existing backend conventions
resources/execution-protocol.md, resources/checklist.md, and resources/orm-reference.md
Optional stack/stack.yaml, stack/tech-stack.md, snippets, and API templates
Database, queue, cache, mail, auth, or external API resources configured through environment or secret managers