The embedded Clips bug-report flow — the `/bug-report` iframe launcher, `/record?intent=bug-report` capture, `save-bug-report-context`, and its intake limits. Use when embedding bug capture in another product, wiring the launcher, or asked to collect customer bug recordings.
Scanned 9/3/2026
Install to Claude Code
Skills Directorynpx -y skills add BuilderIO/agent-native --skill bug-reports --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Bug Reports?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/builderio-bug-reports)More formats (shields.io, HTML) on the badges page.
---
name: bug-reports
description: >-
The embedded Clips bug-report flow — the `/bug-report` iframe launcher,
`/record?intent=bug-report` capture, `save-bug-report-context`, and its
intake limits. Use when embedding bug capture in another product, wiring the
launcher, or asked to collect customer bug recordings.
---
# Embedded Bug Reports
## Rule
`/bug-report` is an iframe-friendly launcher only. The actual capture runs
top-level at `/record?intent=bug-report`, because browser media capture needs a
top-level user gesture.
## How it works
1. The host page embeds `/bug-report` in an iframe.
2. The launcher stores redacted host metadata through `save-bug-report-context`.
3. Capture opens top-level at `/record?intent=bug-report`.
4. The recording remains the canonical resource and defaults to workspace
(organization) visibility.
## Intake limit
Do not present this as anonymous customer intake until a signed intake/upload
token flow exists — the current upload endpoints are owner-scoped, so an
anonymous reporter cannot upload.
## Related skills
- `recording` — the capture and upload path behind `/record`.
- `video-sharing` — why bug-report recordings default to organization
visibility instead of public.
- `security` — redaction rules for host metadata and diagnostics.
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.
