Repository navigation
Add LLM structured output guardrails skill and prompt - #93
Merged
Merged
Conversation
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.
Adds the
llm-structured-output-guardrailsskill and matchingenforce-llm-structured-outputprompt.The LLM entries so far touch structured output only in passing: prompt injection says to validate tool arguments, routing skips targets without
json_schema, and the eval gate lists JSON validity as a hard check. None of them says how a service actually gets a schema-valid document or a clean failure. This pair covers that.additionalProperties: false, every property required (nullable instead of optional), enums with an escape value, no free-form unions. Rules a provider's strict subset rejects move into the validator instead of being deleted.$ref, format assertions on when a field depends onformat.{path, keyword}feedback and no values, then fail closed with a problem+json code or a sealed result type. No guessing fixers, no relaxing the schema on retry.Cross-links to the prompt-injection, routing, PII redaction, eval gate, and cost/latency entries rather than repeating them.
Only
skillbook/skills.jsonandpromptbook/prompts.jsonchange. Catalogs are 55 skills and 55 prompts. Local site check and script tests passed.