Start with XiaomiMiMo/MiMo-Code if your real task is a coding session that got interrupted. It can read a project, edit files, run commands, and save task notes plus checkpoints across sessions. A sensible first experiment: open a half-finished branch, ask it to reconstruct the current state from the latest checkpoint before touching anything, and confirm it names the files it changed, the commands already run, and the next safe step.
If the pain is an assistant that starts typing too early, mattpocock/skills is the smaller click. It offers editable coding-assistant workflows, including one that asks detailed questions before implementation. Try it on one vague ticket: keep only the questioning workflow, replace generic prompts with your acceptance criteria, deadline, test command, and files that must not change, then compare the plan with your last rushed patch. This pairs well with MiMo-Code: one protects continuity, the other protects intent.
If you plan to install skills found online, NVIDIA/SkillSpector gives you a way to inspect them first. Scan one skill folder and read the findings about suspicious instructions or credential access. Once you have triaged that first scan, its baseline feature helps you spot new findings when the package changes.