honcho
starsforks
How to install honcho?
alexai-mcp/hermes-ccc/honcho
$npx -y skills add AlexAI-MCP/hermes-CCC --skill honchoAI-native cross-session user modeling — builds a persistent, growing model of who you are, your expertise, preferences, and working style across all Claude sessions.
SKILL.md
| 1 | # Honcho — Cross-Session User Modeling |
| 2 | |
| 3 | "The agent that grows with you." Honcho builds a persistent model of who you are across every session — your expertise, communication style, recurring topics, and working preferences. |
| 4 | |
| 5 | ## Philosophy |
| 6 | |
| 7 | Unlike simple memory (saving facts), Honcho models the **user as a person** — updating its understanding through **dialectic reasoning**: observing patterns, forming hypotheses about your preferences, and refining them over time. |
| 8 | |
| 9 | This is the core of what makes Hermes Agent feel like it "knows" you. |
| 10 | |
| 11 | --- |
| 12 | |
| 13 | ## hermes-CCC Implementation |
| 14 | |
| 15 | In hermes-CCC, Honcho runs as a structured user profile in the memory system. Full Honcho (honcho.dev) adds a cloud backend with dialectic reasoning. |
| 16 | |
| 17 | ### User Profile Structure |
| 18 | |
| 19 | Profile stored at: `~/.claude/projects/*/memory/user_honcho_profile.md` |
| 20 | |
| 21 | ```markdown |
| 22 | --- |
| 23 | name: honcho-user-profile |
| 24 | type: user |
| 25 | description: Cross-session user model built by Honcho |
| 26 | updated: 2026-04-07 |
| 27 | --- |
| 28 | |
| 29 | ## Identity |
| 30 | - Name: [inferred or stated] |
| 31 | - Role: [developer / researcher / executive / etc.] |
| 32 | - Timezone: [UTC+9 / Korea] |
| 33 | - Primary language: [Korean/English] |
| 34 | |
| 35 | ## Expertise |
| 36 | - Deep expertise: [Python, AI/ML, ontology design, business strategy] |
| 37 | - Intermediate: [Next.js, Neo4j, blockchain] |
| 38 | - Learning: [Rust, Solana] |
| 39 | |
| 40 | ## Communication Style |
| 41 | - Preferred verbosity: terse (skip explanations I know) |
| 42 | - Output format: code-first, then explanation |
| 43 | - Language mix: Korean for strategy, English for code |
| 44 | - Tone: direct, no fluff |
| 45 | |
| 46 | ## Working Patterns |
| 47 | - Session length: typically 2-4 hours |
| 48 | - Recurring projects: [OpenCrab SaaS, hermes-CCC, Ontology workspace] |
| 49 | - Tools always in use: [Claude Code, Discord, Obsidian, Neo4j, LM Studio] |
| 50 | - Peak hours: [evening KST] |
| 51 | |
| 52 | ## Recurring Interests |
| 53 | - Multi-agent systems and orchestration |
| 54 | - Knowledge graphs / ontology |
| 55 | - AI infrastructure (vLLM, GRPO training) |
| 56 | - SaaS monetization strategy |
| 57 | |
| 58 | ## Preferences |
| 59 | - Never explain basics I already know |
| 60 | - Always show full code, not snippets |
| 61 | - When blocked, say so immediately |
| 62 | - Prioritize speed over perfection on first pass |
| 63 | - Delegate heavy builds to Codex |
| 64 | |
| 65 | ## Session History Patterns |
| 66 | - Often starts: checking project status |
| 67 | - Common requests: code generation, architecture review, Discord automation |
| 68 | - Frequently uses: /hermes-route, /hermes-memory, codex:rescue |
| 69 | ``` |
| 70 | |
| 71 | --- |
| 72 | |
| 73 | ## Commands |
| 74 | |
| 75 | ### `/honcho profile` |
| 76 | Display the current user model. Claude reads the profile and summarizes key facts about how it understands you. |
| 77 | |
| 78 | ### `/honcho update` |
| 79 | After a session, analyze what was discussed and update the profile: |
| 80 | 1. New expertise demonstrated? |
| 81 | 2. New tools or projects mentioned? |
| 82 | 3. Communication preferences revealed? |
| 83 | 4. New recurring topics? |
| 84 | |
| 85 | Then write updates to `user_honcho_profile.md`. |
| 86 | |
| 87 | ### `/honcho calibrate` |
| 88 | Run a quick 5-question calibration: |
| 89 | 1. What's your primary role? |
| 90 | 2. What are your strongest technical areas? |
| 91 | 3. How do you prefer explanations? (terse/detailed) |
| 92 | 4. What projects are you currently working on? |
| 93 | 5. Any specific preferences for how I should behave? |
| 94 | |
| 95 | ### `/honcho reset` |
| 96 | Clear the user model and start fresh. |
| 97 | |
| 98 | ### `/honcho export` |
| 99 | Export profile as JSON for backup or transfer. |
| 100 | |
| 101 | --- |
| 102 | |
| 103 | ## How Claude Uses the Profile |
| 104 | |
| 105 | When Honcho profile is loaded, Claude should: |
| 106 | - **Skip** explanations of tools/concepts the user knows deeply |
| 107 | - **Use** preferred verbosity level in all responses |
| 108 | - **Reference** current projects when suggesting approaches |
| 109 | - **Adapt** language mix (Korean/English as preferred) |
| 110 | - **Assume** expertise level from profile when writing code |
| 111 | - **Prioritize** working patterns (e.g., "delegate to Codex") |
| 112 | |
| 113 | --- |
| 114 | |
| 115 | ## Full Honcho Integration (Optional) |
| 116 | |
| 117 | For cloud-backed dialectic reasoning: |
| 118 | |
| 119 | ```bash |
| 120 | pip install honcho-ai |
| 121 | ``` |
| 122 | |
| 123 | ```python |
| 124 | from honcho import Honcho |
| 125 | |
| 126 | honcho = Honcho(app_id="your-app-id", api_key="your-api-key") |
| 127 | |
| 128 | # Create/get user session |
| 129 | user = honcho.apps.users.get_or_create(app_id="hermes-ccc", name="alexlee") |
| 130 | session = honcho.apps.users.sessions.create(app_id="hermes-ccc", user_id=user.id) |
| 131 | |
| 132 | # Add observation |
| 133 | honcho.apps.users.sessions.messages.create( |
| 134 | app_id="hermes-ccc", |
| 135 | user_id=user.id, |
| 136 | session_id=session.id, |
| 137 | is_user=True, |
| 138 | content="User prefers terse responses with code-first approach" |
| 139 | ) |
| 140 | |
| 141 | # Dialectic inference — Honcho reasons about the user |
| 142 | response = honcho.apps.users.sessions.chat( |
| 143 | app_id="hermes-ccc", |
| 144 | user_id=user.id, |
| 145 | session_id=session.id, |
| 146 | query="What communication style does this user prefer?" |
| 147 | ) |
| 148 | print(response.content) |
| 149 | ``` |
| 150 | |
| 151 | See [docs.honcho.dev](https://docs.honcho.dev) for f |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
