What you can do

The connector exposes three kinds of capability. Here's what each one is for, with example prompts.

1. Tools (your AI calls these automatically)

• search_knowledge_base - finds the most relevant passages across OpenOrg's playbooks, policies, frameworks, and articles. *Try: "What does OpenOrg recommend for a first performance review cycle?"*
• get_document - fetches the full text of a specific document. *Try: "Open the full progression framework you just referenced."*
• list_knowledge_base - lists what exists, optionally by type. *Try: "What playbooks does OpenOrg have?"*
• search_openverse - searches the community directory. *Try: "Find an onboarding checklist in Openverse."*
• get_openverse_resource - opens a specific Openverse resource by its slug.

2. Resources (you browse and attach these)

Your client can browse OpenOrg items and attach a specific one to the conversation:

• openorg://kb/{documentId} - a single knowledge base document
• openorg://openverse/{slug} - a single Openverse resource
• openorg://reference-index - the curated reference index

Use these when you already know the exact document you want, rather than searching.

3. Prompts (you invoke these like slash-commands)

The OpenOrg skills, available as guided prompts:

• Roadmap Builder - build a prioritised people roadmap
• Survey Question Creator - design effective survey questions
• Survey Analyser - turn survey exports into themes and actions
• Competency Framework Builder - design career ladders and matrices
• Facilitation Designer - plan workshops and offsites
• Data-driven Storymaker - turn people data into exec narratives
• Job Description Generator - draft and improve JDs
• Job Ad Generator - write external job ads

Pick one from your client's prompts menu; it will walk you through the workflow conversationally and use the search tools to pull in OpenOrg content as needed.