Library to work against complex domain names, subdomains and URIs
82
Pending
Does it follow best practices?
Impact
82%
1.03xAverage score across 10 eval scenarios
Pending
The risk profile of this skill
{
"context": "This criteria evaluates how effectively the engineer uses the tldts library to extract and process hostnames from URLs. The focus is on correct usage of tldts functions for hostname extraction, IP detection, and proper handling of the library's return types.",
"type": "weighted_checklist",
"checklist": [
{
"name": "getHostname usage",
"description": "Uses tldts's getHostname() function to extract hostnames from URLs in the normalizeHostname function",
"max_score": 30
},
{
"name": "IP detection",
"description": "Uses tldts's parse() function with isIp field or similar mechanism to detect and return null for IP addresses",
"max_score": 20
},
{
"name": "Batch processing",
"description": "Correctly applies tldts functions (getHostname or parse) to process arrays of URLs in normalizeHostnames function",
"max_score": 15
},
{
"name": "Hostname validation",
"description": "Properly handles tldts return values including null/empty results for invalid URLs",
"max_score": 15
},
{
"name": "Grouping implementation",
"description": "Uses tldts hostname extraction functions to implement the groupByHostname functionality correctly",
"max_score": 15
},
{
"name": "Options usage",
"description": "Demonstrates appropriate use of tldts options if needed (e.g., detectIp, extractHostname, or validateHostname options)",
"max_score": 5
}
]
}docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10