CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

55

Quality

62%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/glean-project/skills/project-awareness/SKILL.md
SKILL.md
Quality
Evals
Security

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:

**[Project]**
- **Status**: [Active/Planning/Blocked]
- **Owner**: [Name]
- **Recent Update**: [What's happening]
- **Details**: [Link to main doc]

For more detail, include:

## [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
Repository
gleanwork/claude-plugins
Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.