Evidence URL Verifier

v1.0.0

Verify evidence URLs are real and accessible. Check that artifact links resolve to actual content, not placeholders.

0· 453· 1 versions· 0 current· 0 all-time· Updated 4m ago· MIT-0

Install

openclaw skills install evidence-url-verifier

Evidence URL Verifier

Verify evidence URLs are real and accessible.

Problem

Evidence links often:

  • Point to non-existent resources
  • Are placeholders (example.com)
  • Expire or get deleted
  • Don't match claimed content

Workflow

1. URL Validation

function Test-EvidenceUrl {
    param([string]$url)
    
    try {
        $response = Invoke-WebRequest -Uri $url -Method Head -TimeoutSec 10
        return @{
            Valid = $true
            Status = $response.StatusCode
            ContentType = $response.ContentType
        }
    } catch {
        return @{
            Valid = $false
            Error = $_.Exception.Message
        }
    }
}

# Usage
$result = Test-EvidenceUrl "https://example.com/artifact"
if ($result.Valid) {
    Write-Host "URL valid: $($result.Status)"
} else {
    Write-Error "URL invalid: $($result.Error)"
}

2. Content Verification

# Check URL matches claimed content type
$response = Invoke-WebRequest -Uri $url
if ($response.ContentType -notlike "text/*" -and $expectedType -eq "text") {
    Write-Warning "Content type mismatch"
}

# Check for placeholder text
$content = $response.Content
if ($content -match "lorem ipsum|placeholder|example") {
    Write-Warning "Content appears to be placeholder"
}

3. Artifact Existence

# For local paths
if (Test-Path $artifactPath) {
    $size = (Get-Item $artifactPath).Length
    if ($size -eq 0) {
        Write-Warning "Artifact file is empty"
    }
} else {
    Write-Error "Artifact not found: $artifactPath"
}

Executable Completion Criteria

CriteriaVerification
URL resolvesHTTP 200 response
Content matchesType matches expected
No placeholdersContent is substantive
Local paths existTest-Path returns true

Privacy/Safety

  • Don't log full URL contents
  • Redact sensitive data in responses
  • Respect rate limits (max 1 req/sec)

Self-Use Trigger

Use when:

  • Task claims evidence artifact
  • URL provided as proof
  • Before marking task complete
  • Audit of past completions

Verify evidence. Trust but confirm.

Version tags

latestvk97akjm801vjhj8qtswpj90xah822817