This skill should be used when validating the documentation build and preparing for GitHub Pages deployment. It runs the Eleventy build, validates output, checks component counts, and provides deployment instructions.
From soleurnpx claudepluginhub jikig-ai/soleur --plugin soleurThis skill uses the workspace's default tool permissions.
Validate the documentation build and prepare it for GitHub Pages deployment.
# Install dependencies (if needed)
npm ci
# 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"
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:
.md files (excluding README.md) under plugins/soleur/agents/SKILL.md files under plugins/soleur/skills/Cards in the output must match source file counts exactly.
git status --porcelain plugins/soleur/docs/ eleventy.config.js package.json
If there are uncommitted changes, warn the user to commit first.
Deployment is automated via .github/workflows/deploy-docs.yml:
main that changes docs, agents, skills, commands, plugin.json, or eleventy.config.jsThe workflow:
npx @11ty/eleventy to build_site/ as a Pages artifactProvide 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/