web-skills-protocollisted

# Web Skills Protocol — Agent Skill When a user asks you to interact with a website, **check for published skills first** before attempting to scrape HTML, guess at UI elements, or reverse-engineer APIs. ## Discovery Workflow ### Step 1: Check for skills.txt Fetch `{origin}/skills.txt` (e.g., `https://bobs-store.com/skills.txt`). - **200 response** → Parse it. Proceed to Step 3. - **404 response** → Go to Step 2. ### Step 2: Check for agents.txt (fallback) Fetch `{origin}/agents.txt`. - **200 response** → Parse it. Proceed to Step 3. - **Both 404** → The site does not support WSP. Fall back to normal browsing/scraping. ### Step 3: Parse the discovery file The discovery file is Markdown with this structure: ``` # Site Name > Brief description of the site. General notes (auth info, rate limits, etc.) ## Skills - [Skill Name](/skills/skill-name/SKILL.md): What the skill does ## Optional - [Extra Skill](/skills/extra/SKILL.md): Less important skills ``` Extract: 1. **Site description** (the blockquote) — context for understanding the site 2. **General notes** (prose paragraphs) — auth overview, rate limits, terms 3. **Skill entries** — each `- [Name](url): description` line is one skill ### Step 4: Match user intent to a skill Compare the user's request against each skill's description. Pick the best match. - If the user's intent clearly matches one skill → fetch that SKILL.md - If the intent could match multiple skills → fetch all candidates, pick the best fit -