public-equity-investing
Public Equity Investing Router
Bundled Path Resolution
Derive the plugin root once from the actual filesystem location of this SKILL.md: it is two parent directories above this router directory. Set the shell working directory to that plugin root before the first bundled read or command, and resolve every router-owned bundled path from that root. Use only plugin-root-relative paths such as shared/..., skills/..., and skills/public-equity-investing/internal-support/.... Do not apply ../.. to an already resolved plugin root, resolve paths from the broader marketplace or cache root, or probe alternate relative paths.
Invocation Gate
Read shared/invocation-policy.md before choosing any specialist. If the prompt is neither an explicit Public Equity Investing invocation nor a perfect-fit listed-equity investor mandate, do not route into this plugin.
User Context Preflight
After the invocation gate passes and before substantive Public Equity Investing work, run python3 skills/user-context/scripts/user_context_preflight.py with the shell working directory set to this plugin's root. Set the working directory before the first attempt; do not probe alternate relative paths.
Use the returned envelope as a soft read-only preflight. Pass relevant entries from saved_context to the selected lead skill as handoff context. The router must not interpret saved output preferences, resolve or announce a presentation surface, or decide whether the requested work belongs in chat. Missing, malformed, unreadable, or uninitialized state must never block the requested workflow. Do not initialize, overwrite, repair, or reset state during ordinary workflow preflight. Do not inspect connectors or source readiness.
When an ordinary workflow returns next_action.id = "offer_orientation", complete the requested work and then append one short optional setup offer: I can also save a couple of Public Equity Investing defaults, connect source tools, offer one optional automation, and help you pick a starter workflow. Want to do that now?
Do not append the offer for direct saved-context setup or status requests. Do not append it when next_action is null, including after onboarding is completed, deferred, or quiet. Leave other onboarding steps to the explicit user-context flow.