$ ~/registry/skill/composiohq-composio-skills-nextdns-automation

SKILL

nextdns-automation

Name: nextdns-automation
Author: Composio

Automate NextDNS queries, configuration, and management tasks through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill itself is an open-source prompt/instruction artifact with no direct local secret requirement, no declared code execution, and no fixed outbound endpoint in the material, so the baseline risk is low. However, it is designed around external Rube MCP/Composio/NextDNS connectivity and remote tool execution, so actual use still involves third-party authorization and data flow that should be verified.

CredentialsCaution

The material says 'No API keys needed,' but it also requires an active Nextdns connection via `RUBE_MANAGE_CONNECTIONS` and completion of an auth link. This implies reliance on third-party account authorization/connection tokens that are abstracted away from the skill layer, creating normal delegated-credential and misconfiguration risk.

Network egressCaution

The instructions require adding `https://rube.app/mcp` as an MCP server and reference the Composio/NextDNS toolchain. Although the system field lists no fixed host, the README confirms interaction with remote Rube/Composio services, and task arguments/session data may traverse that path, which is a typical egress pattern for this class of tool.

Code executionLow risk

The system flags this as prompt-only, and the content is mainly workflow guidance and tool invocation order. It does not ask for local executable installation, script execution, or system-level command privileges; the material refers to remote MCP tool use rather than local code execution.

Data accessCaution

This skill targets NextDNS operational tasks and executes discovered tools through Rube/Composio. While it does not declare local file read/write access, it will access NextDNS account-related configurations/resources and may process session data, pagination results, and operation arguments. No request for local data permissions beyond the stated purpose is evident.

Supply chainLow risk

The source is an open GitHub repository, the system marks it as open-source, and community adoption is high (64.7k stars), all of which materially lower risk. Note that this repository appears to be a skill collection rather than the full backend implementation for this specific function, and the README depends on external Rube MCP/Composio services; maintenance status is unknown, so external service documentation should still be reviewed.

Recommendations

Before connecting, verify the data flow, log retention, and authorization scope across `rube.app/mcp`, Composio, and NextDNS.
Use a least-privilege NextDNS account or test environment for authorization instead of granting full production control.
Review the external MCP server and toolkit documentation to confirm actual endpoints, operation scope, and auditability.
If used for sensitive DNS configuration, validate the available tool list and parameter schema in an isolated environment first.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "nextdns-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/nextdns-automation/SKILL.md
2. Save it as ~/.claude/skills/nextdns-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Nextdns Automation via Rube MCP

Automate Nextdns operations through Composio's Nextdns toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/nextdns

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Nextdns connection via RUBE_MANAGE_CONNECTIONS with toolkit nextdns
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit nextdns
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Nextdns operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Nextdns task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["nextdns"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Nextdns-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `nextdns`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Automate Moz SEO tasks via Rube MCP using current tool schemas first.

ComposioGet→

$ loading_