← Products

Developer Tools
⚙ Needs: A dev.to API key (Settings > Account), kept in your…

Dev.to Connector for Muse

Read and write dev.to: own profile, own articles (published, drafts, all), public articles by username, create and update articles with a safe draft default.

At a glance
What
Read and write dev.to: own profile, own articles (published, drafts, all), public articles by username, create and update articles with a safe draft default.
Cost
Free
Needs
A dev.to API key (Settings > Account), kept in your Muse's secure vault (never paste secrets here). Note: article-create defaults to a private draft (safe); publishing (--published) goes live immediately — always confirm the exact title and content first. dev.to is free.
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

@
Created by: @bluman1
Creator of the bluman1/muse-connectors catalog — 150 free open-source (MIT) connector skills for the Muse agent. Curated listings — credit to the creator.
⌁

Install

Prerequisites: A dev.to API key (Settings > Account), kept in your Muse's secure vault (never paste secrets here). Note: article-create defaults to a private draft (safe); publishing (--published) goes live immediately — always confirm the exact title and content first. dev.to is free. No GitHub account needed unless listed here. Install "Dev.to Connector for Muse" for me. A Muse agent skill that reads and writes your dev.to account: own profile and articles, public articles by username, create and update articles with a safe draft default. Repository: https://github.com/bluman1/muse-connectors/tree/main/connectors/devto 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "devto". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my dev.to API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

Free and open-source (MIT): https://github.com/bluman1/muse-connectors/tree/main/connectors/devto — Read and write dev.to: own profile, own articles (published, drafts, all), public articles by username, create and update articles with a safe draft default.
?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.