Instead of immediately falling back to Puppeteer mode when both CDP and
Bridge prechecks fail, try opening Chrome first using a platform-appropriate
shell command, wait briefly, then re-run the precheck before falling back.
- CDP: curl WebSocket handshake on port 9222
- Bridge: curl Socket.IO on port 3766
- Route to Puppeteer if both unavailable
- Add implicit login state as CDP trigger
Add CDP (Chrome DevTools Protocol) support to the existing
browser-automation skill, allowing connection to an already-running
Chrome browser via --cdp <ws-endpoint> flag.
Add a check script (scripts/check-skill-description-length.mjs) that
verifies SKILL.md description fields do not exceed 1200 characters.
Also trim redundant use-case entries in browser, chrome-bridge, and
computer-automation skill descriptions to stay within the limit.
When macOS is locked, screenshots return black images due to a
system-level restriction. Added guidance to use a screensaver instead
of locking the screen during automation sessions.
https://claude.ai/code/session_018doP2rApBG4cYAwHnrLhem
Add testing-related trigger keywords (e.g. "test app", "QA", "verify",
"end-to-end test") to all automation skills so they are correctly matched
when users want to test applications.
Clarify browser vs desktop automation: browser skill now states it runs
headless and does not take over mouse/keyboard; computer-automation skill
warns that it does take over input devices and recommends browser skill
for web apps.
Add a new Midscene-powered skill for automating HarmonyOS NEXT devices via HDC, supporting natural language commands for taps, swipes, text input, app launches, and screenshots.
Add CRITICAL RULE #4 requiring agents to proactively report task results
before finishing. Previously, result summarization was only a soft "best
practice" recommendation, causing agents to silently end after the last
automation step — users had to send a second message to get results.
Changes across all 5 skills (browser, chrome-bridge, computer, android, ios):
- Add CRITICAL RULE #4: "Always report task results before finishing"
- Add "Report results" as a workflow step
- Strengthen Best Practice from "Summarize report files" to "Always report
results after completion" with explicit requirements
Make disconnect optional in Chrome Bridge automation to support multi-turn
conversation scenarios. Previously, the workflow mandated disconnecting
after every task, breaking the user's ability to continue interacting with
the browser in subsequent conversation turns.
Changes:
- Update Workflow Pattern to explain that browser state is always preserved
- Change disconnect from mandatory step to conditional (only when fully done)
- Update Best Practice #5 from "Disconnect when done" to "Disconnect only
when fully done" with guidance for multi-turn conversations
- Health check: observe connect command output first; only do manual
health check if connect did not already perform one
- Add best practice #8: export PATH on macOS before running to prevent
system_profiler not found errors
https://claude.ai/code/session_014boNXomePtBtKmFhA5LeFn
quanruzhuoxiu