Plugin · Claude Code · AI Agents

Ken Cavanagh Glean Fieldkit

ken-cavanagh-glean-fieldkit is a Claude Code plugin for the Build phase that connects Claude to Glean enterprise search, MCP, and agent workflows across five bundled plugins.

by ken-cavanagh-glean · github.com/ken-cavanagh-glean/fieldkit

Install when your team already uses Glean and you want Claude Code plugins for company search, briefings, MCP workflows, and agent-building on live enterprise context.

3
GitHub stars
0
Installs
0
Community votes
One vote per signed-in builder - it helps surface the tools the community actually relies on.
Install

Add it to Claude Code

Install the plugin in Claude Code. One command, paste-ready.

Install the plugin
/plugin install ken-cavanagh-glean-fieldkit@ken-cavanagh-glean/fieldkit
Add to ClaudeUse the Agent APISkillselion is itself an MCP server - your agent can fetch this config directly.
Agent API

Built to be called by your agent

Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.

Retrieve this entry with skillselion.get_details("plugin:ken-cavanagh-glean/fieldkit") and the paste-ready config with skillselion.get_install_config("plugin:ken-cavanagh-glean/fieldkit").

About

What it does

ken-cavanagh-glean-fieldkit is a five-plugin Claude Code bundle built to “empower your Claude” with Glean-backed enterprise context. Solo builders rarely run Glean end to end, but small teams and technical operators inside companies use it to connect Claude Code to accounts, documents, meetings, work activity, and oracle-style Q&A over the company graph. Ingest metadata highlights automation, briefings, premeeting prep, specifications, testing, and MCP—so the catalog placement emphasizes Build integrations while acknowledging Grow and Operate use for customer success and ops tracking. Expect agent-builder and importable skills patterns rather than a single CRUD skill: you register the bundle, supply Glean access, then chain search → briefing → spec workflows. It is intermediate complexity because enterprise graph permissions and MCP configuration matter. Skip it if you do not have Glean; prefer plain skills if you only need generic web research without corporate knowledge bases.

Highlights

  • Five-plugin Claude Code bundle aimed at empowering Claude with Glean enterprise knowledge
  • Keywords span Glean agent, MCP, company-search, people-search, briefings, and multi-agent workflows
  • Agent-builder and agent-skills hooks for production-grade ops and customer-success scenarios
  • Dev-browser and spec-generator style tooling for specs, checklists, and workflow automation
  • Context-engineering and memory-systems oriented keywords for repeatable enterprise answers

Why builders use it

Claude Code sessions go stale fast when your answers need live company documents, people, and meeting context locked inside Glean.

After install, Claude can run Glean-oriented search, briefings, and multi-agent workflows through FieldKit’s five-plugin integration surface.

At a glance

  • Type - Plugin in AI Agents.
  • Adoption - 0 installs, 3 stars, 0 votes.

FAQ

Who is ken-cavanagh-glean-fieldkit for?

It is for Claude Code users with Glean access who need company knowledge, briefings, and agent workflows wired into coding and ops sessions.

When should I use ken-cavanagh-glean-fieldkit?

Use it during Build when integrating agents with Glean MCP, and during Grow or Operate when customer-success or internal briefings need live enterprise context.

How do I add ken-cavanagh-glean-fieldkit to my agent?

Install the ken-cavanagh-glean/fieldkit Claude Code plugin bundle, configure Glean and MCP credentials per your org, then enable the five plugins in Claude Code.

Discussion

Comments

Share how you use ken-cavanagh-glean-fieldkit, gotchas, or tips for other indie builders.

No comments yet - be the first to share how you use it.

This week for builders

Five minutes, every Monday — the tools, releases and tactics for shipping solo.

unsubscribe anytime.