The narrow `prepare-crm-call-evidence` contract and the approved CRM A2A recipe boundary. Use when a CRM, sales, or A2A workflow asks for call evidence, a clip link for a deal, or a `clip.created` automation trigger.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add BuilderIO/agent-native --skill crm-call-evidence --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Crm Call Evidence?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/builderio-crm-call-evidence)More formats (shields.io, HTML) on the badges page.
---
name: crm-call-evidence
description: >-
The narrow `prepare-crm-call-evidence` contract and the approved CRM A2A
recipe boundary.
Use when a CRM, sales, or A2A workflow asks for call evidence, a clip link
for a deal, or a `clip.created` automation trigger.
---
# CRM Call Evidence
## Rule
Use `prepare-crm-call-evidence` only for a viewer-accessible recording that is
explicitly identified by a user action or by the exact approved CRM A2A recipe.
Never call it to fish for a plausible clip.
## What it returns
- An opaque clip ID.
- A durable HTTPS `/r/<id>` page.
- Optionally, the capture time for the CRM record.
## What it never returns
It never returns the event media URL, a transcript, a temporary token, a quote,
or a summary. If a CRM workflow needs more than a link, stop and ask the user
rather than widening the payload.
## Automation triggers
A CRM recipe may install a Clips-owned `clip.created` trigger only through an
exact, user-approved A2A automation definition. Do not synthesize a trigger,
broaden its filter, or reuse it for another recipe.
## Related skills
- `a2a-protocol` — how approved agent-to-agent recipes are defined and called.
- `video-sharing` — the access model behind a viewer-accessible recording and
the `/r/<id>` share page.
- `security` — why the payload stays link-only.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.