What it does
- Connects Instruction files the AI reads
- Account or key Not confirmed yet (README not read yet)
- Category 自动化与智能体
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/basecamp-hey-cli)相似的 Skill
同类工作,排序与 Skill 列表相同
Skill 和 MCP 有什么不同
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
适用的应用
Claude CodeCodex
依据开发者 README 和 repo 中的文件夹
安装
Is it safe?
- Who made it
GitHub account basecamp (organization), 18 years old
- Use and upkeep
★ 427 stars, few users so far · code last changed 2026年11月16日
- Any scripts?
No, plain text files the AI reads and follows
- Uses the internet?
No scripts, so it does not go online by itself
- Changes machine-wide settings?
Installing the maker’s way adds hooks that run without you asking: run every time a chat starts
Checked automatically from the repo files at commit 8145386 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
Option 1Upload to claude.ai (web and app)
Uploading to claude.ai would fail: the description is over 200 characters (207). Use "Let the AI install it" instead
Option 1让 Claude Code 帮你安装
复制这句话,粘贴到 Claude Code 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
重新打开 Claude Code,输入 /hey,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.claude/skills
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
重新打开 Claude Code,输入 /hey,或直接提出相关任务,Claude 会自动选用
ChatGPT 桌面应用
ChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
Option 1让 ChatGPT 帮你安装
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2自己放入文件夹
把 hey 文件夹放到 ~/.agents/skills/hey
~ 是你的主文件夹($HOME)
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.agents/skills
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
安装之后
- ChatGPT 桌面应用:打开侧边栏中的 Skills,确认 Skill 已出现
- 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
- Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
网页版和手机版 ChatGPT
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Option 1让 Codex 帮你安装
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.agents/skills
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
重新打开 Codex 并提出相关任务,Codex 会列出这个 skill
Option 1让 Cursor 帮你安装
复制这句话,粘贴到 Cursor 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
在 Cursor 的 Agent 聊天中输入 / 并选择 hey
Checked against official docs 2026年11月12日 · Source: cursor.com
For Terminal users
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
打开终端
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
把 skill 文件夹复制到 ~/.cursor/skills
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
在 Cursor 的 Agent 聊天中输入 / 并选择 hey
Option 1Let the AI install it
适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
查看原始 SKILL.md
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
显示前 8,000 个字符 · 在 GitHub 打开完整文件
---
name: hey
description: |
Interact with HEY via the HEY CLI. Read and send emails, manage contacts,
boxes, labels, collections, calendars, todos, habits, time tracking, and journal entries. Use for ANY
HEY-related question or action.
triggers:
# Direct invocations
- hey
- /hey
# Email actions
- hey account
- hey box
- hey label
- hey collection
- hey set-aside
- hey workflow
- hey clip
- hey snippet
- hey search
- hey contact
- hey bundle
- hey thread read
- hey thread comment
- hey thread update
- rename a thread
- hey attachment
- hey share
- hey unshare
- hey reply
- hey bulk-reply
- hey forward
- hey compose
- hey draft list
- hey draft show
- hey draft edit
- hey draft send
- hey draft delete
- hey screener
- hey watch
- screen a sender
- approve a sender
- deny a sender
# Calendar actions
- hey calendar list
- hey event
# Todos
- hey todo
# Seen/unseen
- hey seen
- hey unseen
- hey move
- hey bubble
- hey trash
- hey spam
- hey ignore
- hey stop-ignoring
- move email
- bubble a thread up
- trash email
- mark as spam
- ignore email thread
- stop ignoring email thread
- mark as read
- mark as seen
- mark as unseen
- mark as unread
# Habits
- hey habit
# Time tracking
- hey timetrack
# Journal
- hey journal
# Auth
- hey auth
# Common actions
- check my email
- read email
- send email
- reply to email
- forward email
- share email thread
- turn off sharing link
- compose email
- list mailboxes
- search email
- find email
- list contacts
- add contact
- edit contact
- hide contact
- bundle contact mail
- unbundle contact mail
- contact note
- contact photo
- find a contact by email
- check calendar
- add todo
- complete todo
- track time
- write journal
# Questions
- can I hey
- how do I hey
- what's in hey
- what hey
- does hey
# My work
- my emails
- my inbox
- my imbox
- my todos
- my calendar
- my journal
# URLs
- hey.com
invocable: true
argument-hint: "[command] [args...]"
---
# /hey - HEY Email Workflow Command
CLI for HEY: mailboxes, labels, collections, email threads, contacts, replies, compose, calendars, todos, habits, time tracking, and journal entries.
Use the installed CLI as the command reference. This skill holds the rules that span commands; it does not copy the command catalog, because the binary's own help is the source of truth and always matches the version you are running.
## Discovery-first workflow
For each task:
1. Infer the deepest plausible leaf command from the user's words.
2. Unless its arguments and flags are already established by a tool result in this conversation, read that leaf's help before running it:
```bash
hey <group> <subcommand> --agent --help
```
3. If the leaf does not exist, read its nearest parent group. Use root help only when the top-level group itself is unclear:
```bash
hey <group> --agent --help # fallback
hey --agent --help # last resort
hey commands --json # every command with its agent_notes
```
4. Treat the leaf's `short`, `long`, `agent_notes` and `flags` as the source of truth. Do not guess positional arguments, flags, accepted values, or limits.
5. Run with an explicit output mode, then read structured errors before deciding what to do next.
Leaf help is cheap; root help and `hey commands --json` print the whole catalog and are not. Global flags (`--json`, `--jq`, `--quiet`, `--account`, `--stats`) apply wherever a command supports them.
## Non-negotiable rules
1. **Choose the right structured output.** Use `--jq '<expression>'` to filter or extract fields and `--json` for the full response. Never pipe to an external `jq`; `--jq` is built in and implies `--json`.
2. **Reuse stored authentication.** Run the requested data command; it uses stored credentials and refreshes expiring OAuth tokens automatically. If it returns an auth error, follow the retry in [Authentication](#authentication) before you report the task as blocked. Use `hey auth status --json` when an explicit authentication check is needed (it reports stored credentials and does not contact HEY). Never run `hey auth login` unattended; use it only for interactive recovery with the user present.
3. **Linked mail accounts share one login.** Use `hey account list --json`, then `--account <id|all>` when a task must target one account.
4. **Local HEY configuration requires human trust.** Never run `hey config trust-local` without the user's explicit approval.
5. **Never resend a send that failed with `not_delivered`.** See [Sending](#sending).
6. **Confirm box item mutations.** See [IDs](#ids): HEY does not report IDs that matched nothing.
## Output
`--jq` filters the full JSON success envelope, so result data is under `.data`. String results print as plain text; objects and arrays print as formatted JSON. Use `--quiet --jq` when the expression should run against result data directly. Errors keep their complete structured envelope. Commands with raw output of their own (`auth token`, `shell-completion generate`, `setup`, `skill`, `tui`, `--version`, and `timetrack export` without `--output`) reject `--jq`. `hey watch` writes one raw JSON event per line with no envelope and does not apply `--jq`.
```bash
hey box list --jq '.data[] | {id, name}'
hey search "quarterly planning" --jq '.data[].topic_id'
hey box list --quiet --jq '.[].name'
```
- An empty result is an empty array rather than `null`, so `.data[]` is safe on a listing that found nothing.
- A field HEY's answer leaves out is left out, never guessed. A posting's `seen` is present only when true, so test `.seen != true` for unseen.
- `--ids-only` prints one ID per line and `--count` a bare number. They work on listings: every `list` command, the thread listings, `hey workflow view`, `hey search`, `hey screener history`, `hey event day|week`, `hey timetrack categories`, `hey attachment list` and `hey thread read` (its entries, read from the index without bodies). Both answer for what was read, which is the first page unless `--all` or `--limit` reads more, and not every listing warns that more pages exist; `hey screener list --count` is the exception and counts the whole queue. On thread listings they count the postings, not the box, label or contact around them.
- `--all` stops at a page cap, which each listing's help names. A capped read says where to continue: `next_page` for a cursor listing such as `hey box view`, or the `notice`, naming the `--page` value, for a numbered one such as `hey search` or `hey contact list`. Continue from there rather than treating the list as complete.
- `--html` writes the original HTML of `hey thread read`, `hey journal read` and a contact's private note to a pipe or file; a terminal is refused.
## IDs
Every email thread has two IDs: `id`, its **box item ID** (one posting in one box), and `topic_id`, its **thread ID**. Each posting in a thread listing has `id`, `topic_id`, `kind` (`bundle` for a bundle row), `name` (subject), `created_at` and `app_url`; a thread row also has `contacts`, `summary` and `visible_entry_count`.
- **Box item ID** (`id`): `hey seen`, `unseen`, `move`, `label add|remove|create`, `trash`, `spam`, `ignore`, `stop-ignoring`, `bubble up|pop`, `set-aside group`, `bulk-reply` and `bundle view`.
- **Thread ID** (`topic_id`): `hey thread read|update|comment`, `share`, `unshare`, `attachment list`, `reply`, `forward`, `compose --thread-id`, `collection add|remove` and `workflow add|move|remove`.
- **Entry ID**: an entry's `id` from `hey thread read`; `hey clip create` takes it, and the passage must appear in that message's text.
- **Contact ID** from `hey contact list` or contact data, **clearance ID** from `hey screener list` (which also gives the `topic_id` of the thread to read before deciding; `hey screener approve|deny` also take the sen讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
来自 GitHub
- GitHub 星标
- 427
- 开发者
- basecamp
- 许可证
- MIT
- 最近代码更新
- 2026年11月16日
- repo 中的 SKILL.md 文件(含译本和模板)
- 1
- 主题
- agent-skills, hey
- Repo
- basecamp/hey-cli