Management Talk
thananon/9arm-skills
Rewrite engineer-to-engineer content for engineering-org leadership (VPs, directors, PMs, release managers, execs in an engineering-savvy company) and shape it for the channel it is going to — JIRA…
Draft professional emails, feedback (SBI/BID), difficult conversations, meeting notes, and escalation templates.
Install Communication
$ npx skills add EliasOulkadi/shokunin --skill communication -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install EliasOulkadi/shokunin communication --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/EliasOulkadi/shokunin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.pack/skills/communication .claude/skills/communication && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "communication" agent skill from https://github.com/EliasOulkadi/shokunin/tree/master/.pack/skills/communication into .claude/skills/communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "communication", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/EliasOulkadi/shokunin/tree/master/.pack/skills/communicationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add EliasOulkadi/shokunin --skill communication -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install EliasOulkadi/shokunin communication --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EliasOulkadi/shokunin.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.pack/skills/communication .agents/skills/communication && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "communication" agent skill from https://github.com/EliasOulkadi/shokunin/tree/master/.pack/skills/communication into .agents/skills/communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "communication", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add EliasOulkadi/shokunin --skill communication -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install EliasOulkadi/shokunin communication --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EliasOulkadi/shokunin.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.pack/skills/communication .cursor/skills/communication && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "communication" agent skill from https://github.com/EliasOulkadi/shokunin/tree/master/.pack/skills/communication into .cursor/skills/communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "communication", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/EliasOulkadi/shokunin.git --path .pack/skills/communication--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add EliasOulkadi/shokunin --skill communication -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install EliasOulkadi/shokunin communication --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EliasOulkadi/shokunin.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.pack/skills/communication .gemini/skills/communication && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "communication" agent skill from https://github.com/EliasOulkadi/shokunin/tree/master/.pack/skills/communication into .gemini/skills/communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "communication", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install EliasOulkadi/shokunin communicationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add EliasOulkadi/shokunin --skill communication -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/EliasOulkadi/shokunin.git skills-src && mkdir -p .github/skills && cp -r skills-src/.pack/skills/communication .github/skills/communication && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "communication" agent skill from https://github.com/EliasOulkadi/shokunin/tree/master/.pack/skills/communication into .github/skills/communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "communication", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add EliasOulkadi/shokunin --skill communication -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install EliasOulkadi/shokunin communication --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EliasOulkadi/shokunin.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.pack/skills/communication .opencode/skills/communication && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "communication" agent skill from https://github.com/EliasOulkadi/shokunin/tree/master/.pack/skills/communication into .opencode/skills/communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "communication", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
communication- GitHub stars
- 114
- Token cost
- ~2.6k tokens
- SKILL.md length
- 1,113 words
- Files
- 1
- Skills in repo
- 49
- Repo updated
- First seen
- Licence
- MIT
At a glance
Draft professional emails, feedback (SBI/BID), difficult conversations, meeting notes, and escalation templates.
- Works in 6 steps: Subject: [Verb] + [Topic]. Max 50 chars.… → Context: reference previous… → Purpose: the ask or update in the FIRST… → …
- Tasks that involve Meeting notes and agendas
- SKILL.md covers Sub-Commands, Workflow, Filler Phrases to Delete… and Feedback (SBI Model), plus 9 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Communication is an agent skill from EliasOulkadi/shokunin. Draft professional emails, feedback (SBI/BID), difficult conversations, meeting notes, and escalation templates. Covers tone matrix, cross-cultural communication, Slack/Teams async patterns, and structured notes from raw transcripts.
Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: opencode 1.0+
It sits in Productivity & Automation, covering Meeting notes and agendas and Email writing. It works with Slack. The repository describes itself as: 職人 Shokunin 62 AI agent skills for OpenCode, Claude Code, Cursor, Windsurf. ChromaDB memory, MCP servers, declarative self-updates. Multi-model, open source, zero cost. The licence is MIT.
When your agent uses it
- Tasks that involve Meeting notes and agendas
- Tasks that involve Email writing
Example prompts
- “/communication”
Requirements
- Compatibility (from SKILL.md): opencode 1.0+
- Pre-approved tools (allowed-tools): -, read, -, write, -, edit, -, grep, -, glob, -, bash, -, webfetch, -, websearch, -, skills
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Subject: [Verb] + [Topic]. Max 50 chars. Prefix: [Request/Update/Follow-up/Escalation]
- Context: reference previous communication in one sentence
- Purpose: the ask or update in the FIRST paragraph
- Detail: supporting info, bulleted if > 3 items
- Next step: who does what by when
- Closing: matched to relationship
What it can do on your machine
Read from SKILL.md and the folder at commit 4c68e5b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
-read-write-edit-grep-glob
…and 8 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
opencode 1.0+
From compatibility in the SKILL.md frontmatter.
Context cost
Communication loads about 2.6k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 1,113 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from EliasOulkadi/shokunin at commit 4c68e5b, republished under its MIT licence (© EliasOulkadi). 1,113 words, ~2,631 tokens.
Download SKILL.mdSave it as
.claude/skills/communication/SKILL.md (or your agent's skills folder).- name
- communication
- description
- Draft professional emails, feedback (SBI/BID), difficult conversations, meeting notes, and escalation templates. Covers tone matrix, cross-cultural communication, Slack/Teams async patterns, and structured notes from raw transcripts.
- allowed-tools
- -, read, -, write, -, edit, -, grep, -, glob, -, bash, -, webfetch, -, websearch, -, skills
- compatibility
- opencode 1.0+
- triggers
- - "write an email" - "draft feedback" - "difficult conversation" - "meeting notes" - "escalate" - "compose a message" - "corporate email" - "tone check"…
- negatives
- - "sales outreach" -> use business-proposals - "cold email sequence" -> use business-proposals - "proposal" -> use business-proposals - "SOW" -> use…
- license
- MIT
- metadata
- version: "4.0.0" workflow: communication audience: developers
Communication
Professional writing that gets results. Based on Harvard Business Review, Radical Candor (Kim Scott), Crucial Conversations (Patterson et al.), Amazon Working Backwards, and Google Project Aristotle.
Sub-Commands
| Command | Description |
|---|---|
draft | Draft an email, message, or document from context |
polish | Polish tone, cut filler, strengthen ask |
feedback | Draft feedback using SBI/BID model |
notes | Structure meeting notes from raw transcript or notes |
escalate | Draft escalation with clear facts, impact, and request |
reply | Reply to a message with appropriate tone |
Workflow
Step 1 — Identify audience & context
- Who is the recipient? What is your relationship?
- What is their communication style (direct/indirect, formal/casual)?
- What is the power dynamic (peer, manager, report, client, exec)?
- What has happened before this communication?
Step 2 — Choose tone from matrix
| Context | Tone | Salutation | Closing |
|---|---|---|---|
| Internal peer | Casual-direct | "Hi [Name]" | "Thanks" |
| Internal manager | Professional | "Hi [Name]" | "Thanks" |
| Cross-team | Professional | "Hi [Name]" | "Best" |
| Client (established) | Cordial | "Hi [Name]" | "Best regards" |
| Client (new) | Formal-cordial | "Dear [Name]" | "Best regards" |
| Executive / VP+ | Formal | "Dear [Title] [Last]" | "Sincerely" |
| Escalation | Firm, respectful | "Hi [Name]" | "Regards" |
| Complaint | Calm, professional | "Hi [Name]" | "Best regards" |
Step 3 — Select channel
| Scenario | Channel |
|---|---|
| Simple question, needs quick answer | DM (Slack/Teams) |
| Team-wide decision or update | Public channel |
| Sensitive feedback | In-person or video call |
| Complex explanation | Loom or shared doc |
| Formal request or escalation | |
| Needs paper trail | |
| External client |
Step 4 — Draft using structure
Email structure:
- Subject:
[Verb] + [Topic]. Max 50 chars. Prefix:[Request/Update/Follow-up/Escalation] - Context: reference previous communication in one sentence
- Purpose: the ask or update in the FIRST paragraph
- Detail: supporting info, bulleted if > 3 items
- Next step: who does what by when
- Closing: matched to relationship
Step 5 — Review checklist
- Subject ≤ 50 chars, prefixed with
[Request/Update/Follow-up/Escalation] - One explicit ask per message, with deadline
- Length ≤ 150 words internal, ≤ 200 client
- Tone matches recipient in matrix
- Zero filler: no "hope this finds you well", "just checking in", "I wanted to reach out"
- No passive-aggression: no "as per my last email", "per our conversation"
- Blame externalized: "The deployment failed" not "You failed"
Step 6 — Send at appropriate time
- During recipient's working hours (respect timezone)
- Avoid Friday afternoon (unless urgent)
- Avoid right before lunch or end of day
Step 7 — Follow up
- If no response in 48h, send ONE follow-up
- Format: same subject, first line = "Gentle ping on this — do you need anything from me to move forward?"
Filler Phrases to Delete (exact replacements)
| Delete | Replace with |
|---|---|
| "I hope this email finds you well" | Nothing. Start with the purpose. |
| "I just wanted to reach out" | State the purpose directly. |
| "Per my last email" | Restate the ask directly. |
| "Just checking in" | "Following up on [specific thing] — do you have an ETA?" |
| "Quick question" | Ask the question directly in the subject. |
| "Sorry to bother you" | "When you have a moment, [ask]" |
| "To be honest" | Everything you write should be honest. Drop the phrase. |
| "I think" / "I feel" | "I recommend" / "The data shows" — be direct. |
Feedback (SBI Model)
- Situation: when and where
- Behavior: what exactly was said/done (observable, not interpreted)
- Impact: what effect it had
Rules:
- Always in private for redirecting feedback
- As close to the event as possible
- Focus on actions, not personality
- End with a question: "Does that resonate?"
- Ask permission first: "Can I share some feedback?"
- One topic per session
- Never: "you always", "you never", comparison to others
Meeting Notes Format
Every meeting produces exactly four things:
## [Topic] — [Date]
## Summary
One paragraph. A non-attendee should understand what happened.
## Decisions
- [DECIDED] We will use X instead of Y because Z
## Action Items
| Owner | Task | Due |
|-------|------|-----|
| @name | Specific task description | 2026-05-15 |
## Open Questions
- [QUESTION] ... → @owner to decide by Friday
## Risks
- Risk description → mitigationRules:
- Notes sent within 2 hours of meeting end
- Every action has a named owner + ISO date deadline
- No verbatim discussion. Strip to 4 sections.
Cross-Cultural Communication
| Culture | Directness | Formality | Time | Feedback |
|---|---|---|---|---|
| US | Direct | Informal | Strict deadlines | Direct + positive |
| Japan | Indirect | Formal | Punctual | Indirect, private |
| Germany | Direct | Formal | Strict | Direct, factual |
| Brazil | Indirect | Relationship-first | Flexible | Indirect, relationship |
| India | Context-dependent | Formal with seniors | Flexible | Indirect, hierarchical |
Async Communication Protocols
- Default to async: assume response within 24h (not instant)
- No "hi" messages: include context + question in first message
- Status updates: visible in project tool, not via DM
- Meeting notes: posted within 1h. Action items with owners + deadlines.
- Decision log: key decisions documented with rationale + date + decider.
Show full SKILL.md (433 more words)Show less
Meeting Facilitation
- Agenda sent 24h before. Start with purpose + desired outcome.
- Timebox: 15min (standup), 30min (decision), 60min max (workshop)
- Parking lot: off-topic items written down for later
- Round-robin: every voice heard before discussion
Error Handling
| Cause | Fix |
|---|---|
| Recipient didn't respond in 48 hours | Send one follow-up with same subject. First line: "Gentle ping on this — do you need anything from me to move forward?" |
| Email draft is too long (>200 words client, >150 internal) | Cut to essentials. Move details to bullet points. Complex topics → Loom video or shared doc. |
| Tone feels passive-aggressive on re-read | Replace "per my last email" with direct restatement. Remove "as I mentioned." Check for blame language. |
| Cross-cultural miscommunication risk | Check culture table. Japanese: add polite preamble, drop subject pronouns. German: complete information, use Sie. French: context before ask. |
| Emotional reaction while drafting | Save draft. Wait 1 hour minimum. Revise before sending. Remove all loaded language. |
| Vague action items after meeting | Every action item must have: named owner + ISO date deadline + specific verb. No "we should think about." |
| Feedback received negatively | Check SBI structure: Situation (when/where) + Behavior (observable) + Impact (effect). End with "Does that resonate?" Never "you always/never." |
| Escalation email ignored by leadership | Structure: clear facts first, business impact second, specific request third. Keep under 150 words. No blame. Include deadline. |
Anti-Patterns
| Anti-Pattern | Why It Fails | Fix |
|---|---|---|
| No clear ask | Reader doesn't know what to do | State CTA explicitly in first paragraph |
| Reply-all for 1:1 matters | Noise for others, exposes private context | DM or email only relevant person |
| Wall of text | Nobody reads it | Max 2 paragraphs. Bullets for > 3 items. Loom for complex. |
| Sending when emotional | Regret within the hour | Draft, wait 1h, revise, send |
| CC'ing manager unnecessarily | Political escalation | Only CC when they need to know |
| False urgency ("URGENT" / "ASAP") | Boy who cried wolf | Reserve for actual outages. Use specific deadline otherwise. |
| Over-apologizing | Undermines confidence | Apologize once sincerely, pivot to solution |
| Vague follow-ups ("Checking in") | No context, no action | "Following up on X — ETA for Y?" |
Constraints
- Max 150 words internal, 200 for client emails
- No passive-aggressive language
- No assigning blame to a person
- Signature: Name, Title, Company, Phone. No quotes. No ASCII art.
Checklist
- Audience identified (executive, peer, client, direct report)
- Purpose clear: inform, persuade, align, or escalate
- Tone matched to relationship and context
- Key action item or ask stated explicitly near the top
- Proofread for ambiguity and unnecessary jargon
Sources
- Radical Candor — Kim Scott
- Crucial Conversations — Patterson, Grenny, McMillan, Switzler
- Harvard Business Review — Communication guides
- Center for Creative Leadership — SBI model
- Amazon Working Backwards methodology
- Google Project Aristotle — Psychological safety
- Thanks for the Feedback — Stone & Heen
© EliasOulkadi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .pack/skills/communication of EliasOulkadi/shokunin.
Open the folder on GitHubat commit 4c68e5b
Compare with similar skills
Communication next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Communication this skillEliasOulkadi/shokunin | 114 | — | ~2.6k | Automated safety check: Pass | MIT | |
| Management Talkthananon/9arm-skills | 3.2k | — | ~3.2k | Automated safety check: Pass | None | |
| Claap Weekly RecapOthmane-Khadri/YALC-the-GTM-operating-system | 318 | — | ~5.4k | Automated safety check: Pass | MIT | |
| Meeting Notes To Actionssgharlow/claude-code-recipes | 389 | — | ~558 | Automated safety check: Pass | Custom licence | |
| Qv Devops Daily Updatetetherto/qvac | 685 | — | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Kill The StandupVarnan-Tech/opendirectory | 674 | — | ~1.3k | Automated safety check: Notes | MIT |
Similar skills
Claap Weekly Recap
Othmane-Khadri/YALC-the-GTM-operating-system
Turns a week of Claap-recorded sales calls into action items and focus blocks on a Notion Kanban, delivered with a Slack summary.
Meeting Notes To Actions
sgharlow/claude-code-recipes
Turn raw meeting notes into a shareable summary, an action-item table with owners and deadlines, and follow-up email drafts.
Qv Devops Daily Update
tetherto/qvac
Compose a daily standup in the team's Slack format (🔨 Done today / 📅 Planned for tomorrow / 🚧 Blockers / risks), aggregating recent PRs, reviews, and CI from tetherto/qvac.
Kill The Standup
Varnan-Tech/opendirectory
Reads yesterday's Linear issues and GitHub commits for the authenticated user, formats a standup update (done / doing / blockers), and posts it to Slack.
Foundation Meeting Agenda
product-on-purpose/pm-skills
Produces an attendee-facing agenda that sets what will be discussed, who owns each topic, and how time will be spent.
More from EliasOulkadi/shokunin
All 49 skills in this repoCI CD
EliasOulkadi/shokunin
Design CI/CD pipelines for GitHub Actions, GitLab CI, and CircleCI with matrix builds, test sharding, caching, Docker layer caching, OIDC auth, deployment strategies (rolling, blue-green, canary)…
Component Forge
EliasOulkadi/shokunin
Build production-grade components for React, Vue 3, and Svelte 5 with all states (loading, empty, error, success, idle), TypeScript strict, WCAG 2.2 accessibility, server components (RSC), and…
DB Admin
EliasOulkadi/shokunin
PostgreSQL database administration — backup/restore (pgdump, PITR, WAL archiving), health monitoring (connections, bloat, cache hit ratio, dead tuples), connection pooling (PgBouncer), replication…
DB Sculptor
EliasOulkadi/shokunin
Design database schemas with Prisma/Drizzle, PostgreSQL index strategy (B-tree, GIN, GiST, BRIN, Hash), query optimization (EXPLAIN ANALYZE), migration safety (expand/contract, zero-downtime), and…
Docker
EliasOulkadi/shokunin
Optimize Docker images with multi-stage builds, distroless bases, BuildKit cache mounts, multi-arch builds, compose watch, security hardening (non-root, seccomp, capabilities drop), and…
Error Handler
EliasOulkadi/shokunin
Design error handling, structured logging, and observability with OpenTelemetry (traces, metrics, logs), error classification, recovery patterns (retry with jitter, circuit breaker, bulkhead…
Related
Works with
Categories
Questions about Communication
What does Communication do?
Draft professional emails, feedback (SBI/BID), difficult conversations, meeting notes, and escalation templates. Communication is an agent skill from EliasOulkadi/shokunin. Draft professional emails, feedback (SBI/BID), difficult conversations, meeting notes, and escalation templates.
When should I use Communication?
Communication fits situations like: tasks that involve Meeting notes and agendas; tasks that involve Email writing.
How do I install Communication in Claude Code?
Run `npx skills add EliasOulkadi/shokunin --skill communication -a claude-code`. Or copy the skill folder (.pack/skills/communication in EliasOulkadi/shokunin) into .claude/skills/communication in your project. Claude Code loads it when a task matches its description.
How do I install Communication in Codex?
Run `npx skills add EliasOulkadi/shokunin --skill communication -a codex`. Or copy the skill folder (.pack/skills/communication in EliasOulkadi/shokunin) into .agents/skills/communication in your project. Codex loads it when a task matches its description.
Can I use Communication in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add EliasOulkadi/shokunin --skill communication -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/communication, .gemini/skills/communication, .github/skills/communication and .opencode/skills/communication in your project.
What does Communication need to run?
SKILL.md names no scripts, command-line tools or credentials: Communication is instructions for the agent only. Its frontmatter pre-approves these tools: -, read, -, write, -, edit, -, grep, -, glob, -, bash, -, webfetch, -, websearch, -, skills. Compatibility (from SKILL.md): opencode 1.0+.
Does Communication access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Communication safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Communication use?
Communication is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Communication use?
About 2.6k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Communication?
Skills that share tags, products or a category with Communication: Management Talk (thananon/9arm-skills, 3.2k stars), Claap Weekly Recap (Othmane-Khadri/YALC-the-GTM-operating-system, 318 stars), Meeting Notes To Actions (sgharlow/claude-code-recipes, 389 stars) and Qv Devops Daily Update (tetherto/qvac, 685 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Communication?
EliasOulkadi (a GitHub user) maintains it in EliasOulkadi/shokunin, which has 114 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 5, 2026.
Source: EliasOulkadi/shokunin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.