Generated skill frontmatter compliance.

[marcog83]

​I’ve been using @tanstack/intent and I absolutely love the interview step and the code analysis logic—the way it surfaces implicit knowledge is fantastic.
​However, I noticed that the generated SKILL.md file frontmatter structures aren't fully compliant with the de-facto Agent Skills Specification (e.g., specific frontmatter constraints or naming patterns).
​Is there a plan to bring the scaffolded output into full compliance with this spec?

[LadyBluenotes]

Would probably be a good idea to! Do you mind making a feat request for this? I can work to get that involved soon

[escwxyz]

I want to add that there is also no validation for the name field as well. Slash is injected to represent directories. Related: reduxjs/redux-toolkit#5303. I did some code changes locally but not sure which would work for nested directories, as may have the same naming results with different dirs, e.g. xxx/query-tool and xxx-query/tool.

[LadyBluenotes]

@escwxyz Ah, yes, you’re right. The old behavior was wrong here: name should not be used to encode the directory path, and slashes in name were not spec-compliant.

I fixed this with the latest release (@tanstack/intent@0.2.0). name must be a spec-legal leaf segment and skill identity is now derived from the directory path instead of the frontmatter name, which avoids the collision problem you mentioned with cases like xxx/query-tool vs xxx-query/tool.

intent validate --check should flag invalid names, and intent validate --fix can handle the mechanical migration cases. If you have a nested-directory case that still behaves oddly on latest, please let me know!

[LadyBluenotes]

Just for the sake of closing this with a comment - I did want to mention that it was a good catch. The latest update generates SKILL.md frontmatter as spec-compliant and the Intent-specific fields live under metadata, and intent validate --check / intent validate --fix can help migrate existing skills.

sources / requires are still tracked as a separate follow-up because they need a more deliberate structured shape.

If you find any further issues please let me know!