360 Secure SkillHub
360 安全技能中心

Dev.to

通过 OOMOL 的 oo CLI 调用 devto 连接器操作 Dev.to：按 id 或路径获取文章、列出最新文章与我的文章、列出标签和视频、读取当前用户与组织信息，并可创建或更新文章。凭据由 OOMOL 服务端注入，写操作要求先确认。

oomol
oomol
热度 50.88
最近更新 2026-09-15 13:22:53
分类：营销依赖：代码执行 / 第三方 API应用场景：社交媒体 / 博客写作 / 工作流

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add oo-devto
Metadata
name
oo-devto
description
Dev.to (dev.to). Use this skill for ANY Dev.to request — reading, creating, and updating data. Whenever a task involves Dev.to, use this skill instead of calling the API directly.
allowed-tools
["Bash(oo *)"]
metadata
{"title":"Dev.to","author":"OOMOL","version":"1.0.3","services":["devto"],"icon":"https://static.oomol.com/logo/third-party/devto.svg"}

Dev.to

Operate Dev.to through your OOMOL-connected account. This skill calls the devto connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Dev.to. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "devto" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "devto" --action "<action_name>" --data '<json>' --json
  • --data takes a JSON object string or @path/to/file.json; omit it to send {}.
  • The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

  • create_article — Create a new Dev.to article. [write]
  • get_article — Get a Dev.to article by numeric id.
  • get_article_by_path — Get a Dev.to article by username and slug.
  • get_current_user — Get the current authenticated Dev.to user profile.
  • get_organization — Get Dev.to organization profile.
  • list_articles — List published Dev.to articles with query filters.
  • list_latest_articles — List latest Dev.to articles.
  • list_my_articles — List current user's own Dev.to articles by status.
  • list_organization_articles — List articles under a Dev.to organization.
  • list_tags — List Dev.to tags.
  • list_videos — List Dev.to videos.
  • update_article — Update an existing Dev.to article. [write]

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change Dev.to state — confirm the exact payload and effect with the user before running.
  • Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

  • oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

    curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux

    irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell

  • Not signed in / authentication error — sign in to your OOMOL account once:

    oo auth login

  • scope_missing / credential_expired / app_not_ready / app_not_found — Dev.to is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

    https://console.oomol.com/app-connections?provider=devto

  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources