📦
meme-factory
84Generate Memes with Memegen
Teams often need quick visual humor without opening design tools. This skill builds meme URLs, Markdown embeds, and text meme formats from a prompt.
Design & Creative View
Skills professional-communication
📦
professional-communication
Content revision r1 Safe ⚙️ External commands
Improve Developer Communication
Software teams lose time when messages are unclear or aimed at the wrong audience. This skill helps Claude, Codex, and Claude Code draft clear emails, chat updates, meeting notes, and stakeholder messages.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "professional-communication" from https://skillstore.io/skills/softaworks-professional-communication.md and its manifest at https://skillstore.io/api/skills/softaworks-professional-communication/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "professional-communication". A developer needs to tell a manager that a release is delayed because QA found a payment bug.
Expected outcome:
Subject: Release Update: New Target Date Needed
The release needs to move by one week because QA found a payment issue that could affect customers. The team is fixing the bug now, QA will retest by Thursday, and I will share a confirmed launch date on Friday.
Using "professional-communication". A vague chat message says: “Hey, can I ask something about deploy?”
Expected outcome:
Hi Sarah, quick question about the deployment script. I am seeing a permission error on line 42 during deploy. Have you seen this before, or should I open a support ticket?
Using "professional-communication". A design review ended with two decisions and three action items.
Expected outcome:
- Meeting: API Design Review
- Key decisions: Use versioned endpoints. Keep the existing authentication flow for this release.
- Action items: Priya updates the design doc by Wednesday. Marcus reviews error handling by Thursday. Alex schedules a follow-up if blockers remain.
Security Audit
Safev5 • 7/7/2026 Open versioned report
All static findings were adjudicated as false positives. The external-command alerts are Markdown fences or inline file references, and the reconnaissance alerts are ordinary communication and meeting prompts with no malicious intent.
6
Files scanned
1,572
Lines analyzed
0
Review items
0
False positives ignored
Risk Factors
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/softaworks-professional-communication/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/softaworks-professional-communication?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/softaworks-professional-communication?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/softaworks-professional-communication/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/softaworks-professional-communication.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
softaworks. (2026). professional-communication security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/softaworks-professional-communication/audits/5BibTeX citation
@techreport{softaworks-softaworks-professional-communication-2026,
author = {softaworks},
title = {professional-communication security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/softaworks-professional-communication/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "professional-communication security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "softaworks"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/softaworks-professional-communication/audits/5"
identifiers:
- type: other
value: "skillstore:softaworks-professional-communication:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: High 59
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance
What You Can Build
Write stakeholder updates
Turn project status, risks, and next steps into concise updates for managers or business partners.
Improve async team messages
Convert vague chat messages into clear requests with context, urgency, and expected action.
Prepare meeting communication
Create agendas, decision summaries, and action-item follow-ups for planning, retrospectives, and design reviews.
Try These Prompts
Draft a clear email
Draft a professional email about [topic]. Include a clear subject, the main point first, brief context, the action needed, and a polite close.
Rewrite a chat message
Rewrite this team chat message so it is direct, async-friendly, and easy to answer: [paste message]. Keep the tone professional and concise.
Create a meeting follow-up
Create a meeting follow-up for [meeting topic]. Use these notes: [paste notes]. Include key decisions, action items with owners, open questions, and next steps.
Adapt for multiple audiences
Rewrite this technical update for three audiences: engineering peers, technical managers, and non-technical stakeholders. Preserve accuracy and adjust detail, tone, and jargon for each audience: [paste update].
Best Practices
- Lead with the main point, then add context and next steps.
- Match detail, terminology, and tone to the audience receiving the message.
- Use bullets, headings, owners, and dates when a message includes actions.
Avoid
- Starting with vague greetings before stating the request.
- Sending long blocks of text without structure or clear action items.
- Using technical jargon with audiences who need business impact and plain language.
Frequently Asked Questions
Can this skill write emails for managers and stakeholders?
Yes. It can structure status updates, requests, escalations, announcements, and follow-ups for professional audiences.
Does it work for Slack, Teams, or Discord messages?
Yes. The guidance applies to team chat tools and focuses on clear, async-friendly messages.
Can it translate technical language for non-technical readers?
Yes. It helps preserve accuracy while reducing jargon and emphasizing business or customer impact.
Does this skill send messages automatically?
No. It drafts and improves communication, but it does not connect to email, calendar, or chat services.
What information should I provide for best results?
Provide the audience, goal, context, deadline, facts to include, and any tone requirements.
Is it suitable for sensitive workplace issues?
It can improve clarity and tone, but legal, human resources, or compliance issues need qualified review.
Developer Details
Author
softaworksLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
f93e9bb0daca99badb6a7e574b97737155d57cb3
Maintenance freshness
7/18/2026
Usage
17 downloads · 149 views
File structure
More from softaworks
View all📦
react-dev
82Build Type-Safe React Components
React TypeScript work often needs precise event, hook, and route types. This skill provides focused patterns for typed components, React 19 APIs, and routing.
Coding & Development View
📦
humanizer
80Humanize AI Drafts With Natural Editing
AI drafts often sound polished but generic. This skill finds common AI writing patterns and rewrites text with clearer, more natural wording.
Writing & Content View
📦
database-schema-designer
80Design Production Database Schemas
Teams need schemas that preserve data integrity and stay fast as products grow. This skill turns domain requirements into SQL or MongoDB designs with indexes, constraints, and migration guidance.
Data & Analytics View
📦
reducing-entropy
80Reduce Codebase Entropy
Codebases grow because each change often adds more structure than it removes. This skill gives Claude, Codex, and Claude Code a deletion-first review method for smaller final designs.
Coding & Development View
📦
mermaid-diagrams
79Create Mermaid Diagrams for Software Documentation
Teams often need clear diagrams that stay close to code and documentation. This skill guides Claude, Codex, and Claude Code through Mermaid syntax for maintainable visual models.
Documentation View
Related Skills
View all📦
gws-gmail
81Manage Gmail with Google Workspace CLI
by googleworkspace
Managing Gmail through API commands requires accurate resource names and parameters. This skill guides Claude and Codex through supported Gmail CLI workflows.
Communication View
📦
converting-email-templates
81Convert Email Templates to Mailtrap
by mailtrap
Moving templates between email providers can break variables, conditionals, and send calls. This skill converts provider syntax to Mailtrap Handlebars and flags changes that need review.
Communication View
📦
reactivation-specialist
81Build a compliant email reactivation program
by aaron-he-zhu
Lapsed subscriber lists can reduce deliverability and create consent risk. This skill designs a staged win-back program with fresh consent signals and clear suppression outcomes.
Communication View
📦
email-sequence-designer
81Design a lifecycle email sequence
by aaron-he-zhu
Email teams often lack a clear lifecycle map and send too frequently. This skill creates flow plans with timing, exits, and safeguards before copywriting begins.
Communication View
📦
cold-outbound-sequencer
81Plan a compliant B2B outreach sequence
by aaron-he-zhu
Cold outreach plans can miss reply handling, sending limits, and jurisdiction requirements. This skill creates a structured sequence plan with deliverability and compliance guardrails before copy is written.
Communication View
📦
lark-im
80Manage Lark Messages and Chats
by larksuite
Teams need controlled access to Lark messages, chats, files, and cards from AI tools. This skill guides Claude, Codex, and Claude Code through lark-cli workflows with clear permission boundaries.
Communication View