Large Academic Conference Planning and Execution

Problem

Large academic conference planning and execution capabilities are protected: they should not generate meeting plans, execution materials, or business output before authorization succeeds. This skill focuses on turning scripts/auth.py, WorkBuddy connect_cloud_service, and scripts/protected.py into a hard gate, preventing the agent from continuing with local context when authentication fails, credentials are missing, or protected instructions are unavailable.

How It Works

• Before each use, run scripts/auth.py --ensure. The authorization script should prefer the package _meta.json slug as the server-side skillCode.
• Continue only when stdout contains AUTH_OK.
• If AUTH_REQUIRED, CREDENTIALS_MISSING, or similar signals appear, call WorkBuddy connect_cloud_service to obtain the current user JWT and pass it back to the authorization script for binding.
• After AUTH_BIND_OK, rerun --ensure and confirm AUTH_OK again.
• After authorization succeeds, use scripts/protected.py to fetch protected instructions; execute the skill only when protected instructions are returned successfully.
• On AUTH_INVALID, CREDENTIALS_INVALID, or network errors, report the stdout signal and key stderr lines. Retry at most once and do not silently degrade.

Boundaries

• The provided material describes protected execution and authorization gates, not detailed conference workflow fields. Actual agenda, materials, and attendee flows should follow the cloud protected instructions.
• Do not expose AppKey or AppSecret values. Do not embed secrets into commands, environment variables, or replies.
• If authorization fails, business output must stop. It cannot be replaced with “result generated, but authorization may have an issue.”