external-comms

Draft community responses for open issues and route them for human approval.

1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/DeDuva/squad --skill external-comms-deduva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: external-comms
Source: https://github.com/DeDuva/squad/tree/main/packages/squad-sdk/templates/skills/external-comms
Command: npx skills add https://github.com/DeDuva/squad --skill external-comms-deduva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PAO workflow automates scanning open issues and discussions, drafts responses with the humanizer skill, and presents a review table for human approval.

Core Features & Use Cases

  • Scan open issues and discussions to find candidates for PAO responses with deterministic filtering
  • Classify responses by type (Welcome, Troubleshooting, Feature Guidance, Redirect, Acknowledgment, Closing, Technical Uncertainty, Empathetic Disagreement, Information Request)
  • Ensure a mandatory human review gate and log all actions to an audit trail

Quick Start

Draft the first PAO response for an open issue or discussion and route it for human approval.

Frequently Asked Questions about external-comms

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

FAQPage Schema
How do I automate drafting community responses for open issues and discussions?

To automate drafting community responses, this Skill scans open issues and discussions, classifies them by type, and applies the correct template to generate a draft routed for human approval.

What types of community discussion responses can be classified and drafted automatically?

Community discussion responses are classified into types like Welcome, Troubleshooting, Feature Guidance, Redirect, Acknowledgment, Closing, Technical Uncertainty, Empathetic Disagreement, and Information Request.

Can I require human review before posting automated community replies?

Yes, a mandatory human review gate requires explicit approval before any drafted community response is posted, while all automated actions are logged to an audit trail.

What is the best way to ensure consistent templates across community support replies?

The best way to ensure consistent templates is using deterministic filtering to scan open issues and select the correct response template for each specific community interaction type.

How do I start drafting a PAO response for a GitHub issue?

To start drafting a PAO response, trigger the workflow to scan your open issues, apply phase-1 rules to classify the item, and generate the initial draft for human review.