external-comms

Automate scanning, drafting, and presenting GitHub community responses with human review.

Updated May 10, 2026

Search Tags:#workflow #GitHub #community management #audit logging #response automation

Ready to run

npx skills add https://github.com/AshleyHollis/agentic-identity-lab --skill external-comms-ashleyhollis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: external-comms
Source: https://github.com/AshleyHollis/agentic-identity-lab/tree/main/.copilot/skills/external-comms
Command: npx skills add https://github.com/AshleyHollis/agentic-identity-lab --skill external-comms-ashleyhollis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github-mcp-server-list_issues, github-mcp-server-issue_read, github-mcp-server-search_issues, gh CLI, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of scanning, drafting, and presenting community responses on GitHub with human review, saving time and reducing errors in communication workflows.

Core Features & Use Cases

Automated Scanning: Identifies unanswered community items on GitHub.
Drafting: Generates response drafts using templates and humanizer patterns.
Human Review: Requires manual approval before posting responses.
Audit Logging: Tracks all actions for accountability.
Use Case: For organizations using GitHub to manage community discussions, this Skill helps streamline the process of responding to community queries and feedback.

Quick Start

Use the external-comms skill to start the response workflow for a new issue or discussion.

Frequently Asked Questions about external-comms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate community management responses on GitHub?▼

Automate community management responses on GitHub by using a workflow that scans unanswered issues, generates draft responses from templates, and requires human review before posting. This ensures accountability through audit logging while streamlining support.

Can I require human review before automated responses are posted to GitHub issues?▼

Yes, you can require human review before posting automated responses to GitHub issues. The workflow generates response drafts using templates and humanizer patterns, then pauses for manual approval to ensure quality control before any public reply is submitted.

Do I need GitHub MCP tools to scan and draft responses for unanswered issues?▼

Yes, you need GitHub MCP tools to scan and draft responses for unanswered issues. The workflow specifically requires the GitHub MCP server for listing, reading, and searching issues, alongside the gh CLI, to manage community discussions effectively.

What is the best way to track accountability when automating GitHub community support?▼

Track accountability when automating GitHub community support by using a workflow with built-in audit logging. This records all scanning, drafting, and human review actions, ensuring every automated response and manual approval is documented for compliance.

Does this community response workflow work with GitHub discussions and issue tracking?▼

Yes, this community response workflow works with GitHub discussions and issue tracking. It uses GitHub MCP server capabilities to search and list issues, allowing you to identify unanswered community items and manage responses across your repository.

Why use humanizer patterns for drafting automated GitHub issue responses?▼

Use humanizer patterns for drafting automated GitHub issue responses to ensure generated replies sound natural and empathetic. Combined with template structures and manual review gates, this approach maintains a professional community tone while reducing manual effort.