Install
$ agentstack add skill-jerrylalala-compound-engineering-deploy-docs ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ● Network access Used
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Deploy Documentation Command
Validate the public documentation site and GitHub Pages deployment for Jerrylalala/compound-engineering.
Step 1: Validate Documentation
Run these checks:
bun run release:validate
python -m mkdocs build --strict
If Python dependencies are missing, install them first:
pip install -r requirements-docs.txt
Step 2: Check GitHub Pages Workflow
test -f .github/workflows/docs.yml
gh workflow view docs.yml --repo Jerrylalala/compound-engineering
The workflow should:
- Build with
mkdocs build --strict. - Upload the generated
site/directory. - Deploy to GitHub Pages with
actions/deploy-pages.
Step 3: Check for Uncommitted Changes
git status --porcelain
If mkdocs build created an untracked site/ directory, remove it before committing unless the user explicitly asked to inspect the built artifact.
Step 4: Deployment Instructions
After merging to main, docs deploy automatically when files matched by .github/workflows/docs.yml change. Manual deployment is also available:
- Open the repository Actions tab.
- Select
部署文档站点. - Click
Run workflow.
Step 5: Verify Published Pages
Check the deployed public URLs:
for url in \
https://jerrylalala.github.io/compound-engineering/ \
https://jerrylalala.github.io/compound-engineering/INSTALL/ \
https://jerrylalala.github.io/compound-engineering/SUPPORT-MATRIX/ \
https://jerrylalala.github.io/compound-engineering/PUBLISHING/ \
https://jerrylalala.github.io/compound-engineering/workflow.html \
https://jerrylalala.github.io/compound-engineering/pencil.html
do
curl -fsSL -o /dev/null "$url" && echo "ok $url"
done
Step 6: Report Status
Provide a summary:
## Deployment Readiness
✓ release metadata valid
✓ MkDocs strict build passed
✓ docs workflow exists
✓ published pages return HTTP 200
### Next Steps
- [ ] Commit any pending changes
- [ ] Push to main branch
- [ ] Verify the `部署文档站点` workflow passed
- [ ] Check deployment at https://jerrylalala.github.io/compound-engineering/
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Jerrylalala
- Source: Jerrylalala/compound-engineering
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.