project-awareness
Project Awareness
When users ask about projects, their status, or ownership, use Glean to quickly gather relevant context.
Tool Naming
See the glean-tools-guide skill for Glean MCP tool naming conventions.
When This Applies
Use this approach when users ask:
- "What's the status of [project]?"
- "Who owns [project]?"
- "What's happening with [project]?"
- "Where does [project] stand?"
- "Who's working on [project]?"
- Quick project context questions
BE SKEPTICAL
More from gleanwork/claude-plugins
enterprise-search
Use when the user asks about company documents, internal wikis, policies, specifications, design docs, RFCs, or enterprise knowledge. Triggers on phrases like "find the doc about", "what's our policy on", "where is the spec for", "company guidelines", "internal documentation", or when searching for information that would be in enterprise systems rather than the local codebase.
12confidence-signals
Use when you need to communicate the reliability, freshness, or authority of information from Glean. Triggers when presenting search results, when data might be stale, when sources have different authority levels, when the user should verify information, or when you're uncertain about completeness of results.
11priority-signals
Use when the user asks about urgent items, what needs attention, priorities, or blockers. Triggers on phrases like "what's urgent", "what needs my attention", "what's blocking", "what should I focus on", "priorities", "critical items", "what's on fire", "what can't wait", or when helping the user triage their workload.
10release-workflow
Use when preparing or executing a release for the glean-claude-plugins marketplace. Triggers on "release", "bump version", "publish", "npm run release", "new version", or when the user wants to cut a new plugin version.
4