home / skills / ken-cavanagh-glean / fieldkit / brief

This skill provides a pre-meeting briefing for any account by aggregating local checklists and real-time Glean data for actionable insights.

npx playbooks add skill ken-cavanagh-glean/fieldkit --skill brief

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
4.1 KB
---
name: brief
description: "Get a pre-meeting briefing for any account. Usage: /brief {account name}. Returns checklist progress, hours remaining, last interaction, missed comms, and open to-dos."
---

# Account Briefing

Quick situational awareness before client calls. Combine local checklist with real-time Glean data.

## Usage

```
/brief Snap
/brief northbeam
/brief golden gate bridge
```

## Workflow

When invoked with an account name, execute these steps:

### Step 1: Parse Account Name

The account name is provided as the argument. Normalize it for file lookup (lowercase, spaces preserved for file paths).

### Step 2: Read Local Entity File

Read the entity file from `exo/entities/orgs/{account name}.md`:

```
Read: exo/entities/orgs/{account}.md
```

Extract:
- **Deployment Checklist** — count `[x]` vs `[ ]` items, identify next incomplete item
- **Deal table** — TCV, seats, package, region, dates, team members
- **Next Steps** — local to-do items
- **Risks** — known blockers
- **Context** — situational notes

### Step 3: Query Glean Account Status Agent

Run the agent query script to call the Account Status Agent directly via the Glean API.

**IMPORTANT:** The Glean Agent API takes 60-90 seconds to respond (it runs multiple searches + LLM synthesis). You MUST set a 120-second timeout:

```bash
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/query_account_status.py "{account name}"
# Use timeout: 120000 (milliseconds) when calling via Bash tool
```

**Required environment variables:**
- `GLEAN_API_TOKEN` — API token for Glean
- `GLEAN_INSTANCE` — Glean instance (defaults to `scio-prod`)

The script returns JSON with:
```json
{
  "account": "Snap",
  "status": "...",
  "sources": [{"title": "...", "url": "..."}]
}
```

The agent returns:
1. **Last Meeting** — most recent calendar event with this customer + Gong summary
2. **Open To-Dos** — action items from meetings/emails since last interaction
3. **Missed Communications** — unanswered Slack/email since last meeting
4. **Internal Flags** — concerns flagged by AE/DEM/Support in internal channels
5. **Hours** — hours used vs. remaining from Rocketlane

**Agent ID:** `ccdc8e55722e48f98ef04d548f2b7e58`

### Step 4: Synthesize Briefing

Combine the data into a structured briefing:

```markdown
## [[{Account}]] Status Briefing

**Checklist Progress:** X/Y complete
- Last completed: {most recent [x] item}
- Next up: {first [ ] item} {(scheduled/not scheduled)}

**Hours:** {used}/{total} ({remaining} remaining)

**Last Interaction:** {date} {meeting title}
- {key points from Gong summary}

**Needs Attention:**
- {unread messages count and from whom}
- {pending emails}

**Risks/Notes:**
- {items from Risks section}
- {relevant context notes}

**Open To-Dos:**
- [ ] {from agent + local Next Steps}
```

## Checklist Parsing

The deployment checklist in entity files follows this structure:

```markdown
## Deployment Checklist

### Setup
- [x] Kickoff call completed
- [x] Client has launched Glean

### Enablement
- [ ] Enablement session scheduled
- [ ] Enablement session completed

### Success Planning
- [ ] Success planning workshop scheduled
- [ ] Success planning workshop completed

### Training
- [ ] Platform fundamentals training scheduled
- [ ] Platform fundamentals training completed
- [ ] Agent fundamentals training scheduled
- [ ] Agent fundamentals training completed
- [ ] Advanced Agents training scheduled
- [ ] Advanced Agents training completed

### Governance & Review
- [ ] Agent Governance Workshop completed
- [ ] First Quarterly Business Review completed
```

Count all items with `[x]` as completed, `[ ]` as pending.

## Entity File Locations

All account entity files live at:
```
exo/entities/orgs/{account name}.md
```

File names use lowercase with spaces (e.g., `golden gate bridge.md`, `snap.md`).

## Error Handling

- **File not found:** Report "No entity file found for {account}. Check exo/entities/orgs/"
- **No Glean data:** Report what's available from local file only
- **Partial data:** Always output what's available, note missing sections

---

*Part of account-ops plugin for fieldkit*

Overview

This skill provides a concise pre-meeting briefing for any account using a combined local entity file and real-time Glean account status. Invoke with /brief {account name} to get checklist progress, hours remaining, last interaction, missed communications, and open to-dos. It surfaces what needs attention so you can join calls informed and focused.

How this skill works

The skill normalizes the provided account name and reads the local entity file at exo/entities/orgs/{account name}.md to extract the deployment checklist, deal details, next steps, risks, and context. It then calls the Glean Account Status Agent (via a provided script) to retrieve last meeting summaries, open to-dos, missed communications, internal flags, and hours used/remaining. Finally it synthesizes both sources into a structured briefing showing checklist progress, hours, last interaction, risks, and consolidated open tasks.

When to use it

  • Before client or internal calls to get quick situational awareness
  • When preparing account handoffs or escalation calls
  • To check current checklist progress and identify next actions
  • After noticing missed messages or unclear ownership on an account
  • When you need consolidated status combining local notes and search-driven signals

Best practices

  • Keep the local entity file up to date with checklist items, next steps, and risks
  • Use the exact account name (case-insensitive, spaces preserved) for reliable file lookup
  • Set GLEAN_API_TOKEN and GLEAN_INSTANCE before running Glean queries
  • Allow the Glean agent 120-second timeout; responses can take 60–90 seconds
  • If the Glean script fails, rely on local file output and note missing live signals

Example use cases

  • /brief Snap before a QBR to confirm remaining enablement steps and hours
  • /brief golden gate bridge when preparing for a handoff to support to surface open to-dos
  • /brief northbeam to spot recent missed Slack threads and unanswered emails prior to an AE check-in
  • Run before internal syncs to show checklist completion and the next scheduled step
  • Use during on-call rotations to quickly see internal flags and outstanding risks

FAQ

What if the entity file is missing?

The skill reports “No entity file found for {account}. Check exo/entities/orgs/” and returns whatever Glean data is available.

What if the Glean agent times out or returns nothing?

The skill will output the local file data only and clearly note missing Glean sections; ensure GLEAN_API_TOKEN and GLEAN_INSTANCE are set and use the required 120s timeout.