From 1cced7817eb6c06294a494839e2237486a0d7f76 Mon Sep 17 00:00:00 2001 From: ajspig Date: Tue, 14 Apr 2026 12:42:11 -0400 Subject: [PATCH] chore: updating skill --- .claude/skills/honcho-integration/SKILL.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/.claude/skills/honcho-integration/SKILL.md b/.claude/skills/honcho-integration/SKILL.md index 68f436d1..ecfdb009 100644 --- a/.claude/skills/honcho-integration/SKILL.md +++ b/.claude/skills/honcho-integration/SKILL.md @@ -91,6 +91,8 @@ Based on interview responses, implement the integration: ### Phase 4: Verification +- If the Honcho CLI is available, run `honcho doctor` to confirm connectivity before testing the integration code +- Use `honcho peer list` and `honcho peer chat` to verify peers exist and the dialectic endpoint works independently of the integration - Ensure all message exchanges are stored to Honcho - Verify AI peers have `observe_me=False` (unless user specifically wants AI observation) - Check that the workspace ID is consistent across the codebase @@ -106,6 +108,16 @@ Based on interview responses, implement the integration: 2. **Get an API key** ask the user to get a Honcho API key from and add it to the environment. +3. **Verify with the CLI** (optional but recommended). If the user has the Honcho CLI installed (`pip install honcho-cli`), they can validate their setup before writing any integration code: + + ```bash + honcho init # persist API key + URL to ~/.honcho/config.json + honcho doctor # verify connectivity, config, workspace health + honcho peer chat # test the dialectic endpoint interactively + ``` + + This is the fastest way to confirm the API key and URL are correct before debugging SDK code. + ## Installation ### Python (use uv) @@ -524,6 +536,8 @@ When integrating Honcho into an existing codebase: - [ ] Pre-fetch pattern for simpler integrations - [ ] context() for conversation history - [ ] Store messages after each exchange to build user models +- [ ] (Optional) Run `honcho doctor` to verify connectivity before testing integration code +- [ ] (Optional) Use `honcho peer chat` to test dialectic queries independently ## Common Mistakes to Avoid