Agent skill

DDNS Provider Development

Adds or changes a DNS provider in the DDNS project while keeping its code, schemas, tests and Chinese and English docs consistent.

MITAuto-check passedDevelopment

Install DDNS Provider Development

skills CLI

$ npx skills add NewFuture/DDNS --skill provider-development -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install NewFuture/DDNS provider-development --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/NewFuture/DDNS.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/provider-development .claude/skills/provider-development && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "provider-development" agent skill from https://github.com/NewFuture/DDNS/tree/master/.agents/skills/provider-development into .claude/skills/provider-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "provider-development", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/NewFuture/DDNS/tree/master/.agents/skills/provider-development

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add NewFuture/DDNS --skill provider-development -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install NewFuture/DDNS provider-development --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NewFuture/DDNS.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/provider-development .agents/skills/provider-development && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "provider-development" agent skill from https://github.com/NewFuture/DDNS/tree/master/.agents/skills/provider-development into .agents/skills/provider-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "provider-development", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add NewFuture/DDNS --skill provider-development -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install NewFuture/DDNS provider-development --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NewFuture/DDNS.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/provider-development .cursor/skills/provider-development && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "provider-development" agent skill from https://github.com/NewFuture/DDNS/tree/master/.agents/skills/provider-development into .cursor/skills/provider-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "provider-development", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/NewFuture/DDNS.git --path .agents/skills/provider-development

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add NewFuture/DDNS --skill provider-development -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install NewFuture/DDNS provider-development --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NewFuture/DDNS.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/provider-development .gemini/skills/provider-development && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "provider-development" agent skill from https://github.com/NewFuture/DDNS/tree/master/.agents/skills/provider-development into .gemini/skills/provider-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "provider-development", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install NewFuture/DDNS provider-development

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add NewFuture/DDNS --skill provider-development -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/NewFuture/DDNS.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/provider-development .github/skills/provider-development && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "provider-development" agent skill from https://github.com/NewFuture/DDNS/tree/master/.agents/skills/provider-development into .github/skills/provider-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "provider-development", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add NewFuture/DDNS --skill provider-development -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install NewFuture/DDNS provider-development --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NewFuture/DDNS.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/provider-development .opencode/skills/provider-development && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "provider-development" agent skill from https://github.com/NewFuture/DDNS/tree/master/.agents/skills/provider-development into .opencode/skills/provider-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "provider-development", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: provider-development
GitHub stars: 4.7k
Token cost: ~558 tokens
SKILL.md length: 222 words
Files: 1
Skills in repo: 4
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Adds or changes a DNS provider in the DDNS project while keeping its code, schemas, tests and Chinese and English docs consistent.

Works in 7 steps: Read the root AGENTS.md,… → Research the provider's official API… → Choose BaseProvider for APIs that query… → …
Adding support for a new DNS provider to DDNS
Calls ruff, python and npm
Changing how an existing provider authenticates or updates records

What it does

The agent first reads the root and provider AGENTS.md files, the nearest similar provider and its tests, then researches the provider's official API documentation. It records the authentication shape, permission scope, endpoints, zone and record lookup, create and update behavior, record types and TTL or route limits, without using credentials or changing any live DNS record.

It chooses BaseProvider for APIs that look up zones and records before writing, and SimpleProvider only for direct update-only APIs, reusing _http(), masking, response handling and standard-library patterns that stay compatible with Python 2.7. The provider ID and aliases are registered in ddns/provider/__init__.py, and ddns/config/field-model.json, both provider and dns enums in schema/v4.1.json and every --dns CLI choice are updated. Mocked tests cover requests, responses, matching and failures with no network.

Documentation goes under docs/providers and docs/en/providers in both languages, with provider indexes, locale navigation and llms.txt updated. Verification runs the provider's unittest module and ruff check and format, then the full test and lint run, and the docs build if its dependencies are already installed. The agent reports changed files and any check it skipped, and does not install dependencies, publish or change repository settings.

When your agent uses it

Adding support for a new DNS provider to DDNS
Changing how an existing provider authenticates or updates records
Keeping provider schemas, CLI choices and bilingual docs in step
Writing mocked provider tests that need no network or real credentials

Example prompts

“Add a DDNS provider for a new DNS service, starting from its official API docs.”
“Change how the Cloudflare provider updates records, then refresh its tests and docs.”
“Write the Chinese and English docs for the new provider and update the provider index.”

Requirements

A checkout of the NewFuture/DDNS repository
Python with unittest and ruff
npm for the optional docs build

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

Read the root AGENTS.md, ddns/provider/AGENTS.md, the nearest similar
Research the provider's official API documentation. Record the
Choose BaseProvider for APIs that query zones and records before creating
Register the canonical provider ID and intentional aliases in
Add deterministic mocked provider tests. Cover the supported request and
Add equivalent Chinese and English provider documentation under
Verify with focused checks

What it can do on your machine

Read from SKILL.md and the folder at commit 1c17f4e. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- ruff
- python
- npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

DDNS Provider Development loads about 558 tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 222 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~38
When it runs · the whole SKILL.md, loaded when a task matches: ~558

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NewFuture/DDNS at commit 1c17f4e, republished under its MIT licence (© NewFuture). 222 words, ~558 tokens.

Download SKILL.mdSave it as .claude/skills/provider-development/SKILL.md (or your agent's skills folder).

name: provider-development
description: Implement or modify a DDNS DNS provider while keeping its code, metadata, schemas, tests, and bilingual documentation consistent.

Provider Development

Read the root AGENTS.md, ddns/provider/AGENTS.md, the nearest similar provider, its tests, and the affected configuration and documentation files.
Research the provider's official API documentation. Record the authentication shape, permission scope, endpoints, zone and record lookup behavior, record create/update behavior, supported record types, and TTL/route constraints. Do not use credentials or mutate a live DNS record.
Choose BaseProvider for APIs that query zones and records before creating or updating them; choose SimpleProvider only for direct update-only APIs. Reuse _http(), masking, response handling, and Python 2.7-compatible standard-library patterns from adjacent providers.
Register the canonical provider ID and intentional aliases in ddns/provider/__init__.py. Update ddns/config/field-model.json, both provider and dns enums in schema/v4.1.json, and every --dns CLI choice surface.
Add deterministic mocked provider tests. Cover the supported request and response paths, matching behavior, and failures without network access or real credentials.
Add equivalent Chinese and English provider documentation under docs/providers/ and docs/en/providers/. Keep configuration keys, provider IDs, permissions, and examples aligned. Update the provider indexes, locale navigation in docs/.vitepress/config.mts, and docs/llms.txt.
Verify with focused checks:
sh
```
python -m unittest tests.test_provider_<provider> -v
ruff check ddns/provider/<provider>.py tests/test_provider_<provider>.py
ruff format --check ddns/provider/<provider>.py tests/test_provider_<provider>.py
```
Then run python -m unittest discover tests -v, ruff check ., and ruff format --check .. When documentation dependencies are already available, run npm --prefix docs run build. Report changed files and any validation not run. Do not install dependencies, publish, or change repository settings.

Files

Just SKILL.md in .agents/skills/provider-development of NewFuture/DDNS.

Open the folder on GitHubat commit 1c17f4e

Compare with similar skills

DDNS Provider Development next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

DDNS Provider Development compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
DDNS Provider Development this skillNewFuture/DDNS	4.7k	—	~558	Automated safety check: Pass	MIT	yesterday
Adk Stylegoogle/adk-python	22k	—	~748	Automated safety check: Pass	Apache-2.0	today
Kedro Babysitkedro-org/kedro	11k	—	~4k	Automated safety check: Pass	Custom licence	yesterday
Python ProJeffallan/claude-skills	12k	—	~1.6k	Automated safety check: Pass	MIT	4 days ago
Modern Pythonantoinebou12/uml-mcp	105	—	~1k	Automated safety check: Pass	MIT	yesterday
Specx Project Toolingmaksimzayats/specx	202	—	~965	Automated safety check: Pass	MIT	2 mo ago

Similar skills

Adk Style
google/adk-python
Official
Python style and codebase conventions for ADK (Agent Development Kit): private-by-default file visibility, imports, type hints, Pydantic v2 models, formatting, docstrings, logging, async I/O, file…
22k GitHub stars~748 tokensUpdated today
DevelopmentAuto-check passed
Kedro Babysit
kedro-org/kedro
Run Kedro's local lint / format / type-check / tests on changed files (uses the project's pre-commit hooks, ruff, mypy, pytest, lint-imports, detect-secrets, Make targets — in the right venv), or…
11k GitHub stars~4k tokensUpdated yesterday
DevelopmentAuto-check passed
Python Pro
Jeffallan/claude-skills
Writes type-annotated Python 3.11+ with async patterns, dataclasses and pytest suites, validated with mypy in strict mode, black and ruff.
12k GitHub stars~1.6k tokensUpdated 4 days ago
DevelopmentAuto-check passed
Modern Python
antoinebou12/uml-mcp
Modern Python tooling and best practices using uv, ruff, ty, and pytest.
105 GitHub stars~1k tokensUpdated yesterday
DevelopmentAuto-check passed
Specx Project Tooling
maksimzayats/specx
Add strict Python project tooling for a specx service. An agent skill from maksimzayats/specx.
202 GitHub stars~965 tokensUpdated 2 mo ago
DevelopmentAuto-check passed
Python Code Style
wshobson/agents
Python code style, linting, formatting, naming conventions, and documentation standards.
40k GitHub stars~2k tokensUpdated 3 days ago
DevelopmentAuto-check passed

Questions about DDNS Provider Development

What does DDNS Provider Development do?

Adds or changes a DNS provider in the DDNS project while keeping its code, schemas, tests and Chinese and English docs consistent. md files, the nearest similar provider and its tests, then researches the provider's official API documentation. It records the authentication shape, permission scope, endpoints, zone and record lookup, create and update behavior, record types and TTL or route limits, without using credentials or changing any live DNS record.

When should I use DDNS Provider Development?

DDNS Provider Development fits situations like: adding support for a new DNS provider to DDNS; changing how an existing provider authenticates or updates records; keeping provider schemas, CLI choices and bilingual docs in step; writing mocked provider tests that need no network or real credentials.

How do I install DDNS Provider Development in Claude Code?

Run `npx skills add NewFuture/DDNS --skill provider-development -a claude-code`. Or copy the skill folder (.agents/skills/provider-development in NewFuture/DDNS) into .claude/skills/provider-development in your project. Claude Code loads it when a task matches its description.

How do I install DDNS Provider Development in Codex?

Run `npx skills add NewFuture/DDNS --skill provider-development -a codex`. Or copy the skill folder (.agents/skills/provider-development in NewFuture/DDNS) into .agents/skills/provider-development in your project. Codex loads it when a task matches its description.

Can I use DDNS Provider Development in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NewFuture/DDNS --skill provider-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/provider-development, .gemini/skills/provider-development, .github/skills/provider-development and .opencode/skills/provider-development in your project.

What does DDNS Provider Development need to run?

Going by SKILL.md and its folder, DDNS Provider Development needs the command-line tools its instructions call (ruff, python and npm). Our summary lists: A checkout of the NewFuture/DDNS repository; Python with unittest and ruff; npm for the optional docs build.

Does DDNS Provider Development access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is DDNS Provider Development safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does DDNS Provider Development use?

DDNS Provider Development is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does DDNS Provider Development use?

About 558 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to DDNS Provider Development?

Skills that share tags, products or a category with DDNS Provider Development: Adk Style (google/adk-python, 22k stars), Kedro Babysit (kedro-org/kedro, 11k stars), Python Pro (Jeffallan/claude-skills, 12k stars) and Modern Python (antoinebou12/uml-mcp, 105 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains DDNS Provider Development?

NewFuture (a GitHub user) maintains it in NewFuture/DDNS, which has 4,696 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.

Source: NewFuture/DDNS on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

DDNS Provider Development

Install DDNS Provider Development

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Provider Development

Files

Compare with similar skills

Similar skills

Adk Style

Kedro Babysit

Python Pro

Modern Python

Specx Project Tooling

Python Code Style

More from NewFuture/DDNS

DDNS VitePress Docs Maintenance

DDNS Build and Release Maintenance

CI Failure Triage

Questions about DDNS Provider Development

Install DDNS Provider Development

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Provider Development

Files

Compare with similar skills

Similar skills

More from NewFuture/DDNS

Related

Questions about DDNS Provider Development