Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →When the user wants to publish on Dev.to, Hashnode, or other developer blogging platforms. Trigger phrases include "Dev.to," "Hashnode," "developer blog," "cross-posting," "technical blogging," "canonical URL," or "developer content platform."
.claude/skills/sickn33-dev-to-hashnode/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-19 | ✗→✓ | ▲ Improved | 96% | 0% |
| case-11 | ✓→✗ | ▼ Worse | 114% | 0% |
| case-01 | ✓→✓ | ＝ Same ✓ | 504% | 0% |
| case-02 | ✓→✓ | ＝ Same ✓ | 131% | 0% |
| case-03 | ✓→✓ | ＝ Same ✓ | 194% | 0% |
Use this skill when you need when the user wants to publish on Dev.to, Hashnode, or other developer blogging platforms. Trigger phrases include "Dev.to," "Hashnode," "developer blog," "cross-posting," "technical blogging," "canonical URL," or "developer content platform.".
Developer blogging platforms offer built-in audiences of hundreds of thousands of developers. This skill covers cross-posting strategy, platform-specific optimization, and building followers on Dev.to and Hashnode.
.agents/developer-audience-context.md if it exists| Feature | Dev.to | Hashnode | |---------|--------|----------| | Monthly visitors | ~10M+ | ~3M+ | | Custom domain | No (subdomain only) | Yes (free) | | Canonical URL support | Yes | Yes | | SEO benefits | High domain authority | Your domain gets SEO | | Monetization | No native | Sponsors, newsletter | | Newsletter | No | Built-in | | Series support | Yes | Yes | | Code highlighting | Excellent | Excellent | | Community features | Strong (reactions, comments) | Growing | | Audience | Broader, more beginners | More senior, focused |
| Use Dev.to when | Use Hashnode when | |-----------------|-------------------| | Maximum reach is priority | Building your own brand | | Targeting beginners/mid-level | Want custom domain SEO | | Community engagement matters | Building email list | | Quick validation of content | Long-term content strategy | | Don't have your own blog | Supplementing your main blog |
| Strategy | Pros | Cons | |----------|------|------| | Original on your blog | SEO to your domain, full control | Platforms may rank lower | | Original on Dev.to | Maximum initial reach | No SEO to your domain | | Original on Hashnode (custom domain) | SEO + platform reach | Smaller initial audience |
Dev.to (in frontmatter):
yaml--- title: Your Title canonical_url: https://yourblog.com/your-post ---
Hashnode (in editor):
yaml--- title: "Specific, Keyword-Rich Title (Not Clickbait)" published: true description: "One compelling sentence that shows up in previews and SEO" tags: javascript, webdev, tutorial, beginners cover_image: https://your-cdn.com/image.png canonical_url: https://yourblog.com/original-post series: "Building a CLI from Scratch" ---
| Tag | Followers | Use for | |-----|-----------|---------| | #javascript | 200K+ | JS content | | #webdev | 150K+ | General web development | | #beginners | 120K+ | Accessible content | | #tutorial | 100K+ | Step-by-step guides | | #react | 80K+ | React specific | | #programming | 80K+ | General programming | | #python | 70K+ | Python content | | #devops | 50K+ | DevOps, CI/CD | | #opensource | 40K+ | OSS projects | | #productivity | 40K+ | Dev tools, workflows |
Rules:
| Content type | Performance | Notes | |--------------|-------------|-------| | Beginner tutorials | High | Largest audience segment | | Listicles ("10 tools...") | High | Easy to consume | | Career advice | High | Aspirational content | | Hot takes | Medium-high | Controversial drives engagement | | Deep technical | Medium | Niche but engaged audience | | Project showcases | Medium | Best with story behind it | | News/updates | Low | Competes with official sources |
| Feature | How to use | |---------|------------| | Reactions | Heart, unicorn, saved, fire — different meanings | | Comments | Reply to every comment for algorithm boost | | Series | Group related posts, drives binge reading | | Discussion | Tag #discuss for opinion/question posts | | Listings | Post jobs, events, products |
| Setting | Recommendation | |---------|----------------| | Subtitle | Use for SEO keywords | | Cover image | 1600x840 optimal size | | SEO title | Can differ from article title | | SEO description | 155 characters max | | Canonical URL | Your original if cross-posting | | Enable table of contents | Yes for long posts | | Disable comments | No — engagement helps |
Hashnode tags work differently:
Popular Hashnode tags:
javascript, web-development, reactdevops, cloud, awsbeginners, tutorialopensource, programming| Content type | Performance | Notes | |--------------|-------------|-------| | In-depth tutorials | High | Audience expects depth | | Architecture posts | High | More senior audience | | DevOps/cloud content | High | Strong niche presence | | Career stories | Medium-high | Personal narratives work | | Quick tips | Medium | Less than on Dev.to | | Listicles | Medium | Less effective here |
| Feature | How to use | |---------|------------| | Newsletter | Enable to collect subscribers | | Series | Great for tutorials, courses | | Custom CSS | Style your blog uniquely | | Widgets | Add GitHub, newsletter CTAs | | Sponsors | Hashnode has sponsor program | | Analytics | Built-in, more detailed than Dev.to |
markdown# Title [Compelling hook — why should they care?] ## Table of Contents (for long posts) - [Section 1](#section-1) - [Section 2](#section-2) ## The Problem [What pain point are you solving?] ## The Solution [Your approach, with code examples] ### Code Example
// Well-commented code const example = "explained";
## Step-by-Step
1. **Step one** — Explanation
2. **Step two** — Explanation
3. **Step three** — Explanation
## Common Pitfalls
[What to watch out for]
## Conclusion
[Summary + CTA]
---
*If you found this helpful, [follow me](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/dev-to-hashnode/link) for more content about [topic].*| Element | Guideline | |---------|-----------| | Headers | Use H2 for sections, H3 for subsections | | Code blocks | Always specify language for syntax highlighting | | Images | Use descriptive alt text, compress for speed | | Links | Descriptive text, not "click here" | | Length | 1000-2500 words performs best | | Paragraphs | Keep short, 2-3 sentences max | | Lists | Use liberally for scannability |
| Frequency | Result | |-----------|--------| | 4+ posts/month | Rapid follower growth | | 2-3 posts/month | Steady growth | | 1 post/month | Slow but sustainable | | Sporadic | Minimal follower retention |
| Tactic | Why it works | |--------|--------------| | Reply to every comment | Algorithm boost + relationship building | | Comment on others' posts | Visibility + community | | Follow relevant authors | Often reciprocated | | Share on social media | Drives external traffic | | Link between your posts | Keeps readers on your content | | Create series | Encourages following for updates |
Dev.to profile:
Hashnode profile:
| Metric | What it tells you | |--------|-------------------| | Views | Reach/impressions | | Reactions | Engagement quality | | Comments | Discussion value | | Reading time | Content depth | | Followers from post | Conversion rate |
| Metric | What it tells you | |--------|-------------------| | Total views | Reach | | Unique visitors | Audience size | | Read ratio | Completion rate | | Time on page | Engagement depth | | Referrers | Traffic sources | | Newsletter signups | List growth |
| Low metric | Try this | |------------|----------| | Low views | Better title, different tags | | Low reactions | More engaging opening | | Low comments | End with a question | | High bounce | Better structure, hook | | Low followers | Stronger CTA, series |
| Tool | Use case | |------|----------| | Octolens | Monitor Dev.to and Hashnode for mentions of your topic, competitors, and trends. Find popular content to learn from. | | Hemingway Editor | Improve readability | | Carbon | Beautiful code screenshots | | Unsplash | Free cover images | | Canva | Custom cover image design | | Grammarly | Catch errors before publishing |
| Week | Dev.to | Hashnode | Topic | |------|--------|----------|-------| | 1 | Publish | Cross-post (day 2) | Tutorial | | 2 | Cross-post | Publish | Deep dive | | 3 | Publish | Cross-post (day 2) | Listicle | | 4 | Cross-post | Publish | Opinion/experience |
developer-audience-context — Know who you're writing forhacker-news-strategy — Drive traffic from HN to your postsreddit-engagement — Share posts in relevant subredditsgithub-presence — Link from READMEs to your contentx-devs — Promote posts on Twitter/X| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | pass→pass | 2,651 | 2,208 | -17% | 1 | 1 | 0% | 562 | 3,392 | +504% | 0 | 0 | — |
case-02 | pass→pass | 9,075 | 5,561 | -39% | 1 | 1 | 0% | 1,750 | 4,038 | +131% | 0 | 0 | — |
case-03 | pass→pass | 7,418 | 6,376 | -14% | 1 | 1 | 0% | 1,430 | 4,207 | +194% | 0 | 0 | — |
case-20 | pass→pass | 12,580 | 9,575 | -24% | 1 | 1 | 0% | 2,025 | 4,449 | +120% | 0 | 0 | — |
case-04 | fail→fail | 8,112 | 5,381 | -34% | 1 | 1 | 0% | 1,487 | 3,919 | +164% | 0 | 0 | — |
case-05 | pass→pass | 12,038 | 5,856 | -51% | 1 | 1 | 0% | 2,075 | 4,076 | +96% | 0 | 0 | — |
case-06 | pass→pass | 8,444 | 6,458 | -24% | 1 | 1 | 0% | 1,702 | 4,337 | +155% | 0 | 0 | — |
case-07 | pass→pass | 7,041 | 4,318 | -39% | 1 | 1 | 0% | 1,323 | 3,705 | +180% | 0 | 0 | — |
case-08 | pass→pass | 6,107 | 3,774 | -38% | 1 | 1 | 0% | 1,154 | 3,661 | +217% | 0 | 0 | — |
case-09 | pass→pass | 4,984 | 3,699 | -26% | 1 | 1 | 0% | 907 | 3,587 | +295% | 0 | 0 | — |
case-10 | pass→pass | 10,666 | 7,315 | -31% | 1 | 1 | 0% | 1,795 | 4,323 | +141% | 0 | 0 | — |
case-11 | pass→fail | 13,001 | 9,630 | -26% | 1 | 1 | 0% | 2,086 | 4,456 | +114% | 0 | 0 | — |
case-12 | pass→pass | 9,529 | 6,538 | -31% | 1 | 1 | 0% | 1,490 | 4,004 | +169% | 0 | 0 | — |
case-13 | pass→pass | 7,903 | 3,142 | -60% | 1 | 1 | 0% | 1,269 | 3,483 | +174% | 0 | 0 | — |
case-14 | pass→pass | 12,242 | 11,395 | -7% | 1 | 1 | 0% | 1,982 | 4,887 | +147% | 0 | 0 | — |
case-15 | pass→pass | 6,121 | 4,235 | -31% | 1 | 1 | 0% | 1,049 | 3,702 | +253% | 0 | 0 | — |
case-16 | pass→pass | 6,504 | 4,552 | -30% | 1 | 1 | 0% | 1,168 | 3,796 | +225% | 0 | 0 | — |
case-17 | pass→pass | 3,237 | 3,036 | -6% | 1 | 1 | 0% | 556 | 3,464 | +523% | 0 | 0 | — |
case-18 | pass→pass | 13,721 | 11,050 | -19% | 1 | 1 | 0% | 2,158 | 4,765 | +121% | 0 | 0 | — |
case-19 | fail→pass | 12,988 | 6,679 | -49% | 1 | 1 | 0% | 2,039 | 3,997 | +96% | 0 | 0 | — |
case-21 | pass→pass | 13,473 | 13,282 | -1% | 1 | 1 | 0% | 2,210 | 5,003 | +126% | 0 | 0 | — |
case-22 | pass→pass | 14,584 | 12,078 | -17% | 1 | 1 | 0% | 2,842 | 5,235 | +84% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of 0 percentage points is the difference between those two pass rates over the 22 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.