B2A
v1.0.0Sell to AI agents with machine-readable products, agent-optimized APIs, structured pricing, and discovery strategies for the agentic economy.
⭐ 2· 559·0 current·0 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (B2A: selling to AI agents) match the provided content: guidance on machine-readable products, APIs, pricing, discovery, and payments. No unrelated credentials, binaries, or installs are requested.
Instruction Scope
SKILL.md and linked docs are guidance and API examples (OpenAPI, OAuth client_credentials, Stripe patterns, schema.org). They do not instruct the agent to read local files or exfiltrate data. Note: the docs explicitly recommend publishing manifests, exposing metrics, and logging agent_id/user_id per-query for analytics — these are expected for the purpose but carry privacy/data-handling implications if implemented.
Install Mechanism
Instruction-only skill with no install spec, no code files to write, and no downloads. This is the lowest-risk install profile and is proportionate for a documentation/strategy skill.
Credentials
The skill requests no environment variables or credentials. However, it recommends implementing OAuth client_credentials, Stripe (or similar) payments, and per-agent API keys in your implementation — those recommendations imply you will handle credentials and payment secrets when you implement the guidance. That is expected but requires secure handling (not a problem with the skill itself).
Persistence & Privilege
No special persistence or privileges requested (always: false). The skill does not attempt to modify other skills or agent settings; autonomous invocation defaults are unchanged.
Assessment
This skill is a content/strategy guide only and does not request credentials or install code. It's coherent with its stated purpose. Before you act on its recommendations: (1) treat any guidance to publish manifests or expose APIs as a prompt to design proper authentication, rate-limiting, and access controls; (2) protect any payment credentials and user-agent linking data (agent_id, user_id) and comply with privacy rules; (3) avoid exposing supplier/private/internal details as advised in the docs; and (4) if you implement agent-driven payments or pre-authorized budgets, audit for abuse scenarios (compromised agents, runaway spending) and implement spending caps and strong audit trails.Like a lobster shell, security has layers — review code before you run it.
latestvk973w8467w7ybhrwwd80hep76h81adrx
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🤖 Clawdis
OSLinux · macOS · Windows