Update to Subsalt

{
  "description": "Guide an authorized user through safe exploration of Subsalt metadata, synthetic data, cohorts, and Secure Compute.",
  "included_files": [],
  "name": "subsalt-data-analysis",
  "skill_md_contents": "---\nname: subsalt-data-analysis\ndescription: Guide an authorized user through safe exploration of Subsalt metadata, synthetic data, cohorts, and Secure Compute.\n---\n\nUse this skill for requests to explore or analyze data available through Subsalt.\n\n- Identify the user's analytical goal before choosing a tool. Use metadata and workspace tools to find a permitted database, cohort, or Secure Compute grid.\n- Use `synthetic_run_query` only for a single read-only SELECT against an identified built cohort. Keep queries narrowly scoped, use an explicit small limit for sample rows, and report if the result is truncated or stale.\n- Prefer descriptive and read-only tools while the user is still deciding what to do. Do not create, edit, delete, build, lock, publish, report, recount, or close anything without an explicit confirmation immediately before that action.\n- Treat identifiers returned by Subsalt as internal references. Use them in follow-up calls when needed, but do not claim that a resource exists unless the server returned it.\n- When working with Secure Compute, retrieve the analysis-plan guidance before preparing a publication. Describe the proposed plan in plain language and confirm it before locking a plan or submitting a publication.\n- Explain results faithfully: distinguish synthetic data from privacy-preserving Secure Compute output, retain caveats about banding, withholding, truncation, and staleness, and never infer unreleased values.\n"
}