AF ddns-updator
Dynamic DNS updater for self-hosted / homelab / edge devices. Detects the device's public IPv4 and IPv6 addresses via public APIs (ipify, ifconfig.me, icanhazip), compares them against the last-known addresses, and pushes updates to the configured DDNS provider (currently dynv6, with an extensible provider architecture). Trigger by telling the agent: - "Update my DDNS" / "Check and update DNS" / "Run DDNS" - "What's my public IP?" / "Check my IP address" - Any request that involves current public IP or DDNS synchronization Supported providers: dynv6 (default). DuckDNS, Cloudflare, and No-IP APIs are documented in references/providers.md for easy extension. Security: sensitive tokens are stored in a chmod-600 config file at ~/.config/picoclaw-ddns/config.json, outside the skill directory.
Dynamic DNS updater for self-hosted / homelab / edge devices.
As a process F 38/100 · Will not run — References files that are not bundled: scripts/ddns.sh, scripts/get_ip.sh, scripts/update_dynv6.sh
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/ddns.sh - warning
missing-refreference to a missing file: scripts/get_ip.sh - warning
missing-refreference to a missing file: scripts/update_dynv6.sh - warning
missing-refreference to a missing file: references/providers.md - warning
missing-refreference to a missing file: scripts/update_<provider>.sh
Process rating: all ten parameters 38/100
- 0Tools and files. 5 referenced file(s) missing: scripts/ddns.sh, scripts/get_ip.sh, scripts/update_dynv6.sh
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 8 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1103 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 801: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +4Structure: 16 headings
- +3Step-by-step instructions: 8 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.