All skills
nvidia-nemo avatar

/switchyard-docs

@239a413
by nvidia-nemonvidia-nemo/switchyard3.3k stars
317

Edit or debug the published Switchyard MkDocs site. Use for docs pages, mkdocs.yml navigation, mkdocs_hooks.py source links, strict build failures, local previews, or .github/workflows/docs.yml.

Use this Skill: https://skilld.dev/gh/nvidia-nemo/switchyard/switchyard-docs

This session only. Nothing lands on disk.

SKILL.md

≈53 tokens always: the name and description. ≈396 when used: this file.

Switchyard Documentation

The published site is the subset of docs/ selected by mkdocs.yml. Strict MkDocs warnings fail CI, so fix warnings rather than weakening validation.

Source Of Truth

Concern File
Navigation, exclusions, theme mkdocs.yml
Source-link rewriting mkdocs_hooks.py
Local commands docs/Makefile
Build, preview, deployment .github/workflows/docs.yml
Documentation dependencies pyproject.toml docs group

Workflow

  1. Decide whether a new page is public. Public pages go in nav; internal notes go in exclude_docs.
  2. Match the surrounding file naming and documentation style.
  3. Use relative links. For repository files outside docs/, use paths relative to the Markdown file and let mkdocs_hooks.py produce the source URL.
  4. Verify public examples use supported public imports and current CLI syntax.
  5. Run the strict build:
cd docs
make publish

CI Constraints

  • Keep the docs workflow path-filtered.
  • Keep default permissions read-only and grant write access only to deployment jobs.
  • Keep PR previews limited to same-repository pull requests.
  • Do not use pull_request_target to run untrusted documentation code with write permissions.
  • Build once and pass the site/ artifact to preview and deployment jobs.
  • Preserve keep_files: true so a main deployment does not remove PR previews.

Common strict-build fixes are direct: add or remove a missing nav entry, repair the relative link, or explicitly exclude an internal page. Do not disable strict mode.

Source: SKILL.md on GitHub

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides comprehensive instructions for managing a MkDocs-based documentation site, including build commands, directory structure, and CI/CD best practices. It correctly emphasizes security by recommending against risky GitHub Actions configurations like `pull_request_target`. No security vulnerabilities or malicious patterns were identified.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 239a413. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago

README badge

README badge for nvidia-nemo/switchyard/switchyard-docs