Route lifecycle requests through the Nexus /discover path via the office-hours alias.
npx skills add https://github.com/LaPaGaYo/nexus --skill office-hours-lapagayo
Please help me install this Agent Skill. Skill: office-hours Source: https://github.com/LaPaGaYo/nexus/tree/main/skills/aliases/office-hours Command: npx skills add https://github.com/LaPaGaYo/nexus --skill office-hours-lapagayo
This transitional alias routes requests to the canonical Nexus /discover path, simplifying access to powered lifecycle routing without owning its own contracts or transition logic.
Invoke the office-hours alias to route your request through Nexus discover and begin the canonical workflow.
High-intent search queries and answers about installing and using this skill.
To route requests to the Nexus discover path, invoke the office-hours alias, which acts as a thin routing layer to channel your flow into the canonical lifecycle workflow.
A transitional alias for routing lifecycle workflows is a thin proxy layer that redirects requests to a canonical entrypoint like Nexus /discover without duplicating logic or owning separate contracts.
No, you do not need special dependencies to use the Nexus discover routing alias beyond the Nexus runtime itself, as it requires only Bash and Read tools to function.
You should use a shell alias instead of direct lifecycle routing when you want to seamlessly channel user flows into a canonical path without maintaining your own transition logic or contracts.
No, the office-hours alias does not manage its own transition contracts, as its scope is strictly limited to proxying requests to the Nexus discover entrypoint.
LaPaGaYoRoute lifecycle commands through the Nexus alias to the canonical /frame command.
withkynamIndex feature-group files and load domain-routed context for agent sessions.
LaPaGaYoRoute Nexus frame commands through the canonical /frame surface.
abra5umenteRoute API requests through a residential proxy to bypass cloud IP blocks.
