Book Publisher
dmccreary/ibook-skills
Publishes and promotes a finished intelligent textbook - GitHub README with badges and site statistics, LinkedIn announcement posts, LinkedIn carousel document posts (PPTX/PDF slideshows), and…
Prepare or publish eunomia.dev content for LinkedIn posts, articles, carousels, and professional updates.
Install Linkedin Publisher
$ npx skills add eunomia-bpf/eunomia.dev --skill linkedin-publisher -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install eunomia-bpf/eunomia.dev linkedin-publisher --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/eunomia-bpf/eunomia.dev.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/linkedin-publisher .claude/skills/linkedin-publisher && 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-publisher" agent skill from https://github.com/eunomia-bpf/eunomia.dev/tree/main/.agents/skills/linkedin-publisher into .claude/skills/linkedin-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-publisher", 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/eunomia-bpf/eunomia.dev/tree/main/.agents/skills/linkedin-publisherType 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 eunomia-bpf/eunomia.dev --skill linkedin-publisher -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install eunomia-bpf/eunomia.dev linkedin-publisher --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eunomia-bpf/eunomia.dev.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/linkedin-publisher .agents/skills/linkedin-publisher && 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-publisher" agent skill from https://github.com/eunomia-bpf/eunomia.dev/tree/main/.agents/skills/linkedin-publisher into .agents/skills/linkedin-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-publisher", 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 eunomia-bpf/eunomia.dev --skill linkedin-publisher -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install eunomia-bpf/eunomia.dev linkedin-publisher --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eunomia-bpf/eunomia.dev.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/linkedin-publisher .cursor/skills/linkedin-publisher && 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-publisher" agent skill from https://github.com/eunomia-bpf/eunomia.dev/tree/main/.agents/skills/linkedin-publisher into .cursor/skills/linkedin-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-publisher", 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/eunomia-bpf/eunomia.dev.git --path .agents/skills/linkedin-publisher--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 eunomia-bpf/eunomia.dev --skill linkedin-publisher -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install eunomia-bpf/eunomia.dev linkedin-publisher --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eunomia-bpf/eunomia.dev.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/linkedin-publisher .gemini/skills/linkedin-publisher && 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-publisher" agent skill from https://github.com/eunomia-bpf/eunomia.dev/tree/main/.agents/skills/linkedin-publisher into .gemini/skills/linkedin-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-publisher", 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 eunomia-bpf/eunomia.dev linkedin-publisherInstalls 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 eunomia-bpf/eunomia.dev --skill linkedin-publisher -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/eunomia-bpf/eunomia.dev.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/linkedin-publisher .github/skills/linkedin-publisher && 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-publisher" agent skill from https://github.com/eunomia-bpf/eunomia.dev/tree/main/.agents/skills/linkedin-publisher into .github/skills/linkedin-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-publisher", 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 eunomia-bpf/eunomia.dev --skill linkedin-publisher -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install eunomia-bpf/eunomia.dev linkedin-publisher --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eunomia-bpf/eunomia.dev.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/linkedin-publisher .opencode/skills/linkedin-publisher && 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-publisher" agent skill from https://github.com/eunomia-bpf/eunomia.dev/tree/main/.agents/skills/linkedin-publisher into .opencode/skills/linkedin-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linkedin-publisher", 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-publisher- GitHub stars
- 236
- Token cost
- ~1.1k tokens
- SKILL.md length
- 485 words
- Files
- 3 (incl. references)
- Skills in repo
- 18
- Repo updated
- First seen
- Licence
- MIT
At a glance
Prepare or publish eunomia.dev content for LinkedIn posts, articles, carousels, and professional updates.
- Works in 5 steps: For a long-form share, read the source… → Choose the format → For a LinkedIn article that syndicates… → …
- Record LinkedIn content for blog
- SKILL.md covers Inputs, Platform Entry Points, References and Browser-Only Platform Boundary, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Linkedin Publisher is an agent skill from eunomia-bpf/eunomia.dev. Prepare or publish eunomia.dev content for LinkedIn posts, articles, carousels, and professional updates. Use when asked to draft, adapt, paste, publish, QA, or record LinkedIn content for blog, tutorial, project, paper, release, consulting, research, or GitHub updates. Covers professional positioning, reader targeting, publication authorization, browser QA, comment/DM follow-up, and media ledger updates.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/platform-preferences.md`).
It sits in Writing & Content, covering Social media posts and Positioning and messaging. It works with LinkedIn and GitHub. The repository describes itself as: https://github.com/eunomia-bpf homepage, documents and blogs. The licence is MIT.
When your agent uses it
- Record LinkedIn content for blog
- Tasks that involve Social media posts
- Tasks that involve Positioning and messaging
Example prompts
- “/linkedin-publisher”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- For a long-form share, read the source and identify only its core problem,
- Choose the format
- For a LinkedIn article that syndicates an existing long-form source, preserve
- Do not add a separate interpretation, summary, or professional story arc to
- Use a project, GitHub, or paper link instead only when that is the actual
What it can do on your machine
Read from SKILL.md and the folder at commit 7779f61. 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
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
Links to these hosts (documentation or services it may open):
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 Publisher loads about 1.1k tokens when it runs, and up to ~3.2k if it reads all its reference files. Until then it costs about 107 tokens; SKILL.md has 485 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 eunomia-bpf/eunomia.dev at commit 7779f61, republished under its MIT licence (© eunomia-bpf). 485 words, ~1,065 tokens.
Download SKILL.mdSave it as
.claude/skills/linkedin-publisher/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- linkedin-publisher
- description
- Prepare or publish eunomia.dev content for LinkedIn posts, articles, carousels, and professional updates. Use when asked to draft, adapt, paste, publish, QA, or record LinkedIn content for blog, tutorial, project, paper, release, consulting, research, or GitHub updates. Covers professional positioning, reader targeting, publication authorization, browser QA, comment/DM follow-up, and media ledger updates.
LinkedIn Publisher
Prepare professional LinkedIn posts that build technical credibility. Publication authorization follows CLAUDE.md's Precedence Rule and Publishing section.
Inputs
- Source Markdown path, project, repo URL, paper, or topic.
- Intended audience, format, and posting account when specified.
- Optional media, canonical link, GitHub link, hashtags, or follow-up plan.
If the source path is missing, inspect .github/publisher/posts_queue.txt,
.github/publisher/media/not-published.md, recent docs/blog/posts/, and
relevant GitHub repos before asking the user.
Platform Entry Points
- Feed/composer: https://www.linkedin.com/feed/
- Articles/newsletters: https://www.linkedin.com/pulse/new/
- Notifications: https://www.linkedin.com/notifications/
- Messaging: https://www.linkedin.com/messaging/
Use a browser surface with the logged-in session when UI work is required. Never bypass authentication with search results or alternate sources.
References
Load references/platform-preferences.md when choosing LinkedIn-native framing,
professional positioning, first-lines hook, media/link treatment, promotion
balance, or follow-up. Do not load broad strategy drafts for routine posting
unless the user asks for campaign or content-platform planning.
Browser-Only Platform Boundary
Do not directly access LinkedIn APIs, internal endpoints, or background HTTP interfaces. All drafting, QA, screenshots, and ledger evidence must come from normal browser interactions.
Draft Preparation
- For a long-form share, read the source and identify only its core problem, tension, or result and the published link.
- Choose the format:
- feed post for the default long-form share case: the published link plus one or two hook sentences
- document/carousel only when the user explicitly asks for one
- article only when the user explicitly asks for long-form on LinkedIn
- For a LinkedIn article that syndicates an existing long-form source, preserve the source title exactly and keep the body substantively unchanged. Only make mechanical rendering fixes and set platform metadata. A rewrite requires an explicit request for that article.
- Do not add a separate interpretation, summary, or professional story arc to a long-form share. Use one or two sentences for the hook, then the link.
- Use a project, GitHub, or paper link instead only when that is the actual long-form or primary artifact being shared.
Show full SKILL.md (171 more words)Show less
Draft Archive
Before opening the LinkedIn composer, write or update the LinkedIn draft under
draft/media/YYYY-MM-DD/<source-slug>/linkedin.md using the local date. Include
the full paste-ready post or exact long-form source reference,
first-visible-lines check, primary
link, optional first-comment links, media/alt text, visibility target when
known, and QA state.
Browser QA
- first visible lines make the value clear before "see more"
- link card, media, or document preview renders correctly
- audience/visibility setting is intentional
- mentions and hashtags are relevant and minimal
- no confidential customer, partner, or roadmap information appears
- the final action matches the task: published when authorized, untouched for a draft-only task
Follow-Up
After a confirmed publish, capture the URL and monitor comments, reactions, and messages only when the user asks or follow-up was part of the task. Draft substantive replies to technical questions and move implementation work to GitHub when appropriate. Do not send connection requests, DMs, likes, reposts, or comments without explicit instruction.
Ledger Update
After confirmed publish, update .github/publisher/media/published.md with
source path, LinkedIn URL, date, format, media, link target, and follow-up notes.
© eunomia-bpf, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in .agents/skills/linkedin-publisher of eunomia-bpf/eunomia.dev.
- SKILL.md
- agents/openai.yaml
- references/platform-preferences.md
Open the folder on GitHubat commit 7779f61
Compare with similar skills
Linkedin Publisher 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 Publisher this skilleunomia-bpf/eunomia.dev | 236 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Book Publisherdmccreary/ibook-skills | 105 | — | ~1.3k | Automated safety check: Pass | CC-BY-NC-4.0 | |
| Product Update LoggerVarnan-Tech/opendirectory | 674 | — | ~3.9k | Automated safety check: Pass | MIT | |
| Producthunt Launch KitVarnan-Tech/opendirectory | 674 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Linkedin Post GeneratorVarnan-Tech/opendirectory | 674 | — | ~2.6k | Automated safety check: Notes | MIT | |
| Social Contentshawnpang/startup-founder-skills | 343 | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Product Update Logger
Varnan-Tech/opendirectory
Tell the skill what your product shipped. An agent skill from Varnan-Tech/opendirectory.
Producthunt Launch Kit
Varnan-Tech/opendirectory
A skill your agent uses when the user asks to prepare a Product Hunt launch or generate Product Hunt listing assets.
Linkedin Post Generator
Varnan-Tech/opendirectory
Converts any content, blog post URL, pasted article, GitHub PR description, or a description of something built, into a formatted LinkedIn post with proper hook, story arc, and formatting.
Social Content
shawnpang/startup-founder-skills
When the user needs to build a LinkedIn authority system, create social content strategy, define content pillars, write posts, or establish thought leadership positioning.
Linkedin Announcement Generator
dmccreary/ibook-skills
Generates a LinkedIn post announcing an intelligent textbook milestone by pulling book metrics, chapter count, and key statistics.
More from eunomia-bpf/eunomia.dev
All 18 skills in this repoEunomia Community Radar
eunomia-bpf/eunomia.dev
Monitor approved eBPF, Linux, observability, and AI-infrastructure communities through watchlist-opted-in read-only Slack archives plus ordinary visible browser UI, turn the strongest daily…
Eunomia Research Report
eunomia-bpf/eunomia.dev
Research, write, validate, and publish source-grounded Eunomia Daily Reports for technical readers.
Juejin Publisher
eunomia-bpf/eunomia.dev
Prepare or publish eunomia.dev Markdown articles on Juejin. An agent skill from eunomia-bpf/eunomia.dev.
Content Launch Planner
eunomia-bpf/eunomia.dev
Plan contribution-first cross-platform launches for eunomia.dev content, GitHub projects, papers, tutorials, demos, and public updates.
Devto Publisher
eunomia-bpf/eunomia.dev
Prepare or publish eunomia.dev Markdown articles on DEV Community through faithful long-form syndication.
Eunomia Social Radar
eunomia-bpf/eunomia.dev
Monitor the continuing public performance and conversation around Eunomia blogs, reports, projects, and platform posts.
Related
Categories
Questions about Linkedin Publisher
What does Linkedin Publisher do?
Prepare or publish eunomia.dev content for LinkedIn posts, articles, carousels, and professional updates. dev.dev content for LinkedIn posts, articles, carousels, and professional updates.
When should I use Linkedin Publisher?
Linkedin Publisher fits situations like: record LinkedIn content for blog; tasks that involve Social media posts; tasks that involve Positioning and messaging.
How do I install Linkedin Publisher in Claude Code?
Run `npx skills add eunomia-bpf/eunomia.dev --skill linkedin-publisher -a claude-code`. Or copy the skill folder (.agents/skills/linkedin-publisher in eunomia-bpf/eunomia.dev) into .claude/skills/linkedin-publisher in your project. Claude Code loads it when a task matches its description.
How do I install Linkedin Publisher in Codex?
Run `npx skills add eunomia-bpf/eunomia.dev --skill linkedin-publisher -a codex`. Or copy the skill folder (.agents/skills/linkedin-publisher in eunomia-bpf/eunomia.dev) into .agents/skills/linkedin-publisher in your project. Codex loads it when a task matches its description.
Can I use Linkedin Publisher 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 eunomia-bpf/eunomia.dev --skill linkedin-publisher -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-publisher, .gemini/skills/linkedin-publisher, .github/skills/linkedin-publisher and .opencode/skills/linkedin-publisher in your project.
What does Linkedin Publisher need to run?
SKILL.md names no scripts, command-line tools or credentials: Linkedin Publisher is instructions for the agent only.
Does Linkedin Publisher access the network?
SKILL.md names 1 domain. As links in the text: linkedin.com. This is read from the text; nothing was executed.
Is Linkedin Publisher 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 Linkedin Publisher use?
Linkedin Publisher is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Linkedin Publisher use?
About 1.1k tokens (SKILL.md is roughly 4.3k 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 2.1k tokens, read only when the agent opens those files.
What are the alternatives to Linkedin Publisher?
Skills that share tags, products or a category with Linkedin Publisher: Book Publisher (dmccreary/ibook-skills, 105 stars), Product Update Logger (Varnan-Tech/opendirectory, 674 stars), Producthunt Launch Kit (Varnan-Tech/opendirectory, 674 stars) and Linkedin Post Generator (Varnan-Tech/opendirectory, 674 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Linkedin Publisher?
eunomia-bpf (a GitHub organization) maintains it in eunomia-bpf/eunomia.dev, which has 236 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 11, 2026.
Source: eunomia-bpf/eunomia.dev on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.