一键在 Manus 中运行任何 Skill

log-person

星标0

分支1

更新时间2026年4月24日 19:58

Create a new person atomic note at + Atlas/People/<Full Name>.md from the Person template, optionally seeding context from Gmail/Slack searches across all accounts.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

davidianstyle

davidianstyle/openbrain-gemini-starter

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

/log-person

Inputs

$1: full name (quoted if it contains spaces), e.g. "Alice Example"
$2 (optional): quick to skip the cross-account context seed, deep (default) to search all Gmail + Slack for prior mentions.

Procedure

Check for existing note. If + Atlas/People/<name>.md already exists, stop and tell the user — offer to open it instead.
Scaffold from template. Copy + Extras/Templates/Person.md to + Atlas/People/<name>.md. Set title: <name> and created: to today.
Context seed (unless quick). Fan out across every google_* and every slack_* in a single tool-use block — all calls are independent and must never be serialized.
- For each google_* MCP, google_gmail_search_emails for the person's name (as both sender and recipient). Collect top 5 hits per account. Extract email addresses and populate frontmatter emails:.
- For each slack_* MCP, slack_search_users for the name. Populate slack: with workspace-slug:user_id entries.
- Cross-reference across accounts — if the same email address appears in multiple google_* account sweeps, that's fine (common for cc'd threads).
Relationship inference. Based on which accounts surfaced the person, suggest a default relationship: value:
- Appears only in the user's work Google/Slack sources → work
- Appears in one of the user's other accounts mapped to a specific community (see GEMINI.md §11 account table) → use that community's label
- Otherwise → network (user can correct)
Add to MOC. Append - [[<name>]] under the correct section of + Spaces/People.md (based on relationship).
Report. Show the populated frontmatter and the inferred context; ask the user to confirm or correct before saving.

Output

Path to new person note
Populated frontmatter
Any context gathered (summarized, not verbatim)

Notes

Only populate frontmatter from unambiguous matches. If multiple people with the same name surface, flag it and don't guess.
Never write real phone numbers from email signatures automatically — leave phones: [] for the user to fill.

同仓库更多 Skills

同仓库

daily-brief

davidianstyle/openbrain-gemini-starter

Produce today's daily briefing across all Google Calendars, Gmail accounts, Slack workspaces, and Asana. Writes to + Atlas/Daily/YYYY-MM-DD.md and surfaces anything that needs the user's attention today. Safe to re-run — refreshes the `## Morning brief` section in place.

2026-06-100

draft-follow-up

davidianstyle/openbrain-gemini-starter

Draft a follow-up email or Slack message for a given person or thread, using the correct account. Never sends.

2026-06-100

learn-writing-style

davidianstyle/openbrain-gemini-starter

Scan sent messages across configured Google and Slack accounts to derive a personalized writing-style profile (email vs Slack, by audience size), then update GEMINI.md §6 in place. Run after initial bootstrap or anytime you want to refresh.

2026-06-100

process-inbox

davidianstyle/openbrain-gemini-starter

Triage + Inbox/ together with fresh items in Gmail and Slack across all accounts. Proposes classification per GEMINI.md §4 and surfaces anything needing a reply.

2026-06-100

daily-review

davidianstyle/openbrain-gemini-starter

End-of-day (or any-time) reconciliation — compare today's plan against what actually got done, interactively check off Asana tasks, surface outstanding follow-ups, summarize for review, then update OpenBrain and Asana (mark complete, create tasks, adjust due dates). Safe to re-run — refreshes the `## Evening review` section in place.

2026-06-070

capture-meeting

davidianstyle/openbrain-gemini-starter

Turn rough meeting notes or a transcript into an atomic interaction note, update linked people's last_contact + Threads, and propose follow-up tasks.

2026-05-260

name	log-person
description	Create a new person atomic note at + Atlas/People/<Full Name>.md from the Person template, optionally seeding context from Gmail/Slack searches across all accounts.

/log-person

Inputs

$1: full name (quoted if it contains spaces), e.g. "Alice Example"
$2 (optional): quick to skip the cross-account context seed, deep (default) to search all Gmail + Slack for prior mentions.

Procedure

Check for existing note. If + Atlas/People/<name>.md already exists, stop and tell the user — offer to open it instead.
Scaffold from template. Copy + Extras/Templates/Person.md to + Atlas/People/<name>.md. Set title: <name> and created: to today.
Context seed (unless quick). Fan out across every google_* and every slack_* in a single tool-use block — all calls are independent and must never be serialized.
- For each google_* MCP, google_gmail_search_emails for the person's name (as both sender and recipient). Collect top 5 hits per account. Extract email addresses and populate frontmatter emails:.
- For each slack_* MCP, slack_search_users for the name. Populate slack: with workspace-slug:user_id entries.
- Cross-reference across accounts — if the same email address appears in multiple google_* account sweeps, that's fine (common for cc'd threads).
Relationship inference. Based on which accounts surfaced the person, suggest a default relationship: value:
- Appears only in the user's work Google/Slack sources → work
- Appears in one of the user's other accounts mapped to a specific community (see GEMINI.md §11 account table) → use that community's label
- Otherwise → network (user can correct)
Add to MOC. Append - [[<name>]] under the correct section of + Spaces/People.md (based on relationship).
Report. Show the populated frontmatter and the inferred context; ask the user to confirm or correct before saving.

Output

Path to new person note
Populated frontmatter
Any context gathered (summarized, not verbatim)

Notes

Only populate frontmatter from unambiguous matches. If multiple people with the same name surface, flag it and don't guess.
Never write real phone numbers from email signatures automatically — leave phones: [] for the user to fill.