Repository navigation
spec: list recognized media types in §3.3 and align skill example (#37, #95) - #105
Merged
Merged
Conversation
mindpower
force-pushed
the
fix-skill-and-recognized-media-types
branch
from
October 11, 2026 21:30
ef8b30d to
cbe4bbf
Compare
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.
Align
spec/ard.mdskill media type example withconformance-test(Inconsistent skill media types between spec examples and conformance tool allowlist #37):spec/ard.md(§5) fromapplication/agent-skill+markdowntoapplication/agent-skills+mdso the prose spec matchesconformance/bin/conformance-test.RECOGNIZED_MEDIA_TYPESinconformance/bin/conformance-testandconformance/tests/test_media_type_diagnostics.py.List standard recognized media types and clarify open
typebehavior inspec/ard.md§3.3 ( Discussion: what is the intended shape of the media-type taxonomy? #95):Entry Fields->type) alongside a clear explanation thattypeis an open field and custom/vendor media types remain valid (producing an informational note inconformance-testrather than a validation error).Closes #37, Closes #95