SKILLEMALL.ai
GitHub ↗ RU Sign in

BB domain-strategy

Plan, manage, and optimize a domain portfolio. Use this skill for DNS architecture decisions, redirect strategies, registrar choice, parking unused domains, multi-site setups, and domain consolidation or split planning. Triggers on DNS, domain, registrar, redirect, parking, subdomain, apex, www vs non-www, multi-site, portfolio, hreflang setup, domain migration. Also triggers when planning a new site that needs domain decisions made before launch.

rampstackco/claude-skills Agent Skills author: rampstackco 2 files body ≈ 2 045 tokens Open the sourcegithub.com↗ analyzed 9 h ago

Plan, manage, and optimize a domain portfolio.

As a process B 68/100 · Nearly there — weak spots: running it twice, progress reporting

ProcedureOperations and projectstype and topics are labelled automatically from the skill text
Runs in: 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) OpenClaw Goose OpenCode
JSON
Technical rating
B
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
B
68/100
Nearly there
Progress reporting w 2
0
Running it twice w 4
30
Failures and branches w 10
50
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: domain-strategy (rampstackco/claude-skills)

How to improve

    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 · 0

    ✓ No critical or high findings

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

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "catalog_summary"
    • note frontmatter-key unknown frontmatter key "display_order"

    Process rating: all ten parameters 68/100

    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 3 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 85Steps. 65 steps, 1 vague phrases
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2045 tokens

    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
    • +4Description does not say when NOT to use the skill (false activations)
    • +4No input/output examples
    • -5TODO / placeholder text left in the skill
    • +1No license
    • +2Single-language instructions
    • +3Description length 451: enough signal without eating the budget
    • +4Structure: 21 headings
    • +3Step-by-step instructions: 65 items
    • +3Output format is stated explicitly
    • +4Reference files are cited in the instructions (1 of 1)

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