Repository navigation
feat: add /glean skill for cited company answers at minimal tool cost - #49
aditya-scio wants to merge 4 commits into
Conversation
|
@aditya-scio, this skill overlaps almost completely with
Could we add those rules to One more thing: this repo is public, so please keep internal repo links and ticket keys out of PR descriptions, commits, and comments. I removed the internal PR links from the description. |
|
@aditya-scio, I folded this into What carried over from this PR:
That last point became a rule for every skill. The server's I left out the For the server-side |
Adds a short
gleanskill (invocable as/gleanin Claude Code, Cursor, and Codex) that lets the agent default to Glean for company questions. It maps each question to the cheapest Glean tool that answers it (search,employee_search,meeting_lookup,memory,user_activity,read_document,chat), pushes for parallel calls and stopping early, and requires a source link for every claim, so answers stay high quality at the lowest token cost.The Glean MCP server serves the same skill to MCP clients through
skills/list.npm test: all three targets build and validate, and the skill is emitted underdist/{claude,cursor,codex}.