菜单
Use when creating, editing, previewing, or publishing blog posts through the local working-copy flow, especially when the task involves `content/blog`, `npm run blog:*` commands, or `/blog-preview/...` URLs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
One API and one credential for frontier and open-source LLMs, built into your Neon branch and powered by Databricks. Use when a user wants to call an LLM, add AI/chat/an agent to their app, route between model providers (OpenAI, Google/Gemini, Meta, Alibaba, DeepSeek), or avoid juggling separate provider API keys and accounts — especially when they already use Neon and want AI requests to branch with their project. Works with the OpenAI SDK, google-genai, the Vercel AI SDK, and Mastra by changing only the base URL. Triggers include "call an LLM", "add AI to my app", "chat completion", "model routing", "LLM proxy/gateway", "one API for all models", "use GPT/Gemini", "AI SDK", "Mastra agent", "Neon AI Gateway", and "log/rate-limit AI calls".
Build and operate multi-tenant AI agent platforms on Neon. Use this skill whenever the user is designing an agent/app builder, provisioning a Neon project or database per user/app/agent run, managing thousands of tenant projects, separating sponsored free users from paid customers, moving projects between orgs, choosing personal vs organization vs project-scoped API keys, tracking fleet consumption or Agent Plan costs, creating compound checkpoints that combine DB snapshots with source revisions/secrets/deploy metadata, or orchestrating snapshot/restore flows for generated apps. Also use it for Neon Agent Program, Agent Plan, org/project limits, HIPAA, co-marketing, support, or neondatabase/neon-for-agent-platforms examples.
| name | blog-authoring |
| description | Use when creating, editing, previewing, or publishing blog posts through the local working-copy flow, especially when the task involves `content/blog`, `npm run blog:*` commands, or `/blog-preview/...` URLs. |
Default editing workflow:
content/blog/.Do not default to editing the remote source-of-truth repository directly unless the user explicitly asks for it.
Before changing content, verify the current state:
git branch --show-current
npm run blog:status
If content/blog is missing, initialize it:
npm run blog:bootstrap
If the user explicitly wants to refresh the working copy from remote state:
npm run blog:sync -- --force
Edit only:
content/blog/posts/*.mdcontent/blog/authors/data.jsoncontent/blog/categories/data.jsonThen run:
npm run dev
Use the local app to review:
/blog/blog/<slug>blogUse the built-in CLI:
npm run blog:publish-branch -- --branch <branch-name>
Defaults:
--branch is omitted, the current git branch name is usedcontent/blog snapshot into the configured remote content repository/blog-preview/...Open the generated preview URL, for example:
/blog-preview/<slug>?branch=<branch>&secret=<secret>
If the preview returns 404, treat that as “access denied or missing branch/slug”. Do not assume the route is public.
content/blog in the current repository as the editing surface.content/blog automatically; only use blog:sync -- --force when the user explicitly wants a refresh.git remote -v first and confirm which remote is safe to push to.src/scripts/compare-sites.js.Load only what you need:
references/commands.md