{"owner":"pytorch","repo":"tutorials","hasSkills":true,"totalSkillsCount":4,"totalTokensCount":1653,"categories":["claude-rule","mcp-config","marketplace","plugin-manifest"],"hasMcp":true,"mcpConfig":{"mcpServers":{"tutorials":{"command":"npx","args":["-y","@modelcontextprotocol/server-tutorials"]}}},"found":["CLAUDE.md",".cursor/mcp.json",".claude-plugin/marketplace.json",".claude-plugin/plugin.json"],"skills":{"CLAUDE.md":"# Project Structure\n\nThis is the PyTorch Tutorials website (`pytorch.org/tutorials`), built with Sphinx and Sphinx Gallery.\n\n- `beginner_source/`, `intermediate_source/`, `advanced_source/`, `recipes_source/`, `unstable_source/` — tutorial source files (`.py` and `.rst`)\n- `index.rst`, `recipes_index.rst` — card listings and toctrees for the website\n- `conf.py` — Sphinx configuration (gallery dirs, extensions, theme)\n- `_static/` — images, CSS, and thumbnails\n- `requirements.txt` — all Python dependencies (Sphinx, tutorial packages)\n- `.jenkins/` — CI build scripts, data download logic, post-processing\n- `Makefile` — build entry points\n\nTutorials authored as `.py` files use Sphinx Gallery format: top-level docstrings become RST prose, code blocks become executable cells. These are executed during builds and converted to Jupyter notebooks and HTML. Tutorials authored as `.rst` are static and their code is not executed.\n\n# Build\n\n- `make html-noplot` — builds HTML without executing tutorial code. Fast, no GPU needed. Use this for quick validation of RST/Sphinx structure.\n- `make docs` — full build that downloads data, executes all `.py` tutorials, and produces the final site. Requires a GPU-powered machine with CUDA.\n- `GALLERY_PATTERN=\"my_tutorial.py\" make html` — build only a single tutorial by name (regex supported).\n\nThe CI build runs inside Docker across 15 GPU-powered shards via `.jenkins/build.sh`.\n\n# Linting\n\nThis repo uses `lintrunner`. Do not use `spin`, `flake8`, or other linters directly.\n\n- `lintrunner -m main` — lint changes relative to the main branch\n- `lintrunner --all-files` — lint all files in the repo\n\nLintrunner checks trailing whitespace, tabs, and newline issues only. It does not check Python formatting, RST syntax, or Sphinx directives.\n\n# Testing\n\nThere is no unit test suite. Validation is done by building tutorials:\n\n- `make html-noplot` is the quick sanity check for RST and Sphinx errors.\n- Full execution of `.py` tutorials runs in CI on GPU shards.\n- To test a single tutorial: `GALLERY_PATTERN=\"my_tutorial.py\" make html`\n\n# Tutorial File Format\n\n- Interactive tutorials are `.py` files using Sphinx Gallery conventions. Filenames should end in `_tutorial.py`.\n- Non-interactive tutorials are `.rst` files.\n- Data dependencies must be added via `.jenkins/download_data.py`, not the Makefile. Follow the existing patterns in that file.\n- New Python package dependencies go in `requirements.txt`.\n\n# Adding a New Tutorial\n\n1. Place the file in the appropriate `*_source/` directory based on difficulty level.\n2. Add a `customcarditem` entry in `index.rst` (or `recipes_index.rst` for recipes).\n3. Add the tutorial to the corresponding `toctree` in `index.rst`.\n4. Add a square, high-resolution thumbnail image to `_static/img/thumbnails/cropped/`.\n\n# Coding Style Guidelines\n\nFollow these rules for all code changes in this repository:\n\n- Minimize comments; be concise; code should be self-explanatory.\n- Match existing code style and architectural patterns.\n- Tutorial prose should be written for a global audience with clear, easy to understand language. Avoid idioms.\n- Use active voice in tutorial instructions.\n- If uncertain, choose the simpler, more concise implementation.\n",".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/pytorch/tutorials/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/pytorch/tutorials/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/pytorch/tutorials/HEAD/.claude-plugin/plugin.json)"},"files":{"CLAUDE.md":"# Project Structure\n\nThis is the PyTorch Tutorials website (`pytorch.org/tutorials`), built with Sphinx and Sphinx Gallery.\n\n- `beginner_source/`, `intermediate_source/`, `advanced_source/`, `recipes_source/`, `unstable_source/` — tutorial source files (`.py` and `.rst`)\n- `index.rst`, `recipes_index.rst` — card listings and toctrees for the website\n- `conf.py` — Sphinx configuration (gallery dirs, extensions, theme)\n- `_static/` — images, CSS, and thumbnails\n- `requirements.txt` — all Python dependencies (Sphinx, tutorial packages)\n- `.jenkins/` — CI build scripts, data download logic, post-processing\n- `Makefile` — build entry points\n\nTutorials authored as `.py` files use Sphinx Gallery format: top-level docstrings become RST prose, code blocks become executable cells. These are executed during builds and converted to Jupyter notebooks and HTML. Tutorials authored as `.rst` are static and their code is not executed.\n\n# Build\n\n- `make html-noplot` — builds HTML without executing tutorial code. Fast, no GPU needed. Use this for quick validation of RST/Sphinx structure.\n- `make docs` — full build that downloads data, executes all `.py` tutorials, and produces the final site. Requires a GPU-powered machine with CUDA.\n- `GALLERY_PATTERN=\"my_tutorial.py\" make html` — build only a single tutorial by name (regex supported).\n\nThe CI build runs inside Docker across 15 GPU-powered shards via `.jenkins/build.sh`.\n\n# Linting\n\nThis repo uses `lintrunner`. Do not use `spin`, `flake8`, or other linters directly.\n\n- `lintrunner -m main` — lint changes relative to the main branch\n- `lintrunner --all-files` — lint all files in the repo\n\nLintrunner checks trailing whitespace, tabs, and newline issues only. It does not check Python formatting, RST syntax, or Sphinx directives.\n\n# Testing\n\nThere is no unit test suite. Validation is done by building tutorials:\n\n- `make html-noplot` is the quick sanity check for RST and Sphinx errors.\n- Full execution of `.py` tutorials runs in CI on GPU shards.\n- To test a single tutorial: `GALLERY_PATTERN=\"my_tutorial.py\" make html`\n\n# Tutorial File Format\n\n- Interactive tutorials are `.py` files using Sphinx Gallery conventions. Filenames should end in `_tutorial.py`.\n- Non-interactive tutorials are `.rst` files.\n- Data dependencies must be added via `.jenkins/download_data.py`, not the Makefile. Follow the existing patterns in that file.\n- New Python package dependencies go in `requirements.txt`.\n\n# Adding a New Tutorial\n\n1. Place the file in the appropriate `*_source/` directory based on difficulty level.\n2. Add a `customcarditem` entry in `index.rst` (or `recipes_index.rst` for recipes).\n3. Add the tutorial to the corresponding `toctree` in `index.rst`.\n4. Add a square, high-resolution thumbnail image to `_static/img/thumbnails/cropped/`.\n\n# Coding Style Guidelines\n\nFollow these rules for all code changes in this repository:\n\n- Minimize comments; be concise; code should be self-explanatory.\n- Match existing code style and architectural patterns.\n- Tutorial prose should be written for a global audience with clear, easy to understand language. Avoid idioms.\n- Use active voice in tutorial instructions.\n- If uncertain, choose the simpler, more concise implementation.\n",".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/pytorch/tutorials/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/pytorch/tutorials/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/pytorch/tutorials/HEAD/.claude-plugin/plugin.json)"},"items":[{"name":"CLAUDE.md","path":"CLAUDE.md","rawUrl":"https://raw.githubusercontent.com/pytorch/tutorials/HEAD/CLAUDE.md","title":"Claude Agent Guidelines & System Prompt","category":"claude-rule","format":"markdown","content":"# Project Structure\n\nThis is the PyTorch Tutorials website (`pytorch.org/tutorials`), built with Sphinx and Sphinx Gallery.\n\n- `beginner_source/`, `intermediate_source/`, `advanced_source/`, `recipes_source/`, `unstable_source/` — tutorial source files (`.py` and `.rst`)\n- `index.rst`, `recipes_index.rst` — card listings and toctrees for the website\n- `conf.py` — Sphinx configuration (gallery dirs, extensions, theme)\n- `_static/` — images, CSS, and thumbnails\n- `requirements.txt` — all Python dependencies (Sphinx, tutorial packages)\n- `.jenkins/` — CI build scripts, data download logic, post-processing\n- `Makefile` — build entry points\n\nTutorials authored as `.py` files use Sphinx Gallery format: top-level docstrings become RST prose, code blocks become executable cells. These are executed during builds and converted to Jupyter notebooks and HTML. Tutorials authored as `.rst` are static and their code is not executed.\n\n# Build\n\n- `make html-noplot` — builds HTML without executing tutorial code. Fast, no GPU needed. Use this for quick validation of RST/Sphinx structure.\n- `make docs` — full build that downloads data, executes all `.py` tutorials, and produces the final site. Requires a GPU-powered machine with CUDA.\n- `GALLERY_PATTERN=\"my_tutorial.py\" make html` — build only a single tutorial by name (regex supported).\n\nThe CI build runs inside Docker across 15 GPU-powered shards via `.jenkins/build.sh`.\n\n# Linting\n\nThis repo uses `lintrunner`. Do not use `spin`, `flake8`, or other linters directly.\n\n- `lintrunner -m main` — lint changes relative to the main branch\n- `lintrunner --all-files` — lint all files in the repo\n\nLintrunner checks trailing whitespace, tabs, and newline issues only. It does not check Python formatting, RST syntax, or Sphinx directives.\n\n# Testing\n\nThere is no unit test suite. Validation is done by building tutorials:\n\n- `make html-noplot` is the quick sanity check for RST and Sphinx errors.\n- Full execution of `.py` tutorials runs in CI on GPU shards.\n- To test a single tutorial: `GALLERY_PATTERN=\"my_tutorial.py\" make html`\n\n# Tutorial File Format\n\n- Interactive tutorials are `.py` files using Sphinx Gallery conventions. Filenames should end in `_tutorial.py`.\n- Non-interactive tutorials are `.rst` files.\n- Data dependencies must be added via `.jenkins/download_data.py`, not the Makefile. Follow the existing patterns in that file.\n- New Python package dependencies go in `requirements.txt`.\n\n# Adding a New Tutorial\n\n1. Place the file in the appropriate `*_source/` directory based on difficulty level.\n2. Add a `customcarditem` entry in `index.rst` (or `recipes_index.rst` for recipes).\n3. Add the tutorial to the corresponding `toctree` in `index.rst`.\n4. Add a square, high-resolution thumbnail image to `_static/img/thumbnails/cropped/`.\n\n# Coding Style Guidelines\n\nFollow these rules for all code changes in this repository:\n\n- Minimize comments; be concise; code should be self-explanatory.\n- Match existing code style and architectural patterns.\n- Tutorial prose should be written for a global audience with clear, easy to understand language. Avoid idioms.\n- Use active voice in tutorial instructions.\n- If uncertain, choose the simpler, more concise implementation.\n","isInternal":false,"tokens":753,"sizeBytes":3264},{"name":"marketplace.json","path":".claude-plugin/marketplace.json","rawUrl":"https://raw.githubusercontent.com/pytorch/tutorials/HEAD/.claude-plugin/marketplace.json","title":"Claude Plugin Marketplace Catalog","category":"marketplace","format":"json","content":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/pytorch/tutorials/HEAD/.claude-plugin/marketplace.json)","tokens":300,"sizeBytes":196},{"name":"plugin.json","path":".claude-plugin/plugin.json","rawUrl":"https://raw.githubusercontent.com/pytorch/tutorials/HEAD/.claude-plugin/plugin.json","title":"claude-plugin Plugin Manifest","category":"plugin-manifest","format":"json","content":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/pytorch/tutorials/HEAD/.claude-plugin/plugin.json)","tokens":300,"sizeBytes":182},{"name":"mcp.json","path":".cursor/mcp.json","rawUrl":"https://raw.githubusercontent.com/pytorch/tutorials/HEAD/.cursor/mcp.json","title":"Model Context Protocol (MCP) Configuration","category":"mcp-config","format":"json","content":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/pytorch/tutorials/HEAD/.cursor/mcp.json)","tokens":300,"sizeBytes":175}],"systemPromptSnippet":"<yakaai_skills repo=\"pytorch/tutorials\">\n<!-- File: CLAUDE.md (Tokens: ~753 | Category: claude-rule) -->\n# Project Structure\n\nThis is the PyTorch Tutorials website (`pytorch.org/tutorials`), built with Sphinx and Sphinx Gallery.\n\n- `beginner_source/`, `intermediate_source/`, `advanced_source/`, `recipes_source/`, `unstable_source/` — tutorial source files (`.py` and `.rst`)\n- `index.rst`, `recipes_index.rst` — card listings and toctrees for the website\n- `conf.py` — Sphinx configuration (gallery dirs, extensions, theme)\n- `_static/` — images, CSS, and thumbnails\n- `requirements.txt` — all Python dependencies (Sphinx, tutorial packages)\n- `.jenkins/` — CI build scripts, data download logic, post-processing\n- `Makefile` — build entry points\n\nTutorials authored as `.py` files use Sphinx Gallery format: top-level docstrings become RST prose, code blocks become executable cells. These are executed during builds and converted to Jupyter notebooks and HTML. Tutorials authored as `.rst` are static and their code is not executed.\n\n# Build\n\n- `make html-noplot` — builds HTML without executing tutorial code. Fast, no GPU needed. Use this for quick validation of RST/Sphinx structure.\n- `make docs` — full build that downloads data, executes all `.py` tutorials, and produces the final site. Requires a GPU-powered machine with CUDA.\n- `GALLERY_PATTERN=\"my_tutorial.py\" make html` — build only a single tutorial by name (regex supported).\n\nThe CI build runs inside Docker across 15 GPU-powered shards via `.jenkins/build.sh`.\n\n# Linting\n\nThis repo uses `lintrunner`. Do not use `spin`, `flake8`, or other linters directly.\n\n- `lintrunner -m main` — lint changes relative to the main branch\n- `lintrunner --all-files` — lint all files in the repo\n\nLintrunner checks trailing whitespace, tabs, and newline issues only. It does not check Python formatting, RST syntax, or Sphinx directives.\n\n# Testing\n\nThere is no unit test suite. Validation is done by building tutorials:\n\n- `make html-noplot` is the quick sanity check for RST and Sphinx errors.\n- Full execution of `.py` tutorials runs in CI on GPU shards.\n- To test a single tutorial: `GALLERY_PATTERN=\"my_tutorial.py\" make html`\n\n# Tutorial File Format\n\n- Interactive tutorials are `.py` files using Sphinx Gallery conventions. Filenames should end in `_tutorial.py`.\n- Non-interactive tutorials are `.rst` files.\n- Data dependencies must be added via `.jenkins/download_data.py`, not the Makefile. Follow the existing patterns in that file.\n- New Python package dependencies go in `requirements.txt`.\n\n# Adding a New Tutorial\n\n1. Place the file in the appropriate `*_source/` directory based on difficulty level.\n2. Add a `customcarditem` entry in `index.rst` (or `recipes_index.rst` for recipes).\n3. Add the tutorial to the corresponding `toctree` in `index.rst`.\n4. Add a square, high-resolution thumbnail image to `_static/img/thumbnails/cropped/`.\n\n# Coding Style Guidelines\n\nFollow these rules for all code changes in this repository:\n\n- Minimize comments; be concise; code should be self-explanatory.\n- Match existing code style and architectural patterns.\n- Tutorial prose should be written for a global audience with clear, easy to understand language. Avoid idioms.\n- Use active voice in tutorial instructions.\n- If uncertain, choose the simpler, more concise implementation.\n\n<!-- File: .claude-plugin/marketplace.json (Tokens: ~300 | Category: marketplace) -->\n# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/pytorch/tutorials/HEAD/.claude-plugin/marketplace.json)\n\n<!-- File: .claude-plugin/plugin.json (Tokens: ~300 | Category: plugin-manifest) -->\n# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/pytorch/tutorials/HEAD/.claude-plugin/plugin.json)\n\n<!-- File: .cursor/mcp.json (Tokens: ~300 | Category: mcp-config) -->\n# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/pytorch/tutorials/HEAD/.cursor/mcp.json)\n</yakaai_skills>"}