RomanNum3ral
/
honcho
mirror of https://github.com/plastic-labs/honcho.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs: add skill install section to Vercel AI SDK guide (#649) 

Add "Use the Skill" section recommending `npx skills add plastic-labs/vercel-ai-sdk`
with the manual symlink approach as a collapsed alternative.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
ajspig 2026-05-05 11:26:33 -04:00 committed by GitHub
parent e38085177c
commit c165c51fae
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 22 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/v3/guides/integrations/vercel-ai-sdk.mdx
View File

@ -51,6 +51,28 @@ HONCHO_API_KEY=your-api-key
HONCHO_WORKSPACE_ID=your-workspace-id HONCHO_WORKSPACE_ID=your-workspace-id
``` ```
## Use the Skill
The package ships a Skill that can walk an agent through wiring Honcho into your Vercel AI SDK app automatically — it greps for your `generateText` / `streamText` call sites, asks where `userId` / `sessionId` come from, and applies the integration in place.
```bash
npx skills add plastic-labs/vercel-ai-sdk
```
Then invoke `/honcho-vercel-ai-sdk`.
<Accordion title="Alternative: manual symlink from npm package">
If you've already installed `@honcho-ai/vercel-ai-sdk` via npm, you can symlink the skill directly. Example shown is for Claude Code:
```bash
mkdir -p ~/.claude/skills/honcho-vercel-ai-sdk
ln -sf "$(pwd)/node_modules/@honcho-ai/vercel-ai-sdk/skills/honcho-vercel-ai-sdk/SKILL.md" \
~/.claude/skills/honcho-vercel-ai-sdk/SKILL.md
```
Restart the session, then invoke `/honcho-vercel-ai-sdk`.
</Accordion>
## Create a Provider Instance ## Create a Provider Instance
`createHoncho()` is the entry point. It reads your API key and workspace from environment variables and returns a provider object with `middleware()`, `tools()`, and `send()`. `createHoncho()` is the entry point. It reads your API key and workspace from environment variables and returns a provider object with `middleware()`, `tools()`, and `send()`.