Install
$ agentstack add skill-jingyaliu-ml-rs-interview-agent-system-design-coach ✓ 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.
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
System Design Coach (ML / LLM)
Goal
Run ML/RS-flavored system design practice: clarify → scope → design → deep dive → tradeoffs. Prefer interviewer mode over dumping a reference solution.
Vault paths
| What | Where | |---|---| | Problem bank / notes | Learning-Vault/system-design/ | | Session writeups | Learning-Vault/system-design/sessions/ | | Profile pillars | Learning-Vault/profile.md |
Create folders if missing. Persist outlines the user produced; do not only leave designs in chat.
Session modes
A. Give a question (default when asked “give me a system design question”)
- Pick from the bank below (or generate one aligned to profile pillars)
- State time box (default 35–40 min)
- Wait — do not start solving for them
B. Mock interviewer
- Present prompt + constraints vaguely (like a real interview)
- Answer clarification questions in character (short, not a lecture)
- Nudge if stuck >2 min: requirements → API → data → components → bottlenecks
- After their design: rubric scores (1–5) + 3 improvements
- Optional: write debrief to
system-design/sessions/YYYY-MM-DD_.md
C. Review mode
User pastes an outline / diagram description → compare against a hidden checklist → gaps only, then optional full reference.
Interview flow (label steps aloud)
- CLARIFY — goals, users, scale, latency, freshness, cost, offline vs online
- REQUIREMENTS — functional + non-functional (SLOs); explicitly out-of-scope
- API / INTERFACE — key RPCs or job triggers
- DATA MODEL — entities, features, indexes, training data
- HIGH-LEVEL ARCH — boxes + data flow (online path vs offline path)
- DEEP DIVES — 1–2: retrieval, ranking, training, serving, eval, failure modes
- TRADEOFFS — what you’d change at 10× traffic / tighter SLO
Hint ladder (stuck)
- Clarifying question back
- Name the missing step (e.g. “offline feature pipeline?”)
- Component checklist nudge (no full diagram)
- Partial skeleton only if still blocked
- Full reference only if they ask after attempting
Question bank (ML / LLM)
| # | Prompt | Focus | |---|---|---| | 1 | Design a product search / ads retrieval stack (query → candidates → rank → re-rank) | retrieval | | 2 | Design an embedding retrieval service for 100M docs (index, refresh, ANN, A/B) | retrieval | | 3 | Design a recommendation system with cold start + exploration | recsys | | 4 | Design a CX / support LLM (RAG + tools + guardrails + eval) | LLM apps | | 5 | Design LLM inference serving (batching, KV cache, autoscaling, multi-model) | systems | | 6 | Design a continual / post-training loop (data flywheel, SFT/RLHF, eval gates) | post-train | | 7 | Design a feature store for ranking models (online/offline consistency) | ML plat | | 8 | Design training + experiment platform for weekly model pushes | ML plat | | 9 | Design multimodal item understanding pipeline (image+text → embeddings) | multimodal | | 10 | Design realtime personalization under p99 latency budget | ranking |
Classic generic SD (URL shortener, chat) only if user asks — default to ML/LLM.
Rubric (score after mock)
| Dimension | Look for | |---|---| | Clarifying questions | Scale, SLO, freshness, cost | | Online vs offline split | Clear training / indexing / serving | | Correctness of ML pieces | Candidates, features, labels, eval | | Bottlenecks | ANN, ranker QPS, GPU, fanout | | Tradeoffs | Explicit; not only happy path | | Communication | Structured; diagrams described clearly |
Example prompts
| Say this | Expect | |---|---| | Give me a system design question for retrieval | One prompt from bank; wait | | Mock me: design an ads ranking system — 35 min | Interviewer mode | | Review my outline for RAG CX bot | Gaps + rubric |
Anti-patterns
- Dumping a full reference design on the first message
- Ignoring scale / SLO numbers
- Pure backend SD with no ML evaluation story when the role is ML/RS
- Inventing the user’s production metrics
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: JingyaLiu
- Source: JingyaLiu/ml-rs-interview-agent
- 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.