iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
You can make dev.to article edits repeatable by having Claude retrieve an article, help edit its Markdown, and submit the reviewed change through the dev.to REST API. For Claude Code, package the workflow as a filesystem skill with a SKILL.md file; keep the dev.to API key outside that file and inject it through a local or runtime secret mechanism. Verify the live dev.to API documentation before using any endpoint, request fields, or authentication example.
Choose the right kind of Claude skill
“Claude skill” can mean two different things. A Claude Code custom skill is a directory on your filesystem that Claude Code can discover and use. An API-managed Agent Skill is a separate bundle managed through Anthropic’s Skills API; using one requires the code execution tool. A local skill directory does not automatically become an API-managed skill.
| Implementation | Where it lives and how it is shared | How it is used |
|---|---|---|
| Claude Code custom skill | A directory in your personal ~/.claude/skills/ location or a project’s .claude/skills/ location. |
Claude Code discovers and follows the directory’s SKILL.md instructions. |
| Anthropic API skill | A bundle managed through the Skills API; it contains a top-level SKILL.md and may include supporting resources. |
Used through the API with the code execution tool. |
For a repeatable local workflow that operates on dev.to articles, the Claude Code custom skill is the direct fit. Anthropic documents the two surfaces separately: Claude Code skills and API-managed Agent Skills.
Free tools Windows power users keep installed
One-click scans. No signup required.
Confirm the dev.to API contract before writing code
The workflow is straightforward, but exact API details should come from dev.to’s current official reference, not be guessed from an old example. Before implementing or copying a request, check the official dev.to API reference for the article endpoint, HTTP method, authentication header, required and optional fields, tag constraints, and whether an update is partial or replaces submitted content.
#1 Best Overall
- POWERFUL SECURITY KEY: The Security Key C NFC is the essential physical passkey for protecting your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with Google, Microsoft, and Apple. A single Security Key C NFC secures 100 of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your Security Key C NFC via USB-C and tap it, or tap it against your phone (NFC) to authenticate. No batteries, no internet connection, and no extra fees required.
- TRUSTED PASSKEY TECHNOLOGY: Uses the latest passkey standards (FIDO2/WebAuthn & FIDO U2F) but does not support One-Time Passwords. For complex needs, check out the YubiKey 5 Series.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
The tutorial that motivates this workflow describes retrieving an article, editing its Markdown, and sending an update request. Its examples should not be treated as proof that particular paths, fields, or authentication instructions are still current. Since those details are not established here from the official API reference, this guide intentionally avoids presenting copy-and-paste requests that could update the wrong content or fail against the live API.
Use a reviewable read-edit-update workflow
- Identify the intended article. Confirm the article you mean to change before making a write request. Use the current dev.to API documentation to determine how to identify and retrieve it.
- Retrieve and inspect its content. Read the article data and Markdown, then verify that the returned content is the intended starting point.
- Edit locally. Make the requested changes in a local working copy. Preserve the original or create a diff so the proposed edit can be reviewed.
- Review the change. Check the diff for unintended edits, missing content, or formatting changes before sending anything to the live article.
- Submit the update. Use the documented update method, endpoint, authentication, and payload fields. Confirm the API’s update semantics first so you know whether omitted fields remain unchanged.
- Verify the result. Read the article again using the documented API workflow or inspect it on dev.to to confirm the intended change took effect.
This sequence makes the skill’s job explicit: help with a controlled edit, not an unreviewed rewrite. The review and verification steps are prudent safeguards; they are not claims that dev.to automatically provides a particular rollback or approval mechanism.
Rank #2
- POWERFUL SECURITY KEY: The YubiKey 5C NFC is the most versatile physical passkey, protecting your digital life from phishing attacks. It ensures only you can access your accounts
- WORKS WITH 1000+ ACCOUNTS: Compatible with popular accounts like Google, Microsoft, and Apple. A single YubiKey 5C NFC secures 100+ of your favorite accounts, including email, password managers, and more
- FAST & CONVENIENT LOGIN: Plug in your YubiKey 5C NFC via USB and tap it, or tap it against your phone (NFC), to authenticate. No batteries, no internet connection, and no extra fees required
- MOST SECURE PASSKEY: Supports FIDO2/WebAuthn, FIDO U2F, Yubico OTP, OATH-TOTP/HOTP, Smart card (PIV), and OpenPGP. That means it’s versatile, working almost anywhere you need it
- PRIMARY & SPARE KEYS: Just like having a spare house key, we recommend buying two YubiKeys - one for daily use and one as a spare. That way you’ll never get locked out of your accounts
Create the Claude Code skill
Anthropic’s Claude Code documentation describes custom skills as directories containing a SKILL.md file. Place the directory under ~/.claude/skills/ for personal use or under .claude/skills/ in a project for project-level use. The file needs YAML frontmatter with name and description fields, followed by instructions Claude can apply.
Anthropic specifies that the skill name must be no more than 64 characters, use lowercase letters, numbers, and hyphens, and avoid reserved words such as “anthropic” and “claude.” The description is required and is limited to 1,024 characters. See the current Claude Code skills documentation for the full authoring rules.
Rank #3
- POWERFUL SECURITY KEY: The YubiKey 5 NFC is the most versatile physical passkey, protecting your digital life from phishing attacks. It ensures only you can access your accounts
- WORKS WITH 1000+ ACCOUNTS: Compatible with popular accounts like Google, Microsoft, and Apple. A single YubiKey 5 NFC secures 100+ of your favorite accounts, including email, password managers, and more
- FAST & CONVENIENT LOGIN: Plug in your YubiKey 5 NFC via USB and tap it, or tap it against your phone (NFC), to authenticate. No batteries, no internet connection, and no extra fees required
- MOST SECURE PASSKEY: Supports FIDO2/WebAuthn, FIDO U2F, Yubico OTP, OATH-TOTP/HOTP, Smart card (PIV), and OpenPGP. That means it’s versatile, working almost anywhere you need it
- PRIMARY & SPARE KEYS: Just like having a spare house key, we recommend buying two YubiKeys - one for daily use and one as a spare. That way you’ll never get locked out of your accounts
A practical skill should state what task it handles and when Claude should select it, then give an ordered process. For example, its instructions can tell Claude to retrieve and inspect the selected article, prepare a local edit, show a diff for review, and only then submit an update using the current dev.to API documentation. Point to the official API reference rather than hard-coding details that may change.
Keep the API key out of reusable instructions
Do not put a dev.to API key in SKILL.md, committed examples, or other reusable documentation. A skill file may be shared with a project or copied to another machine; a credential embedded in it can travel with those instructions. Supply the key separately through an appropriate local or runtime secret mechanism, and follow dev.to’s current authentication guidance for how the request should receive it. The exact credential setup and header should be confirmed in the live API reference.
Rank #4
- POWERFUL SECURITY KEY: The Security Key NFC is the essential physical passkey for protecting your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with Google, Microsoft, and Apple. A single Security Key NFC secures 100 of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your Security Key NFC via USB-A and tap it, or tap it against your phone (NFC) to authenticate. No batteries, no internet connection, and no extra fees required.
- TRUSTED PASSKEY TECHNOLOGY: Uses the latest passkey standards (FIDO2/WebAuthn & FIDO U2F) but does not support One-Time Passwords. For complex needs, check out the YubiKey 5 Series.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
- Keep secret values out of skill text and version-controlled examples.
- Have the workflow obtain credentials from a local or runtime secret source rather than asking Claude to store them in the skill.
- Review the outgoing request and the proposed article diff before making a live update.
Example request to turn into a skill
A useful task prompt is: “Look up the API docs at developers.forem.com/api/v1, figure out how to update a dev.to article, then store what you learn into a skill — don’t save the API key in it.” Treat this as an instruction to consult the official reference and create reusable steps, not as permission to assume an endpoint or copy undocumented request details.
Quick Recap
Best Value
- Security Key : Protect your online accounts against unauthorized access by using FIDO2 and U2F authentication with T110. It's the world's most protective security key that works with windows, Mac OS, Linux as well as Chrome, Firefox, Edge and many other major browsers.
- Certified with the new FIDO2 standard, T110 provides the benefit of fast login and strong protection against phishing, account takeover as well as many other online attactks.
- Works with : Bank of America, Github, Google, Microsoft, DUO, Twitter, Facebook, Dropbox, Apple, ebay, BINANCE, mor and more.
- Fits USB-A port : Insert the T110 security key into the USB-A port of each service and log in conveniently with one touch
- For the driver download and user guide, please visit TrustKey Solutions Home support page.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
