菜单
Check and respond to GitHub Issues from the human researcher team. Use this skill whenever you need to handle a human_issue event, respond to human issues, or check team communications. Also triggers for: "any human messages?", "check issues", "respond to humans".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/wandb/senpai --skill check-human-issues命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Create a typed assignment branch and draft PR for one student. Use when the advisor has a concrete hypothesis and the student has no open `status:wip` or `status:review` assignment.
Maintain and publish the advisor-owned current research state, durable research-ideas syntheses, and dataset analysis. Use when evidence or human guidance changes the research focus or direction, durable research ideas should be recorded, or dataset understanding changes.
Review one terminal experiment and choose the next step: merge a reproducible winner, close a useful negative or dead end, or request missing evidence.
基于 SOC 职业分类
正在显示 SKILL.md
| name | check-human-issues |
| description | Check and respond to GitHub Issues from the human researcher team. Use this skill whenever you need to handle a human_issue event, respond to human issues, or check team communications. Also triggers for: "any human messages?", "check issues", "respond to humans". |
| argument-hint | <name> <ADVISOR|STUDENT> |
Check GitHub Issues tagged human for messages from the research team, and respond to any that need a reply.
ADVISOR, or student name for
STUDENTADVISOR or STUDENTHuman researchers communicate with agents through GitHub Issues. Issues are
tagged with human plus team for a broadcast, the configured advisor branch
for an advisor, or student:<student-name> for a student. Your job is to check
messages routed to your exact role, respond to new ones, and skip ones you've
already handled.
Read the current human_issue event. The controller supplies the issue
identity and the exact human message ID that triggered the wake. It polls
GitHub for issues addressed to you or the whole team.
Decide whether to respond:
id of the issue body or human comment you are
answering. Never substitute the issue number for a comment ID.Respond through respond_to_human_issue with the issue number, the exact
human_message_id, and the response text without a role prefix. This verified,
idempotent operation refuses closed issues, pull requests, missing human
labels, stale message IDs, messages authored by the agent identity, and
issues not addressed to this configured advisor branch or student.
{
"issue_number": 123,
"human_message_id": 987654,
"response": "<your response>"
}
Never mutate the issue through gh or curl.
When you're done, record a structured summary of the issues you checked and responded to in the current conversation:
If there are research directives in the issues, include them in detail so they remain available for subsequent planning in this conversation.