← Products

Productivity
⚙ Needs: nothing — the skill is a communication methodology p…

Professional communication playbook for developers

Structure emails, team messages and meeting agendas — What-Why-How framework, audience calibration, jargon translation, email templates

At a glance
What
Structure emails, team messages and meeting agendas — What-Why-How framework, audience calibration, jargon translation, email templates
Cost
Free
Needs
nothing — the skill is a communication methodology plus templates, no accounts or keys required
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

@
Created by: @softaworks
⌁

Install

Prerequisites: nothing — the skill is a communication methodology plus templates, no accounts or keys required Install "Professional communication playbook for developers" for me. It teaches the agent @softaworks' frameworks for clear professional communication: the What-Why-How message structure, audience calibration, email templates by type, subject-line formulas, team-messaging etiquette, meeting agendas and summaries, clarity principles — plus reference files with ready-to-use templates. MIT-licensed. Repository: https://github.com/softaworks/agent-toolkit/blob/main/dist/plugins/professional-communication/skills/professional-communication/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "professional-communication". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — ask the agent to draft a message when you need one). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.