prism-startup

# Prism Startup Use this skill once, on the first user turn of a conversation. A greeting such as "hi", "hello", or "ready?" is still a first user turn and must activate it. Do not run it again after startup context has already been shown in the same conversation. Portable native-skill activation starts when the host processes the first user turn. It cannot display anything before the developer sends that first input. That first-turn behavior is the cross-host contract. ## Provisioning contract This skill ships with the `prism` plugin, alongside the Prism MCP server registration. The `prism connect` CLI installs the same protected skill for hosts configured that way; when both are present, the re-entry rule above keeps startup to a single display. Startup must not modify a host's lifecycle configuration. The skill remains available on every subscription tier, and it is intentionally absent from session skill routing so loading context cannot inject this startup procedure recursively. ## First action: bootstrap context Before greeting the developer or answering their task: 1. If `session_bootstrap` is available, call it with no arguments. Do not guess a project, role, developer name, or context depth. 2. If `session_bootstrap` is unavailable but `session_load_context` is available, call `session_load_context` for the current project and omit the `level` argument. Use the repository or workspace name as the project; use `prism-mcp` only when no project can be...