원클릭으로 Manus에서 모든 스킬 실행

connect-glean

스타3

포크0

업데이트2026년 7월 14일 16:38

Help the user connect a Glean MCP server so the Glean skills have tools to call — use when setting up Glean for the first time, adding another Glean server, checking whether Glean is connected, or troubleshooting missing Glean tools. Trigger phrases include "set up Glean", "connect Glean", "configure Glean MCP", "add a Glean server", "is Glean connected", "check Glean status", "Glean isn't working", "no Glean tools", "the Glean tools aren't showing up", "I installed the Glean plugin but nothing happens". Don't use it for actual enterprise queries once connected (use the using-glean skill); this skill only sets up and verifies the connection.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

gleanwork

gleanwork/agent-plugins

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

관련 직업SOC

SOC 직업 분류 기준

기타 컴퓨터 관련 직업컴퓨터 및 수학직·SOC 15-1299

SKILL.md

readonly

이 저장소의 다른 Skills

같은 저장소

using-glean-productivity

gleanwork/agent-plugins

Synthesize the user's own work activity, priorities, and recent context using Glean — use when the user asks about their recent work, what they accomplished, what is urgent, what needs their attention, or wants help with status updates, 1:1 prep, or weekly summaries. Trigger phrases include what have I been working on, what did I do last week, what should I focus on, summarize my week, help me with my status update, what's blocking me, morning briefing, what happened while I was out. Do not use for general enterprise queries (use the using-glean skill), for someone else's activity, or for project-status questions where the user is not the subject (use a project-awareness skill).

2026-07-173

using-glean

gleanwork/agent-plugins

Use Glean MCP tools to answer questions about company documents, internal wikis, policies, RFCs, design docs, people, teams, meetings, decisions, action items, email, calendar events, internal code, and the user's own work activity. Reach for this whenever the answer lives in enterprise systems rather than the local codebase or public web. Trigger phrases include "find the doc about", "what's our policy on", "where is the spec for", "who works on", "who owns", "find someone who knows", "what was decided in the meeting", "action items from", "search my email", "what did I work on last week", and "find the implementation in our repos". Don't use it for questions answerable from the local working directory, the public web, or generic programming knowledge.

2026-07-173

project-handoff

gleanwork/agent-plugins

Generate a comprehensive handoff document so someone new can take over a project — current state, key people, essential knowledge, open items, and a first-30-days plan. Use when the user is handing off a project (trigger phrases include "generate a handoff", "hand off this project", "create a handoff doc", "I'm going on PTO / leaving / changing teams and need to document", "help someone take over") rather than a quick status read (use project-awareness for that).

2026-07-143

skill-creation-guide

gleanwork/agent-plugins

Guide the user through authoring a new agent skill — when a skill is worth creating, the SKILL.md format, progressive disclosure, and common pitfalls. Also covers discovering skill opportunities from the user's work patterns and generating a SKILL.md from a description. Trigger phrases include "create a skill", "write a skill", "make a skill", "new skill", "SKILL.md format", "how do skills work", "skill best practices", "convert this workflow into a skill", "what should I automate", and "find skill opportunities". Don't use it for invoking existing skills — only when authoring a new one or understanding the skill format.

2026-07-143

skill-creation-guide

gleanwork/agent-plugins

Discover and vet reusable skill opportunities from the user's Glean work patterns. Use when the user asks "what should I automate", "find skill opportunities", or wants to turn recurring work into skills. For authoring a known skill in Codex, hand off to the built-in skill-creator.

2026-07-143

name

connect-glean

description

Connect Glean

The Glean plugin ships skills but does not bundle an MCP server — the skills call whatever Glean MCP tools the host exposes. If no Glean MCP server is connected, the skills have nothing to call. This skill connects one, or verifies and troubleshoots an existing connection. Follow the section for the user's host.

When this applies

First-time setup — the Glean plugin is installed but no Glean tools appear.
Adding another server — e.g. a second backend or a code-search server.
Status / troubleshooting — "is Glean connected?", "no Glean tools showing".

What you need first (all hosts)

Gather these once, then apply them in the host-specific step:

Server URL — the Glean backend, found at https://app.glean.com/admin/about-glean. Looks like https://acme-be.glean.com or https://be-4f5226e2.glean.com.
Server name — organization-specific, from the user's Glean admin. Often default.
Friendly name — what to call it in the host. Use glean for a single server, or glean-<server-name> when adding several (e.g. glean-default, glean-code).

The MCP endpoint is always <server-url>/mcp/<server-name>. It is a remote HTTP server and uses OAuth — there is no API key to paste. Follow the host-specific authentication and reload steps below.

Claude Code

Run:

claude mcp add <friendly-name> <server-url>/mcp/<server-name> --transport http --scope user

Verify with claude mcp list (look for a glean.com/mcp URL). Restart Claude Code; authenticate on first use.

Codex

Run:

codex mcp add <friendly-name> --url <server-url>/mcp/<server-name>
codex mcp login <friendly-name>

Complete the browser OAuth flow, then verify with codex mcp list (look for a glean.com/mcp URL). Start a new Codex task so the MCP tools are available.

Cursor

Add an entry to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "<friendly-name>": {
      "url": "<server-url>/mcp/<server-name>"
    }
  }
}

Restart Cursor; authenticate via OAuth on first use.

Other hosts

Any MCP-capable host can use Glean: register <server-url>/mcp/<server-name> as a remote HTTP MCP server in that host's MCP configuration, then restart and authenticate on first use. Consult the host's own MCP setup docs for where its config lives and the exact field names.

Checking status / troubleshooting "no Glean tools"

If the Glean skills run but report missing tools, the host has no usable Glean MCP server in the current session or task:

Confirm a server is configured: use claude mcp list in Claude Code, codex mcp list in Codex, or inspect the host's MCP config for a glean.com/mcp URL.
If none is configured, run the host setup above.
If Codex is configured but not authenticated, run codex mcp login <friendly-name>, then start a new task.
In other hosts, restart the host and trigger OAuth by running any Glean tool once.

Glean developer docs server (separate, optional)

The glean-dev-docs plugin uses a different, public server — no URL, server name, or auth needed:

Claude Code: claude mcp add glean-dev-docs https://developers.glean.com/mcp --transport http --scope user
Codex: codex mcp add glean-dev-docs --url https://developers.glean.com/mcp, then start a new task.
Other hosts: register https://developers.glean.com/mcp as a remote HTTP MCP server (no OAuth required).

Related skills

using-glean — once connected, drives enterprise search, Q&A, and synthesis.