AC domain-cma-valuation
Apply the substitution principle to position a compound or keyword-plus-modifier domain within the current asking-price market. Build a Comparative Market Analysis from verified, currently for-sale domains that are credible substitutes in the same value-bearing keyword market, then adjust for TLD, keyword position, length, modifier quality, and linguistic coherence. Use when a user asks what such a domain is worth, wants a competitive listing-positioning range, or needs current replacement-market context for buying or selling. Do not use historical sale prices to set or calibrate the range. Treat exact single-keyword domains, pure short domains, coined names without a shared keyword market, fixed-target buyer situations, and domains with active operating websites as out of scope. Do not use for technical analysis (use domain-analyze) or availability checks (use available).
Apply the substitution principle to position a compound or keyword-plus-modifier domain within the current asking-price market.
As a process C 61/100 · Has gaps — weak spots: inputs and preconditions, running it twice, progress reporting
How to improve
- 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
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 61/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 4420 tokens
- 85Steps. 70 steps, 1 vague phrases
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 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
- +5Description has no quoted example phrases that should trigger the skill
- +3Description length 885: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 12 headings
- +3Step-by-step instructions: 70 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.