一键导入
daily-briefing
Get a clear view of what matters most today. This skill works with whatever you tell me, and gets richer when you connect your tools.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Get a clear view of what matters most today. This skill works with whatever you tell me, and gets richer when you connect your tools.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
How to send a notetaker bot into a video meeting (Google Meet / Zoom / Teams) and work with what it captures — join a call, confirm it got admitted, monitor its lifecycle, pull the speaker-attributed transcript, and produce a recap with decisions + action items, then remove it. Drives the `meet` CLI, which runs through the Kortix Executor (the meeting-bot provider key is resolved server-side; nothing in the sandbox). Load this WHENEVER the user asks to join / attend / record / transcribe / take notes on a meeting, "send a notetaker", "summarize that call", drops a Meet/Zoom/Teams link, or asks how to do anything with a meeting bot.
Kortix brand + design system: the rules, tokens, and component library for building any Kortix frontend UI (apps/web). Load this WHENEVER you create or edit a page, screen, component, list, card, badge, avatar, modal, form, empty state, toast, tooltip, or any visual surface in apps/web. Always load the companion skill make-interfaces-feel-better (apps/web/.agents/skills/make-interfaces-feel-better/SKILL.md) in the same session — brand/tokens here, polish/motion/haptics there. Source of truth: globals.css + the live /design-system page + src/components/ui + the reference implementations listed below.
How to roll Kortix PRODUCTION back to an older already-released version — the inverse of a release. Covers the one-dispatch rollback-prod.yml engine, the per-surface mechanics (API + gateway = Argo image-tag swap; frontend = Vercel promote), the all-important Vercel frontend behavior (why a backend-only push can 'clobber' a FE rollback, and the 'don't rebuild the FE for backend-only pushes' skip that fixes it), the DB/migration-drift safety check that is the real blocker, and how a later promote returns prod to latest. Load WHENEVER the user wants to roll back / revert / downgrade / 'go back a version' on prod, asks how the rollback or the frontend clobber/skip behavior works, or needs to run rollback-prod.yml. Pairs with kortix-release (the forward direction).
Create, manage, validate, preview, and export HTML presentation slides (1920x1080). Load this skill when you need to build a slide deck, export to PDF/PPTX, or preview slides in a browser.
Create, manage, validate, preview, and export HTML presentation slides (1920x1080). Load this skill when you need to build a slide deck, export to PDF/PPTX, or preview slides in a browser.
Canonical reference for a Kortix project: the platform model (repo-native projects, sessions on ephemeral branches, the strict boundary between `kortix.toml` and OpenCode config under `.kortix/opencode/`); the full `kortix.toml` manifest (keys, trigger fields, secrets contract, `[[apps]]` deploy surface); the complete `kortix` CLI (commands, flags, the project-scoped token model, the in-sandbox `KORTIX_TOKEN`); the change-request (CR) system for landing session work on `main` (an agent MUST open a CR to merge); the session sandbox runtime (which supports Docker and Docker-in-Docker); and the OpenCode runtime (agents, skills, commands, tools, plugins, MCP servers, permissions, AGENTS.md rules, models). Load whenever the user asks how Kortix works, about `kortix.toml`, the `kortix` CLI, anything under `.kortix/opencode/`, how to merge/ship/land work on `main`, change requests/CRs/PRs, or to author/edit any OpenCode primitive.
| name | daily-briefing |
| description | Get a clear view of what matters most today. This skill works with whatever you tell me, and gets richer when you connect your tools. |
Get a clear view of what matters most today. This skill works with whatever you tell me, and gets richer when you connect your tools.
┌─────────────────────────────────────────────────────────────────┐
│ DAILY BRIEFING │
├─────────────────────────────────────────────────────────────────┤
│ ALWAYS (works standalone) │
│ ✓ You tell me: today's meetings, key deals, priorities │
│ ✓ I organize: prioritized action plan for your day │
│ ✓ Output: scannable 2-minute briefing │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + Calendar: auto-pull today's meetings with attendees │
│ + CRM: pipeline alerts, tasks, deal health │
│ + Email: unread from key accounts, waiting on replies │
│ + Enrichment: overnight signals on your accounts │
└─────────────────────────────────────────────────────────────────┘
When you run this skill, I'll ask for what I need:
If no calendar connected:
"What meetings do you have today? (Just paste your calendar or list them)"
If no CRM connected:
"What deals are you focused on this week? Any that need attention?"
If you have connectors: I'll pull everything automatically and just show you the briefing.
Connect your tools to supercharge this skill:
| Connector | What It Adds |
|---|---|
| Calendar | Today's meetings with attendees, times, and context |
| CRM | Open pipeline, deals closing soon, overdue tasks, stale deals |
| Unread from opportunity contacts, emails waiting on replies | |
| Enrichment | Overnight signals: funding, hiring, news on your accounts |
No connectors? No problem. Tell me your meetings and deals, and I'll create your briefing.
# Daily Briefing | [Day, Month Date]
---
## #1 Priority
**[Most important thing to do today]**
[Why it matters and what to do about it]
---
## Today's Numbers
| Open Pipeline | Closing This Month | Meetings Today | Action Items |
|---------------|-------------------|----------------|--------------|
| $[X] | $[X] | [N] | [N] |
---
## Today's Meetings
### [Time] — [Company] ([Meeting Type])
**Attendees:** [Names]
**Context:** [One-line: deal status, last touch, what's at stake]
**Prep:** [Quick action before this meeting]
### [Time] — [Company] ([Meeting Type])
**Attendees:** [Names]
**Context:** [One-line context]
**Prep:** [Quick action]
*Run `call-prep [company]` for detailed meeting prep*
---
## Pipeline Alerts
### Needs Attention
| Deal | Stage | Amount | Alert | Action |
|------|-------|--------|-------|--------|
| [Deal] | [Stage] | $[X] | [Why flagged] | [What to do] |
### Closing This Week
| Deal | Close Date | Amount | Confidence | Blocker |
|------|------------|--------|------------|---------|
| [Deal] | [Date] | $[X] | [H/M/L] | [If any] |
---
## Email Priorities
### Needs Response
| From | Subject | Received |
|------|---------|----------|
| [Name @ Company] | [Subject] | [Time] |
### Waiting On Reply
| To | Subject | Sent | Days Waiting |
|----|---------|------|--------------|
| [Name @ Company] | [Subject] | [Date] | [N] |
---
## Suggested Actions
1. **[Action]** — [Why now]
2. **[Action]** — [Why now]
3. **[Action]** — [Why now]
---
*Run `call-prep [company]` before your meetings*
*Run `call-follow-up` after each call*
If connectors available:
1. Calendar → Get today's events
- Filter to external meetings (non-company attendees)
- Pull: time, title, attendees, description
2. CRM → Query your pipeline
- Open opportunities owned by you
- Flag: closing this week, no activity 7+ days, slipped dates
- Get: overdue tasks, upcoming tasks
3. Email → Check priority messages
- Unread from opportunity contact domains
- Sent messages with no reply (3+ days)
4. Enrichment → Check signals (if available)
- Funding, hiring, news on open accounts
If no connectors:
Ask user:
1. "What meetings do you have today?"
2. "What deals are you focused on? Any closing soon or needing attention?"
3. "Anything urgent I should know about?"
Work with whatever they provide.
Priority ranking:
1. URGENT: Deal closing today/tomorrow not yet won
2. HIGH: Meeting today with high-value opportunity
3. HIGH: Unread email from decision-maker
4. MEDIUM: Deal closing this week
5. MEDIUM: Stale deal (7+ days no activity)
6. LOW: Tasks due this week
Select #1 Priority:
- If meeting with >$50K deal today → prep that
- If deal closing today → focus on close
- If urgent email from buyer → respond first
- Else → highest-value stale deal
Assemble sections based on available data:
1. #1 Priority — Always include (even if simple)
2. Today's Numbers — If CRM connected, otherwise skip
3. Today's Meetings — From calendar or user input
4. Pipeline Alerts — If CRM connected
5. Email Priorities — If email connected
6. Suggested Actions — Always include top 3 actions
Say "quick brief" or "tldr my day" for abbreviated version:
# Quick Brief | [Date]
**#1:** [Priority action]
**Meetings:** [N] — [Company 1], [Company 2], [Company 3]
**Alerts:**
- [Alert 1]
- [Alert 2]
**Do Now:** [Single most important action]
Say "wrap up my day" or "end of day summary" after your last meeting:
# End of Day | [Date]
**Completed:**
- [Meeting 1] — [Outcome]
- [Meeting 2] — [Outcome]
**Pipeline Changes:**
- [Deal] moved to [Stage]
**Tomorrow's Focus:**
- [Priority 1]
- [Priority 2]
**Open Loops:**
- [ ] [Unfinished item needing follow-up]