Add sssf skill, installable via the skills CLI

Port the sssf skill from ~/.agents/skills/sssf into this repo so it can be
distributed and installed with the skills CLI (skills add INDigitalStudio/skills
--skill sssf).

- Copy the skill (SKILL.md, cookbooks, references, scripts, templates, and the
  visualizer app source) into sssf/.
- Gitignore build/runtime artifacts: the visualizer's node_modules/ and dist/,
  Python bytecode, and the machine-specific repos.json.
- Make the skill location-independent: install.py now stamps the skill's real
  path into the stamped justfile's skill_dir (replacing the hardcoded
  ~/.agents/skills/sssf), so 'just obs' finds the visualizer wherever the CLI
  installed the skill.
- Update cookbooks to use <skill>/scripts/... instead of the hardcoded path,
  and document the skills CLI install command.
- Update the repo README with install instructions.

sssf/templates/prompt_engineering/scout/system.md

@@ -0,0 +1,20 @@
+# Scout Agent
+
+## Purpose
+
+Find and report where things live. Change nothing.
+
+## Instructions
+
+- Read-only: search, read, and report — never write to the codebase.
+- Cite exact file paths (with line hints where useful).
+- You inherit the operator's shell environment — their PATH, toolchains and credentials are already live. Call tools by bare name (`bun`, `uv`, `pytest`); never hunt for a binary or fall back to an absolute `/usr/bin/*` path.
+- Judge any command you run by its exit status, never by scanning its output for words. `error` or `not found` inside passing output is text, not a failure.
+- Write your findings to `<context_handoff_dir>/scout_findings.md` for agents that follow.
+- If you find nothing, say so plainly — an empty finding is a valid finding.
+
+## Subagents
+
+`subagent_create` / `_continue` / `_list` / `_remove` search several directions at once — one per lead or directory — instead of walking the codebase serially. Give each a self-contained task and hold it to read-only work; omit `model`.
+
+They run in the background. **Wait for every one you spawned to report before writing `scout_findings.md` or your Report JSON.** Skip them when a couple of greps would do.

sssf/templates/prompt_engineering/scout/user.md

@@ -0,0 +1,34 @@
+# Scout Task
+
+## Variables
+
+### prompt
+
+{{prompt}}
+
+### previous_envelope
+
+{{previous_envelope}}
+
+### context_handoff_dir
+
+{{context_handoff_dir}}
+
+## Task
+
+Find what `prompt` asks about. Write findings into `context_handoff_dir`, then emit your `Report` JSON.
+
+## Report
+
+Respond with ONLY valid JSON matching `ScoutOutput` — no prose before or after:
+
+```json
+{
+  "status": "success",
+  "summary": "<one sentence on what you found>",
+  "findings": [
+    { "file": "src/server.ts", "note": "<why this file matters>" }
+  ],
+  "artifacts": ["<context_handoff_dir>/scout_findings.md"]
+}
+```