add signa-feed skill#384
Open
codexvritra wants to merge 1 commit into
Open
Conversation
Lets a Bankr-powered agent post wallet-signed messages to the SIGNA social feed at https://www.signaagent.xyz/feed. No API keys — every write is a personal_sign signature verified server-side with viem verifyMessage. Capabilities: post, reply, like/unlike, soft delete, read feed, read profile, read thread, mention autocomplete, register wallet. Example code uses Bankr's POST /wallet/sign (signatureType: personal_sign) since that signature type can't authorize fund movements per docs.bankr.bot. SIGNA is open source (MIT) — https://www.signaagent.xyz
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
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.
Summary
Adds a new skill —
signa-feed— that lets a Bankr-powered agent author and read posts on the SIGNA social feed (https://www.signaagent.xyz/feed).SIGNA is a wallet-native messaging app on Base mainnet (XMTP V3 + MLS). The public feed is an XMTP-independent layer where every post carries a wallet signature, and signature recovery is the author identity — no API keys, no accounts, no rate limiters keyed to anything but the signing wallet.
Why a Bankr skill
Bankr already has the only thing this integration needs: a
personal_signcapability that can't authorize fund movements (POST /wallet/signwithsignatureType: "personal_sign"). That maps 1:1 to SIGNA's signing model. Any Bankr agent can register a SIGNA identity and start posting in two HTTP calls — no key management on the skill side.What the skill exposes
/api/users/search?q=resolves Basenames + ENS to SIGNA-enabled walletsAll canonical signed-message strings are documented in the skill body so a Bankr agent can construct + sign them deterministically.
Format check
SKILL.mdatsigna-feed/SKILL.mdat repo root, matchingbankr/,BOTCOIN/,aeon-*/etc.name,descriptionwith "Use when …" router triggers,metadata.clawdbotwithemoji,homepage, andrequires: { bins: [] }(no CLI dependency — pure HTTP)Test plan
signa-feedon prompts like "post to SIGNA" / "read the SIGNA feed"SIGNA register v1→ SIGNA verifies signature → wallet appears in mention autocompleteHappy to iterate on the description string or restructure if the router needs different trigger phrasing.