feat: install one Webcmd discovery skill

[ankitranjan7]

Summary

• Moves runtime workflow skills from skills/ to skill-data/.
• Adds a single installable skills/webcmd discovery skill.
• Updates webcmd skills so agents can list runtime skills and load them with webcmd skills get <name>.
• Updates package publishing metadata to include skills/webcmd/** and skill-data/**.
• Updates tests for listing and reading runtime skill content.

Reasoning

The current repository shape causes generic skill installers to find multiple Webcmd skills and ask users to install them one by one. That creates friction and increases the always-visible skill list inside agent harnesses. The cleaner model is the one used by Agent Browser and now discussed by other CLI projects: install one small discovery skill, then let the installed CLI serve the detailed, version-matched instructions on demand.

This keeps the CLI and skill content coupled by version: when a user upgrades Webcmd, webcmd skills get webcmd-usage returns instructions matching that installed Webcmd version instead of stale copied markdown.

Industry practice followed

• One discovery skill for open agent harnesses instead of many always-registered workflow skills.
• Runtime skill content served by the CLI, matching Agent Browser-style skills list/get flows.
• Keep published package files explicit: installable skill under skills/, runtime data under skill-data/.
• Keep read backward-compatible while adding get for the more common CLI vocabulary.

Testing

• npx -y skills add . --list
• npm run dev -- skills list -f json
• npm run dev -- skills get webcmd-usage --json
• npm test -- src/skills.test.ts
• npm run typecheck
• npm pack --dry-run