check-human-issues

SkillCommunication

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".

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the check-human-issues skill

What this skill tells your AI

The instructions your AI receives, as published by wandb/senpai in plugins/senpai/skills/check-human-issues/SKILL.md and read by ahel’s review.

Check GitHub Issues tagged human for messages from the research team, and respond to any that need a reply.

Arguments

  • $0 — The configured advisor branch for ADVISOR, or student name for STUDENT
  • $1 — Either ADVISOR or STUDENT

How it works

Human 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.

Steps

  1. 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.

  2. Decide whether to respond:

    • If you haven't commented on this issue yet → respond.
    • If you have commented, check if the human posted a new comment after your last response. If so → respond to the new message. If not → skip, you're waiting for the human.
    • Record the exact numeric id of the issue body or human comment you are answering. Never substitute the issue number for a comment ID.
  3. 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.

  1. Never close human issues. Only the human does that.

Return format

When you're done, record a structured summary of the issues you checked and responded to in the current conversation:

New research directives from the human researcher team

If there are research directives in the issues, include them in detail so they remain available for subsequent planning in this conversation.

Signals

GitHub stars
34
Forks
5
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
check-human-issues
Source
github.com/wandb/senpai