deploy-docs
/deploy-docs
This skill should be used when validating the documentation build and preparing for Cloudflare Pages deployment. It runs the Eleventy build, validates output, checks component counts, and provides deployment instructions.
- Author
- jikig-ai ↗
- Repository
- soleur ↗
- Licence
- Apache-2.0
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 2
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.
What it does and when to use it
This skill should be used when validating the documentation build and preparing for Cloudflare Pages deployment. It runs the Eleventy build, validates output, checks component counts, and provides deployment instructions.
Original author description
This skill should be used when validating the documentation build and preparing for Cloudflare Pages deployment. It runs the Eleventy build, validates output, checks component counts, and provides deployment instructions.
How it works
- Step 1: Build and Validate
- Step 2: Verify Component Counts
- Step 3: Check for Uncommitted Changes
- Step 4: Deployment
- Step 5: Report Status
SKILL.md preview
--- name: deploy-docs description: "This skill should be used when validating the documentation build and preparing for Cloudflare Pages deployment. It runs the Eleventy build, validates output, checks component counts, and provides deployment instructions." --- <!-- grok-harness-invoke:start --> **Grok Build (`plugins/soleur/lib/harness.ts` `invokeSkill()`):** Read this SKILL.md in this process and run it to completion. A one-segment `soleur:<name>` in this document names a SKILL — on Grok Build, Read `plugins/soleur/skills/<name>/SKILL.md` in this process; it is not a nested tool_use. A multi-segment id such as `soleur:<domain>:<name>` names an AGENT: spawn it, never Read it, and on Grok Build spawn_subagent takes the id with its colons replaced by hyphens (`agentIdToGrokSubagentType`). **Claude Code:** Skill tool for a skill (`soleur:<name>`), Task tool with `subagent_type` for an agent. Forbidden is executing a subset, not the Read. <!-- grok-harness-invoke:end --> # Deploy Documentation Command Validate the documentation build and prepare it for Cloudflare Pages deployment. ## Step 1: Build and Validate ```bash # Install dependencies (if needed) npm ci --ignore-scripts # Run Eleventy build npx @11ty/eleventy # Verify build output test -f _site/index.html && echo "OK index.html" test -f "_site/pages/agents.html" && echo "OK agents.html" test -f "_site/pages/skills.html" && echo "OK skills.html" test -f "_site/pages/changelog.html" && echo "OK changelog.html" test -f "_site/pages/getting-started.html" && echo "OK getting-started.html" test -f _site/404.html && echo "OK 404.html" test -f _site/css/style.css && echo "OK style.css" test -f _site/CNAME && echo "OK CNAME" test -f _site/sitemap.xml && echo "OK sitemap.xml" ``` ## Step 2: Verify Component Counts Use Grep to count occurrences of `component-card` in `_site/pages/agents.html` and `_site/pages/skills.html`. Then compare with source counts using Glob: - Agent files: count `.md` files (excluding README.md) under `plugins/soleur/agents/` - Skill files: count `SKILL.md` files under `plugins/soleur/skills/` Cards in the output must match source file counts exactly. ## Step 3: Check for Uncommitted Changes ```bash git status --porcelain plugins/soleur/docs/ eleventy.config.js package.json ``` If there are uncommitted changes, warn the user to commit first. ## Step 4: Deployment Deployment is automated via `.github/workflows/deploy-docs.yml`: - **Trigger:** Push to `main` that changes docs, agents, skills, commands, plugin.json, or eleventy.config.js - **Manual:** Go to Actions > "Deploy Documentation to Cloudflare Pages" > "Run workflow" The workflow: 1. Checks out the repo 2. Installs Node.js 20 and npm dependencies 3. Runs `npx @11ty/eleventy` to build 4. Verifies all required files are present 5. Stamps `_site/version.txt` with the commit SHA 6. Deploys `_site/` to the `soleur-docs` Cloudflare Pages project with wrangler 7. Fetches `version.txt` back and fails the job unless it matches the SHA just built ## Step 5: Report Status Provide a summary: ``` ## Deployment Readiness OK All HTML pages present OK CSS and fonts present OK Component counts match source OK CNAME and sitemap present ### Next Steps - [ ] Commit any pending changes - [ ] Push to main branch - [ ] Verify deployment at https://soleur.ai/ (the live apex) > **The ADR-194 cutover is COMPLETE (2026-09-03).** `https://soleur.ai/` is > served by Cloudflare Pages and DOES advance with these deploys — verify at the > apex, not at `pages.dev`. Until PR4b this block said the opposite and sent the > operator to the `pages.dev` hostname; that was correct then and is misdirection > now. `soleur-docs.pages.dev` still resolves and is still a useful > origin-vs-edge discriminator, but it is not where a deploy is confirmed. See > `knowledge-base/engineering/operations/runbooks/cloudflare-pages-cutover.md`. ```
Versions
The database has no other skills named deploy-docs.
Database snapshot: 13.11.2026 · package version ba4461ebb31c (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95Cloudflare
Deploy Cloudflare Workers/Pages. USE WHEN Cloudflare, worker, deploy, Pages, MCP server. SkillSearch('cloudflare') for docs. - 100cloudflare-pages
Deploy static sites to Cloudflare Pages with custom domains and CI/CD. Use when the user wants to deploy a site to Cloudflare Pages, add a custom domain to a Pages project, set up GitHub Actions CI/CD for Cloudflare Pages, roll back a deployment, or verify deployment status.… - 100release-docs
This skill should be used when updating documentation metadata after adding or removing plugin components. It updates plugin.json description and README.md counts, then verifies the Eleventy build produces correct output. - 100docs-site
This skill should be used when scaffolding a Markdown-based Eleventy documentation site: base layout, data files, GitHub Pages deployment workflow, and passthrough copy configuration. - 100cloudflare-deploy
Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare. - 95cloudflare-deploy
Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.