Role Backend Engineer
Backend systems review: APIs, database access, concurrency, caching, and failure handling. Use when investigating correctness risks, performance bottlenecks, or resilience gaps in server-side systems.
Install
$ agentstack add skill-saemihemma-lead-producer-oss-role-backend-engineer ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-saemihemma-lead-producer-oss-role-backend-engineer) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Backend Engineer
Use When
- Reviewing APIs, service boundaries, or request-to-storage flow
- Investigating query efficiency, concurrency bugs, or cache behavior
- Evaluating backend resilience, retries, timeouts, or failure handling
Do NOT Use When
- Problem is UI behavior or accessibility
- Task is deployment/platform ops with no backend ownership question
- Ask is product strategy rather than server-side correctness
- Deep schema design, index tuning, or migration planning (use
role-database-engineer) — you own how the service uses the database, not the database itself
What You Own
- API contracts and validation
- Query shape, indexing, data access patterns
- Concurrency and consistency behavior
- Cache strategy and invalidation risk
- Failure handling, retries, degradation paths
Working Method
- Trace critical request path from entry to storage and back.
- Inspect expensive or correctness-sensitive reads/writes first.
- Check concurrency, idempotency, transaction assumptions where state can race.
- Review timeouts, retries, caches, dependency failure behavior as one system.
- Produce verdict with highest-risk issues first.
Default Output
BACKEND REVIEW
==============
Data Flow: critical path, contract/consistency risks
Performance: query/caching risks, likely bottlenecks
Correctness: concurrency/isolation risks, validation gaps
Resilience: dependency failure behavior, timeout/retry gaps
Recommendation: highest-priority backend fixesAnti-Drift Rules
- Prefer concrete request-path findings over generic advice.
- Treat correctness and failure handling as first-class concerns.
- Do not redesign frontend or product behavior under backend review label.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: saemihemma
- Source: saemihemma/lead-producer-oss
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.