fix: resolve ClaWHub suspicious flag on manifest skill

[SebConejo]

Summary

• Add metadata frontmatter with requires.bins: ["openclaw"] so ClaWHub knows the skill depends on the OpenClaw CLI
• Fix Step 5 command from openclaw gateway install to openclaw gateway restart
• Add user confirmation prompts before every bash command execution
• Disclose API key storage location (~/.openclaw/openclaw.json) in Step 3

Test plan

• Verify ClaWHub no longer flags the skill as suspicious after republish
• Confirm openclaw gateway restart is the correct command per plugin README

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.58%. Comparing base (6d6cc96) to head (6bd873c).
⚠️ Report is 8 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #839      +/-   ##
==========================================
+ Coverage   91.38%   92.58%   +1.19%     
==========================================
  Files         177      183       +6     
  Lines        6968     7372     +404     
  Branches     1895     2042     +147     
==========================================
+ Hits         6368     6825     +457     
+ Misses        488      435      -53     
  Partials      112      112              

Flag	Coverage Δ
backend	92.80% <ø> (-0.18%)	⬇️
frontend	94.22% <ø> (+2.67%)	⬆️
plugin	77.43% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.