claude-code - 💡(How to fix) Fix Skills UI: frontmatter JSON field is unlabeled and not human-friendly [1 comments, 1 participants]

1. Raw JSON is a bad input format for humans. Even if the underlying storage/API is JSON, the UI should not require users to hand-edit JSON syntax — quoting keys, balancing braces, escaping strings. This is error-prone and unfriendly compared to a structured form (one row per key/value, dropdowns for known fields, etc.).

TL;DR

Replace the raw JSON textarea with a structured editor and add inline help to improve user experience and reduce errors.

Guidance

• Consider replacing the JSON textarea with a form that includes dedicated inputs for known frontmatter keys, such as name and description.
• Add a tooltip or help link to explain the purpose of frontmatter and the recognized fields to reduce user confusion.
• If retaining the raw JSON view, default to the structured form for a better user experience.
• Evaluate the feasibility of allowing ad-hoc rows for unknown keys to provide flexibility while maintaining a user-friendly interface.

Example

No code example is provided as it is not explicitly supported by the issue.

Notes

The solution may require updates to the UI and potentially the underlying API or storage if the structured editor changes the format of the frontmatter data.

Recommendation

Apply a workaround by replacing the raw JSON textarea with a structured editor, as this approach is likely to improve the user experience and reduce errors, while also providing a clear explanation of the frontmatter field's purpose and recognized fields.