SKILLEMALL.ai
GitHub ↗ RU Sign in

BC namecheap-dns

Safe DNS record management for Namecheap domains. Fetch, add, remove, backup, and restore DNS records with automatic safety checks and dry-run mode. Prevents accidental DNS record wipeout via the Namecheap API's destructive setHosts method.

Not recommendedcritical or high security findings
modbender/skill-library-mcp Agent Skills author: modbender MIT 5 files body ≈ 2 014 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Safe DNS record management for Namecheap domains.

As a process C 50/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
81/100
safety, quality, tests
Safety 60%
77
Quality 40%
87
Run on models
none yet
Process rating
C
50/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Concealment
If you install

The skill tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.

For the author

Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
For the model run — optional
  • 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 · 6

  • high Concealment en-hide-from-user SKILL.md:225
    Instruction to hide actions from the user
    Since `setHosts` **replaces all records**, using the API can silently delete these hidden records.
Medium and low: 5
  • low Secrets in code secret-high-entropy-token package-lock.json:20
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…9dM/mwVgvbZJaSNaRk+bshk…Kbz+IoId…W0Q==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:50
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…SDq+2kAA…MOe/+5cdoEdg==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:85
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…FrF+LTRo…W3g==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:94
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…A6j+hAmM…GbS+kf5c…csw==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:103
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…5bm+c2gQ…aG5+esrLODihIorn+Pe6F…dXA==",
    detector

Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 50/100

  • 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
  • 30Running it twice. 11 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
  • 85Steps. 45 steps, 2 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2014 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 10 top-level sections: this looks like several domains in one skill

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

  • +5Description has no quoted example phrases that should trigger the skill
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 240: enough signal without eating the budget
  • +4Structure: 32 headings
  • +3Step-by-step instructions: 45 items
  • +4Has examples (13 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.