1. Connect with OAuth
Add this entry tomcp_servers in ~/.hermes/config.yaml, preserving your other servers:
get_workspace and list_projects. Check that it names the intended workspace and websites. If no website exists, add one first. Follow the returned connection recovery instructions if authorization fails.
2. Save the job and skills
Copy your role prompt into Hermes and ask it to save the agreed role and separate site briefs. Have it readhttps://agentlinkops.com/SKILL.md and follow its current installation instructions for Hermes. Loading a web reference does not install a local skill. Verify the maintained skills appear in Hermes before relying on them in later sessions.
Continue with the role’s first campaign or saved-link report. Connect a sender only for Link Builder; use sender handoff for existing campaigns.
3. Schedule the proven task
After reviewing an ad hoc result, agree cadence, timezone, report destination and sending authority. Ask Hermes to inspect existing jobs, then propose the schedule. Attach the required skills so each fresh scheduled session receives them. The Hermes gateway must be running for scheduled agent jobs; a sleeping or offline host cannot provide local execution. Checkhermes cron status and inspect execution history after the first due run. See Hermes scheduled tasks.
This path follows Hermes documentation reviewed November 15, 2026. We have not yet tested this AgentLinkOps OAuth setup or a scheduled campaign in Hermes. Compare agent setup paths.