Add kimi-webbridge-fleet skill (macOS + Chrome multi-profile via Kimi WebBridge)

[jeet-dhandha]

Submit a Skill

Thank you for contributing a skill to the Goose community!

---

📛 Skill Info

• Skill name (folder name): kimi-webbridge-fleet
• Short description (what does this skill help Goose do?): Drive multiple real Google Chrome profiles with their live logged-in sessions at once on macOS via Kimi WebBridge, routing browser commands to a chosen profile by name.
• Author / handle: jeet-dhandha
• Version: "1.0"

---

📁 Structure Checklist

• My skill is in a top-level folder (kimi-webbridge-fleet/)
• The folder contains a SKILL.md file
• SKILL.md includes valid YAML frontmatter:
  • name
  • description
  • author
  • version
  • tags (list of strings)
• Supporting files (scripts/templates) live inside the skill folder (none needed — the skill links to the source repo for code/setup)

---

🔐 Security Acknowledgement

• This skill does not contain malicious behavior
• This skill does not attempt to exfiltrate secrets, tokens, or credentials
• This skill does not contain obfuscated payloads (base64 blobs, packed binaries, etc.)
• I understand that all submissions run through automated security scanning
• I understand this PR may be rejected if it fails validation or security review

---

📝 Additional Notes

This skill teaches an agent how to drive the user's actual Google Chrome — including more than one profile with its own live login, simultaneously — through Kimi WebBridge. It runs one stock WebBridge daemon per Chrome profile and a router on :10086 that proxies each /command to the right daemon based on a top-level "profile" field.

Honest scope (the SKILL.md says so up front):

• macOS + Google Chrome only — relies on Chrome's profile layout and macOS process control.
• Requires Kimi WebBridge (daemon + Chrome Web Store extension); this skill orchestrates them, it does not replace them.
• Drives the real browser (acting as the user), not a headless one — by design, for tasks where real login state matters.

Full code and setup live in the source repo, which the SKILL.md links to: https://github.com/jeet-dhandha/kimi-webbridge-fleet

Validation: node scripts/validate-skills.mjs passes (Structure validation PASSED). The security scanner reports FAIL=0; the only WARN findings are network:curl-wget / network:url, which come from the documented example curl request to the local 127.0.0.1:10086 router — intrinsic to a browser-bridge skill, routed to CODEOWNERS review rather than blocking.

🤖 Generated with Claude Code

[github-actions]

✅ Validate Skills — PASSED

Summary: FAIL=0 · WARN=0
Changed skill dirs: kimi-webbridge-fleet

Output (last 200 lines)

✅ Found 8 skill directories.
✅ api-setup: structure validated
✅ beads: structure validated
✅ code-review: structure validated
✅ frontend-design: structure validated
✅ goose-blog-post: structure validated
✅ kimi-webbridge-fleet: structure validated
✅ rp-why: structure validated
✅ testing-strategy: structure validated

Structure validation PASSED.

[github-actions]

🛡️ Skills Security Scan — WARN

Summary: FAIL=0 · WARN=5 · FILES=1
Changed skills scanned: kimi-webbridge-fleet

⚠️ WARN requires investigation + CODEOWNERS review.

⚠️ Warnings

kimi-webbridge-fleet

• network:curl-wget — kimi-webbridge-fleet/SKILL.md:84

curl -s -X POST http://127.0.0.1:10086/command \

Guidance: Review: network tool usage; ensure it's necessary and safe.

• network:url — kimi-webbridge-fleet/SKILL.md:20

[Kimi WebBridge](https://www.kimi.com/features/webbridge).

Guidance: Review: URL present; confirm expected destination and purpose.

• network:url — kimi-webbridge-fleet/SKILL.md:28

**https://github.com/jeet-dhandha/kimi-webbridge-fleet**

Guidance: Review: URL present; confirm expected destination and purpose.

• network:url — kimi-webbridge-fleet/SKILL.md:84

curl -s -X POST http://127.0.0.1:10086/command \

Guidance: Review: URL present; confirm expected destination and purpose.

• network:url — kimi-webbridge-fleet/SKILL.md:86

  -d '{"action":"navigate","args":{"url":"https://example.com"},"session":"s1","profile":"Work"}'

Guidance: Review: URL present; confirm expected destination and purpose.

---

Notes: This comment auto-updates on each push to keep PRs clean.