external-comms

Draft human-reviewed responses for unanswered GitHub issues and discussions.

Updated Apr 3, 2026

Search Tags:#community #github #audit-logging #issue-triage #discussion-management #human-review #response-drafting

Ready to run

npx skills add https://github.com/sachinnair90/gitgloss --skill external-comms-sachinnair90

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: external-comms
Source: https://github.com/sachinnair90/gitgloss/tree/main/.copilot/skills/external-comms
Command: npx skills add https://github.com/sachinnair90/gitgloss --skill external-comms-sachinnair90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams scan GitHub issues and discussions, determine the right community response, and prepare a draft for human approval instead of posting blindly.

Core Features & Use Cases

Scan open issues and discussions for unanswered community items.
Classify each thread into response types such as welcome, troubleshooting, feature guidance, redirect, acknowledgment, closing, technical uncertainty, empathetic disagreement, or information request.
Draft responses from reusable templates, verify full-thread context, and present a review table with confidence levels and audit-ready notes.
Use case: a community manager can review recent GitHub threads, identify which ones need a reply, and hand off polished drafts to a human reviewer for approval.

Quick Start

Ask the skill to scan recent GitHub issues and discussions, classify the best response type, and prepare a human-reviewed draft for each item.

Frequently Asked Questions about external-comms

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

FAQPage Schema

How do I draft responses for unanswered GitHub issues and discussions?▼

To draft responses for GitHub issues and discussions, this Skill scans open threads, classifies the response type, and generates template-based drafts. It verifies full-thread context and requires explicit human approval before posting any reply.

What is the best way to classify GitHub community threads for triage?▼

Classifying GitHub community threads for triage involves analyzing open conversations and sorting them into categories like troubleshooting, feature guidance, or acknowledgment. This process ensures each thread receives an appropriate, contextual draft response for human review.

Can I automate GitHub issue triage without posting replies directly?▼

Yes, you can automate GitHub issue triage without posting directly. The Skill prepares response drafts with confidence levels and audit-ready notes, enforcing a strict human approval checkpoint so no automated replies are published blindly.

How does audit logging work for GitHub discussion management drafts?▼

Audit logging for GitHub discussion management records the classification, contextual review, and confidence assessment of each drafted response. This creates an audit-ready trail of the drafting process that reviewers can verify before granting final approval.

What response templates are available for GitHub issue triage?▼

Available response templates for GitHub issue triage cover welcome, troubleshooting, feature guidance, redirect, acknowledgment, closing, technical uncertainty, empathetic disagreement, and information request. These templates help structure drafts based on the thread's classification.

When should I not use automated response drafting for GitHub threads?▼

You should not use automated response drafting for GitHub threads when a conversation requires immediate posting or lacks clear classification. The process mandates full-thread verification and human approval, making it unsuitable for bypassing review workflows.