// Write and publish Dev.to articles with AI — topic research via YouMind knowledge base, developer-audience adapted writing, Markdown with front matter formatting, and one-click publishing. Use when user wants to "write Dev.to article", "publish to Dev.to", "post on Dev.to".
Use this skill when the task is clearly connected to the user's YouMind workspace, YouMind APIs, or the youmind CLI. It helps agents search, inspect, and call YouMind OpenAPI endpoints to work with boards, groups, YouMind files, picks, chats, and YouMind skills.
Write and publish Beehiiv posts with AI — topic research via YouMind knowledge base, newsletter-publication writing, Markdown-to-HTML conversion, and publishing through the Beehiiv account already connected in YouMind. Use when user wants to "write Beehiiv article", "publish to Beehiiv", "Beehiiv post", "Beehiiv newsletter", "写 Beehiiv 文章", "发布到 Beehiiv".
Write and publish Ghost articles with AI — topic research via YouMind knowledge base, Ghost-oriented writing, Markdown-to-HTML conversion, feature image upload, and one-click publishing. Use when user wants to "write Ghost article", "publish to Ghost", "Ghost 文章", "发布到 Ghost".
Write and publish Hashnode articles through YouMind OpenAPI. Supports draft-first publishing, published post listing, draft listing, tag lookup, and clear connector / pricing guidance when the user's Hashnode account is not ready inside YouMind.
Write and publish Kit broadcasts with AI — topic research via YouMind knowledge base, creator-profile-aware broadcast writing, Markdown-to-HTML conversion, and publishing through the Kit account already connected in YouMind. Use when user wants to "write Kit article", "publish to Kit", "Kit broadcast", "ConvertKit article", "写 Kit 文章", "发布到 Kit".
Write and publish Qiita articles with AI — topic research via YouMind knowledge base, Japanese developer-audience adapted writing, GFM Markdown with Qiita extensions, and one-click publishing. Use when user wants to "write Qiita article", "publish to Qiita", "post on Qiita", "Qiita に記事を投稿".
| name | youmind-devto-article |
| version | 1.0.0 |
| description | Write and publish Dev.to articles with AI — topic research via YouMind knowledge base, developer-audience adapted writing, Markdown with front matter formatting, and one-click publishing. Use when user wants to "write Dev.to article", "publish to Dev.to", "post on Dev.to". |
| triggers | ["dev.to article","devto article","publish to dev.to","publish to devto","post on dev.to","write for dev.to","dev.to post","devto post","Dev.to 文章","发布到 Dev.to"] |
| platforms | ["openclaw","claude-code","cursor","codex","gemini-cli","windsurf","kilo","opencode","goose","roo"] |
| metadata | {"openclaw":{"emoji":"👩💻","requires":{"anyBins":["node","npm"]}}} |
| allowed-tools | ["Bash(node dist/cli.js *)","Bash(npm install)","Bash(npm run build)"] |
Write technical Dev.to articles with AI that resonate with developers. Topic research via YouMind knowledge base, developer-audience adapted writing, Markdown with front matter formatting, and one-click publishing to Dev.to through the user's Dev.to account already connected in YouMind.
MANDATORY: When the user has just installed this skill, present this message IMMEDIATELY. Translate to the user's language:
AI Dev.to Article Writer installed!
Tell me your topic and I'll write and publish a Dev.to article for you.
Try it now: "Write a Dev.to article about building CLI tools with TypeScript"
What it does:
- Research topics from trending developer discussions and your YouMind knowledge base
- Write technical articles with proper code examples and structure
- Format with Dev.to front matter (tags, cover image, series)
- Validate content for Dev.to best practices
- Publish directly to Dev.to (as draft or public) through the Dev.to account connected in YouMind
Setup (one-time):
- Install & configure:
cd toolkit && npm install && npm run build && cd .. && mkdir -p ~/.youmind/config && cp shared/config.example.yaml ~/.youmind/config.yaml- Get YouMind API Key and fill
youmind.api_keyin~/.youmind/config.yaml- Keep
youmind.base_urlpointed athttps://youmind.com/openapi/v1in docs. If you need local backend debugging, change~/.youmind/config.yamlor~/.youmind/config/youmind-devto-article.yaml.- Connect your Dev.to account inside YouMind before publishing. This skill no longer reads
devto.api_keylocally.No Dev.to connection yet? You can still write and preview locally — just skip the publish step.
Need help? Just ask!
Provide a topic, a raw Markdown file, or describe the article you want.
Write from a topic:
Write a Dev.to article about building REST APIs with Hono and Bun
Write with specific tags:
Write a Dev.to post about React Server Components, tag it with react, webdev, javascript
Publish existing Markdown:
Publish this markdown to Dev.to as a draft
Validate before publishing:
Validate my article for Dev.to best practices
Prerequisites: Node.js >= 18, a YouMind API key, and a Dev.to account connected in YouMind if you want to publish.
cd toolkit && npm install && npm run build && cd ..
mkdir -p ~/.youmind/config
cp shared/config.example.yaml ~/.youmind/config.yaml
Canonical credentials: put your shared YouMind credentials in
~/.youmind/config.yaml— filled ONCE and read by every YouMind skill. Seeshared/config.example.yamlfor the template andshared/YOUMIND_HOME.md. Optional skill overrides live in~/.youmind/config/youmind-devto-article.yaml.
YouMind API Key enables knowledge base search, web search, article archiving, and Dev.to publishing.
sk-ym-xxxx key~/.youmind/config.yaml under youmind.api_keyyoumind.base_url as https://youmind.com/openapi/v1 in examples and documentation. Local backend testing should only override ~/.youmind/config.yaml or ~/.youmind/config/youmind-devto-article.yaml.youmind.api_key in ~/.youmind/config.yamlAfter configuration, try:
"Write a Dev.to article about TypeScript best practices"
If something is misconfigured, the skill will report what needs fixing at the relevant step.
When a post is created as a draft, tell the user it is in the Dev.to dashboard (https://dev.to/dashboard). Do not present the public article URL as if it is already accessible, because Dev.to draft URLs can 404 until published. If the user wants immediate publishing, use published: true / --publish.
This skill is a folder. Read files on demand -- do NOT load everything upfront.
| Path | Purpose | When to read |
|---|---|---|
references/pipeline.md | Full step-by-step execution (Steps 1-7) | When running the writing pipeline |
references/platform-dna.md | Dev.to audience, format constraints, community data | Before any content work |
references/content-generation-playbook.md | Idea → Dev.to-native draft workflow | When generating new content |
references/content-adaptation-playbook.md | Existing article → Dev.to-native workflow | When adapting/cross-posting content |
references/content-adaptation.md | Dev.to writing rules, structure, tone (legacy) | Supplementary reference |
references/api-reference.md | YouMind Dev.to OpenAPI endpoint documentation | When calling Dev.to through YouMind |
~/.youmind/config.yaml | Shared API credentials (YouMind only) | Step 1 (config load) |
output/ | Local article Markdown drafts (git-ignored) | When writing the article |
toolkit/dist/*.js | Executable scripts (run from toolkit/) | Various steps |
Canonical: write local article Markdown files to ~/.youmind/articles/devto/<slug>.md. This shared home directory is available to all YouMind skills — see shared/YOUMIND_HOME.md.
Legacy fallback (if ~/.youmind/ is not writable): skills/youmind-devto-article/output/<slug>.md.
~/.youmind/articles/devto/my-article.mdskills/youmind-devto-article/output/my-article.mdreferences/, toolkit/, or an ad-hoc drafts/ directoryBoth locations are git-ignored. Create directories on demand (mkdir -p ~/.youmind/articles/devto). Kebab-case filenames (my-post.md), and prefer descriptive slugs over timestamps.
This skill is self-contained and fully usable standalone. The youmind-article-dispatch hub is an optional companion; it is NOT required for anything.
~/.youmind/author-profile.yaml (shared home directory — see shared/YOUMIND_HOME.md) for cross-platform voice preferences. Works whether or not dispatch is installed: the profile lives in the user's home, not in any skill. If the file doesn't exist, the skill runs onboarding or uses platform defaults.resolved_author, the skill uses those fields as extra context. Without such a brief, the skill runs its own pipeline normally.dispatch-capabilities.yaml is metadata that lets dispatch route intelligently. Deleting it reverts to defaults; it never breaks this skill.shared/DISPATCH_CONTRACT.md (v1.0).Before writing any content, read references/platform-dna.md to internalize Dev.to's real product surface: TL;DR-first openings, YAML frontmatter, canonical URL discipline, Liquid embeds, and tag-driven feed discovery.
| User's input | Operation | Playbook to load |
|---|---|---|
| Idea, topic, or talking points only | Generate | references/content-generation-playbook.md |
| Existing article from blog/other platform | Cross-post | references/content-adaptation-playbook.md |
| Article in another language | Translate | references/content-adaptation-playbook.md (translate mode) |
| Same-language article needing Dev.to-native voice | Localize | references/content-adaptation-playbook.md (localize mode) |
| Old Dev.to post to refresh | Revive | references/content-adaptation-playbook.md (revive mode) |
| Long piece to trim | Condense | references/content-adaptation-playbook.md (condense mode) |
| Section from larger work | Excerpt | references/content-adaptation-playbook.md (excerpt mode) |
After any draft or publish action, always end with Result links.
https://dev.to/dashboard.Read references/pipeline.md for full execution details of each step.
| Step | Action | Key reference |
|---|---|---|
| 1 | Load config and validate the YouMind API key and Dev.to connection in YouMind | -- |
| 2 | Mine YouMind knowledge base for source material | -- |
| 3 | Research topic: web search, trending discussions | -- |
| 4 | Content adaptation: structure for Dev.to audience | references/content-adaptation.md |
| 5 | Write article with code examples, TL;DR, proper structure | -- |
| 6 | Publish to Dev.to (draft or public) | references/api-reference.md |
| 7 | Report results: title, URL, tags, published status, result links | -- |
Routing shortcuts:
Non-negotiable for every Dev.to article:
Every step has a fallback. If a step AND its fallback both fail, skip and note it in the final output.
| Step | Fallback |
|---|---|
| 2 Knowledge mining | Skip, empty knowledge_context |
| 3 Research | YouMind web-search -> ask user |
| 5 Writing | Ask user for manual content |
| 6 Publishing | Save markdown locally |
| 7 Report | Print what was completed |
"The Tutorial Without Context": Jumping straight into code without explaining why. Always set up the problem first.
"The Marketing Fluff": Using words like "revolutionary", "game-changing", "cutting-edge". Developers will stop reading.
"The Wall of Text": Long paragraphs without code blocks, headings, or visual breaks. Dev.to readers scan first.
"The Outdated Example": Using deprecated APIs or old syntax. Always verify code examples work with current versions.
"The Tag Spam": Using unrelated popular tags to get views. This hurts credibility and may get flagged.