CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

publish-site-custom-domain

Publish a finished website or connect a hosted preview to a custom domain using Add Domain. Use when the owner wants to put HTML online, share a client preview, update a public site at the same URL, or buy and connect a domain for a ready project.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an exemplar of lean, operational instruction writing: a tight five-step workflow with concrete API calls, verification checkpoints at every phase, explicit pending-state handling, and a handover checklist. The only soft spot is the connect-and-verify step, where host-specific actions (adding the hostname, enabling HTTPS) are delegated to the referenced platforms page rather than given concretely.

DimensionReasoningScore

Conciseness

The body is lean and telegraphic ("A registry timeout is unknown.", "A link click alone does not confirm a purchase.") with no explanations of concepts Claude already knows and no padding; every clause carries operational weight. It matches anchor 5 rather than anchor 4 because nothing is clearly trimmable.

5 / 5

Actionability

The two API calls are copy-paste ready with exact URLs, query parameters, and source labels ("GET https://www.adddomain.net/api/check?name=LABEL&tlds=com,si,ai&src=publish-skill"), and Netlify Drop's URL is given. The connection step is less executable ("Add the chosen hostname in that project's domain settings", "Open HTTPS on the chosen hostname" lacks a concrete mechanism), fitting anchor 4's "minor gaps" rather than anchor 5.

4 / 5

Workflow Clarity

A clearly sequenced 5-step process with explicit validation checkpoints ("verify a stylesheet or image and the primary interaction", "verify the expected records through public DNS", "compare the page and an asset with the preview"), pending-state error handling ("Report the exact pending check if DNS, certificate or content is still pending"), an early exit condition, and a final handover checklist. This matches anchor 5's explicit validation with error-recovery guidance; anchor 4 would require missing checkpoints, which are absent.

5 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, with no bundle files and no need for external references; the body is well organized into a short intro, five bold-titled numbered steps, and a closing note. Per the simple-skill guideline, this scores 5 on organization alone, and the one external pointer (https://www.adddomain.net/platforms#hosting) is a live resource that appropriately cannot be bundled.

5 / 5

Total

19

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states concrete capabilities in third person and pairs them with an explicit, multi-scenario "Use when" clause full of natural trigger phrases. The only weakness is slightly incomplete synonym coverage (e.g., no "deploy" or "go live").

DimensionReasoningScore

Specificity

Quotes like "Publish a finished website or connect a hosted preview to a custom domain" and the when-clause actions ("put HTML online", "share a client preview", "update a public site at the same URL", "buy and connect a domain") list several concrete actions. Minor gaps (no mention of DNS setup or verification) keep it below the comprehensive anchor 5, but it exceeds the 1-2 actions of anchor 3.

4 / 5

Completeness

The description gives a clear "what" ("Publish a finished website or connect a hosted preview to a custom domain using Add Domain") and an explicit "Use when..." clause with four concrete trigger scenarios. This clearly matches anchor 5; the when-clause is fully explicit, so anchor 4's qualifier does not apply.

5 / 5

Trigger Term Quality

Natural phrases users would say include "put HTML online", "share a client preview", "custom domain", and "buy and connect a domain". Coverage is good but misses common synonyms such as "deploy", "go live", or "web hosting", so it fits anchor 4 rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

"using Add Domain" names the specific service and triggers like "custom domain", "client preview", and "buy... a domain" carve out a clear niche with distinct triggers. Overlap with generic deploy/publish skills is possible but minimal, matching anchor 5's "clear niche with distinct triggers" better than anchor 4's "minor overlap risk".

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

vitaliiphangan-code/add-domain-website-skills

Path

skills/publish-site-custom-domain/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.