Removed the strict language to allow for an only kind of application without having to 'fix' the login action after creation.#26
Merged
Conversation
…without having to 'fix' the login action after creation.
Co-authored-by: Blake Krammes <49688912+blakekrammes@users.noreply.github.com>
Co-authored-by: Blake Krammes <49688912+blakekrammes@users.noreply.github.com>
blakekrammes
approved these changes
Jun 25, 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
2 participants
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 is currently an issue where if you prompt for the application to be used by only "admins" that it will add "user" to the Admin Login action. This needs to be fixed post application creation, and the cause of this behavior is the strict no-admin language in the skill files. This PR relieves the strictness of this language that justifies when it is ok to use "admin" as the login resource.