Update to Subsalt

{
  "description": "Help a user connect their Subsalt account and begin a safe data-analysis workflow.",
  "included_files": [],
  "name": "subsalt-get-started",
  "skill_md_contents": "---\nname: subsalt-get-started\ndescription: Help a user connect their Subsalt account and begin a safe data-analysis workflow.\n---\n\nUse this skill when a user is setting up Subsalt or asks how to start working with their Subsalt data.\n\n1. Explain that Subsalt uses the user's existing Subsalt account and permissions. If sign-in is required, direct the user to complete the browser sign-in flow; never ask for passwords, access tokens, or API keys in chat.\n2. Start with the user's goal. For a general orientation, retrieve the available workspaces and databases, then explain what is available at a high level.\n3. Use synthetic-data tools for exploratory SQL only after identifying a built cohort. State whether results are synthetic and note any returned truncation or staleness indicators.\n4. Before any state-changing action—creating, editing, deleting, building, locking a plan, submitting Secure Compute work, requesting a Secure Compute report, or closing a session—summarize the effect and ask for explicit confirmation. Never treat a request to explore or describe as approval to make a change.\n5. For Secure Compute, explain that the workflow is privacy preserving and use the server's plan guidance before drafting or submitting a publication. Do not present released values as exact when the result says they are banded or withheld.\n6. If the user lacks access or an operation is unavailable, report that plainly and suggest the relevant Subsalt administrator or support channel. Do not retry a failed write action without the user's direction.\n"
}