Email Drafting
mgonto/executive-assistant-skills
Draft email replies for Gonto's Gmail accounts (m@gon.to, gonto@hypergrowthpartners.com).
LinkedIn inbox management with scheduled scanning, auto-draft responses following user's communication style, and approval workflows.
Install Linkedin Inbox
$ npx skills add sundial-org/awesome-openclaw-skills --skill linkedin-inbox -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sundial-org/awesome-openclaw-skills linkedin-inbox --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/sundial-org/awesome-openclaw-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/linkedin-inbox .claude/skills/linkedin-inbox && 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 "linkedin-inbox" agent skill from https://github.com/sundial-org/awesome-openclaw-skills/tree/main/skills/linkedin-inbox into .claude/skills/linkedin-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-inbox", 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/sundial-org/awesome-openclaw-skills/tree/main/skills/linkedin-inboxType 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 sundial-org/awesome-openclaw-skills --skill linkedin-inbox -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sundial-org/awesome-openclaw-skills linkedin-inbox --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sundial-org/awesome-openclaw-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/linkedin-inbox .agents/skills/linkedin-inbox && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "linkedin-inbox" agent skill from https://github.com/sundial-org/awesome-openclaw-skills/tree/main/skills/linkedin-inbox into .agents/skills/linkedin-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-inbox", 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 sundial-org/awesome-openclaw-skills --skill linkedin-inbox -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sundial-org/awesome-openclaw-skills linkedin-inbox --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sundial-org/awesome-openclaw-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/linkedin-inbox .cursor/skills/linkedin-inbox && 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 "linkedin-inbox" agent skill from https://github.com/sundial-org/awesome-openclaw-skills/tree/main/skills/linkedin-inbox into .cursor/skills/linkedin-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-inbox", 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/sundial-org/awesome-openclaw-skills.git --path skills/linkedin-inbox--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 sundial-org/awesome-openclaw-skills --skill linkedin-inbox -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sundial-org/awesome-openclaw-skills linkedin-inbox --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sundial-org/awesome-openclaw-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/linkedin-inbox .gemini/skills/linkedin-inbox && 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 "linkedin-inbox" agent skill from https://github.com/sundial-org/awesome-openclaw-skills/tree/main/skills/linkedin-inbox into .gemini/skills/linkedin-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-inbox", 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 sundial-org/awesome-openclaw-skills linkedin-inboxInstalls 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 sundial-org/awesome-openclaw-skills --skill linkedin-inbox -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sundial-org/awesome-openclaw-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/linkedin-inbox .github/skills/linkedin-inbox && 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 "linkedin-inbox" agent skill from https://github.com/sundial-org/awesome-openclaw-skills/tree/main/skills/linkedin-inbox into .github/skills/linkedin-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-inbox", 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 sundial-org/awesome-openclaw-skills --skill linkedin-inbox -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sundial-org/awesome-openclaw-skills linkedin-inbox --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sundial-org/awesome-openclaw-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/linkedin-inbox .opencode/skills/linkedin-inbox && 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 "linkedin-inbox" agent skill from https://github.com/sundial-org/awesome-openclaw-skills/tree/main/skills/linkedin-inbox into .opencode/skills/linkedin-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-inbox", 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
linkedin-inbox- GitHub stars
- 663
- Token cost
- ~1.5k tokens
- SKILL.md length
- 382 words
- Files
- 6 (incl. scripts, references)
- Skills in repo
- 383
- Repo updated
- First seen
- Licence
- None found
At a glance
LinkedIn inbox management with scheduled scanning, auto-draft responses following user's communication style, and approval workflows.
- Works in 3 steps: One-time Setup → Configure User Style → Start Monitoring
- Monitoring LinkedIn messages
- SKILL.md covers Requirements, Quick Start, Core Workflow and Communication Style Matching, plus 6 more sections
- Runs Shell scripts from its folder; calls brew; reaches linkedin.com
What it does
Linkedin Inbox is an agent skill from sundial-org/awesome-openclaw-skills. LinkedIn inbox management with scheduled scanning, auto-draft responses following user's communication style, and approval workflows. Use when monitoring LinkedIn messages, drafting replies, managing inbox during off-hours, or setting up morning ping summaries of LinkedIn activity.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `config-example.json`, `references/style-extraction.md` and `scripts/open_conversation.sh`).
It sits in Productivity & Automation, covering Email management and Email writing. It works with LinkedIn. The repository describes itself as: Top OpenClaw skills, with the most popular and useful ones.
When your agent uses it
- Monitoring LinkedIn messages
- Drafting replies
- Managing inbox during off-hours
- Setting up morning ping summaries of LinkedIn activity
Example prompts
- “/linkedin-inbox”
Requirements
- A Bash shell
Workflow steps
3 steps, taken from the step headings in SKILL.md.
- One-time Setup
- Configure User Style
- Start Monitoring
What it can do on your machine
Read from SKILL.md and the folder at commit b80cde2. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
brew
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
linkedin.com
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.
Context cost
Linkedin Inbox loads about 1.5k tokens when it runs, and up to ~2.4k if it reads all its reference files. Until then it costs about 74 tokens; SKILL.md has 382 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); the scripts in this folder are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 382 words (~1,498 tokens).
“Automated LinkedIn inbox monitoring with human-in-the-loop approval for responses. Uses Peekaboo for UI automation (no API rate limits, works with any LinkedIn account).”
- name
- linkedin-inbox
Files
SKILL.md and 5 other files (scripts, references) in skills/linkedin-inbox of sundial-org/awesome-openclaw-skills.
- SKILL.md
- config-example.json
- references/style-extraction.md
- scripts/open_conversation.sh
- scripts/scan_inbox.sh
- scripts/send_message.sh
Open the folder on GitHubat commit b80cde2
Compare with similar skills
Linkedin Inbox 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 |
|---|---|---|---|---|---|---|
| Linkedin Inbox this skillsundial-org/awesome-openclaw-skills | 663 | — | ~1.5k | Automated safety check: Pass | None | |
| Email Draftingmgonto/executive-assistant-skills | 118 | — | ~2.8k | Automated safety check: Pass | None | |
| Li InboxJakeschincariol/linkedin-agent-skill | 1.7k | — | ~723 | Automated safety check: Pass | MIT | |
| Executive AssistantTheCraigHewitt/hermes-chief-of-staff | 104 | — | ~1k | Automated safety check: Pass | MIT | |
| Email Response Simulationextruct-ai/gtm-skills | 109 | — | ~2.8k | Automated safety check: Pass | None | |
| Emailheypinchy/pinchy | 182 | — | ~2.4k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Li Inbox
Jakeschincariol/linkedin-agent-skill
Triage the LinkedIn inbox - sort connection requests and DMs into leads, recruiters, peers and spam, and draft the replies worth sending.
Executive Assistant
TheCraigHewitt/hermes-chief-of-staff
Triage inbox, draft emails, manage calendar, schedule meetings, handle routine communications.
Email Response Simulation
extruct-ai/gtm-skills
Deep persona simulation and skeptical buyer review for cold emails.
Email
heypinchy/pinchy
Read, search, and draft email in the connected mailbox (Gmail or Microsoft 365).
Curviate Inbox
davila7/claude-code-templates
Read and send LinkedIn messages with the Curviate CLI. An agent skill from davila7/claude-code-templates.
More from sundial-org/awesome-openclaw-skills
All 383 skills in this repoUI UX Pro Max
sundial-org/awesome-openclaw-skills
UI/UX design intelligence and implementation guidance for building polished interfaces.
Web Deploy GitHub
sundial-org/awesome-openclaw-skills
Create and deploy single-page static websites to GitHub Pages with autonomous workflow.
Clawd Modifier
sundial-org/awesome-openclaw-skills
Modify Clawd, the Claude Code mascot. An agent skill from sundial-org/awesome-openclaw-skills.
Figma
sundial-org/awesome-openclaw-skills
Professional Figma design analysis and asset export. An agent skill from sundial-org/awesome-openclaw-skills.
Habit Flow
sundial-org/awesome-openclaw-skills
AI-powered atomic habit tracker with natural language logging, streak tracking, smart reminders, and coaching.
Edge Tts
sundial-org/awesome-openclaw-skills
Text-to-speech conversion using node-edge-tts npm package for generating audio from text.
Related
Works with
Categories
Questions about Linkedin Inbox
What does Linkedin Inbox do?
LinkedIn inbox management with scheduled scanning, auto-draft responses following user's communication style, and approval workflows. Linkedin Inbox is an agent skill from sundial-org/awesome-openclaw-skills. LinkedIn inbox management with scheduled scanning, auto-draft responses following user's communication style, and approval workflows.
When should I use Linkedin Inbox?
Linkedin Inbox fits situations like: monitoring LinkedIn messages; drafting replies; managing inbox during off-hours; setting up morning ping summaries of LinkedIn activity.
How do I install Linkedin Inbox in Claude Code?
Run `npx skills add sundial-org/awesome-openclaw-skills --skill linkedin-inbox -a claude-code`. Or copy the skill folder (skills/linkedin-inbox in sundial-org/awesome-openclaw-skills) into .claude/skills/linkedin-inbox in your project. Claude Code loads it when a task matches its description.
How do I install Linkedin Inbox in Codex?
Run `npx skills add sundial-org/awesome-openclaw-skills --skill linkedin-inbox -a codex`. Or copy the skill folder (skills/linkedin-inbox in sundial-org/awesome-openclaw-skills) into .agents/skills/linkedin-inbox in your project. Codex loads it when a task matches its description.
Can I use Linkedin Inbox 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 sundial-org/awesome-openclaw-skills --skill linkedin-inbox -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linkedin-inbox, .gemini/skills/linkedin-inbox, .github/skills/linkedin-inbox and .opencode/skills/linkedin-inbox in your project.
What does Linkedin Inbox need to run?
Going by SKILL.md and its folder, Linkedin Inbox needs a shell for the scripts in its folder and the command-line tools its instructions call (brew). Our summary lists: A Bash shell.
Does Linkedin Inbox access the network?
SKILL.md names 1 domain. In commands or code: linkedin.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Linkedin Inbox 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Linkedin Inbox use?
No licence was found for Linkedin Inbox or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Linkedin Inbox use?
About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 910 tokens, read only when the agent opens those files.
What are the alternatives to Linkedin Inbox?
Skills that share tags, products or a category with Linkedin Inbox: Email Drafting (mgonto/executive-assistant-skills, 118 stars), Li Inbox (Jakeschincariol/linkedin-agent-skill, 1.7k stars), Executive Assistant (TheCraigHewitt/hermes-chief-of-staff, 104 stars) and Email Response Simulation (extruct-ai/gtm-skills, 109 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Linkedin Inbox?
sundial-org (a GitHub organization) maintains it in sundial-org/awesome-openclaw-skills, which has 663 GitHub stars. The repository holds 383 skills in this directory. The repository was last updated on March 7, 2026.
Source: sundial-org/awesome-openclaw-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.