deploy

Deploy the joost-blog site. Regenerates the NLWeb search index (including embeddings), commits changes, and pushes to trigger a Cloudflare Pages deploy.

Jump to install

Repository: jdevalk/joost-blog
Last source activity: May 13, 2026 at 20:04
Detected SKILL.md language: English
Stars: 1
Forks: 1

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/jdevalk/joost-blog --skill deploy

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

astro-seo

Audits and improves SEO for Astro sites. Use when the user asks to audit, set up, or improve SEO on an Astro site, or mentions head metadata, structured data, JSON-LD, sitemaps, IndexNow, Open Graph images, schema endpoints, NLWeb, hreflang, or search engine indexing in an Astro project. Produces drop-in code routed through `@jdevalk/astro-seo-graph` and chains into `metadata-check` for generated SEO strings.

2026-05-04

emdash-github-actions

Sets up GitHub Actions CI/CD workflows for EmDash plugins — TypeScript type-checking, ESLint linting, Vitest testing, npm publishing, and automated releases. ALWAYS use this skill when a user wants to create, add, set up, or configure GitHub Actions, CI/CD, automated checks, or deployment workflows for an EmDash plugin — even if they don't use the exact phrase "GitHub Actions". This includes any request to: add automated type-checking or linting to an EmDash plugin repo; set up testing in CI for a plugin; auto-publish a plugin to npm from GitHub; add security scanning or dependency auditing to a plugin pipeline; or generally "add CI", "add automated checks", "set up workflows", or "automate" anything related to an EmDash plugin's GitHub repository. Also trigger when someone wants quality gates on PRs or is setting up a new EmDash plugin repo and wants best practices for automation. If the user is inside an EmDash plugin repository and mentions anything about automated testing, code quality, deployment, or Git

2026-05-03

github-profile

Audits and optimizes GitHub profile pages — profile README, metadata fields, pinned repositories, stats widgets, and contribution visibility. Use this skill whenever the user asks to improve, create, review, or optimize their GitHub profile, or mentions "profile README", "GitHub bio", "pinned repos", "GitHub stats", "contribution graph", or "GitHub presence". Also trigger when someone says things like "make my GitHub look good", "I want a better GitHub profile", "help me stand out on GitHub", "set up my GitHub page", or "optimize my developer profile". Works for both personal profiles and organization profile pages.

2026-05-03

View all from this repository

Deploy

Deploys the joost-blog site to Cloudflare Pages.

What it does

Fetches YouTube transcripts for any new videos (scripts/fetch-transcripts.mjs)

Uses cached transcripts when the file already exists
Requires yt-dlp on PATH (install via brew install yt-dlp)

Regenerates the NLWeb search index (scripts/generate-nlweb-index.mjs)

Scans all blog posts, pages, and videos
Skips draft content
Appends each video's transcript to its search body
Generates embeddings for new/changed content via Cloudflare API
Uses cached embeddings for unchanged content

Stages the updated index + any new transcript files

Commits with a descriptive message

Pushes to origin, triggering the Cloudflare Pages deploy

Steps

Run node scripts/fetch-transcripts.mjs and show the output to the user

Run node --env-file-if-exists=.env scripts/generate-nlweb-index.mjs and show the output

Check what changed under src/generated/ with git status --short src/generated/

Stage:

git add src/generated/nlweb-index.json src/generated/nlweb-index.mjs src/generated/embedding-cache.json src/generated/transcripts/

(plus any other staged content the user is shipping)

Run git status to show the user what will be deployed

Ask the user for a commit message (suggest one based on what changed)

Commit and push to origin

Confirm the deploy was triggered

Notes

The CF_API_TOKEN and CF_ACCOUNT_ID environment variables must be available for embedding generation; they live in .env. Pass --env-file-if-exists=.env to Node so the script picks them up.

The prebuild step was removed from package.json — the index must be regenerated locally before deploying.

If only code changes (no content changes), the index regeneration will show "0 to generate" and the cached index is reused.

fetch-transcripts.mjs is a no-op for videos that already have a cached transcript, so it's safe to run on every deploy.

Deploy

Deploys the joost-blog site to Cloudflare Pages.

What it does

Fetches YouTube transcripts for any new videos (scripts/fetch-transcripts.mjs)

Uses cached transcripts when the file already exists
Requires yt-dlp on PATH (install via brew install yt-dlp)

Regenerates the NLWeb search index (scripts/generate-nlweb-index.mjs)

Scans all blog posts, pages, and videos
Skips draft content
Appends each video's transcript to its search body
Generates embeddings for new/changed content via Cloudflare API
Uses cached embeddings for unchanged content

Stages the updated index + any new transcript files

Commits with a descriptive message

Pushes to origin, triggering the Cloudflare Pages deploy

Steps

Run node scripts/fetch-transcripts.mjs and show the output to the user

Run node --env-file-if-exists=.env scripts/generate-nlweb-index.mjs and show the output

Check what changed under src/generated/ with git status --short src/generated/

Stage:

git add src/generated/nlweb-index.json src/generated/nlweb-index.mjs src/generated/embedding-cache.json src/generated/transcripts/

(plus any other staged content the user is shipping)

Run git status to show the user what will be deployed

Ask the user for a commit message (suggest one based on what changed)

Commit and push to origin

Confirm the deploy was triggered

Notes

The CF_API_TOKEN and CF_ACCOUNT_ID environment variables must be available for embedding generation; they live in .env. Pass --env-file-if-exists=.env to Node so the script picks them up.

The prebuild step was removed from package.json — the index must be regenerated locally before deploying.

If only code changes (no content changes), the index regeneration will show "0 to generate" and the cached index is reused.

fetch-transcripts.mjs is a no-op for videos that already have a cached transcript, so it's safe to run on every deploy.

name	deploy
description	Deploy the joost-blog site. Regenerates the NLWeb search index (including embeddings), commits changes, and pushes to trigger a Cloudflare Pages deploy.
user_invocable	true

name	deploy
description	Deploy the joost-blog site. Regenerates the NLWeb search index (including embeddings), commits changes, and pushes to trigger a Cloudflare Pages deploy.
user_invocable	true

deploy

Source facts

Install options

Review the source files

More from this repository

Deploy

What it does

Steps

Notes

Deploy

What it does

Steps

Notes

More from this repository