githubinferredactive
cursor-chief-of-staff
provenance:github:pauloribeiro92/cursor-chief-of-staff
WHAT THIS AGENT DOES
Okay, here's a summary of the "cursor-chief-of-staff" AI agent, geared towards a non-technical business user: What it is: The "cursor-chief-of-staff" is like having a highly organized and helpful assistant living inside your documents. It's an AI that helps you manage your work, stay on top of tasks, and remember important details. What problem does it solve? It tackles the challenge of feeling overwhelmed by information and tasks. We all struggle with juggling meetings, projects, and remembering key details. This AI helps you get organized, prioritize your work, and stay focused on what matters most. Who would use it? Busy professionals
README
# Personal Assistant Dashboard
> A Cursor-native AI personal assistant that lives entirely in markdown files. Works with **Cursor**, **Claude Code**, and any AI editor that reads a project's files.
Clone it, fill in your context (or let the AI do it for you), and you have a fully functional personal assistant in minutes.
---
## What You Get
- **Task management** — inbox, today, active, backlog with a consistent format scripts can parse
- **Meeting and 1-on-1 notes** — structured templates with Notion sync
- **Three-layer memory** — session scratch (L1), active project context (L2), permanent knowledge (L3)
- **Slash commands** — `/ask`, `/store`, `/review`, `/sleep`, `/observe`, `/selfimprove`
- **Subagents** — daily digest, memory cleanup, workspace compaction
- **Integrations** — Slack, Notion, Google Workspace, Jira, GitHub via MCP
- **Automation scripts** — daily Slack briefing, memory cleanup (Python + uv, no venv needed)
- **Self-improvement loop** — the assistant captures lessons and proposes upgrades to itself
---
## Quick Start
### Step 1 — Clone and open
```bash
git clone https://github.com/YOUR_USERNAME/personal-assistant-template.git
cd personal-assistant-template
```
Open the folder in **Cursor** (or any AI editor). The rules and skills load automatically.
### Step 2 — Fill in your context
**Option A — Let the AI fill it for you (recommended):**
Open Cursor, start a new chat, and say:
```
Help me set up my personal assistant context. Walk me through each file I need to fill in.
```
The assistant will guide you through `role.md`, `team.md`, `meetings.md`, and `preferences.md` conversationally, asking the right questions and writing the files for you.
**Option B — Run the bootstrap script:**
```powershell
# Windows
powershell -ExecutionPolicy Bypass -File scripts\setup.ps1
```
```bash
# macOS / Linux
bash scripts/setup.sh
```
The script prompts for your name, replaces `[YOUR_NAME]` across all files, and creates your `.env`.
**Option C — Fill manually** using the table in [Fill In Your Context](#fill-in-your-context) below.
### Step 3 — Start chatting
```
/ask what's my day look like?
```
---
## Fill In Your Context
These files contain `[placeholder]` values. Fill them in once and the assistant knows who you are permanently.
| File | What to fill in | Time |
| ---------------------------------------------------------------------------- | ------------------------------------------------------------ | ------- |
| `[context/work/role.md](context/work/role.md)` | Your title, company, responsibilities, active projects, OKRs | ~3 min |
| `[context/work/team.md](context/work/team.md)` | Team members, roles, emails, Slack handles | ~3 min |
| `[context/work/meetings.md](context/work/meetings.md)` | Recurring meetings and 1-on-1 schedule | ~3 min |
| `[memory/L3-core/preferences.md](memory/L3-core/preferences.md)` | Communication style, task habits, memory preferences | ~2 min |
| `[.cursor/rules/assistant-persona.mdc](.cursor/rules/assistant-persona.mdc)` | Replace `[YOUR_NAME]` with your name | ~30 sec |
> See `[examples/](examples/)` for pre-filled reference files showing what a completed setup looks like.
> **Tip:** You don't have to fill these manually. Open Cursor and say *"help me set up my assistant context"* — it will walk you through each file conversationally, asking about your role, team, and preferences, and writing everything for you.
---
## How It Works
```mermaid
flowchart TD
User(["You"])
subgraph cmds ["Commands (entry points)"]
Ask["/ask"]
Store["/store"]
Review["/review"]
Sleep["/sleep"]
Observe["/observe"]
end
subgraph skills ["Skills (procedural logic)"]
TM["task-management"]
MN["meeting-notes"]
BR["brainstorm"]
SR["slack-report"]
WH["workspace-hygiene"]
end
subgraph agents ["Subagents (autonomous)"]
DD["daily-digest"]
MC["memory-cleanup"]
WC["workspace-compactor"]
end
subgraph files ["Your Files (plain markdown)"]
Tasks["tasks/"]
Memory["memory/ L1·L2·L3"]
Notes["notes/"]
Context["context/"]
Reminders["reminders/"]
end
subgraph mcp ["MCP Integrations"]
Slack["Slack"]
Notion["Notion"]
GW["Google Workspace"]
Jira["Jira / Atlassian"]
end
User -->|"chat"| cmds
Store --> skills
Review --> skills
Sleep --> agents
Ask -->|"read-only"| files
skills --> files
agents --> files
Observe --> mcp
mcp --> Tasks
SR --> Slack
```
The key design principle: **you own all the data**. Every task, note, memory, and preference is a plain markdown file you can read, edit, or delete. The AI orchestrates across them.
---
## Repository Structure
```
personal-assistant-template/
├── .cursor/
│ ├── mcp.json # Project-level MCP config (Slack)
│ ├── rules/ # Always-on AI behavior rules
│ │ ├── assistant-persona.mdc # Session start, tone, memory routing
│ │ ├── memory-management.mdc # L1/L2/L3 read/write rules
│ │ ├── meta-cursor-files.mdc # Standards for .cursor/ files
│ │ ├── self-improvement.mdc # Proactive lesson capture
│ │ └── task-and-notes-format.mdc # Standard formats for all files
│ ├── commands/ # Slash commands
│ │ ├── ask.md # /ask — read-only briefing and search
│ │ ├── store.md # /store — classify and save anything
│ │ ├── review.md # /review — daily/weekly review
│ │ ├── sleep.md # /sleep — full workspace compaction
│ │ ├── observe.md # /observe — sync from external services
│ │ └── selfimprove.md # /selfimprove — research and upgrade the system
│ ├── skills/ # AI workflow skills (procedural)
│ │ ├── brainstorm/
│ │ ├── daily-review/
│ │ ├── delegation-handoff/
│ │ ├── meeting-notes/
│ │ ├── memory-manager/
│ │ ├── sheets-update/
│ │ ├── slack-report/
│ │ ├── task-management/
│ │ └── workspace-hygiene/
│ └── agents/ # Autonomous subagents
│ ├── daily-digest.md
│ ├── memory-cleanup.md
│ └── workspace-compactor.md
├── memory/
│ ├── L1-working/ # Session scratch (~1 day lifetime)
│ ├── L2-active/ # Active project context (~2 weeks)
│ └── L3-core/ # Permanent knowledge base
│ ├── preferences.md
│ ├── lessons-learned.md
│ ├── decisions-log.md
│ └── workflows.md
├── context/
│ ├── work/ # Role, team, meetings, 1-on-1 templates
│ ├── integrations/ # MCP status and setup guides
│ └── personal/ # Goals
├── tasks/
│ ├── inbox.md # Quick capture — triage daily
│ ├── today.md # Committed for today (≤7 items)
│ ├── active.md # Multi-day in-progress work
│ ├── backlog.md # Future work
│ └── completed/ # Monthly archive (YYYY-MM.md)
├── notes/
│ ├── meetings/ # Meeting notes (YYYY-MM-DD-name.md)
│ ├── 1-on-1/ # 1-on-1 notes by person
│ ├── brainstorm/ # Brainstorm sessions
│ ├── backlog/ # Long-form backlog notes
│ └── handoff/ # OOO/delegation handoff docs
├── reminders/
│ └── active.md
├── examples/ # Pre-filled reference files (not loaded by AI)
│ ├── role-example.md
│ ├── team-example.md
│ └── preferences-ex
[truncated…]PUBLIC HISTORY
First discoveredMar 21, 2026
IDENTITY
inferred
Identity inferred from code signals. No PROVENANCE.yml found.
Is this yours? Claim it →METADATA
platformgithub
first seenMar 14, 2026
last updatedMar 14, 2026
last crawledtoday
version—
README BADGE
Add to your README:
