メニュー
このリポジトリの skills
SkillsMP は BuilderIO/agent-native から 227 件の skill を収集しています。skill を開くとソースと詳細を確認できます。
BuilderIO/agent-native収集済み skill 227 件中 40 件を表示しています。
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 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…
原文の言語: 英語
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.
原文の言語: 英語
The Dictate tab in Clips — press-and-hold desktop dictation, mobile voice dictation, history, AI cleanup, and native capture hand-offs. Use when listing past dictations, polishing dictation text, or wiring native capture.
原文の言語: 英語
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.
原文の言語: 英語
Screen Memory — the disabled-by-default, local-only desktop buffer of recent screen/app/window context, plus its status and query actions. Use when the user asks what was on screen recently, or when reading, exporting, enabling, or describing Screen Memory.
原文の言語: 英語
How Notion sync works. Covers connecting, linking pages, pulling from Notion, pushing to Notion, and checking sync status.
原文の言語: 英語
Build and iterate on a full real app from Design, backed by a running Builder Fusion cloud container instead of an inline HTML prototype. Use when the user wants a real/full app end-to-end through publishing, and only when FULL_APP_BUILDING_ENABLED is true.
原文の言語: 英語
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…
原文の言語: 英語
Use when queuing, reviewing, editing, opening, or sending email drafts requested by organization teammates, including Slack @agent-native intake.
原文の言語: 英語
Create, edit, and send email drafts through compose-{id} application state, manage-draft, and send-email. Use when composing, replying, forwarding, attaching files, applying signatures/writing style, or checking open/click tracking on sent mail.
原文の言語: 英語
Natural-language inbox automation rules (manage-automations, trigger-automations) and provider-native Gmail filters (manage-gmail-filters), including how the two differ. Use when the user asks to auto-label, auto-archive, auto-star, or otherwise handle…
原文の言語: 英語
Listing and searching mail with coverage-aware inventory envelopes, refreshing the UI after mutations, and bulk unread cleanup. Use when reading, searching, counting, archiving, starring, moving, or marking mail read, or when reporting how much of an inbox…
原文の言語: 英語
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.
原文の言語: 英語
Which browser surfaces are directly editable and which patch op each one autosaves through — inline prose, local plan folders, review annotation mode, canvas/design elements, and branding. Use when changing plan prose, styles, or wireframe/prototype HTML.
原文の言語: 英語
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.
原文の言語: 英語
The MDX source surface for plans: export, import, patch by semantic ID, DB-free local plan folders, `comments.json` sidecars, promotion into a repo, and the Desktop folder bridge. Use when a plan must round-trip to or from repo files.
原文の言語: 英語
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.
原文の言語: 英語
Full reference for the 25 tasks actions: HTTP method, arguments, defaults, and confirmation rules. Use when you need an action's method or exact behavior beyond the compact index in AGENTS.md, or before adding an action.
原文の言語: 英語
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.
原文の言語: 英語
How the agent captures, reads, edits, reorders, and deletes tasks and inbox items using view-screen context. Use when the user mentions "this task", "these tasks", "this inbox item", or "the list", or asks to capture, show, review, reorder, complete, or…
原文の言語: 英語
Answer code/product questions as visual Plan artifacts using repo, bridge, or GitHub context; use for API specs, UI look, schema models, and architecture.
原文の言語: 英語
The /agents admin home for Analytics: fleet feature-flag control plane, dashboard usage audit, and connected-app database admin. Use when an admin asks about feature flags/rollouts, dashboard usage stats, or connecting another agent-native app's database.
原文の言語: 英語
Implementation map for the Monitoring tab (uptime checks, public status pages, error triage): component/server file locations, schema, jobs, and scheduler wiring. Use when building or debugging Monitoring UI, uptime checks, status pages, or error…
原文の言語: 英語
Form lifecycle management: draft, published, closed. Use when publishing forms, understanding public URLs, configuring captcha, or managing form branding.
原文の言語: 英語
Cross-platform pattern for handling messaging integration webhooks (Slack, Telegram, WhatsApp, email, etc.) on serverless hosts. Use when adding a new integration adapter, debugging dropped messages, or wiring long-running agent work into a webhook handler.
原文の言語: 英語
Framework-wide voice dictation in the agent sidebar composer. Use when changing composer microphone UX, the transcribe-voice route, or the Voice Transcription settings section. Covers transcription-source routing, cleanup routing, Google realtime gating, and…
原文の言語: 英語
Multi-user collaborative editing with Yjs CRDT, SSE fast-path transport, and granular server-side merge. Use when adding real-time collaborative editing to a template, debugging sync issues, or understanding how the agent and humans edit documents…
原文の言語: 英語
How to keep the UI in sync with agent changes via SSE plus polling fallback. Use when wiring query invalidation for new data models, debugging UI not updating, or understanding jitter prevention.
原文の言語: 英語
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…
原文の言語: 英語
Declare, evaluate, manage, and remove framework feature flags. Use when shipping a capability gradually, targeting users or organizations, or replacing a compile-time rollout switch with a production-safe runtime flag.
原文の言語: 英語