public-relations-manager

Route external communications from GitHub issues into the bead system.

105|16|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/jordanhubbard/loom --skill public-relations-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: public-relations-manager
Source: https://github.com/jordanhubbard/loom/tree/main/personas/default/public-relations-manager
Command: npx skills add https://github.com/jordanhubbard/loom --skill public-relations-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Loom projects require a professional, consistent interface to the outside world. The Public Relations Manager ensures external-facing messages are timely, accurate, and aligned with project goals across GitHub, release notes, and community channels.

Core Features & Use Cases

  • Translate internal technical context into clear public messages for GitHub issues, release notes, and status pages.
  • Create and link beads to issues, route feedback to relevant personas, and track communication progress.
  • Enforce tone, templates, and escalation rules to protect the project's reputation and ensure timely responses.

Quick Start

Spawn a public-relations-manager agent for your Loom project and begin monitoring configured repositories for external communications.

Frequently Asked Questions about public-relations-manager

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

FAQPage Schema
How do I manage external communications for GitHub issues and release notes?

You can manage external communications by spawning a public relations agent to monitor configured repositories, triage community feedback, and link beads directly to GitHub issues to ensure timely, accurate public responses.

What is the best way to translate internal technical context into clear public messages for a Loom project?

The best way to translate internal technical context is by applying defined persona roles and templates that enforce tone and escalation rules across GitHub, release notes, and status pages to protect the project's reputation.

How does routing community feedback into the bead system work for reputation management?

Routing community feedback into the bead system works by triaging external responses, linking relevant beads to GitHub issues, and assigning them to defined personas to track communication progress and ensure accurate alignment with project goals.

Can I enforce communication templates and escalation rules across GitHub and status pages?

Yes, you can enforce communication templates and escalation rules across GitHub and status pages by utilizing a configuration schema that supports a persona-driven workflow to protect the project's reputation during external interactions.

Do I need a Loom project to coordinate external communications and community responses?

Yes, you need a Loom project because the external communications management relies on the bead system to link GitHub issues, route feedback to personas, and track communication progress within the project environment.