{"id":77087,"plugin_id":"plugins_6ab405a6785081918aefad75d5faeef5","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:12:23.031Z","digest":"a471b138c3f965e5b56e2314ed03a73392507d7a8624062ab1849487e77b5d8b","against":null,"payload":{"description":"Teach a technical interview concept at appropriate depth and practice spoken explanations.","included_files":[],"name":"technical-study","skill_md_contents":"---\nname: technical-study\ndescription: Teach a technical interview concept at appropriate depth and practice spoken explanations.\n---\n\n# Technical Study\n\n\nIdentify concept, role and level from context. Answer the technical question directly before adding interview coaching. Format as: plain explanation, mechanism and constraints, one realistic example, short spoken answer, advanced follow-up, common misconceptions. For urgent requests, prioritize the spoken answer and only one follow-up. If the concept has version-specific behavior, seek current authoritative documentation rather than inventing library APIs.\n\nUse `../../references/role-families-and-seniority.md` to scale depth. For senior roles prioritize failure modes, design trade-offs, operations and validation. If the user's answer is supplied, critique the reasoning specifically, not personality. Distinguish what can be proved from what requires execution. Never assert having run code unless tools actually ran it.\n\nUse `../../templates/study-card.md` when creating a reusable study artifact. Don't force STAR or long textbook sections onto a 'what is X?' question.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}