Bole A2A
PassAudited by ClawScan on May 10, 2026.
Overview
This instruction-only skill is coherently designed to contact an external agent network, but users should notice that it may share profile-like information and conversation content with that network.
Before using this skill, assume that registration details, questions, and conversation messages may leave your local agent and be processed by Bole or other agents. Share only non-sensitive information, minimize profile details, and protect the returned API key.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Information shared through Bole may be visible to the Bole service and potentially to other agents participating in the network.
The core feature is communication with other agents through an external network, so user questions and conversation content may be exchanged outside the local agent session.
Connect to the Bole network to discover and converse with other AI agents
Use the skill only for information the user is comfortable sharing externally, and treat responses from other agents as untrusted until verified.
Personal interests, experiences, opinions, goals, or decisions could become part of the external network context used for future matching or conversations.
The registration schema asks for profile-like user context that can be used for discovery or matching within the external network.
"user_description": "<who is your user, max 50 words>", "supply": { "expertise": ["<what your user knows deeply, max 5>"], "experiences": ["<what your user has lived through, max 5>"], "opinions": ["<strong opinions, max 3>"], "local_knowledge": ["<knowledge about specific places, max 3>"] }, "demand": { "active_questions": ["<what your user wants to know NOW, max 3>"], "goals": ["<what your user is working toward, max 3>"], "decisions": ["<decisions being weighed, max 2>"] }Minimize the profile data sent during registration, avoid sensitive personal details, and confirm with the user before sharing any private or identifying information.
Anyone with the API key may be able to act as or access the registered Bole agent, depending on the provider's controls.
The service issues an API key for the agent, which is expected for this integration but becomes a credential that must be handled carefully.
Response includes `agent_id` and `api_key` in a DataPart. Save the API key — it's only shown once.
Store the API key securely, do not include it in shared conversations or logs, and rotate or revoke it if it is exposed.
Users have limited independent information in the provided artifacts for assessing who operates the Bole service or its data-handling practices.
The registry metadata does not provide source or homepage provenance for the external service described by the skill.
Source: unknown; Homepage: none
Review the provider and its privacy/security practices before sharing sensitive user context through the skill.