using-glean
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.
What this skill does
# Using Glean The Glean MCP server exposes a family of tools that let Claude query the user's company knowledge: documents, people, meetings, email, internal code, the user's activity feed, structured memory, and the knowledge graph. This skill is the entry point. It maps a user's question to the right tool, names the rules that apply across all of them, and links to per-tool reference files that carry the deep syntax. ## Where these tools live The tools listed below come from the user's Glean MCP server connection. Refer to them by their bare names (`search`, `employee_search`, `meeting_lookup`, …) — Claude resolves them against the active tool inventory. If no Glean tools are visible, the user has not configured a Glean MCP server. Suggest `/glean-core:mcp-setup`. ## Intent → tool decision tree | The user is asking about... | Reach for | Reference | |---|---|---| | Documents, wikis, policies, RFCs, specs | `search` | [search.md](reference/search.md) | | A complex question that needs synthesis across sources | `chat` | [chat.md](reference/chat.md) | | Internal source code, files, commits across repos | `code_search` | [code-search.md](reference/code-search.md) | | People, teams, org structure, reporting lines | `employee_search` | [employee-search.md](reference/employee-search.md) | | Meetings, transcripts, decisions, action items | `meeting_lookup` | [meeting-lookup.md](reference/meeting-lookup.md) | | Gmail messages, threads, attachments | `gmail_search` | [gmail-search.md](reference/gmail-search.md) | | Outlook messages, threads, attachments | `outlook_search` | [outlook-search.md](reference/outlook-search.md) | | Reading a specific URL / document | `read_document` | [read-document.md](reference/read-document.md) | | The user's own recent activity (standup, weekly summary) | `user_activity` | [user-activity.md](reference/user-activity.md) | | The user's stored memories / personalization | `read_memory` (+ `memory_schema`) | [memory.md](reference/memory.md) | | Structured entity / relationship queries | `knowledge_graph_query` (+ `knowledge_graph_schema`) | [knowledge-graph.md](reference/knowledge-graph.md) | The reference files are loaded only when needed. Open the relevant one before invoking a tool you haven't used recently — each file carries the exact param shape, the filter syntax, and the pitfalls that have bitten previous calls. ## Cross-tool rules These apply regardless of which Glean tool is active. Internalize them, don't re-derive per call. 1. **Never use `search` for people lookups.** It searches documents; it doesn't index people. Use `employee_search`. 2. **Cite every claim with a URL.** Glean returns links; surface them so the user can verify. No URL → likely fabricated. 3. **Permission-empty results are valid signals.** If a tool returns nothing, that often means the user lacks access — not that the information is missing. Don't pad with weak alternatives; report empty cleanly. 4. **Prefer recent over old.** Glean returns by relevance; for currency-sensitive questions, add a date filter or sort by recency rather than presenting stale top hits as authoritative. 5. **Vet before presenting.** Apply the criteria in [reference/vetting.md](reference/vetting.md) — relevance, freshness, authority. Better to return three vetted results than ten unfiltered ones. ## Cross-cutting reference - **[synthesis.md](reference/synthesis.md)** — patterns for combining multiple Glean tools when a single tool doesn't answer the question. - **[vetting.md](reference/vetting.md)** — how to evaluate source quality, freshness, and authority; when to communicate confidence to the user. ## Glean platform agents If the user's Glean instance has platform agents enabled, those agents may surface as additional MCP tools alongside the built-in tools above. The set is org-specific and can change at any time. See [agents-as-tools.md](reference/agents-as-tools.md) for how to recognize, introspect, and invoke them.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.