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.

Category: Social. Exposes 12 action(s).

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 below links to a reference file with its purpose and exact commands. Read the linked file, then fetch the live schema with oo connector schema before constructing --data.

Available actions

• create_article — Create a new Dev.to article.
• 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.

Safety

• Read actions (get / list / search) are safe to run directly.
• Create, update, send, or post actions change Dev.to state — confirm the exact payload and effect with the user before running.
• Delete or remove actions are destructive — 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>):

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

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

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

bash 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:

text 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

• Dev.to homepage: https://dev.to