菜单
Implement or modify a DDNS DNS provider while keeping its code, metadata, schemas, tests, and bilingual documentation consistent.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/NewFuture/DDNS --skill provider-development命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Maintain DDNS GitHub Actions, Docker and Nuitka builds, packaging, installer validation, and release preparation while preserving matrices, caches, and protected publishing.
Diagnose and fix required CI failures for the current DDNS branch without weakening tests, platform coverage, caches, or repository policy.
Maintain DDNS VitePress documentation with bilingual parity, correct navigation and links, safe executable-doc changes, and build verification.
基于 SOC 职业分类
正在显示 SKILL.md
| name | provider-development |
| description | Implement or modify a DDNS DNS provider while keeping its code, metadata, schemas, tests, and bilingual documentation consistent. |
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:
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.