-
-
Notifications
You must be signed in to change notification settings - Fork 840
feat(core): add structured skills prompt context API #1065
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| --- | ||
| "@voltagent/core": patch | ||
| --- | ||
|
|
||
| feat: add structured workspace skills prompt context API for custom prompt assembly | ||
|
|
||
| - Added `workspace.skills.getPromptContext(...)` to return structured prompt metadata for available and activated skills. | ||
| - Each item now includes `id`, `name`, `description`, `path`, and `active`, making it easier to build custom `## Skills` sections without re-assembling data from `discoverSkills(...)`. | ||
| - Updated `workspace.skills.buildPrompt(...)` to reuse the new prompt context path while preserving existing `<workspace_skills>` output behavior. |
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
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
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: VoltAgent/voltagent
Length of output: 199
🏁 Script executed:
rg -n --type=ts -C5 'references|scripts|assets' packages/core/src/workspace/skills/ --max-count=30Repository: VoltAgent/voltagent
Length of output: 24194
🏁 Script executed:
Repository: VoltAgent/voltagent
Length of output: 1256
Add "relative to
root" clarification toreferences,scripts, andassetsdescriptions for consistency with the source-of-truth TypeScript interface.The descriptions in lines 99-110 use relative-path examples (
references/running-code.md,scripts/run.sh,assets/input.csv), which are correct. However, the TypeScript interface inpackages/core/src/workspace/skills/types.ts(lines 93-108) explicitly documents these fields as "relative toroot", while the Zod schema descriptions omit this detail. This creates a documentation inconsistency that will propagate into OpenAPI specs and tool definitions.✏️ Suggested description updates
references: z .array(z.string()) .optional() - .describe("Readable files under `references/` (for example `references/running-code.md`)"), + .describe("Readable files under `references/`, relative to `root` (for example `references/running-code.md`)"), scripts: z .array(z.string()) .optional() - .describe("Readable scripts under `scripts/` (for example `scripts/run.sh`)"), + .describe("Readable scripts under `scripts/`, relative to `root` (for example `scripts/run.sh`)"), assets: z .array(z.string()) .optional() - .describe("Readable assets under `assets/` (for example `assets/input.csv`)"), + .describe("Readable assets under `assets/`, relative to `root` (for example `assets/input.csv`)"),📝 Committable suggestion
🤖 Prompt for AI Agents