Skip to content

kits: the prompt states the output contract, so a weak model writes the file instead of answering in chat - #32

Merged
richard-epsilla merged 1 commit into
mainfrom
kit-prompts-output-contract
Sep 23, 2026
Merged

richard-epsilla merged 1 commit into
mainfrom
kit-prompts-output-contract

Conversation

@richard-epsilla

Copy link
Copy Markdown
Contributor

A Sheets run on codex with gpt-5.4-mini read the sheet-design Skill, researched the question and answered with a table in the conversation; ./sheet.json was never written and the person saw "No sheet has been written for this conversation yet." The Skill says the file is the deliverable, but the prompt let a research question read as a chat task.

The sheets, slides and dashboard prompts now say what the person sees (only the file), what every request ends with (that file written or updated), and that an answer living only in chat is invisible to them. Sheets adds the shape a research question takes: rows for the things found, columns for the facts, an agent column for the work to repeat per row.

Verified on the hosted service with the exact prompt that failed (codex, gpt-5.4-mini): see the follow-up comment.

🤖 Generated with Claude Code

…he file instead of answering in chat

A Sheets run on codex with gpt-5.4-mini read the sheet-design Skill, researched the
question and answered with a table in the conversation; ./sheet.json was never written
and the person saw "No sheet has been written for this conversation yet." The Skill says
the file is the deliverable, but the prompt let a research question read as a chat task.

The sheets, slides and dashboard prompts now say what the person sees (only the file),
what every request ends with (that file written or updated), and that an answer living
only in chat is invisible to them. Sheets adds the shape a research question takes.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant