Skill: clarify how a Python agent receives signal payloads#21
Merged
Conversation
A type:user agent gets input through two channels, and the skill led with "prefer ctx.input over prompt scraping" — true for inputFrom handoffs, but misleading for the common case of a job triggered by a signal with no upstream producer. There, the payload arrives in the `prompt` string and `ctx.input` is empty; an agent following the old guidance guesses a ctx.input key and silently gets nothing back. Add a "which channel?" decision callout at the top of Structured Input Handling, scope the ctx.input intro to inputFrom, and fix the capability table row so it no longer implies ctx.input carries the signal payload. Docs only — no SDK version bump. ## Progress - Task: Workspace-chat mutation-awareness fixes (from a self-modification chat review) - Decisions: Kept the edit to SKILL.md only; left version pinning and the friday-studio re-vendor for a later release. - Key Learnings: The skill is vendored into friday-studio via scripts/sync-sdk-skill.ts at a pinned tag — this branch reaches friday-studio only after release + version bump + re-vendor, so it does not need a coordinated cross-repo change. - Files: packages/python/skills/writing-friday-python-agents/SKILL.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
writing-friday-python-agentsskill led with "preferctx.inputover prompt scraping" — accurate forinputFromstep handoffs, but misleading for the common case of a job triggered by a signal. There, the payload arrives in thepromptstring andctx.inputis empty, so an agent following the old guidance would guess actx.inputkey and silently get nothing back.prompt(useparse_input), upstream step output arrives inctx.input(inputFromonly). Also scopes thectx.inputintro and fixes the capability-table row that impliedctx.inputcarries the signal payload.Test plan