Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add pantheon-org/tekhne --skill professional-communicationgit clone --depth 1 https://github.com/pantheon-org/tekhneWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/pantheon-org/tekhne/professional-communication)<a href="https://agentmods.dev/skills/pantheon-org/tekhne/professional-communication"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/professional-communication/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/pantheon-org/tekhne/professional-communication"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/professional-communication.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00048 | $0.02231 |
| Opus 5 | $0.00024 | $0.01115 |
| Sonnet 5 | $0.00010 | $0.00446 |
| Haiku 4.5 | $0.00005 | $0.00223 |
Grade A, and why
professional-communication scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
86% identical to professional-communication — 22 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Professional Communication
Overview
This skill provides frameworks and guidance for effective professional communication in software development contexts. Whether you're writing an email to stakeholders, crafting a team chat message, or preparing meeting agendas, these principles help you communicate clearly and build professional credibility.
Core principle: Effective communication isn't about proving how much you know - it's about ensuring your message is received and understood.
When to Use This Skill
Use this skill when:
- Writing emails to teammates, managers, or stakeholders
- Crafting team chat messages or async communications
- Preparing meeting agendas or summaries
- Translating technical concepts for non-technical audiences
- Structuring status updates or reports
- Improving clarity of written communication
Keywords: email, chat, teams, slack, discord, message, writing, communication, meeting, agenda, status update, report
Core Frameworks
The What-Why-How Structure
Use this universal framework to organize any professional message:
| Component | Purpose | Example |
|---|---|---|
| What | State the topic/request clearly | "We need to delay the release by one week" |
| Why | Explain the reasoning | "Critical bug found in payment processing" |
| How | Outline next steps/action items | "QA will retest by Thursday; I'll update stakeholders Friday" |
Apply to: Emails, status updates, meeting talking points, technical explanations
Three Golden Rules for Written Communication
- Start with a clear subject/purpose - Recipients should immediately grasp what your message is about
- Use bullets, headlines, and scannable formatting - Nobody wants a wall of text
- Key messages first - Busy people appreciate efficiency; state your main point upfront
Audience Calibration
Before communicating, ask yourself:
- Who are you writing to? (Technical peers, managers, stakeholders, customers)
- What level of detail do they need? (High-level overview vs implementation details)
- What's the value for them? (How does this affect their work/decisions?)
What ships with it
15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/instructions.json 1012 B
- evals/scenario-1/capability.txt 69 B
- evals/scenario-1/criteria.json 589 B
- evals/scenario-1/task.md 158 B
- evals/scenario-2/capability.txt 69 B
- evals/scenario-2/criteria.json 562 B
- evals/scenario-2/task.md 166 B
- evals/scenario-3/capability.txt 46 B
- evals/scenario-3/criteria.json 598 B
- evals/scenario-3/task.md 136 B
- evals/summary.json 151 B
- references/email-templates.md 5.6 KB
- references/jargon-simplification.md 7.9 KB
- references/meeting-structures.md 8.6 KB
- references/remote-async-communication.md 7.9 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 290 lines · 48 tokens per session scan A 581c062a604b
professional-communication is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 2,231 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to professional-communication, differing in 22 lines, and is treated as a copy.
Other skills, from other repositories
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
atlas-obscura
Search Atlas Obscura for weird, wonderful, and hidden gem places near any destination. Find the interesting stuff, not boring plaques. Search by coordinates, get full details with descriptions and images.
agent-code-generator
Generates Agent definitions (.md files) based on user intent and standard templates.
cf-validate
A validator for 1C configuration source files. It checks the XML structure and the files and objects that make up a 1C business-application configuration.