Turn a PR, branch, commit, or git diff into an interactive visual recap with diagrams, file maps, API/schema summaries, annotated diffs, and focused review notes.
Skills in this repository
BuilderIO/agent-native - Page 6
SkillsMP has collected 268 skills from BuilderIO/agent-native. Open a skill to review its source and details.
BuilderIO/agent-nativeShowing 40 of 268 collected skills.
How to find every sibling instance of a reported bug before fixing it. Use whenever a bug report names one file but the defect is a call pattern, hook, duplicated literal, or copy-pasted helper that plausibly exists in other files, apps, or templates.
Route customer, account, CRM, HubSpot, pipeline, renewal, usage, product activity, Gong, and other analytics-backed deck requests through the Analytics agent. Use when generating or updating Slides content that needs external or first-party data.
How extensions render as widgets inside other apps via named UI slots — the framework's optional extension system. Use when an extension-enabled app needs to wire an ExtensionSlot or make an existing one-off custom block installable into a slot.
Framer-style responsive breakpoint editing in Design: one DOM tree per screen with cascading width-scoped overrides. Use when adding/removing breakpoints, editing a design at a specific device width, resolving which value renders at a width, or persisting…
Autonomous multi-app QA sweep that drives template apps with Playwright MCP. Use only when the user explicitly runs /qa or asks for an end-to-end QA sweep. Do not load it for ordinary feature work, single-page checks, or one-off bug fixes.
Generate inline chart images (PNG) for embedding in chat responses. Use this skill when you need to create bar, line, or area charts for data visualization in chat.
How `export-to-brain` sends ready Clips transcripts to Brain — single exports, bounded historical imports, cursor pagination, required secrets, and the retry sweep. Use when exporting transcripts to Brain, backfilling past recordings, or debugging a missing…
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.
How Clips connects to Slack and Atlassian/Jira, and the provider-API boundary for credentialed integrations. Use when installing or debugging the Slack app, connecting Atlassian/Jira, or adding raw provider API access to a Clips integration.
Resolve a name or partial address to a real email and enrich a thread with CRM/contact context (HubSpot, Apollo) before drafting or triaging. Use when the user names a person instead of an email, or asks "who is this" / "what deals/tickets does this contact…
How Mail actions pick between the real Gmail API and synthetic local-emails fallback data per user. Use when mail data looks fake or empty, when a user has no connected Google account, or before claiming a message really was sent or fetched from Gmail.
Call raw Gmail, Google Calendar, or HubSpot endpoints through provider-api-catalog / provider-api-docs / provider-api-request, and stage large result sets with stageAs plus query-staged-dataset. Use when a canned Mail action lacks the exact endpoint, filter,…
Which Plan command and creation action fits a request — document-first, UI-first, prototype-first, design-first, recap, or visual intake — plus how to raise an existing plan to design fidelity. Use when creating, routing, or re-rendering a plan.
Plan review threads end to end: what `get-plan-feedback` returns, how to read anchors, resolver intent, replies, notification email, deletion, and abuse reports. Use when reading, answering, resolving, or removing plan feedback.
The four plan lifecycle events on the framework event bus and how to subscribe with `manage-automations` instead of bespoke integration code. Use when a user wants to be notified or trigger work on plan creation, comments, publishes, or status changes.
Preconditions and protocol for writing hosted plans: real user session, `expectedUpdatedAt` revision guard on destructive writes, post-write verification, and when feedback may be resolved or consumed. Use when performing any hosted plan write.
How Ask Plan links a browser-selected local codebase and how to answer questions from its indexed snapshots instead of guessing from file names. Use when the user asks about their linked local codebase or `localCodebase` is in application state.
The `columns` before/after comparison primitive and the PR Visual Recap GitHub Action (agent/model env vars, required tokens, sticky comment, informational scope). Use when building a recap, configuring recap CI, or explaining a Visual Recap check or comment.
DB-backed plan snapshots: when they are taken, how to list and inspect them, and what `restore-plan-version` preserves. Use when the user asks about plan history, undo, rollback, or restoring an earlier version of a plan.
End agent responses that include code changes with a Change summary table (Code / Tests / Config / Docs) and per-file line counts from git diff, and the commit message conventions for this app. Use after any code change and before creating a commit.
Custom field definitions, types, config, per-task values, and which fields show on task cards. Use when the user asks to add, edit, reorder, show, hide, or delete a custom field, set a field value on a task, or works on /fields.
Naming and transaction rules for server store functions in `server/**/store.ts`. Use when adding, renaming, or calling a store function, writing a bulk or singular CRUD helper, or wiring a query into a transaction.
Answer code/product questions as visual Plan artifacts using repo, bridge, or GitHub context; use for API specs, UI look, schema models, and architecture.
How to rename or rebrand the app so every surface — title, package metadata, PWA manifest, and icons — stays consistent. Use when a prompt establishes or implies a new app name, title, or visual identity, OR when you generate an app title, theme, or icon…
How to enable browser feature permissions (camera, microphone, geolocation, screen capture, clipboard, wake-lock) that the framework's default Permissions-Policy header blocks. Use when the app must access a device or browser capability that is silently…
Client method surface rules. Use when wiring browser/client code to actions, application state, framework routes, app APIs, uploads, auth, or settings.
Enrich contacts and companies via Apollo.io for prospecting and sales intelligence. Use this skill when the user asks about contact details, company research, or finding decision-makers.
Look up community member engagement and signals via Common Room. Use this skill when the user asks about community activity, member engagement, or community signals.
Search and read GitHub PRs, issues, and code across a configured GitHub org or repo. Use this skill when the user asks about pull requests, code reviews, or GitHub issues.
Look up customer support tickets and account history via Pylon. Use this skill when the user asks about support tickets, customer issues, or support history.
Search and reuse approved brand examples before generating decks, designs, content, assets, or dashboards.
Inspect and manage the live agent context window with Context X-Ray. Use when context is getting large, the user asks what is in context, or stale tool results/files should be pinned, evicted, restored, or reported by an external host.
Use when adding or reviewing UI navigation so internal routes preserve normal SPA behavior plus Cmd/Ctrl-click and middle-click new-tab semantics.
Use Design for UI/UX exploration, side-by-side design directions, interactive prototype previews, user selection, iteration, and design-to-code handoff through the hosted Design MCP app.
Calendar + video provider integrations — Google Calendar, Office 365, Zoom, built-in video, Google Meet — and how to write new ones.
Make arbitrary authenticated HTTP calls to configured Analytics provider APIs when first-class actions are too narrow.
Query BigQuery for analytics events, signups, pageviews, subscriptions, and user data. Use this skill when the user asks about metrics, funnels, user activity, or customer usage data.
Monitor Google Cloud Run services and Cloud Functions health, metrics, and logs. Use this skill when the user asks about service health, request counts, latencies, or cloud infrastructure.
Search sales call recordings, transcripts, and participants via Gong. Use this skill when the user asks about sales calls, customer conversations, or call transcripts.