preview
Render and deploy project documents, reports, and notebooks. Use when docs need to be shared or when previewing how documents render with citations and formatting.
How do I install this agent skill?
npx skills add https://github.com/allenai/asta-plugins --skill previewIs this agent skill safe to install?
- Gen Agent Trust Hubfail
This skill provides functionality for rendering and deploying project documentation via Quarto and GitHub Actions. It is flagged as high risk because its instructions guide the agent to weaken or overwrite repository security settings, specifically disabling branch protection requirements like mandatory reviews. It also relies on external GitHub Actions.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
- ZeroLeakspass
Score: 93/100 · 2 sections analyzed
What does this agent skill do?
Preview
Render and deploy project documents, reports, and notebooks using Quarto.
Usage
If _quarto.yml or .github/workflows/docs.yml is missing, complete the setup sections below first.
Push the branch. CI renders and deploys automatically. PR preview URLs: https://<owner>.github.io/<repo>/pr-preview/pr-<number>/ (private repos use an obfuscated domain but the same path structure). Check CI status with gh run list / gh run view.
For local preview: quarto preview (hot reloads). One-time build: quarto render.
Quarto Project Setup
If the project doesn't have a _quarto.yml yet, confirm the plan with the user, then:
- Check
which quarto. If not installed locally, see https://quarto.org/docs/get-started/ — or use the Workspace skill to get a devcontainer with Quarto pre-installed. - Copy assets/_quarto.yml to the project root and adjust the title.
- Create an
index.qmdwith YAML frontmatter (title:at minimum). Use.qmdfor all documents — it's Quarto's canonical format and required for full tooling support. - Add
_site/and.quarto/to.gitignore. - Each subdirectory needs an
index.qmdor its sidebar link will 404.
GitHub Pages Setup
Set this up to deploy rendered docs via GitHub Pages with PR previews. If the project doesn't have .github/workflows/docs.yml yet, confirm the plan with the user, then:
- Copy assets/docs.yml to
.github/workflows/docs.yml. This workflow renders with Quarto, validates the output (fails on warnings like broken citations), and deploys with PR preview support. - Pages must serve from the
gh-pagesbranch, not "GitHub Actions" workflow mode — the artifact model can't host PR previews alongside the main site.gh api repos/{owner}/{repo}/pages -X POST --input - <<'EOF' {"build_type":"legacy","source":{"branch":"gh-pages","path":"/"}} EOF - Require CI to pass and PRs for all changes to
main. This overwrites existing branch protection (docs):gh api repos/{owner}/{repo}/branches/main/protection -X PUT --input - <<'EOF' { "required_status_checks": {"strict": false, "contexts": ["build-and-deploy"]}, "enforce_admins": false, "required_pull_request_reviews": {"required_approving_review_count": 0}, "restrictions": null } EOF
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/allenai/asta-plugins/preview">View preview on skillZs</a>