Session Tools

This skill is coherent with the described purpose (managing local Claude session files) but carries data-exfiltration and supply-chain risks you should understand before installing: - Review pipelines: The "import" and pipeline features can send full session contents to other agents or to Serena memory. Sessions often contain secrets (API keys, tokens, private config). Do not run import/pipeline functions unless you trust the target agent/service and have inspected what will be sent. Prefer dry-run or --analyze-only modes first. - Validate the filtering claim: The docs say sensitive data is filtered, but I couldn't find code that reliably strips secrets. Assume session content may include secrets unless you verify filtering logic yourself. - Inspect scripts locally: The skill includes bash/python scripts that will modify files under ~/.claude/projects (dedup, repair, destroy, rename). Back up important sessions before running destructive commands; the skill already performs some backups, but manual backups are recommended. - Be cautious with npx/UTCP registration: The docs show using `npx -y claude-sessions-mcp` to register an MCP tool — that will download and run remote npm code. Only do this if you trust the npm package and its source. - Test in a safe environment: If possible, run the skill on non-sensitive test sessions or inside an isolated account/container first. - Ask the author or maintainer: Request explicit documentation of what data is sent in import pipelines, what filtering is applied, and any credentials required by the MCP/Serena calls. If those answers are missing, treat pipeline features as high-risk. If you want, I can (a) highlight the specific lines/files to inspect further (summarize-session.py, any code that constructs pipeline Task tools, and whether summarize/export code truncates or filters tokens), or (b) produce a checklist of safe-run steps before using each subcommand.