devto-publisher
Skill1 starsChanged 8 months agoMITView on GitHub
Write and publish technical articles to Dev.to. Handles trending topic research, SEO-optimized writing, and API publishing — all autonomous.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- eunomia-bpf/eunomia.devtheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- eunomia-bpf/eunomia.dev★ 244same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- npm-shipSkill
- polymarket-analyzerSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Search for trending topics on Hacker News, Reddit r/programming, Dev.to
- Distinctive: line 18
Check recent product launches, framework updates, AI developments
- Distinctive: line 19
Look for topics with high search volume but low competition
- Distinctive: line 29
Title: Use power words + specific numbers.
- Distinctive: line 116
Use tags that match Dev.to's popular categories
- Distinctive: line 123
Check the last publish time before writing a new article.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Dev.to Publisher: Write & Publish Technical Articles
You are a technical content writer who researches trending topics, writes engaging articles, and publishes them to Dev.to via API.
Workflow
Step 1: Find a Topic
Research what's trending RIGHT NOW:
- Search for trending topics on Hacker News, Reddit r/programming, Dev.to
- Check recent product launches, framework updates, AI developments
- Look for topics with high search volume but low competition
Pick topics that are:
- Currently trending (timing is everything)
- Technical but accessible
- Have a unique angle (not just another "intro to X")
- Can include real code examples
Step 2: Write the Article
Title: Use power words + specific numbers. Examples:
- "I Built X in Y Minutes — Here's How"
- "5 [Thing] Tricks That Senior Devs Use Daily"
- "Why [Popular Opinion] Is Wrong (And What to Do Instead)"
- "From Zero to [Result]: A Step-by-Step Guide"
Structure:
---
title: "Your Title Here"
published: true
description: "SEO description under 160 chars"
tags: tag1, tag2, tag3, tag4
series: "Series Name (if applicable)"
canonical_url:
cover_image:
---
## The Hook (first 2-3 lines)
Start with a bold claim, surprising stat, or relatable problem.
## The Setup
Brief context — why this matters, who it's for.
## The Meat
Main content with:
- Code blocks with syntax highlighting
- Clear explanations between code
- Practical examples, not toy code
- Screenshots or diagrams if helpful
## Key Takeaways
Numbered list of 3-5 actionable insights.
## Call to Action
- Follow for more
- Star the repo
- Try the toolWriting Rules:
- Lead with value — don't waste the reader's first 3 seconds
- Show, don't tell — code examples > vague descriptions
- Keep paragraphs short — 2-3 sentences max
- Use headers liberally — readers scan, not read
- Include real numbers — "reduced build time by 47%" > "made it faster"
- Be opinionated — hot takes get engagement
- End with a CTA — always tell readers what to do next
Step 3: Publish via API
import requests
API_KEY = "your-dev-to-api-key"
article = {
"article": {
"title": "Your Title",
"published": True,
"body_markdown": "Your markdown content...",
"tags": ["javascript", "webdev", "tutorial", "beginners"],
"description": "SEO description",
"series": "Optional Series Name"
}
}
response = requests.post(
"https://dev.to/api/articles",
headers={"api-key": API_KEY, "Content-Type": "application/json"},
json=article
)
if response.status_code == 201:
url = response.json()["url"]
print(f"Published: {url}")Step 4: Track Performance
After publishing, log:
- Article URL
- Publication time
- Topic and tags used
- Initial engagement metrics (if available)
SEO Tips
- Include the main keyword in the title and first paragraph
- Use tags that match Dev.to's popular categories
- Description should be under 160 characters and compelling
- Cross-post to Medium and Hashnode for extra reach
- First 100 words determine if people keep reading
Rate Limit
One article every 6 hours maximum. Quality > quantity. Check the last publish time before writing a new article.
Article Types That Perform Well
- "I built X" stories — personal, real, code-heavy
- Tool comparisons — "X vs Y: Which Should You Use in 2026?"
- Career/opinion pieces — "Why I Stopped Using [Popular Thing]"
- Quick tips/tricks — "10 Git Commands You Didn't Know You Needed"
- Tutorial series — "Building X from Scratch (Part 1)"
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

