metabot-post-buzz

Post text or attachments as Buzz to MetaWeb via local RPC gateway.

10|2|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/metaid-developers/IDBots --skill metabot-post-buzz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metabot-post-buzz
Source: https://github.com/metaid-developers/IDBots/tree/main/SKILLs/metabot-post-buzz
Command: npx skills add https://github.com/metaid-developers/IDBots --skill metabot-post-buzz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enables MetaBots to broadcast user content as SimpleBuzz onto the MetaWeb, handling on-chain commitments and file attachments securely and predictably.

Core Features & Use Cases

  • Posts text Buzz to the MetaWeb, with optional attachments (images, PDFs, etc.) converted to metafile pins.
  • Accepts local file paths or existing metafile:// URIs for attachments; supports multiple networks (mvc, doge, btc) and content types.
  • Real-world use: publish a status update with an image on-chain or attach a document to a Buzz for archival access.

Quick Start

Post a Buzz by providing content and optionally attachments using the request file or CLI arguments.

Frequently Asked Questions about metabot-post-buzz

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I post a buzz on-chain with file attachments?

Posting a buzz on-chain with attachments involves broadcasting text and files to MetaWeb via a local RPC gateway. Local files are automatically converted to metafile pins, while existing metafile URIs are attached directly to the on-chain Buzz.

Can I attach existing metafile URIs to an on-chain buzz?

Yes, you can attach existing metafile:// URIs to an on-chain buzz. The Skill accepts both local file paths for automatic upload and existing metafile URIs, handling the on-chain commitments and reporting associated costs.

What networks support broadcasting buzz to the MetaWeb?

Broadcasting buzz to the MetaWeb supports the mvc, doge, and btc networks. You can target these specific networks when posting text-only buzz or buzz with file attachments via your local RPC gateway.

Do I need a specific environment to post buzz to MetaWeb via RPC?

Posting buzz to MetaWeb via RPC requires setting the IDBOTS_METABOT_ID environment variable. You can optionally configure IDBOTS_RPC_URL to specify your local RPC gateway endpoint before broadcasting content.

What is the difference between posting text-only buzz and buzz with attachments?

Text-only buzz broadcasts plain content to the MetaWeb, while buzz with attachments converts local files like images or PDFs into metafile pins. Both methods handle on-chain commitments and provide automatic cost reporting.

Why does posting buzz with local file attachments require cost reporting?

Cost reporting is required for posting buzz with local file attachments because the process converts local files to metafile pins on-chain. The Skill handles these on-chain commitments securely and reports the associated transaction costs.