stacklok / stacklok/docs-website

Surface agent SDK examples from toolhive repo in the docs

Open Beginner friendly
#564 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs-triage
Dominant language
TypeScript
Stars
4
Forks
3
Avg merge
1d 7h
Merged PRs (30d)
41

Description

User Story

As a ToolHive user attempting to build my own agent service, I can't easily discover
the agent SDK examples that show how to use ToolHive. Without documentation pointing
to the examples, they're invisible even if they exist in the repo.

Context

The toolhive repo contains worked examples for building agents on ToolHive using
popular SDKs (LangChain, LangGraph, Google ADK) under examples/agents/. These need
to be surfaced in the docs-website so users can find and follow them.

Requirements
  1. Add a new guide or section (e.g., under "Guides" or a new "Building Agents" section)
    that introduces the agent SDK examples
  2. Link to the examples/agents/ directory in the toolhive repo for each SDK
  3. Include a brief description of each example and what the user will build
Acceptance Criteria
  • Docs include a discoverable entry point for agent SDK examples
  • Each of the three SDKs (LangChain, LangGraph, Google ADK) is linked and described
  • Links point to the correct directories in the toolhive repo
  • Content is reviewed for accuracy against the actual examples

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the docs-website structure to find the appropriate Guides or agent-focused entry point, then review the toolhive repo's examples/agents/ directory. Add a discoverable guide linking the LangChain, LangGraph, and Google ADK examples, with a brief description of what each builds; done means all three links are correct and the content matches the examples.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.