Convert To Dev.to
Reformats an existing Markdown post into Dev.to-ready Markdown: frontmatter, liquid tags, fenced-block fixes.
Test report
- Verdict
- Tested · Works
- Score
- Tested
- Jul 15, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Aug 10, 2026 · 75dc661
Installed with a command from an empty HOME without ~/.claude — SKILL.md was in place, frontmatter parsed; the skill consists of a single file, no scripts, network, or hidden instructions (Stage 0 clean). The only change since the last test was the addition of Rule 13 regarding Liquid/Jekyll escaping: wrap blocks with `{{ }}` in tildes, alternate the number of tildes between blocks, tilde toml/ini. Ran the same md (GitHub Actions with `${{ secrets.X }}`, toml, ini, nested markdown block, tweet in mid-sentence) through baseline and skill and parsed both results with markdown-it: baseline yielded 5 blocks instead of 4 — the nested block broke the document, and the image along with the `{% twitter %}` tag moved inside the code (0 liquid tags survived outside vs. 2 for the skill). Could not confirm Rule 13 itself: on a live Liquid engine, `{{ secrets.GCP_KEY }}` is consumed identically in both backticks and tildes, meaning the stated mechanism ('tildes prevent Liquid from compiling brackets') is not reproducible outside a real Forem — for this, points were deducted from docs; however, the advice itself is harmless, tildes and alternating their count are parsed as regular fence blocks, and `${{ }}` is preserved inside. Result: the change is cosmetically additive, the old verdict holds.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 5/5
- Triggers reliably 5/5
- Output vs. baseline 9/10
- Docs & honesty 4/5
What Convert To Dev.to does
A single-shot editor prompt that takes raw Markdown and applies 12 concrete Dev.to publishing rules: adds/repairs YAML frontmatter, demotes heading levels so the H1 lives only in frontmatter, fixes code fences missing a language tag, converts a markdown fence that itself contains nested code fences to tildes, fixes split image/caption syntax, strips 'X highlighted' export artifacts, unescapes unnecessary backslashes, wraps snake_case variables/paths in inline code, and converts standalone Twitter/YouTube links to Dev.to Liquid tags. Triggers when the user asks to format or convert an existing blog post/Markdown file for Dev.to.
How to install Convert To Dev.to
git clone https://github.com/derailed-dash/dazbo-agent-skills
mkdir -p ~/.claude/skills
cp -r dazbo-agent-skills/skills/convert-to-devto ~/.claude/skills/convert-to-devto
Skills live in ~/.claude/skills/ (global) or .claude/skills/
(per-project). Restart Claude Code after installing.
Commands — how to trigger Convert To Dev.to
-
/convert-to-devtoReformats an existing Markdown post into Dev.to-ready Markdown: frontmatter, liquid tags, fenced-block fixes.
It also activates on plain-language prompts like these:
-
Can you convert this blog post markdown into Dev.to-ready format? -
Fix the missing language tags on the code fences in this draft -
Turn this Twitter link into a proper Dev.to liquid embed tag
Frequently asked questions
- Is the Convert To Dev.to skill free?
- Yes. The skill itself is free from derailed-dash/dazbo-agent-skills. SkillProof publishes the install command and an independent test verdict at no cost.
- Does Convert To Dev.to work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 15, 2026. Verdict: Tested · Works. Installed with a command from an empty HOME without ~/.claude — SKILL.md was in place, frontmatter parsed; the skill consists of a single file, no scripts, network, or hidden instructions (Stage 0 clean). The only change since the last test was the addition of Rule 13 regarding Liquid/Jekyll escaping: wrap blocks with `{{ }}` in tildes, alternate the number of tildes between blocks, tilde toml/ini. Ran the same md (GitHub Actions with `${{ secrets.X }}`, toml, ini, nested markdown block, tweet in mid-sentence) through baseline and skill and parsed both results with markdown-it: baseline yielded 5 blocks instead of 4 — the nested block broke the document, and the image along with the `{% twitter %}` tag moved inside the code (0 liquid tags survived outside vs. 2 for the skill). Could not confirm Rule 13 itself: on a live Liquid engine, `{{ secrets.GCP_KEY }}` is consumed identically in both backticks and tildes, meaning the stated mechanism ('tildes prevent Liquid from compiling brackets') is not reproducible outside a real Forem — for this, points were deducted from docs; however, the advice itself is harmless, tildes and alternating their count are parsed as regular fence blocks, and `${{ }}` is preserved inside. Result: the change is cosmetically additive, the old verdict holds.
- What is the Convert To Dev.to SkillProof Score?
- 9.2/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 9/10, docs & honesty 4/5.
- How do I install Convert To Dev.to?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use Convert To Dev.to with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.