readme: agent interface as its own section; one-row-per-command reference - #9
Merged
Conversation
…e row per invocation Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
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.
Why
For an agentic-workflows submission, "use it from inside your agent" was a short subsection under the shell usage, and the command reference hid flags in a third column instead of showing complete commands.
What changed
/fairtaskwith its three inputs and what happens for each (including the fail-closed PR flow), a verbatim in-session verdict fromexamples/psf__requests-2317/, how the engine is located and installed at the pinned release, manual mode;/fairtask-evalwith seven example invocations and what each runs and shows; what the skills may and may not do (read-only tools, workspace guard, cost, triage not decision).