agentleFS
tang-vutang-vu/social-posting-skills/.agents/skills/post-devto/SKILL.md

post-devto

Skill9 starsChanged 2 months agoMITView on GitHub

Adapt and publish campaign items on Dev.to — markdown articles via official Forem API (draft-safe default)

  • Reads credentials

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Default is safe: posts go up as UNPUBLISHED drafts (published: false) unless the item's target sets live: true.

    line 30
  2. Distinctive:

    Read and comment on others' articles — Dev.to is a community first.

    line 39

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Dev.to Adapter

Facts live in platforms/devto.json (≤4 tags, cover image, canonical_url). Official Forem API — implemented in this adapter.

What Dev.to rewards (culture)

  • Teaching. Step-by-step tutorials, honest postmortems, annotated code.
  • Beginner-friendly framing travels far; gatekeeping does not.
  • Tags are first-class discovery metadata — pick them carefully (≤4).
  • Series for multi-part content; canonical_url for syndicated posts.

Drafting from the content graph

  • core-claim → descriptive title with the real subject (keywords help).
  • context → intro: what it is, who it's for.
  • proof/technical → the body: sections, code blocks, specifics.
  • demo → "Try it" section with the actual commands.
  • roadmap → closing "What's next" — Dev.to readers like a thread to pull.
  • cta + links → footer; canonical_url when the piece is cross-posted.

Publishing

  • api → DEVTO_API_KEY env (dev.to/settings/extensions). Default is safe: posts go up as UNPUBLISHED drafts (published: false) unless the item's target sets live: true. A remote draft lets the human do a final in-editor review — prefer it.
  • agent-browser → playbook for the dev.to/new markdown editor.
  • manual → full draft package (title, tags, markdown body, cover ref).

Genuine engagement

  • Answer comments with real technical help.
  • Read and comment on others' articles — Dev.to is a community first.

Pitfalls

  • 4 tags → validation error.

  • A bare announcement with no teaching value underperforms — the campaign should adapt the launch into a story or a how-it-works piece.
  • Rate limits exist; one article per launch is the right cadence.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.