メニュー
Prepares files for a new blog post — creates the markdown file in content/blog, writes frontmatter, copies media assets, and sets up a branch. Use when starting a new blog post from a .md/.doc file or raw text.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Apply the Diataxis documentation framework to Inngest docs. Use this when authoring new content, reviewing draft PRs, or deciding whether a proposed page fits the Explanation quadrant (especially for pattern pages like "Flash sales and bursty workflows").
Suggests, then implements internal links for new blog posts
Suggests, then implements internal links for new documentation pages
Hide docs pages, doc sections, nav items, changelog entries, and blog posts behind a `?unreleased=<label>` URL param until a feature ships. Use when staging unreleased documentation, changelog entries, or blog posts, previewing not-yet-public content, gating nav links, or working with the `<Unreleased>` component or `unreleased` exports/frontmatter in the website repo.
Use when planning, writing, reviewing, or updating Inngest documentation, docs metadata, docs PRs, launch docs, tutorials, how-to guides, reference pages, migration guides, LLM/AX docs, or docs-related Linear/Notion/Slack/GitHub workflows. This skill helps agents build source-grounded docs from Notion, Slack, Linear, GitHub, and the local website repo; apply SEO and metadata rules from the June 2026 docs SEO work; choose pragmatic Diataxis-style content shapes; check agent-readable docs surfaces; and close the loop with circular links across PRs, tickets, Notion, and Slack.
| name | new-blog-post |
| description | Prepares files for a new blog post — creates the markdown file in content/blog, writes frontmatter, copies media assets, and sets up a branch. Use when starting a new blog post from a .md/.doc file or raw text. |
| argument-hint | [source-file-or-text] |
Prepare the following files for a new blog post. Follow best practices in @AGENTS.md.
First, ensure that the repo is on the main branch and has the latest changes pulled from the remote.
Take any file, like a .md or .doc file, or raw text input, and create a new markdown file in the /content/blog directory.
tags field with one or more topics from this list (pick all that apply):
"AI & Agents", "Background Jobs & Scheduling", "Company & Product News", "Durable Execution", "Engineering", "Incidents & Security", "Integrations & Partners", "Next.js & Frameworks", "Observability & Debugging", "Queues & Flow Control", "Realtime", "SDKs & Languages", "Tutorials & Guides", "Workflows & Orchestration"AGENTS.md.http://www.inngest.com.?ref=blog-introducing-checkpointing) on internal links for marketing attribution. The ref tag should be in the format of blog-<slugified-title>.For all media do the following:
/public/assets/blog/<slugified-title>If assets are copied from a directory, remove those files after they are successfully copied.
/content/blog or /public/assets/blog directories unless explicitly asked.Create a new branch in the format blog/<slugified-title> and stage only the new files.