tools-update-cron: sync 2026-07-15 — 23 skill(s) updated

ask-claude/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ask-claude
 description: "Consult Claude Opus 4.8 on 10.0.0.28 via SSH print mode with session resumption. Multi-turn back-and-forth without tmux or polling."
-version: 2.6.1
+version: 2.7.0
 author: Hermes Agent
 license: MIT
 platforms: [linux]
@@ -372,6 +372,7 @@ Sonnet is 3-5x faster and cheaper. Use for: factual lookups, simple analysis, qu
 ## Pitfalls
 
 - **CRITICAL: Pasted inline beats file paths every time.** Claude runs on 10.0.0.28 and has no access to `/home/n8n/workspace/`, `~/workspace/`, or any other local path. "Read the plan at /home/n8n/workspace/.../_plan.md" wastes a turn: Claude searches the wrong filesystem, returns "file not found," and you paid $0.20-$0.35 for nothing. **Always paste the artifact inline** between clear markers like `==== PLAN BEGINS ==== ... ==== PLAN ENDS ====`. The "Claude's Limitations" section above already says this — but the failure mode is costly enough to deserve its own pitfall. File paths in questions should be reserved for files Claude can actually see on its own host (`~/claude/hermes_support/...`).
+- **Large-artifact exception (>~20KB):** For very large plans/reports, pasting inline bloats the question file and the SSH invocation. Instead, `scp` the artifact to the remote host (`scp plan.md n8n@10.0.0.28:/tmp/plan.md`) and tell Claude to read it at that remote path (`/tmp/plan.md`) with its file tools. Claude CAN read files on its own host (10.0.0.28) — the "no local file access" rule only applies to paths on YOUR host. This worked cleanly for a 49.6KB plan validation (ask-claude session a1de5e36, 2026-07-07). Still paste the QUESTION/prompt inline; only the artifact goes via scp.
 - **ask.sh can fail silently while direct `claude -p` works.** The wrapper may return `{"is_error": true, "error": "no Claude output (timeout or CLI failure)"}` even when Claude is healthy. When this happens, fall back to the direct invocation: `ssh n8n@10.0.0.28 'cd ~/claude/hermes_support && timeout 280 /home/n8n/.local/bin/claude -p "$(cat /tmp/ask-claude-q.txt)" --output-format json --model claude-opus-4-8 --max-turns 30 || true'`. The wrapper is preferred (it handles usage API + merge.py), but the direct path is the reliable fallback. If the direct path also fails, Claude is genuinely down.
 - **CRITICAL: Never inline questions in SSH commands.** Shell metacharacters (`"`, `$`, `(`, backticks) will break. Always write to a temp file via `mktemp` first, then `claude -p "$(cat $QFILE)"`.
 - **Always use `--output-format json`** — without it, you get plain text and can't extract session_id for follow-ups.