[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75TFY0PFPDQX92C6S5V6Z8B":3,"skill-same:01M75TFY0PFPDQX92C6S5V6Z8B":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M75TFY0PFPDQX92C6S5V6Z8B","dashboard-chat-best-practices",null,"Apply dashboard-grade chat UX patterns in the Eve chat template. Use when changing Next.js Cache Components\u002FPPR behavior, static shell layout, Suspense bootstrap boundaries, theme hydration, auth display hydration, signed-in\u002Fsigned-out static shell behavior, optimistic messages, streaming row identity, composer\u002Fsidebar interactions, thinking\u002Ftool rendering, responsive styling, visual polish, or Vercel dashboard chat comparisons.","vercel\u002Feve","vercel","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F14985020?v=4","01M75TEEHHNJR9E6CG84ENB3MS","Vercel","01M75TEEJ5BJVTCPRH9YAWSMW4",5902,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Feve-chat-template\u002F.agents\u002Fskills\u002Fdashboard-chat-best-practices\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: dashboard-chat-best-practices\ndescription: Apply dashboard-grade chat UX patterns in the Eve chat template. Use when changing Next.js Cache Components\u002FPPR behavior, static shell layout, Suspense bootstrap boundaries, theme hydration, auth display hydration, signed-in\u002Fsigned-out static shell behavior, optimistic messages, streaming row identity, composer\u002Fsidebar interactions, thinking\u002Ftool rendering, responsive styling, visual polish, or Vercel dashboard chat comparisons.\n---\n\n# Dashboard Chat Best Practices\n\n## Overview\n\nUse this skill to keep the template's web chat feeling like a polished dashboard surface: stable, quiet, fast to first paint, and predictable under streaming state.\n\n## Product Shape\n\n- Build the actual chat surface, not a marketing page. The first screen should be a usable composer, sidebar, or chat route.\n- Keep the aesthetic restrained and work-focused: dense but readable spacing, quiet borders, predictable controls, and minimal decoration.\n- Prefer existing shadcn\u002FTailwind primitives and local components over new abstractions.\n- Use icons for compact commands, with accessible labels\u002Ftooltips. Avoid explanatory in-app text for behavior that good controls can imply.\n\n## Cache Components And PPR Basics\n\n- Keep `cacheComponents: true` enabled in `next.config.ts`. Treat the chat route as a static shell with dynamic data streamed into Suspense boundaries.\n- Keep the shell cheap and deterministic. Do not make `app\u002F(chat)\u002Flayout.tsx` wait on auth, database, chat history, or per-chat data before rendering the shell.\n- Pass cheap initial state into `AgentChatShell`: empty history, `initialNextCursor: null`, `viewer: null`, and `getInitialSetupStatus()`.\n- Load expensive or request-bound data inside hidden Suspense children: `ResolvedChatBootstrap` for setup\u002Fviewer\u002Fsidebar history and `ExistingChat` for active chat data.\n- Use sync components to hand resolved server data to the client shell. `AgentChatBootstrapSync` should update setup status, viewer, and history. `AgentChatRouteSync` should update the active chat for the current route.\n- Keep Suspense fallbacks `null` for these sync boundaries when the visible shell already has stable placeholders. Do not add loading panels that push the chat frame around.\n- Do not call `notFound()` until the dynamic boundary has enough real viewer\u002Fsetup\u002Fchat data to prove the chat is inaccessible. The outer shell should still render while that decision is loading.\n- Keep root and session routes visually distinct but structurally compatible. The root page can center the composer; the session page can pin it near the bottom. Both should live inside the same shell.\n- Treat PPR\u002Fstatic shell work as a latency feature and a correctness feature. The goal is first paint without auth\u002Fdatabase blocking, then precise data reconciliation after bootstrap.\n\n## Static Shell And Hydration\n\n- Preserve the shell-first strategy. `AgentChatShell` should paint the sidebar frame, top controls, and route body before auth, setup, or chat history finishes loading.\n- Keep bootstrap data out of the blocking route path. Use hidden Suspense sync components to hydrate setup status, viewer, sidebar history, and active chat data.\n- Preserve theme pre-hydration. Theme should be resolved before React paints so dark\u002Flight mode does not flash or mismatch.\n- Preserve auth display pre-hydration. The `eve_logged_in` cookie is a display hint only; the head script sets `data-eve-auth-display` so CSS can hide the wrong signed-in\u002Fsigned-out branch before viewer data resolves.\n- Never treat the auth hint as authority. Server actions, chat loading, Eve auth, and rate limits must use the real Better Auth session.\n- Keep `suppressHydrationWarning` only where it protects known pre-hydration document mutations such as theme\u002Fauth display hints.\n\n## Same Route, Signed In Or Out\n\n- Render one shared route shell for signed-in and signed-out states. Do not fork the page into separate auth routes just to show different controls.\n- While bootstrap is loading, render both possible placeholders inside `AuthDisplayLoggedIn` and `AuthDisplayLoggedOut`; let the document dataset hide the wrong branch.\n- For signed-out users, show the Sign in affordance immediately. For signed-in users, show a neutral user-menu placeholder instead of flashing Sign in.\n- After bootstrap resolves, render from real `viewer` state: `viewer ? \u003CUserMenu \u002F> : \u003CSidebarSignInButton \u002F>`.\n- When a signed-out user submits text, save the draft to `sessionStorage`, open the auth modal, and restore the draft after sign-in.\n\n## Optimistic Messaging And Row Identity\n\n- Show an optimistic user bubble immediately on send, but keep persisted Eve events as the source of truth.\n- Clear the optimistic user bubble only when the reduced event log contains the real latest user message.\n- Keep live chat state centralized where possible. Avoid rendering from multiple competing sources in the same frame.\n- Prefer stable row identities for streaming responses. A \"thinking\" or \"streaming reply\" row should become the assistant row without remounting into a different component path.\n- Use a separate thinking presence only when there is no meaningful assistant text yet or a turn is still finalizing. Fade it out rather than abruptly removing it.\n- Avoid letting final snapshot writes fight live state. During streaming, prefer the live source; after settle, reconcile with the canonical snapshot.\n\n## Composer And Sidebar\n\n- Keep `ChatComposer` controlled by the page: `value`, `onChange`, `onSubmit`, `disabled`, `disabledReason`, `isBusy`, and `isPreparing`.\n- Enter should submit. Shift+Enter should insert a newline. Disabled states should expose actionable tooltip text.\n- Busy state should show Stop. Preparing state should show a spinner. Empty or over-limit input should disable send without moving layout.\n- Root and session pages can place the composer differently, but they should share the same component and control contract.\n- Persist desktop sidebar open state in a cookie and write a pre-hydration document hint to avoid open-then-collapse flicker.\n- Keep sidebar history cursor-paginated and optimistic. Use `touchChat`, `removeChat`, and title updates for sidebar state; do not make sidebar state the transcript source of truth.\n- Keep mobile sidebar overlay behavior separate from desktop persistent state.\n\n## Message Rendering\n\n- Render user messages as compact right-aligned bubbles. Render assistant text as full-width left-aligned prose.\n- Use Streamdown for assistant markdown. Keep code blocks, lists, and inline code readable in both themes.\n- Group related dynamic tool parts into compact rows. Expand details only when there is useful input, output, error, or HITL control.\n- Render reasoning as a collapsible block. Label active reasoning as \"Thinking...\" and settled reasoning as \"Reasoning\".\n- Render connection authorization as a structured card, not prose embedded in assistant text.\n- Keep text inside controls and cards from overflowing at mobile widths. Prefer stable dimensions for buttons, tool rows, counters, and composer controls.\n\n## Styling Rules\n\n- Use the existing token system: `background`, `foreground`, `muted`, `border`, `card`, `accent`, and local opacity patterns.\n- Keep cards modest. Do not nest cards inside cards. Use cards for messages, modals, repeated items, or framed controls, not whole-page decoration.\n- Keep radius consistent with the template. Avoid large pill shapes unless the local component already uses them.\n- Avoid large decorative gradients, orbs, blobs, and marketing-style hero layouts in the chat app.\n- Use lucide icons when an icon exists. Add `aria-label` for icon-only buttons and tooltip text where meaning is not obvious.\n- Avoid layout shifts from loading, hover, or stream state. Reserve stable space for composer controls, sidebar rows, auth placeholders, and thinking\u002Ftool rows.\n\n## Verification\n\n- Run `pnpm typecheck` and `pnpm build` after UI or app-router changes.\n- Manually check root signed-out, root signed-in, auth modal draft restore, first-message navigation, follow-up optimistic send, streaming assistant row, Connect\u002FSkip auth cards, theme first paint, desktop sidebar cookie restore, and mobile sidebar overlay when touched.\n- Use screenshots or browser checks for visual changes across desktop and mobile. Watch specifically for auth flicker, theme flash, composer jumps, sidebar jumps, and message remount flicker.\n","# Dashboard Chat Best Practices\n\n## Overview\n\nUse this skill to keep the template's web chat feeling like a polished dashboard surface: stable, quiet, fast to first paint, and predictable under streaming state.\n\n## Product Shape\n\n- Build the actual chat surface, not a marketing page. The first screen should be a usable composer, sidebar, or chat route.\n- Keep the aesthetic restrained and work-focused: dense but readable spacing, quiet borders, predictable controls, and minimal decoration.\n- Prefer existing shadcn\u002FTailwind primitives and local components over new abstractions.\n- Use icons for compact commands, with accessible labels\u002Ftooltips. Avoid explanatory in-app text for behavior that good controls can imply.\n\n## Cache Components And PPR Basics\n\n- Keep `cacheComponents: true` enabled in `next.config.ts`. Treat the chat route as a static shell with dynamic data streamed into Suspense boundaries.\n- Keep the shell cheap and deterministic. Do not make `app\u002F(chat)\u002Flayout.tsx` wait on auth, database, chat history, or per-chat data before rendering the shell.\n- Pass cheap initial state into `AgentChatShell`: empty history, `initialNextCursor: null`, `viewer: null`, and `getInitialSetupStatus()`.\n- Load expensive or request-bound data inside hidden Suspense children: `ResolvedChatBootstrap` for setup\u002Fviewer\u002Fsidebar history and `ExistingChat` for active chat data.\n- Use sync components to hand resolved server data to the client shell. `AgentChatBootstrapSync` should update setup status, viewer, and history. `AgentChatRouteSync` should update the active chat for the current route.\n- Keep Suspense fallbacks `null` for these sync boundaries when the visible shell already has stable placeholders. Do not add loading panels that push the chat frame around.\n- Do not call `notFound()` until the dynamic boundary has enough real viewer\u002Fsetup\u002Fchat data to prove the chat is inaccessible. The outer shell should still render while that decision is loading.\n- Keep root and session routes visually distinct but structurally compatible. The root page can center the composer; the session page can pin it near the bottom. Both should live inside the same shell.\n- Treat PPR\u002Fstatic shell work as a latency feature and a correctness feature. The goal is first paint without auth\u002Fdatabase blocking, then precise data reconciliation after bootstrap.\n\n## Static Shell And Hydration\n\n- Preserve the shell-first strategy. `AgentChatShell` should paint the sidebar frame, top controls, and route body before auth, setup, or chat history finishes loading.\n- Keep bootstrap data out of the blocking route path. Use hidden Suspense sync components to hydrate setup status, viewer, sidebar history, and active chat data.\n- Preserve theme pre-hydration. Theme should be resolved before React paints so dark\u002Flight mode does not flash or mismatch.\n- Preserve auth display pre-hydration. The `eve_logged_in` cookie is a display hint only; the head script sets `data-eve-auth-display` so CSS can hide the wrong signed-in\u002Fsigned-out branch before viewer data resolves.\n- Never treat the auth hint as authority. Server actions, chat loading, Eve auth, and rate limits must use the real Better Auth session.\n- Keep `suppressHydrationWarning` only where it protects known pre-hydration document mutations such as theme\u002Fauth display hints.\n\n## Same Route, Signed In Or Out\n\n- Render one shared route shell for signed-in and signed-out states. Do not fork the page into separate auth routes just to show different controls.\n- While bootstrap is loading, render both possible placeholders inside `AuthDisplayLoggedIn` and `AuthDisplayLoggedOut`; let the document dataset hide the wrong branch.\n- For signed-out users, show the Sign in affordance immediately. For signed-in users, show a neutral user-menu placeholder instead of flashing Sign in.\n- After bootstrap resolves, render from real `viewer` state: `viewer ? \u003CUserMenu \u002F> : \u003CSidebarSignInButton \u002F>`.\n- When a signed-out user submits text, save the draft to `sessionStorage`, open the auth modal, and restore the draft after sign-in.\n\n## Optimistic Messaging And Row Identity\n\n- Show an optimistic user bubble immediately on send, but keep persisted Eve events as the source of truth.\n- Clear the optimistic user bubble only when the reduced event log contains the real latest user message.\n- Keep live chat state centralized where possible. Avoid rendering from multiple competing sources in the same frame.\n- Prefer stable row identities for streaming responses. A \"thinking\" or \"streaming reply\" row should become the assistant row without remounting into a different component path.\n- Use a separate thinking presence only when there is no meaningful assistant text yet or a turn is still finalizing. Fade it out rather than abruptly removing it.\n- Avoid letting final snapshot writes fight live state. During streaming, prefer the live source; after settle, reconcile with the canonical snapshot.\n\n## Composer And Sidebar\n\n- Keep `ChatComposer` controlled by the page: `value`, `onChange`, `onSubmit`, `disabled`, `disabledReason`, `isBusy`, and `isPreparing`.\n- Enter should submit. Shift+Enter should insert a newline. Disabled states should expose actionable tooltip text.\n- Busy state should show Stop. Preparing state should show a spinner. Empty or over-limit input should disable send without moving layout.\n- Root and session pages can place the composer differently, but they should share the same component and control contract.\n- Persist desktop sidebar open state in a cookie and write a pre-hydration document hint to avoid open-then-collapse flicker.\n- Keep sidebar history cursor-paginated and optimistic. Use `touchChat`, `removeChat`, and title updates for sidebar state; do not make sidebar state the transcript source of truth.\n- Keep mobile sidebar overlay behavior separate from desktop persistent state.\n\n## Message Rendering\n\n- Render user messages as compact right-aligned bubbles. Render assistant text as full-width left-aligned prose.\n- Use Streamdown for assistant markdown. Keep code blocks, lists, and inline code readable in both themes.\n- Group related dynamic tool parts into compact rows. Expand details only when there is useful input, output, error, or HITL control.\n- Render reasoning as a collapsible block. Label active reasoning as \"Thinking...\" and settled reasoning as \"Reasoning\".\n- Render connection authorization as a structured card, not prose embedded in assistant text.\n- Keep text inside controls and cards from overflowing at mobile widths. Prefer stable dimensions for buttons, tool rows, counters, and composer controls.\n\n## Styling Rules\n\n- Use the existing token system: `background`, `foreground`, `muted`, `border`, `card`, `accent`, and local opacity patterns.\n- Keep cards modest. Do not nest cards inside cards. Use cards for messages, modals, repeated items, or framed controls, not whole-page decoration.\n- Keep radius consistent with the template. Avoid large pill shapes unless the local component already uses them.\n- Avoid large decorative gradients, orbs, blobs, and marketing-style hero layouts in the chat app.\n- Use lucide icons when an icon exists. Add `aria-label` for icon-only buttons and tooltip text where meaning is not obvious.\n- Avoid layout shifts from loading, hover, or stream state. Reserve stable space for composer controls, sidebar rows, auth placeholders, and thinking\u002Ftool rows.\n\n## Verification\n\n- Run `pnpm typecheck` and `pnpm build` after UI or app-router changes.\n- Manually check root signed-out, root signed-in, auth modal draft restore, first-message navigation, follow-up optimistic send, streaming assistant row, Connect\u002FSkip auth cards, theme first paint, desktop sidebar cookie restore, and mobile sidebar overlay when touched.\n- Use screenshots or browser checks for visual changes across desktop and mobile. Watch specifically for auth flicker, theme flash, composer jumps, sidebar jumps, and message remount flicker.\n",{"name":5,"description":7},"main","a318dcf054343b7a9007dd4e4367ac19374a6809","apps\u002Ftemplates\u002Feve-chat-template\u002F.agents\u002Fskills\u002Fdashboard-chat-best-practices",656,"https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve","https:\u002F\u002Feve.dev","https:\u002F\u002Fgithub.com\u002Fvercel","https:\u002F\u002Fvercel.com","Agentic infrastructure for every app and agent.","2026-11-15 05:08:34",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add vercel\u002Feve --skill dashboard-chat-best-practices",{"tool":40,"command":41},"bunx","bunx skills add vercel\u002Feve --skill dashboard-chat-best-practices",{"tool":43,"command":44},"pnpm","pnpm dlx skills add vercel\u002Feve --skill dashboard-chat-best-practices","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Feve-chat-template\u002F.agents\u002Fskills\u002Fdashboard-chat-best-practices\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",272,"https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Feve-chat-template\u002F.agents\u002Fskills\u002Fdashboard-chat-best-practices\u002Fagents\u002Fopenai.yaml",[55,63,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":62},"01M7DYJETPKENT6T9THCB7WKFD","writing-quality","The review rubric: writing-quality rules and reference lists for judging a content draft, covering AI-sounding phrasing, bloated wording, structure, and web-content specs. Load at the start of every review.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fsubagents\u002Freviewer\u002Fskills\u002Fwriting-quality\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":64,"name":57,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":62},"01M7DYJAZM6Y5VNF2PCM01N145","Writing-quality guardrails for any prose the agent drafts or edits: blog posts, page copy, Notion drafts, release notes, marketing text. Use this skill whenever writing or revising content meant for humans to read, to keep the prose natural, plain, and free of AI-sounding phrasing. Not needed for code, queries, or structural CMS work.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fwriting-quality\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":62},"01M7DYJ40G4YADA5P8YAEQ7W7F","seo-aeo-best-practices","SEO and AEO best practices for metadata, Open Graph, sitemaps, robots.txt, hreflang, JSON-LD structured data, EEAT, and content optimized for search engines and AI answer surfaces. Use this skill when implementing page SEO, technical SEO, schema markup, international SEO, AI-overview readiness, or improving content for Google, ChatGPT, Perplexity, and similar assistants.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fseo-aeo-best-practices\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":62},"01M7DYHX5JXJFHF2DZV64VFC13","sanity-best-practices","Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this skill whenever working with Sanity schemas, defineType or defineField, GROQ or defineQuery, content modeling, Presentation or preview setups, Sanity-powered frontend integrations, Sanity Functions, documentEventHandler, defineDocumentFunction, defineMediaLibraryAssetFunction, @sanity\u002Ffunctions, @sanity\u002Fblueprints, sanity.blueprint.ts, event-driven content automation, or when reviewing and fixing a Sanity codebase.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fsanity-best-practices\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":62},"01M7DYHQG96APC7EV3FANC90WX","portable-text-serialization","Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fportable-text-serialization\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":62},"01M7DYHJJ89WGRXXVWJAQNQW9M","portable-text-conversion","Convert HTML and Markdown content into Portable Text blocks for Sanity. Use when migrating content from legacy CMSs, importing HTML or Markdown into Sanity, building content pipelines that ingest external content, converting rich text between formats, or programmatically creating Portable Text documents. Covers @portabletext\u002Fmarkdown (markdownToPortableText), @portabletext\u002Fblock-tools (htmlToBlocks), custom deserializers, and the Portable Text specification for manual block construction.","https:\u002F\u002Fgithub.com\u002Fvercel\u002Feve\u002Fblob\u002Fmain\u002Fapps\u002Ftemplates\u002Fsanity-copilot-eve-template\u002Fagent\u002Fskills\u002Fportable-text-conversion\u002FSKILL.md",[],[]]