work-skillslisted

# Crew skills ## Decide whether this belongs in memory or a skill - Use root `MEMORY.md` for project-specific truths: verified facts, preferences, decisions, constraints, corrections, and durable context. Test the content with “Crew should remember that…”. - Use `skills/<skill-name>/SKILL.md` for a reusable procedure: when it applies, ordered actions, checks, tools, expected output, and failure handling. Test it with “When asked to do X, Crew should…”. - If both are relevant, keep the fact in memory and the procedure in the skill, then link them rather than duplicating instructions. - Put temporary status, raw chat, guesses, secrets, and reliably retrievable live information in neither. - Memory may be updated proactively after stable verification. A skill changes only when the user explicitly asks to preserve, create, or improve a reusable procedure. - Use `list_skills` to inspect what is already installed before searching or creating another skill. Use `search_skills` to discover an existing skill. - Use `install_skill` for a discovered skill and `import_skill` for a supplied skill source. Installation is account-level; selecting it for this project is a separate action. Call `update_project_skill_selection(action="select", skill="folder-name")` with the exact folder returned by `list_skills`. Use `action="deselect"` to remove only this project's selection. The same selection remains editable in **Setup > Skills**. - When the user explicitly a