fix: use frontmatter description for skill vectorization instead of overview#229
Merged
MaojiaSheng merged 1 commit intovolcengine:mainfrom Feb 20, 2026
Conversation
…verview Reverts the skill_processor embedding change from volcengine#228 while keeping the retriever fix. Skills should embed using the frontmatter description (abstract), not the LLM-generated overview.
MaojiaSheng
approved these changes
Feb 20, 2026
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.
Context
PR #228 fixed two issues with skill search ranking:
This PR reverts change (2) while keeping (1). Skills should embed using the frontmatter description (abstract), not the overview.
Why revert to abstract/frontmatter
Skills are not resources. The two have fundamentally different retrieval patterns:
Resources are document collections where users search for content within files. Using overview/content for embedding makes sense — users query with natural language about what is inside the documents.
Skills are tools selected by matching a short description. In system prompts, agents see only
name + descriptionto decide which skill to activate. The embedding should match this same selection surface — the frontmatter description — so vector search aligns with how skills are actually discovered and used.Using overview introduces unnecessary indirection:
Recall testing confirms abstract works well:
5/5 semantic queries rank correctly with abstract-only embedding. The retriever fix from #228 was the real improvement — it ensures all skills appear in results regardless of embedding text quality.
Changes
skill_processor.py: Revert vectorization text from overview back tocontext.abstract(frontmatter description)