@badlogicgames@xovemnormie It's the HTML strict parsing debate from the late 90s, but for skills. Which of those is better UX for skill *users* (who might not be skill authors)? What is the cost of accepting malformed frontmatter (e.g., are edge cases tightly scoped)?
@badlogicgames@xovemnormie The spec does say "YAML frontmatter followed by Markdown content". Skills authors should follow that. However, if a harness encounters malformed frontmatter matter, what should it do? What would provide the best user experience?
@zeeg The honest answer is that it was copied from Claude Code Skills early on in the standardization process. Since then, CC has introduced even more features, which we decided to wait to standardize until they get more consensus. allowed-tools is a wart, but mostly inconsequential.
@emollick I feel like that's at odds with Google's ethos. One: they aren't very product-centric, and two: they strongly embrace "the cloud is the computer". Seems more likely that their "everything app" will be Chrome.
@raw_works Very cool!! This is probably a dumb question, but why use Python for RLM? Why not Bash + (virtual) file system? To me, it seems like many models are currently trained to do RLM-like things in a Bash environment.
@mattpocockuk I've had this thought too. When the model is well familiar with a named concept, invoking the name nudges it toward that latent space -- very high leverage.
It's startlingly similar to mythology wherein knowing something's true name gives power over the thing itself.