-
Notifications
You must be signed in to change notification settings - Fork 974
Update copies for the registration of the new abilities #23598
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
Open
leonidasmi
wants to merge
4
commits into
feature/yoast-abilities-part-2
Choose a base branch
from
1441-finalize-registration-copies-for-the-getset-data-abilities
base: feature/yoast-abilities-part-2
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+121
−44
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
fa186e5
Update copies for the registration of the new abilities
leonidasmi c3e5046
Merge branch 'trunk' into 1441-finalize-registration-copies-for-the-g…
leonidasmi 53a0b69
Merge branch 'feature/yoast-abilities-part-2' into 1441-finalize-regi…
leonidasmi 1a5f1cc
Inform that empty string clears the schema types too
leonidasmi 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
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.
Is there a reason we don't keep the
title/descriptionformat here?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.
Yeah that was on purpose.
Output descriptions are not added when the keys are pretty self-explanatory and adding them would add length without adding information. I've seen agents reading both schemas when deciding how to use each ability so not adding self-explanatory stuff probably makes our abilities a bit more friendly to agent token costs.
The same keys have descriptions in the input because it's arguably more important for agents to understand what to send when using the abilities than the final results.
I'd keep as is and we can revisit in the future.