Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

deploy

Estrellas1

Forks1

Actualizado13 de mayo de 2026 a las 20:04

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

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

jdevalk

jdevalk/joost-blog

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

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

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.

Más de este repositorio

mismo repositorio

astro-seo

jdevalk/joost-blog

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-041

emdash-github-actions

jdevalk/joost-blog

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-031

github-profile

jdevalk/joost-blog

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-031

github-repo

jdevalk/joost-blog

Audits and improves GitHub repository quality — README structure, community health files, .github directory setup, issue/PR templates, metadata, releases, and branch hygiene. Use this skill whenever the user asks to improve, audit, review, or set up a GitHub repository, or when they mention things like "make my repo look professional", "add contributing guidelines", "set up issue templates", "improve my README", "clean up my repo", "prepare my repo for open source", or "make my GitHub project look good". Also trigger when working inside a git repository and the user asks about best practices for documentation, community files, or repository structure. If the user is in a repo directory and mentions README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT, LICENSE, .github, templates, or release tags, use this skill.

2026-05-031

metadata-check

jdevalk/joost-blog

Reviews short high-value strings — page titles, meta descriptions, schema description fields, FAQ answers, GitHub repo taglines, profile bios, social-card copy, and other metadata where Flesch and paragraph-level readability checks don't apply. Checks front-loading, concreteness, filler, active voice, title/description duplication, difficult words, SERP-truncation fit, and one-idea-per-field. Use when the user asks to review metadata, a tagline, a bio, or SEO strings, or proactively after generating any short string with audience-facing impact. Chained into by astro-seo, wp-readme-optimizer, github-repo, and github-profile for their metadata outputs. For multi-paragraph prose, use the `readability-check` skill instead.

2026-05-031

readability-check

jdevalk/joost-blog

Runs a readability audit on a blog post draft or other multi-paragraph prose, calibrated for readers who read English as a second language. Checks nine categories — paragraph structure, opening paragraph strength, tiered sentence length, passive voice, difficult words, filler and hedging, transitions, variation, and heading hierarchy — and reports a Flesch Reading Ease score with a per-category status. Use when the user asks to check readability, run a readability pass, or asks "is this readable", or proactively as a second pass after a substantial draft is complete. Also invoked by the github-repo, github-profile, and wp-readme-optimizer skills on their generated prose. For short strings (titles, meta descriptions, taglines, bios), use the `metadata-check` skill instead — Flesch and paragraph-level checks don't apply to them.

2026-05-031

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.