Fix YAML front‑matter parsing in agent definitions #71
Conversation
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
- Fix YAML front matter by using a block scalar for description to prevent parsing errors with colons/quotes/tags. - Standardize “Base Account” capitalization for consistency with product naming. - Clarify Zora wording to avoid implying a “Zora wallet”; describe protocol integrations with standard wallet connections. - Remove duplication in Zora integrations section and tighten phrasing. Why this change: - Resolves YAML error: “mapping values are not allowed in this context.” - Improves technical accuracy and reduces potential confusion for implementers. - Keeps documentation concise and consistent with repo terminology. Reference: - File: base-account/agent-spend-permissions/.claude/agents/blockchain-wallet-engineer.md - Upstream repo context: base/demos
Dragboyz
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Why this change:
Reference: