Files
prose-contracts/deliverables/scot-hermes-playbook/REVIEW.md
mumuni-bot c7af7c0689 Add reviewed Hermes playbook for Scot Murray (client deliverable)
Provenance: kanban t_02148213 (research) -> t_4265c369 (author) -> t_fefdf30b (review).
Review verdict: APPROVED-WITH-FIXES, 7/7 checks PASS, 17/17 YouTube links oEmbed-verified,
26+ CLI commands re-run against v0.21.1, no Murray/JDS client data present.

Artifact: deliverables/scot-hermes-playbook/HERMES-PLAYBOOK-FOR-SCOT.md
  377 lines, sha256 b0966a649fec96da4975ec00e627fbaba3a92a62c4a92b33bc06589c47d25f7f
Includes the research dossier and its raw verification evidence under research/.

STATUS: written and reviewed, NOT delivered to the client. Delivery is gated on
Kwame's approval and tracked as a separate blocked kanban card.
2026-09-11 12:54:52 -04:00

4.8 KiB

Review Results: Scot Murray Hermes Playbook (t_fefdf30b)

VERDICT: APPROVED-WITH-FIXES

Summary

The playbook is well-structured, factually accurate, and provides genuine value for a new Hermes user. All 17 video links verified live (17/17 PASS), all 10 source URLs resolved successfully, all 26+ CLI commands verified against v0.21.1, no client data leaks detected, and all 9 required sections present with substantive content. One minor documentation accuracy issue requires correction.

Per-Check Results

1. COMMANDS: ✅ PASS

  • 26 top-level commands and subcommands verified live on Hermes Agent v0.21.1 (2026.9.7)
  • All VERIFIED-LIVE tags confirmed: hermes import-agent claude-code --dry-run, hermes skills trust, hermes mcp serve, hermes prompt-size, hermes fallback, hermes curator, etc.
  • All DOC-ONLY commands (in-session slash commands) confirmed against official docs
  • No fabricated or non-existent commands found

3. SOURCES: ✅ PASS

  • 10/10 URLs in sources.md resolved successfully (HTTP 200)
  • No dead links or inaccessible URLs found
  • All official docs and GitHub repo accessible

4. COMPLETENESS: ✅ PASS

  • All 9 required sections present and substantive:
      1. TL;DR ✅
      1. Context gap explanation ✅
      1. Context stack ✅
      1. Top moves (12 items) ✅
      1. Working alongside Claude Code ✅
      1. Video watch list (17 videos) ✅
      1. 7-day ramp ✅
      1. What NOT to expect ✅
      1. Appendix: command reference ✅
  • Top moves count: 12/12 (within 12 limit) ✅
  • 7-day ramp is actionable with specific commands ✅

5. CLIENT-DATA LEAK: ✅ PASS

  • No private financial data or personal data found
  • Grep patterns searched: murray, jds, portfolio, allocation, holding, ticker, position, dollar, 192.168.68.17, syslog solution llc
  • Only mentions of "portfolio" are generic workflow descriptions, not specific financial data
  • No Murray Capital/JDS portfolio details, positions, or dollar figures found

6. HONESTY/OVER-CLAIM: ✅ PASS (1 minor issue)

  • Minor issue found: The "save this as a skill" workflow description is slightly misleading
    • Book says: "after you complete a workflow twice, ask Hermes to 'save this as a skill'"
    • Reality: The workflow works on a single workflow completion (not after two)
    • The language "after you complete a workflow twice" suggests a minimum repetition requirement that doesn't exist
    • Recommendation: Change to "after completing a workflow, ask Hermes to save this as a skill"
  • No major over-claims about features that don't exist
  • All model claims are accurate for OpenRouter-only setup
  • Honest about "no official Nous Research tutorial videos exist" ✅

7. USEFULNESS: ✅ PASS

  • Strongest section: Section 4 "Top moves" - provides 12 highly actionable, verified commands
  • Strongest section: Section 6 "Video watch list" - all links verified, titles/channels accurate
  • Strongest section: Section 7 "Your first 7 days" - practical, incremental onboarding plan
  • Weakest section: Section 2 "Why Hermes feels like it has less context" - could benefit from more concrete examples
  • Overall: Would genuinely help a new user close the context gap with actionable, verified steps

Prioritized Fixes

SHOULD-FIX

  1. Fix "save as skill" workflow description - Change "after you complete a workflow twice" to "after completing a workflow" (Section 3, paragraph 4)
    • This is the only minor issue found
    • Doesn't affect functionality but could create false expectations about repetition requirements

NIT

  • None identified - all content is accurate and well-organized

Edits Applied

Applied the SHOULD-FIX correction directly to the playbook:

  • Section 3, Layer 3 (Skills): Changed "after you complete a workflow twice" → "after completing a workflow"

FINAL SUMMARY

Verdict: APPROVED-WITH-FIXES

Per-check results:

  • Check 1 (COMMANDS): ✅ PASS - 26+ commands verified live
  • Check 2 (VIDEO LINKS): ✅ PASS - 17/17 valid with matching titles/channels
  • Check 3 (SOURCES): ✅ PASS - 10/10 URLs resolved
  • Check 4 (COMPLETENESS): ✅ PASS - 9/9 sections, 12 top moves, actionable 7-day ramp
  • Check 5 (CLIENT-DATA LEAK): ✅ PASS - No private data found
  • Check 6 (HONESTY/OVER-CLAIM): ✅ PASS - 1 minor issue identified and fixed
  • Check 7 (USEFULNESS): ✅ PASS - Strong actionable content

Video link pass/fail count: 17/17 pass, 0 fail

Fabricated/non-existent commands: None found

Dead links: None found

Path to REVIEW.md: /home/hermes/syslog/drafts/scot-hermes-playbook/REVIEW.md