skills: make web fetch the first fetch path

[ankitranjan7]

Description

Clarifies the skill-guidance portion of #374 for known URL and source-page fetches: agents should use webcmd web fetch --url <url> as the first-choice Webcmd fetch path before browser escalation or non-Webcmd HTTP clients.

The paired product PR supplies CLI/list/help discoverability. This documentation-only PR positions the agent workflow and does not independently fix or close #374.

Dated author-only learnings are retained in skill-src/**/*.src.md and stripped by LitPrompt from the published skills/**/*.md files. They record the baseline evaluation evidence, browser-escalation gate, and corrected TLS-retry claim without adding runtime-agent context.

Related issue: #374

Type of Change

• 🐛 Bug fix
• ✨ New feature
• 🌐 New site adapter
• 📝 Documentation
• ♻️ Refactor
• 🔧 CI / build / tooling

Checklist

• I ran the checks relevant to this PR
• I updated tests or docs if needed
• I included output or screenshots when useful
• If I edited skill-src/, I ran make build and committed skills/

Adapter Notes

• Updated generated or lean docs when command discoverability changed
• Used positional args for the command primary subject unless a named flag is clearly better
• Normalized expected adapter failures to CliError subclasses instead of raw Error

Screenshots / Output

make build: ok: built 21 file(s)
make check: ok: 21 file(s) checked
make verify: ok: no orphaned published files; no SKILL.md inside skill-src; published files are in sync
quick_validate.py skills/smart-search: Skill is valid!
quick_validate.py skills/webcmd-usage: Skill is valid!
npm test -- src/skills.test.ts: 15 passed

[github-actions]

🟠 Maintainer review suggested — low confidence

The automated review could not reach a fully supported conclusion.

Limitations

• The automated review returned an invalid structured result.

This review is advisory and does not block merging.

[beubax]

Slight modification needed. This must be the go-to first choice fetch option for the agent. We must position ourselves this way in the skill. Don't position as a fallback for when other fetch options fail, make sure the agent tries this first and then the browser.