Token导航 LogoToken导航

Agent Skill · 研究检索

dev-to-hashnode(开发到哈希节点)

dev-to-hashnode 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

dev-to-hashnode 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 42,645。

总安装 1,053周安装 43GitHub Stars 69下载 341核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:dev-to-hashnode(开发到哈希节点)
来源仓库:https://github.com/jonathimer/devmarketing-skills
仓库路径:skills/dev-to-hashnode
安装命令:
npx skills add https://github.com/jonathimer/devmarketing-skills --skill dev-to-hashnode
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/jonathimer/devmarketing-skills --skill dev-to-hashnode

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

dev-to-hashnode 管理 Dev.to 与 Hashnode 双平台发布策略,优化 SEO 与读者覆盖。它比较两平台特性差异,指导账号注册、域名绑定与内容排期,提升开发者影响力。强调持续输出与互动参与,利用平台算法推荐机制扩大受众群体,建立可信技术声誉。

使用前请在两平台完成账号设置,注意内容去重与原创声明要求,避免跨平台违规。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/dev-to-hashnode

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/jonathimer/devmarketing-skills --skill dev-to-…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

dev-to-hashnode 怎么安装?

在终端执行 npx skills add https://github.com/jonathimer/devmarketing-skills --skill dev-to-hashnode。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

dev-to-hashnode 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

dev-to-hashnode 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

dev-to-hashnode 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

dev-to-hashnode 用的人多吗?

公开数据是累计安装 1,053 次,近一周安装 43 次,下载 341 次,GitHub 69 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

dev-to-hashnode 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
dev-to-hashnode

开发到哈希节点 · 本页

1,05369需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Dev.to & Hashnode Publishing

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.


Before You Start

  1. Read .agents/developer-audience-context.md if it exists
  2. Decide your canonical URL strategy (important for SEO)
  3. Create accounts on both platforms to reserve your username
  4. Understand: These platforms reward consistency and engagement

Platform Comparison

Dev.to vs Hashnode

FeatureDev.toHashnode
Monthly visitors~10M+~3M+
Custom domainNo (subdomain only)Yes (free)
Canonical URL supportYesYes
SEO benefitsHigh domain authorityYour domain gets SEO
MonetizationNo nativeSponsors, newsletter
NewsletterNoBuilt-in
Series supportYesYes
Code highlightingExcellentExcellent
Community featuresStrong (reactions, comments)Growing
AudienceBroader, more beginnersMore senior, focused

When to Use Each

Use Dev.to whenUse Hashnode when
Maximum reach is priorityBuilding your own brand
Targeting beginners/mid-levelWant custom domain SEO
Community engagement mattersBuilding email list
Quick validation of contentLong-term content strategy
Don't have your own blogSupplementing your main blog

Cross-Posting Strategy

The Canonical URL Decision

StrategyProsCons
Original on your blogSEO to your domain, full controlPlatforms may rank lower
Original on Dev.toMaximum initial reachNo SEO to your domain
Original on Hashnode (custom domain)SEO + platform reachSmaller initial audience

Best Practice: Your Blog + Cross-Post

  1. Publish on your blog first — This is canonical
  2. Wait 1-2 days — Let Google index your original
  3. Cross-post to Dev.to — Set canonical URL to your blog
  4. Cross-post to Hashnode — Set canonical URL to your blog

Setting Canonical URLs

Dev.to (in frontmatter):

---
title: Your Title
canonical_url: https://yourblog.com/your-post
---

Hashnode (in editor):

  • Click "Article settings" gear icon
  • Paste original URL in "Canonical URL" field

Dev.to Optimization

Frontmatter Structure

---
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 Strategy

TagFollowersUse for
#javascript200K+JS content
#webdev150K+General web development
#beginners120K+Accessible content
#tutorial100K+Step-by-step guides
#react80K+React specific
#programming80K+General programming
#python70K+Python content
#devops50K+DevOps, CI/CD
#opensource40K+OSS projects
#productivity40K+Dev tools, workflows

Rules:

  • Maximum 4 tags per post
  • First tag is primary (appears in URL)
  • Check tag follower count before using

What Performs on Dev.to

Content typePerformanceNotes
Beginner tutorialsHighLargest audience segment
Listicles ("10 tools...")HighEasy to consume
Career adviceHighAspirational content
Hot takesMedium-highControversial drives engagement
Deep technicalMediumNiche but engaged audience
Project showcasesMediumBest with story behind it
News/updatesLowCompetes with official sources

Dev.to Engagement Features

FeatureHow to use
ReactionsHeart, unicorn, saved, fire — different meanings
CommentsReply to every comment for algorithm boost
SeriesGroup related posts, drives binge reading
DiscussionTag #discuss for opinion/question posts
ListingsPost jobs, events, products

Hashnode Optimization

Article Settings

SettingRecommendation
SubtitleUse for SEO keywords
Cover image1600x840 optimal size
SEO titleCan differ from article title
SEO description155 characters max
Canonical URLYour original if cross-posting
Enable table of contentsYes for long posts
Disable commentsNo — engagement helps

Tag Strategy

Hashnode tags work differently:

  • Tags are linked to global topics
  • Some tags have dedicated feeds
  • Fewer tags, more focused

Popular Hashnode tags:

  • javascript, web-development, react
  • devops, cloud, aws
  • beginners, tutorial
  • opensource, programming

What Performs on Hashnode

Content typePerformanceNotes
In-depth tutorialsHighAudience expects depth
Architecture postsHighMore senior audience
DevOps/cloud contentHighStrong niche presence
Career storiesMedium-highPersonal narratives work
Quick tipsMediumLess than on Dev.to
ListiclesMediumLess effective here

Hashnode-Specific Features

FeatureHow to use
NewsletterEnable to collect subscribers
SeriesGreat for tutorials, courses
Custom CSSStyle your blog uniquely
WidgetsAdd GitHub, newsletter CTAs
SponsorsHashnode has sponsor program
AnalyticsBuilt-in, more detailed than Dev.to

Content Formatting

Structure That Works

# 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/blob/HEAD/skills/dev-to-hashnode/link) for more content about [topic].*

Formatting Best Practices

ElementGuideline
HeadersUse H2 for sections, H3 for subsections
Code blocksAlways specify language for syntax highlighting
ImagesUse descriptive alt text, compress for speed
LinksDescriptive text, not "click here"
Length1000-2500 words performs best
ParagraphsKeep short, 2-3 sentences max
ListsUse liberally for scannability

Building Followers

Consistency Strategy

FrequencyResult
4+ posts/monthRapid follower growth
2-3 posts/monthSteady growth
1 post/monthSlow but sustainable
SporadicMinimal follower retention

Engagement Tactics

TacticWhy it works
Reply to every commentAlgorithm boost + relationship building
Comment on others' postsVisibility + community
Follow relevant authorsOften reciprocated
Share on social mediaDrives external traffic
Link between your postsKeeps readers on your content
Create seriesEncourages following for updates

Bio and Profile Optimization

Dev.to profile:

  • Clear profile photo
  • Bio with what you write about
  • Link to your main site
  • List your expertise areas

Hashnode profile:

  • Custom domain setup
  • Newsletter enabled
  • Social links populated
  • Blog name and tagline set

Platform-Specific Do's and Don'ts

Do's

  1. Do set canonical URLs to protect your SEO
  2. Do use platform-specific formatting (embeds, etc.)
  3. Do engage with comments within 24 hours
  4. Do cross-post to both platforms
  5. Do use series for related content
  6. Do optimize cover images for each platform
  7. Do include a CTA at the end

Don'ts

  1. Don't post identical content without canonical URLs
  2. Don't ignore comments
  3. Don't use only self-promotional content
  4. Don't neglect tags — they're discovery mechanisms
  5. Don't forget mobile readability
  6. Don't publish unfinished drafts
  7. Don't keyword stuff your content

Analytics and Iteration

Dev.to Dashboard

MetricWhat it tells you
ViewsReach/impressions
ReactionsEngagement quality
CommentsDiscussion value
Reading timeContent depth
Followers from postConversion rate

Hashnode Analytics

MetricWhat it tells you
Total viewsReach
Unique visitorsAudience size
Read ratioCompletion rate
Time on pageEngagement depth
ReferrersTraffic sources
Newsletter signupsList growth

What to Optimize

Low metricTry this
Low viewsBetter title, different tags
Low reactionsMore engaging opening
Low commentsEnd with a question
High bounceBetter structure, hook
Low followersStronger CTA, series

Tools

ToolUse case
OctolensMonitor Dev.to and Hashnode for mentions of your topic, competitors, and trends. Find popular content to learn from.
Hemingway EditorImprove readability
CarbonBeautiful code screenshots
UnsplashFree cover images
CanvaCustom cover image design
GrammarlyCatch errors before publishing

Content Calendar Template

WeekDev.toHashnodeTopic
1PublishCross-post (day 2)Tutorial
2Cross-postPublishDeep dive
3PublishCross-post (day 2)Listicle
4Cross-postPublishOpinion/experience

Related Skills

  • developer-audience-context — Know who you're writing for
  • hacker-news-strategy — Drive traffic from HN to your posts
  • reddit-engagement — Share posts in relevant subreddits
  • github-presence — Link from READMEs to your content
  • x-devs — Promote posts on Twitter/X

平台分布

Codex

37.2%
按下载量换算127

Claude

31.75%
按下载量换算108

Cursor

18.06%
按下载量换算62

Gemini CLI

9.4%
按下载量换算32

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills