Navigate an Assets app to the right library, template, settings page, or chat surface. Understand route targets and navigation state, and determine where a workflow belongs when wiring chat or guiding a user through the interface.
Assets routes, tabs, chat surfaces, and `navigate` targets. Use when sending a user to a screen, interpreting navigation state, deciding which surface owns a workflow, or wiring chat into the Create tab or agent sidebar.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
navigate moves the UI to picker, library, generation, asset, and settings
surfaces. Use view-screen when the active library, selected asset, picker,
generation, or embed target is unclear.
/library is the cross-kit browsing surface./library/:libraryId opens a single brand kit./library with their iframe/auth bridge
params./) is the full-page Assets chat surface. Use the shared
assets chat thread storage there, keep past chats in the left sidebar, and
use the right agent sidebar only on non-Create routes with view-transition
handoff back to /./templates and edit one at
/templates/:templateId. Use navigate with { view: "templates" } or
{ view: "template", templateId }. Legacy { view: "preset", libraryId, presetId } navigation still resolves for existing conversations.logo-composite for the
settings.skeletonSpec shape and compositing behavior./settings/app) holds generation setup: Builder.io,
manual Gemini/OpenAI keys, and object storage (#asset-generation-setup,
#asset-storage). Keys and storage save at workspace scope, so only owners
and admins (or a solo workspace) can change them; members see them
read-only./settings/notifications) holds the generation
email switch. Read or change it with get-assets-notification-prefs and
update-assets-notification-prefs, never a raw settings write.open-settings-page; navigate with { view: "settings" } only opens
/settings.creative-context for submission and reuse rules.library-management — what lives behind the Library routes.inline-embeds — rendering an Assets route inline in chat.creative-context — the Context tab's reuse and provenance rules.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Generate, refine, export, and place brand images or videos from an Assets library into another app. The skill covers choosing a library, handling image batches and video runs, and updating selected assets after feedback.
Prepare a customer account health, renewal, or contract usage readout. Verify the account identity, use approved metric definitions, compare contracted capacity with actual usage, and trace findings to sources, time windows, and known gaps.
Create focused app actions that agents can call as tools and frontend code can use through client hooks. Use them to add provider integrations or fetch UI data, with validated inputs and structured results.
Use this checklist when adding a feature or integration to an agent-native app. It covers the user interface, agent-callable actions, instructions, and app-state sync so both the user and agent can work with the capability consistently.
Investigate complex questions by combining data from multiple sources, then summarize patterns, metrics, and evidence in a clear report. Save requested analyses as dashboards with instructions for future refreshes.
Use the Analytics admin surfaces to inspect and change workspace feature flags, review dashboard ownership and usage activity, or browse and edit databases connected from other agent-native apps. The skill guides administrators to the relevant view and actions.