Replies: 2 comments
-
|
In my VS Code IDE, these top-level fields are highlighted as invalid according to the Skills schema. When I move them under the metadata field, everything is validated correctly. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, you’re right. The Intent-specific fields do belong under With One nuance: Thank you for bringing this up! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I noticed that TanStack Intent generates skills with some custom top-level fields (like
library_version,sources,library,type). The Skills specification defines ametadatafield for "arbitrary key-value mapping for additional metadata". I was wondering if these Intent-specific fields should go there instead.Beta Was this translation helpful? Give feedback.
All reactions