Skip to content

A2: Skill freshness detection — stale skills serving wrong endpoints #113

@lekt9

Description

@lekt9

Problem: When a website updates its API surface, unbrowse's cached skills remain stale. Agents execute against deprecated endpoints, returning 404s or wrong data.

Evidence: docs/agent-experience-issues.md section A2

Proposed Fix: Add a last_validated_at timestamp to skills. Before executing, optionally validate the URL returns 200. If the URL returns 404/5xx, invalidate the cached skill and fall back to cold capture.

This directly supports the agent-experience-issues.md north star: reduce heuristic-based decisions, add self-repair via agent judgment on stale endpoints.

Connects to H1 (LinkedIn browser-open), H4 (server stability) as part of the self-repair loop.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions