fix(skill): align generation template with skill-creator best practices#1434
Open
kagura-agent wants to merge 1 commit intoMemTensor:mainfrom
Open
fix(skill): align generation template with skill-creator best practices#1434kagura-agent wants to merge 1 commit intoMemTensor:mainfrom
kagura-agent wants to merge 1 commit intoMemTensor:mainfrom
Conversation
- Constrain skill name to 2-4 word kebab-case - Limit frontmatter to name + description only - Add rule against creating extra documentation files - Add 'assume agent is smart' principle - Strengthen trigger condition requirements in description - Clarify metadata as optional OpenClaw extension Fixes MemTensor#1423
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.
What
Aligns the skill generation prompt template (
STEP1_SKILL_MD_PROMPT) with skill-creator best practices, addressing all 6 issues raised in #1423.Changes
name+descriptiononlyQuestion for maintainers
The current template includes
metadata: { openclaw: { emoji } }in frontmatter. Per best practices, frontmatter should only havenameanddescription. I've moved the metadata guidance to an HTML comment at the end of the file body, noting it as an optional OpenClaw extension. Please let me know if you'd prefer a different approach.Testing
Fixes #1423