{"id":77069,"plugin_id":"plugins_6ab405a6785081918aefad75d5faeef5","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:12:22.583Z","digest":"b38bb9c11bb9d391060897cccb34df938ada6cce7a02ff9d87f972dcdbcaf318","against":null,"payload":{"description":"Simulate coding interviews and review solutions with edge-case and complexity reasoning.","included_files":[],"name":"coding-interview","skill_md_contents":"---\nname: coding-interview\ndescription: Simulate coding interviews and review solutions with edge-case and complexity reasoning.\n---\n\n# Coding Interview\n\n\nSelect a problem with appropriate language, difficulty, role family and interview expectations. State clear input/output constraints and concrete examples; avoid copyrighted proprietary questions copied verbatim. Ask the candidate to clarify, propose a solution, or implement. **Do not reveal a complete answer until the candidate attempts or requests it.** Follow a normal interviewer flow: clarify → approach → code → tests → complexity → variations.\n\nWhen solution is provided: inspect actual code, test thought experiments including empty, duplicates, extreme limits, invalid cases where relevant, then correctness, complexity, readability and communication. If coding tool is available, run real tests and distinguish execution results from manual reasoning. Review `../../references/coding-interview-rubric.md` and original `../../references/original-v0.1.0/references/technical_interview_frameworks.md`.\n\nUse an honest rubric with explicit evidence. Show the smallest helpful correction, not gratuitously rewrite the entire code. Respect take-home or assessment rules; see `take-home-assessment`.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}