name	eval-oauth
description	Use for `/eval-oauth` requests and eval-oauth account connect, reconnect, or auth-flow test requests. You must run the eval identity check before answering anything else.
allowed-tools	bash

Eval OAuth Flow

This fixture is HTTP-backed, not MCP-backed. Do not use or mention MCP tools for eval-oauth.

Run this command before doing anything else:

curl -fsSL https://example.com/junior-eval-oauth/whoami

Rules:

Use the bash tool for curl -fsSL https://example.com/junior-eval-oauth/whoami.
Do not answer the user's question until that command succeeds.
If the first run does not complete, stop there. Do not summarize, apologize, or ask the user to repeat anything.
After the identity check succeeds, answer the user's real question directly in that same turn.
Never stop after a successful identity check without sending a final user-facing reply.
If the user asks about earlier thread context, use that context plainly.
Do not ask the user to repeat facts that were already stated earlier in the thread.
If the user asks what budget deadline they mentioned earlier, answer plainly that it was Friday.
If the user asks to connect, reconnect, or test the auth flow, reply with a short confirmation that the eval-oauth account is connected.
Keep the final answer short.

name	eval-oauth
description	Use for `/eval-oauth` requests and eval-oauth account connect, reconnect, or auth-flow test requests. You must run the eval identity check before answering anything else.
allowed-tools	bash

This fixture is HTTP-backed, not MCP-backed. Do not use or mention MCP tools for eval-oauth.

Run this command before doing anything else:

curl -fsSL https://example.com/junior-eval-oauth/whoami

Rules:

Use the bash tool for curl -fsSL https://example.com/junior-eval-oauth/whoami.
Do not answer the user's question until that command succeeds.
If the first run does not complete, stop there. Do not summarize, apologize, or ask the user to repeat anything.
After the identity check succeeds, answer the user's real question directly in that same turn.
Never stop after a successful identity check without sending a final user-facing reply.
If the user asks about earlier thread context, use that context plainly.
Do not ask the user to repeat facts that were already stated earlier in the thread.
If the user asks what budget deadline they mentioned earlier, answer plainly that it was Friday.
If the user asks to connect, reconnect, or test the auth flow, reply with a short confirmation that the eval-oauth account is connected.
Keep the final answer short.

eval-oauth