メニュー
Clean up the blog pipeline Kanban dashboard — removes cards that are stuck before the staging column (ideas, creating substages). Leaves cards in staging, review, and scheduled untouched.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Manage the blog.postman.com editorial calendar — list, reschedule, view monthly counts, or get a YTD summary. Enforces Tue/Thu-first scheduling with no conflicts or US public holidays.
Start or stop the blog pipeline Kanban dashboard (Flask app at dashboard/app.py, served on http://localhost:5001).
Show the number of blog posts published on blog.postman.com between two dates. Prompts for a start and end date, then queries WordPress and displays the count with a post listing, broken down by month and author.
Copy edit blog post output for grammar, syntax errors, repetitive sentence structures, and SEO optimization. Suggests an SEO-friendly title and 150-character meta description. Runs automatically as a hook after blog-write, or standalone via /blog-copyeditor [filename].
Convert a Google Doc to a blog-ready markdown file with images. Takes a Google Docs URL, exports the content as markdown, downloads embedded images, and saves everything to blog-output/.
Generate a Postman-branded blog header image (2560×1355 PNG, no text) using the Gemini image generation API (nanobanana). Analyzes reference images and follows the Postman design system for consistent brand visuals.
| name | blog-dashboard-cleanup |
| description | Clean up the blog pipeline Kanban dashboard — removes cards that are stuck before the staging column (ideas, creating substages). Leaves cards in staging, review, and scheduled untouched. |
| argument-hint | [--all] (omit to remove only pre-staging cards; pass --all to clear every card) |
| allowed-tools | ["Read","Write","Bash"] |
Remove stale or stuck cards from the blog pipeline Kanban board before they reach WordPress staging. Safe to run at any time — it never touches WordPress.
By default (no argument), this skill removes cards whose stage is any of:
ideas — never startedwriting — stuck in the writing substagecopyedit — stuck in the copyedit substageheader_image — stuck in the header image substagecreating — stuck in the creating column (catch-all)Cards in staging, review, or scheduled are left untouched — they have live WordPress drafts behind them.
If the user passes --all, remove every card regardless of stage.
The dashboard state lives at dashboard/state.json relative to the plugin root. Read references/state-file-ops.md for the path-resolution and file-locking patterns used in the steps below.
Use the path resolution and shared-lock read pattern from references/state-file-ops.md. Load cards = data.get("cards", []).
Use the filter-cards pattern from references/state-file-ops.md, passing the user's argument (None or "--all").
If there is nothing to remove, tell the user:
Dashboard is already clean — no stuck cards found.
Cards in staging / review / scheduled: N
If there are cards to remove, print a summary and ask for confirmation:
Cards to remove (stuck before staging):
ID Stage Topic
-------- ------------ ------------------------------------------
a1b2c3d4 writing Testing OAuth 2.0 Flows in Postman
e5f6g7h8 ideas GraphQL Testing with Postman
Remove these 2 card(s)? [y/N]
If the user passes --all, the confirmation message should say "Remove ALL N card(s) from the board?" instead.
Read the user's response. If they say anything other than y or yes (case-insensitive), abort:
Cancelled — no cards removed.
Set data["cards"] = to_keep, then use the exclusive-lock write pattern from references/state-file-ops.md.
Removed 2 card(s) from the dashboard.
Kept (staging / review / scheduled): 3
Board is clean — safe to continue the pipeline.
dashboard/state.json. It does not delete blog-output files, WordPress drafts, or any other files.wordpress_id and is still in a pre-staging stage (e.g., stuck in writing with a WP ID somehow), it is still removed — the WP draft remains and can be found manually in wp-admin.