{"id":77073,"plugin_id":"plugins_6ab405a6785081918aefad75d5faeef5","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:12:22.633Z","digest":"9b1488c97c3029dc8aadb143aa3c7c4b4531df29adc76fe8591f99613542ac42","against":null,"payload":{"description":"Pressure-test actual resume bullets and technical project stories for deep interviewer follow-ups.","included_files":[],"name":"experience-deep-dive","skill_md_contents":"---\nname: experience-deep-dive\ndescription: Pressure-test actual resume bullets and technical project stories for deep interviewer follow-ups.\n---\n\n# Experience Deep Dive\n\n\nAnchor every statement to resume/project content explicitly supplied or accessible with permission. Extract confirmed facts (role, system, contribution, decisions, constraints, measured outcomes), identify unknowns, and formulate role-relevant technical follow-ups. Challenge ambiguous 'we built' or invented leadership politely by asking what the person actually owned. Never turn unknown architecture, scale, cost savings or incidents into asserted facts.\n\nProbe data flow, stack choices, alternatives, trade-offs, data quality, security, deployment, operational failures and verification, tailored to the project. Produce a defensible project narrative and follow-up readiness notes from `../../templates/experience-story.md`. Use `../../references/candidate-evidence.md` and original behavioral deep-dive. If metrics are missing, recommend describing outcomes qualitatively instead of inventing numbers. For a mock, ask one question and await answer.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}