Remove install-script workaround once vercel-labs/skills#743 lands

[jdevera]

Context

bin/restore-skills is a thin wrapper that re-issues skills add … -g -s … -y per entry in .skill-lock.json. It works around an architectural gap in the skills CLI: there is no command to restore global skills from the global lockfile (experimental_install only reads the project-scoped skills-lock.json).

The fix is in flight upstream as vercel-labs/skills#743 — feat: add global restore/relink from .skill-lock.json. It adds experimental_install -g. CI is green, but as of filing this issue the PR is unreviewed, has merge conflicts, and no maintainer has engaged despite four user pings.

When to remove

Once a skills npm release ships that contains PR #743 (subscribed for notifications).

Removal checklist

1. Confirm the skills release containing PR #743 is on npm.
2. git rm bin/restore-skills.
3. In site/install, replace "$DOTAGENTS_DIR/bin/restore-skills" with:

   ( cd "$DOTAGENTS_DIR" && npx --yes skills experimental_install -g )

4. In README.md, replace ./bin/restore-skills in the manual flow with npx skills experimental_install -g, drop the explanatory paragraph about the workaround, and remove the bin/restore-skills row from the "What lives here" table.
5. Re-run shellcheck -s sh site/install to confirm POSIX cleanliness.
6. Verify on a clean machine that the one-liner restores skills end-to-end.

Upstream tracking

• [Feature]: global restore/relink from ~/.agents/.skill-lock.json for canonical skills + agent links vercel-labs/skills#683 — feature request
• feat: add global restore/relink from .skill-lock.json vercel-labs/skills#743 — pull request implementing it