Markit
shift-labs-ai/markit
Convert files and URLs to Markdown. An agent skill from shift-labs-ai/markit.
Prepare or publish eunomia.dev Markdown articles on DEV Community through faithful long-form syndication.
Install Devto Publisher
$ npx skills add eunomia-bpf/eunomia.dev --skill devto-publisher -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install eunomia-bpf/eunomia.dev devto-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/devto-publisher .claude/skills/devto-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 "devto-publisher" agent skill from https://github.com/eunomia-bpf/eunomia.dev/tree/main/.agents/skills/devto-publisher into .claude/skills/devto-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devto-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/devto-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 devto-publisher -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install eunomia-bpf/eunomia.dev devto-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/devto-publisher .agents/skills/devto-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 "devto-publisher" agent skill from https://github.com/eunomia-bpf/eunomia.dev/tree/main/.agents/skills/devto-publisher into .agents/skills/devto-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devto-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 devto-publisher -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install eunomia-bpf/eunomia.dev devto-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/devto-publisher .cursor/skills/devto-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 "devto-publisher" agent skill from https://github.com/eunomia-bpf/eunomia.dev/tree/main/.agents/skills/devto-publisher into .cursor/skills/devto-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devto-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/devto-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 devto-publisher -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install eunomia-bpf/eunomia.dev devto-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/devto-publisher .gemini/skills/devto-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 "devto-publisher" agent skill from https://github.com/eunomia-bpf/eunomia.dev/tree/main/.agents/skills/devto-publisher into .gemini/skills/devto-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devto-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 devto-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 devto-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/devto-publisher .github/skills/devto-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 "devto-publisher" agent skill from https://github.com/eunomia-bpf/eunomia.dev/tree/main/.agents/skills/devto-publisher into .github/skills/devto-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devto-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 devto-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 devto-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/devto-publisher .opencode/skills/devto-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 "devto-publisher" agent skill from https://github.com/eunomia-bpf/eunomia.dev/tree/main/.agents/skills/devto-publisher into .opencode/skills/devto-publisher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devto-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
devto-publisher- GitHub stars
- 236
- Token cost
- ~1.7k tokens
- SKILL.md length
- 899 words
- Files
- 3 (incl. references)
- Skills in repo
- 18
- Repo updated
- First seen
- Licence
- MIT
At a glance
Prepare or publish eunomia.dev Markdown articles on DEV Community through faithful long-form syndication.
- Works in 7 steps: Read the canonical English source and… → Convert frontmatter to DEV/Jekyll-style… → Use H2 as the highest body heading… → …
- Record DEV.to posts for blog
- SKILL.md covers Inputs, Platform Entry Points, References and API-First Platform Boundary, plus 5 more sections
- Reaches dev.to and eunomia.dev; needs DEV_TO_API_KEY
What it does
Devto Publisher is an agent skill from eunomia-bpf/eunomia.dev. Prepare or publish eunomia.dev Markdown articles on DEV Community through faithful long-form syndication. Use when asked to paste, import, publish, QA, or record DEV.to posts for blog, tutorial, project, paper, release, or GitHub content. Preserves the English source title and body apart from mechanical Markdown/rendering fixes, with optional canonicalurl settings, publication authorization, browser QA, follow-up, and media ledger updates.
Its SKILL.md is about 1.7k 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 Documents & Office. It works with 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 DEV.to posts for blog
Example prompts
- “/devto-publisher”
Requirements
- A credential in DEV_TO_API_KEY
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Read the canonical English source and record the source URL, GitHub links,
- Convert frontmatter to DEV/Jekyll-style fields when useful. Include
- Use H2 as the highest body heading because the post title is the H1.
- Preserve the source title exactly and keep the body substantively unchanged.
- Preserve GitHub/project/paper links already in the source. Add body text or
- If the source is not suitable for DEV, skip it or fix the source first.
- Strip local YAML front matter and internal HTML comments from the API
What it can do on your machine
Read from SKILL.md and the folder at commit 4cc0b4f. 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
Hosts in commands or code, which the agent is likely to contact:
dev.toeunomia.dev
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
DEV_TO_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Devto Publisher loads about 1.7k tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 115 tokens; SKILL.md has 899 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:44
the local `.env` or an approved secret-backed publisher. Never print, record,
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 4cc0b4f, republished under its MIT licence (© eunomia-bpf). 899 words, ~1,736 tokens.
Download SKILL.mdSave it as
.claude/skills/devto-publisher/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- devto-publisher
- description
- Prepare or publish eunomia.dev Markdown articles on DEV Community through faithful long-form syndication. Use when asked to paste, import, publish, QA, or record DEV.to posts for blog, tutorial, project, paper, release, or GitHub content. Preserves the English source title and body apart from mechanical Markdown/rendering fixes, with optional canonical_url settings, publication authorization, browser QA, follow-up, and media ledger updates.
DEV.to Publisher
Prepare and publish DEV Community articles from canonical eunomia.dev content through the DEV API. Publication authorization follows CLAUDE.md's Precedence Rule and Publishing section.
Inputs
- Source Markdown path or source/canonical eunomia.dev URL.
- Source title, tags, series metadata, cover image, or optional canonical URL.
- Optional GitHub link, paper link, or follow-up plan.
If the source path is missing, inspect .github/publisher/posts_queue.txt,
.github/publisher/media/not-published.md, and recent docs/blog/posts/.
Platform Entry Points
- Account preflight:
GET https://dev.to/api/users/me - Duplicate check:
GET https://dev.to/api/articles/me/all - Create article:
POST https://dev.to/api/articles - New post: https://dev.to/new
- Dashboard: https://dev.to/dashboard
- Editor guide: https://dev.to/p/editor_guide
- Notifications: https://dev.to/notifications
Use a browser surface with the logged-in session when UI work is required.
References
Load references/platform-preferences.md when choosing canonical syndication
settings, light DEV metadata/rendering adaptations, frontmatter, tags, series
shape, browser QA, promotion balance, or follow-up. Do not load broad strategy
drafts for routine publishing unless the user asks for campaign or
content-platform planning.
API-First Platform Boundary
Publish through the documented DEV API by default, using DEV_TO_API_KEY from
the local .env or an approved secret-backed publisher. Never print, record,
or commit the token. Verify the authenticated account, query the author's full
article list for an exact-title duplicate, then create the article with
POST /api/articles. Do not use hidden or internal DEV endpoints.
The visible web editor is a repair surface for behavior the API cannot correct, not the default submission path. Every API-created article still requires a normal visible-browser check of the complete public page.
Draft Preparation
- Read the canonical English source and record the source URL, GitHub links, and paper links when known.
- Convert frontmatter to DEV/Jekyll-style fields when useful. Include
canonical_urlwhen known and convenient, but do not add a visible body source link just to satisfy a checklist. - Use H2 as the highest body heading because the post title is the H1.
- Preserve the source title exactly and keep the body substantively unchanged. Only fix frontmatter, heading levels, code fences, image URLs/uploads, tables, formulas, embeds, links, tags, and DEV-specific rendering.
- Preserve GitHub/project/paper links already in the source. Add body text or links only after the same source change or an explicit user request.
- If the source is not suitable for DEV, skip it or fix the source first. Rewrite, translate, shorten, expand, reorder, or split it only when the user explicitly asks for that specific publication.
- Strip local YAML front matter and internal HTML comments from the API
body_markdown. Send the exact title separately, keep H2 as the highest body heading, include up to four accepted DEV tags, and setcanonical_urlonly when it is useful and available; it is optional.
Draft Archive
Before sending the DEV API request, write or update the DEV draft record under
draft/media/YYYY-MM-DD/<source-slug>/devto.md using the local date. Include
the exact title, description, tags, optional canonical_url, source body path
or paste-ready body, GitHub/paper links, series/cover choices, and QA state.
For long-form posts, finish this API-ready Markdown artifact locally before
publishing. Use the web editor only for supported metadata changes or repairs
that remain necessary after creation.
Show full SKILL.md (401 more words)Show less
Browser QA
- title matches the source exactly; description, tags, cover, and optional canonical URL accurately reflect the unchanged source
- the DEV body has not drifted from the canonical article except for necessary Markdown/frontmatter/rendering edits
- headings start at H2 and code fences have language labels
- images render and have descriptions where supported
- links and embeds resolve
- preview is readable and self-contained
- the API request has not been sent
Before confirmed publishing, inspect the complete local upload artifact. After confirmed publishing, open the public DEV URL and inspect the rendered post from top to bottom before updating the ledger. Verify canonical field when configured, source/project notes when present, title, tags, image loading, H2/H3 hierarchy, tables, code fences, link targets, embeds, and narrow rendering when practical. If the public page reveals duplicated source notes, wrong tags, broken images, heading artifacts, or mangled code blocks, edit the published post through the web UI and repeat the public-page check.
DEV tags must be verified from the selected-tag chips after editing. Do not
assume a desired tag exists or was accepted just because it was typed into the
tag box; if the editor rejects a tag, choose a supported nearby tag and record
the fallback. When canonical_url is set, DEV already displays its own
"Originally published" notice, so avoid adding a duplicate manual source note
at the end unless the user explicitly asks for one.
For images, verify the exact final URL that will appear in the DEV Markdown.
Do not assume a relative imgs/... path becomes
https://eunomia.dev/<article>/imgs/...; that guessed path can 404 even when
the canonical article renders locally. Check each external image URL with a
browser or HEAD request before saving. If the eunomia.dev URL is not directly
200, use the actual rendered image URL, a stable GitHub raw URL for public repo
images, or upload the image through the DEV web editor, then re-check the
public page after lazy loading.
Follow-Up
After confirmed publish and public-page QA, capture the DEV URL. Monitor comments and notifications only when the user asks or follow-up was part of the task. Draft answers with reproducible details and move long-lived issues to GitHub.
Ledger Update
After confirmed publish, update .github/publisher/media/published.md with
source path, canonical URL, DEV URL, date, tags/series, media, and follow-up
notes.
Before final completion, add any DEV-specific issue encountered during this
session to this skill or references/platform-preferences.md, then record the
public-page QA result in the draft record.
© 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/devto-publisher of eunomia-bpf/eunomia.dev.
- SKILL.md
- agents/openai.yaml
- references/platform-preferences.md
Open the folder on GitHubat commit 4cc0b4f
Compare with similar skills
Devto 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 |
|---|---|---|---|---|---|---|
| Devto Publisher this skilleunomia-bpf/eunomia.dev | 236 | — | ~1.7k | Automated safety check: Notes | MIT | |
| Markitshift-labs-ai/markit | 1.3k | — | ~299 | Automated safety check: Pass | MIT | |
| Asu Resume Audit SkillClaycui828/ASu-resume-skills | 374 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Best SkillsLinklyAI/best-skills | 635 | — | ~575 | Automated safety check: Pass | CC-BY-4.0 | |
| Deepxiv Baseline TableDeepXiv/deepxiv_sdk | 804 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Editor Updateqwrtln/Homm3BG-mission-book | 110 | — | ~1.2k | Automated safety check: Pass | Custom licence |
Similar skills
Asu Resume Audit Skill
Claycui828/ASu-resume-skills
以证据为中心的简历真实性审计与报告生成技能。用户要求核验简历、打假履历、调查候选人经历、分析 GitHub/开源贡献、识别 contributor 到 maintainer/core author 的角色膨胀、核验中外合作办学或学校 title、检查业务指标、梳理公开争议，或者把调查结果制作成 HTML/PDF…
Best Skills
LinklyAI/best-skills
Daily cross-platform rankings of AI agent skills (skills.sh, ClawHub, Tencent SkillHub, GitHub, X/HN/Bluesky).
Deepxiv Baseline Table
DeepXiv/deepxiv_sdk
Build a markdown baseline table for a research topic using deepxiv search, brief, head, and experiment-section reads, extracting paper title, URL, open-source status, datasets, benchmark scores, and…
Editor Update
qwrtln/Homm3BG-mission-book
Build a feature or fix a bug in the browser scenario builder under web/ — app, shared parsers, compile/PDF preview, GitHub pull-request flow, picker, search, routes — with tests and every…
Release Latex Fork
zly2006/zhihu-plus-plus
Release the LaTeX fork used by Zhihu++. An agent skill from zly2006/zhihu-plus-plus.
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.
Eunomia Social Radar
eunomia-bpf/eunomia.dev
Monitor the continuing public performance and conversation around Eunomia blogs, reports, projects, and platform posts.
Hackernews Publisher
eunomia-bpf/eunomia.dev
Prepare or publish Hacker News submissions and follow-up drafts for eunomia.dev content, GitHub projects, papers, demos, and Show HN style launches.
Related
Works with
Categories
Questions about Devto Publisher
What does Devto Publisher do?
Prepare or publish eunomia.dev Markdown articles on DEV Community through faithful long-form syndication. dev.dev Markdown articles on DEV Community through faithful long-form syndication.
When should I use Devto Publisher?
Devto Publisher fits situations like: record DEV.to posts for blog.
How do I install Devto Publisher in Claude Code?
Run `npx skills add eunomia-bpf/eunomia.dev --skill devto-publisher -a claude-code`. Or copy the skill folder (.agents/skills/devto-publisher in eunomia-bpf/eunomia.dev) into .claude/skills/devto-publisher in your project. Claude Code loads it when a task matches its description.
How do I install Devto Publisher in Codex?
Run `npx skills add eunomia-bpf/eunomia.dev --skill devto-publisher -a codex`. Or copy the skill folder (.agents/skills/devto-publisher in eunomia-bpf/eunomia.dev) into .agents/skills/devto-publisher in your project. Codex loads it when a task matches its description.
Can I use Devto 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 devto-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/devto-publisher, .gemini/skills/devto-publisher, .github/skills/devto-publisher and .opencode/skills/devto-publisher in your project.
What does Devto Publisher need to run?
Going by SKILL.md and its folder, Devto Publisher needs credentials named DEV_TO_API_KEY. Our summary lists: A credential in DEV_TO_API_KEY.
Does Devto Publisher access the network?
SKILL.md names 2 domains. In commands or code: dev.to and eunomia.dev; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Devto Publisher safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Devto Publisher use?
Devto 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 Devto Publisher use?
About 1.7k tokens (SKILL.md is roughly 6.9k 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 1.4k tokens, read only when the agent opens those files.
What are the alternatives to Devto Publisher?
Skills that share tags, products or a category with Devto Publisher: Markit (shift-labs-ai/markit, 1.3k stars), Asu Resume Audit Skill (Claycui828/ASu-resume-skills, 374 stars), Best Skills (LinklyAI/best-skills, 635 stars) and Deepxiv Baseline Table (DeepXiv/deepxiv_sdk, 804 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Devto 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 10, 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.