Open Skills API

{
  "service_type": "platform",
  "base_url": "http://www.dataatwork.org",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "free",
    "details": {
      "notes": "Open Skills API appears to be a freely available open data initiative related to workforce skills data."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "canonical skills taxonomy",
    "emerging skills tracking",
    "knowledge and abilities mapping",
    "tools and technologies relationships",
    "job-skill relationship data",
    "standardized data store"
  ],
  "raw_analysis": "The Open Skills API, accessible via dataatwork.org, is described as a complete and standard data store for canonical and emerging skills, knowledge, abilities, tools, technologies, and their relationships to jobs. It is categorized under data, api, and edge.\n\nNature of the platform: This appears to be an open data platform aimed at providing a standardized taxonomy and dataset of workforce skills. It is likely intended for developers, data scientists, HR tech companies, educational institutions, and researchers who need to map skills to jobs or build applications around skill taxonomies.\n\nMaturity: The description suggests it is a well-defined data store, but no explicit information about versioning, uptime, or support is given. The term 'Open Skills API' implies a public API, but the provided URL points to a website that may host the API or documentation.\n\nAPI details: The auth method is likely 'none' given the open nature, but this is an assumption. Endpoints are not specified in the provided content, so they remain empty. The base URL is http://www.dataatwork.org, though the actual API might be served under a different subdomain or path.\n\nPricing: The service is likely free, as it is described as an open data store. However, no explicit pricing information is provided.\n\nIntegrations: No specific integrations are mentioned, but the API could be integrated into HR systems, learning platforms, job boards, and analytics tools.\n\nOverall, this is a niche but valuable resource for skills data, and the analysis is based on limited public information. Further exploration of the website would be needed to confirm API specifics."
}

2/3 tests passed

```json
{
  "overall": 58,
  "dimensions": {
    "token_efficiency": 6.5,
    "first_try_success": 5.5,
    "response_parseability": 7.0,
    "error_clarity": 5.0,
    "doc_quality": 5.5,
    "auth_simplicity": 8.0,
    "latency": 6.5,
    "consistency": 5.5
  },
  "pricing_normalized": {
    "model": "free",
    "notes": "Open Skills API appears to be a freely available open data initiative — no paywall, no enterprise gate."
  },
  "issues": [
    "Homepage title reads 'Baccarat: Punto Banco Guide' — strong signal of domain hijack, squatting, or SEO spam. Critical trust issue for an 'open skills data' platform.",
    "No llms.txt (404) — agents have no machine-readable entry point describing the platform capabilities or endpoints.",
    "Missing security headers on all responses (HSTS, CSP, X-Content-Type-Options, etc.).",
    "canonical URL points to dataatwork.org while the served content diverges — inconsistent branding and origin.",
    "No structured data preview returned in checks — capability claims cannot be verified against an actual API surface (e.g., endpoint list, schemas).",
    "Response latency ~600–900ms is acceptable but not snappy for an API-first data store.",
    "No llms.txt or OpenAPI/Swagger discoverable path in checks reduces agent 'first-try success'."
  ],
  "recommendations": [
    "Fix the domain: remove the baccarat/spam homepage and serve a legitimate landing page explaining Open Skills taxonomy, endpoints, and licensing.",
    "Publish /llms.txt or an OpenAPI spec with endpoint schemas so agents can plan calls without human docs parsing.",
    "Add standard security headers (HSTS, CSP, X-Frame-Options, X-Content-Type-Options) to build trust.",
    "Provide a canonical, stable base URL and align canonical/meta with actual served content.",
    "Ship a quickstart with cURL + JSON examples for at least: skills lookup, skill relationships, and job-skill mappings.",
    "Expose a versioned JSON schema for the taxonomy so responses are reliably parseable.",
    "Add a /status or health page to bolster consistency perception.",
    "Reduce p95 latency below 500ms if the target consumer is agents making many lookups."
  ]
}
```