project-awareness
Quick project context — surface a project's status, owner, recent activity, and key links. Use when the user wants a fast situational read on a project, not a deep handoff document.
What this skill does
# Project Awareness When users ask about projects, their status, or ownership, use Glean to quickly gather relevant context. ## Tools This skill drives the standard Glean MCP tools. For full param shape and pitfalls of `chat`, `search`, `employee_search`, and `meeting_lookup`, see the `using-glean` skill's reference files in the `glean-core` plugin. ## 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 Not all project info is current or reliable. Before presenting information, evaluate: **Currency Test** - Is this information fresh? - ✅ INCLUDE: Updated in last 2 weeks - ⚠️ CONTEXT: Last 2-4 weeks (note it's aging) - ❌ EXCLUDE: Older than 1 month (status likely stale) **Authority Test** - Is this from an official source? - ✅ INCLUDE: From project lead, official docs, tracking systems - ⚠️ CONTEXT: From team members (secondary source) - ❌ EXCLUDE: Informal mentions, dated secondhand reports **Ownership Test** - Is the current owner clear? - ✅ INCLUDE: Explicitly assigned owner in system - ⚠️ CONTEXT: Appears to be owner but not confirmed - ❌ EXCLUDE: Unknown or orphaned projects **Cross-Reference Check** - Do sources agree? - ✅ INCLUDE: Multiple sources confirm status - ⚠️ CONTEXT: Single source, note confidence level - ❌ EXCLUDE: Conflicting information (needs clarification) **Filter Out**: - Projects that appear abandoned (no activity for >3 months) - Status without context (just "active" is meaningless) - Owner info you cannot confirm **If unsure**: Mark as "Status Unknown - Recommend checking with [owner]" ## Primary Approach For quick context, use Glean chat: ``` chat "What is the current status of [project]? Who owns it and what are the recent updates?" ``` For deeper investigation, combine: - `search` for project documentation - `employee_search` for people - `meeting_lookup` for recent discussions ## Query Patterns ### Quick Status ``` chat "Give me a 2-3 sentence status update on [project]." ``` ### Find Owner ``` employee_search "[project] lead OR owner" search query="[project] owner OR lead" app="confluence" ``` ### Recent Activity ``` search query="[project]" updated="past_week" sort_by_recency=true ``` ### Current Work ``` search query="[project] in progress OR active" app="jira" ``` ## Output Format For quick questions, respond concisely: ```markdown **[Project]** - **Status**: [Active/Planning/Blocked] - **Owner**: [Name] - **Recent Update**: [What's happening] - **Details**: [Link to main doc] ``` For more detail, include: ```markdown ## [Project Name] ### Quick Status | Attribute | Value | |-----------|-------| | Status | [Status] | | Owner | [Name] | | Last Updated | [Date] | ### Recent Activity - [Activity 1] - [Activity 2] ### Key People - **Owner**: [Name] - **Team**: [Team name] ### Key Links - [Main doc]([link]) - [Tracker]([link]) ``` ## Relationship to Commands For comprehensive project context, suggest: - `/glean-project:project-handoff <name>` - Generate complete handoff document - `/glean-docs:onboarding <topic>` - Get up to speed on a team or area
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.