Skill system checks + drop stale Chrome auto-start status hint#20
Merged
Conversation
conversation-planner, reply-to-post, stats, and sync-planner-persona-from-linkedin were missing the inline outreach-update-check block that setup-outreach and send-connection-request already run, so they could silently run against a stale version or a down browser/cron service.
It's invoked per-prospect by the dashboard scheduler, not directly by the user — an upgrade prompt on every automated run would block the sweep. Health/version checks stay on the user-invoked skills only.
Covers the system-check rollout to reply-to-post, stats, and sync-planner-persona-from-linkedin.
Chrome boots on demand (since 1.0.0.10), so an unregistered always-on browser service isn't a gap worth flagging in `make status` anymore. The auto-start line still prints when a launchd/systemd service is actually registered.
huangruoqi
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
reply-to-post,stats, andsync-planner-persona-from-linkedinnow run the inlinebin/outreach-update-checksystem check (service health + version check) at skill start, matchingsetup-outreachandsend-connection-request. Skipped foroutreach-uninstall(about to tear down) andconversation-planner(scheduler-driven, not user-invoked).make statusno longer prints the Chrome CDP "auto-start not registered (run bin/browser-service install)" hint — Chrome boots on demand since 1.0.0.10, so an unregistered always-on service isn't a gap to flag. Theauto-startline still shows when a launchd/systemd service is actually registered.VERSION/pyproject.toml/uv.lockto1.0.0.12and added CHANGELOG entries for both changes.Test plan
outreach/skills/*/SKILL.mdto confirm every LinkedIn-facing, user-invocable skill (exceptoutreach-uninstalland the scheduler-drivenconversation-planner) referencesoutreach-update-check.uv run pytest testing/tests/test_system_status.py -q— 4 passed.uv run python -m cron.system_statusand confirmed the stale auto-start hint is gone while the "registered" case (cron section) still prints.make check-versionequivalent: confirmedVERSION,pyproject.toml, anduv.lockall read1.0.0.12.🤖 Generated with Claude Code