{"owner":"NVlabs","repo":"curobo","hasSkills":true,"totalSkillsCount":4,"totalTokensCount":1478,"categories":["root-instruction","mcp-config","marketplace","plugin-manifest"],"hasMcp":true,"mcpConfig":{"mcpServers":{"curobo":{"command":"npx","args":["-y","@modelcontextprotocol/server-curobo"]}}},"found":["AGENTS.md",".cursor/mcp.json",".claude-plugin/marketplace.json",".claude-plugin/plugin.json"],"skills":{"AGENTS.md":"# Agent Instructions\n\nThis file is the entry point for coding agents working in this repository. Keep\nchanges small, inspect the existing code before editing, and follow the\nrepository-specific rules in `.agent/`.\n\n## Rule Files\n\n- Read `.agent/design_principles.mdc` before non-trivial code changes.\n- Use `.agent/python_rules.mdc` and `.agent/package_format_rules.mdc` for Python\n  code.\n- Use `.agent/cpp_rules.mdc` for C++, CUDA, and Warp-adjacent native code.\n- Use `.agent/tests.mdc` before adding or changing tests.\n- Use `.agent/sphinx_md.mdc`, `.agent/documenter.mdc`, and\n  `.agent/diataxis.mdc` for documentation changes.\n- Use `.agent/file_naming.mdc` when creating or moving implementation files.\n\n## Development Workflow\n\n- Prefer `rg`/`rg --files` for repository search.\n- Activate `.venv` before running Python commands when it exists.\n- Preserve user changes in the working tree. Do not revert unrelated files.\n- Keep public APIs minimal and user-focused. Do not expose implementation details\n  unless they are required by the user-facing contract.\n- Prefer existing local patterns and helpers over new abstractions.\n- Use only `Copyright (c) 2026` in SPDX copyright headers for new files;\n  preserve existing headers when modifying older files.\n- Add focused tests for behavioral changes. Do not use `float64` in tests.\n- Keep CUDA graph enabled for normal runtime, examples, and performance-sensitive\n  paths. Disable CUDA graph only in tests or debugging paths where eager\n  execution helps catch correctness issues.\n\n## Python Conventions\n\n- Add type hints to all function signatures.\n- Use concise docstrings that describe behavior, inputs, outputs, and tensor\n  shapes when relevant.\n- For dataclasses, document fields where they are declared.\n- Use logging/error helpers from `curobo/_src/util/logging.py` instead of raw\n  prints or ad hoc exceptions in library code.\n- Keep `_src` package initializers marker-only unless they intentionally build a\n  public API aggregation layer.\n- Public modules under `curobo/` should curate user-facing imports. Internal\n  code should import concrete implementation modules directly.\n\n## Naming\n\n- Internal implementation files under `curobo/_src/` should use the\n  category-first pattern from `.agent/file_naming.mdc`.\n- Public API modules under `curobo/` should use descriptive, user-friendly names.\n\n## Documentation\n\n- Prefer Markdown with MyST syntax for new Sphinx documentation.\n- Keep docs in the correct Diataxis category: tutorial, guide, concept, or\n  reference.\n- Write user-facing docs around the outcome and contract, not internal\n  implementation details.\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/NVlabs/curobo/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/NVlabs/curobo/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/NVlabs/curobo/HEAD/.claude-plugin/plugin.json)"},"files":{"AGENTS.md":"# Agent Instructions\n\nThis file is the entry point for coding agents working in this repository. Keep\nchanges small, inspect the existing code before editing, and follow the\nrepository-specific rules in `.agent/`.\n\n## Rule Files\n\n- Read `.agent/design_principles.mdc` before non-trivial code changes.\n- Use `.agent/python_rules.mdc` and `.agent/package_format_rules.mdc` for Python\n  code.\n- Use `.agent/cpp_rules.mdc` for C++, CUDA, and Warp-adjacent native code.\n- Use `.agent/tests.mdc` before adding or changing tests.\n- Use `.agent/sphinx_md.mdc`, `.agent/documenter.mdc`, and\n  `.agent/diataxis.mdc` for documentation changes.\n- Use `.agent/file_naming.mdc` when creating or moving implementation files.\n\n## Development Workflow\n\n- Prefer `rg`/`rg --files` for repository search.\n- Activate `.venv` before running Python commands when it exists.\n- Preserve user changes in the working tree. Do not revert unrelated files.\n- Keep public APIs minimal and user-focused. Do not expose implementation details\n  unless they are required by the user-facing contract.\n- Prefer existing local patterns and helpers over new abstractions.\n- Use only `Copyright (c) 2026` in SPDX copyright headers for new files;\n  preserve existing headers when modifying older files.\n- Add focused tests for behavioral changes. Do not use `float64` in tests.\n- Keep CUDA graph enabled for normal runtime, examples, and performance-sensitive\n  paths. Disable CUDA graph only in tests or debugging paths where eager\n  execution helps catch correctness issues.\n\n## Python Conventions\n\n- Add type hints to all function signatures.\n- Use concise docstrings that describe behavior, inputs, outputs, and tensor\n  shapes when relevant.\n- For dataclasses, document fields where they are declared.\n- Use logging/error helpers from `curobo/_src/util/logging.py` instead of raw\n  prints or ad hoc exceptions in library code.\n- Keep `_src` package initializers marker-only unless they intentionally build a\n  public API aggregation layer.\n- Public modules under `curobo/` should curate user-facing imports. Internal\n  code should import concrete implementation modules directly.\n\n## Naming\n\n- Internal implementation files under `curobo/_src/` should use the\n  category-first pattern from `.agent/file_naming.mdc`.\n- Public API modules under `curobo/` should use descriptive, user-friendly names.\n\n## Documentation\n\n- Prefer Markdown with MyST syntax for new Sphinx documentation.\n- Keep docs in the correct Diataxis category: tutorial, guide, concept, or\n  reference.\n- Write user-facing docs around the outcome and contract, not internal\n  implementation details.\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/NVlabs/curobo/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/NVlabs/curobo/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/NVlabs/curobo/HEAD/.claude-plugin/plugin.json)"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","rawUrl":"https://raw.githubusercontent.com/NVlabs/curobo/HEAD/AGENTS.md","title":"AI Agent Protocol & Instructions","category":"root-instruction","format":"markdown","content":"# Agent Instructions\n\nThis file is the entry point for coding agents working in this repository. Keep\nchanges small, inspect the existing code before editing, and follow the\nrepository-specific rules in `.agent/`.\n\n## Rule Files\n\n- Read `.agent/design_principles.mdc` before non-trivial code changes.\n- Use `.agent/python_rules.mdc` and `.agent/package_format_rules.mdc` for Python\n  code.\n- Use `.agent/cpp_rules.mdc` for C++, CUDA, and Warp-adjacent native code.\n- Use `.agent/tests.mdc` before adding or changing tests.\n- Use `.agent/sphinx_md.mdc`, `.agent/documenter.mdc`, and\n  `.agent/diataxis.mdc` for documentation changes.\n- Use `.agent/file_naming.mdc` when creating or moving implementation files.\n\n## Development Workflow\n\n- Prefer `rg`/`rg --files` for repository search.\n- Activate `.venv` before running Python commands when it exists.\n- Preserve user changes in the working tree. Do not revert unrelated files.\n- Keep public APIs minimal and user-focused. Do not expose implementation details\n  unless they are required by the user-facing contract.\n- Prefer existing local patterns and helpers over new abstractions.\n- Use only `Copyright (c) 2026` in SPDX copyright headers for new files;\n  preserve existing headers when modifying older files.\n- Add focused tests for behavioral changes. Do not use `float64` in tests.\n- Keep CUDA graph enabled for normal runtime, examples, and performance-sensitive\n  paths. Disable CUDA graph only in tests or debugging paths where eager\n  execution helps catch correctness issues.\n\n## Python Conventions\n\n- Add type hints to all function signatures.\n- Use concise docstrings that describe behavior, inputs, outputs, and tensor\n  shapes when relevant.\n- For dataclasses, document fields where they are declared.\n- Use logging/error helpers from `curobo/_src/util/logging.py` instead of raw\n  prints or ad hoc exceptions in library code.\n- Keep `_src` package initializers marker-only unless they intentionally build a\n  public API aggregation layer.\n- Public modules under `curobo/` should curate user-facing imports. Internal\n  code should import concrete implementation modules directly.\n\n## Naming\n\n- Internal implementation files under `curobo/_src/` should use the\n  category-first pattern from `.agent/file_naming.mdc`.\n- Public API modules under `curobo/` should use descriptive, user-friendly names.\n\n## Documentation\n\n- Prefer Markdown with MyST syntax for new Sphinx documentation.\n- Keep docs in the correct Diataxis category: tutorial, guide, concept, or\n  reference.\n- Write user-facing docs around the outcome and contract, not internal\n  implementation details.\n","isInternal":false,"tokens":578,"sizeBytes":2632},{"name":"marketplace.json","path":".claude-plugin/marketplace.json","rawUrl":"https://raw.githubusercontent.com/NVlabs/curobo/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/NVlabs/curobo/HEAD/.claude-plugin/marketplace.json)","tokens":300,"sizeBytes":192},{"name":"plugin.json","path":".claude-plugin/plugin.json","rawUrl":"https://raw.githubusercontent.com/NVlabs/curobo/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/NVlabs/curobo/HEAD/.claude-plugin/plugin.json)","tokens":300,"sizeBytes":178},{"name":"mcp.json","path":".cursor/mcp.json","rawUrl":"https://raw.githubusercontent.com/NVlabs/curobo/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/NVlabs/curobo/HEAD/.cursor/mcp.json)","tokens":300,"sizeBytes":171}],"systemPromptSnippet":"<yakaai_skills repo=\"NVlabs/curobo\">\n<!-- File: AGENTS.md (Tokens: ~578 | Category: root-instruction) -->\n# Agent Instructions\n\nThis file is the entry point for coding agents working in this repository. Keep\nchanges small, inspect the existing code before editing, and follow the\nrepository-specific rules in `.agent/`.\n\n## Rule Files\n\n- Read `.agent/design_principles.mdc` before non-trivial code changes.\n- Use `.agent/python_rules.mdc` and `.agent/package_format_rules.mdc` for Python\n  code.\n- Use `.agent/cpp_rules.mdc` for C++, CUDA, and Warp-adjacent native code.\n- Use `.agent/tests.mdc` before adding or changing tests.\n- Use `.agent/sphinx_md.mdc`, `.agent/documenter.mdc`, and\n  `.agent/diataxis.mdc` for documentation changes.\n- Use `.agent/file_naming.mdc` when creating or moving implementation files.\n\n## Development Workflow\n\n- Prefer `rg`/`rg --files` for repository search.\n- Activate `.venv` before running Python commands when it exists.\n- Preserve user changes in the working tree. Do not revert unrelated files.\n- Keep public APIs minimal and user-focused. Do not expose implementation details\n  unless they are required by the user-facing contract.\n- Prefer existing local patterns and helpers over new abstractions.\n- Use only `Copyright (c) 2026` in SPDX copyright headers for new files;\n  preserve existing headers when modifying older files.\n- Add focused tests for behavioral changes. Do not use `float64` in tests.\n- Keep CUDA graph enabled for normal runtime, examples, and performance-sensitive\n  paths. Disable CUDA graph only in tests or debugging paths where eager\n  execution helps catch correctness issues.\n\n## Python Conventions\n\n- Add type hints to all function signatures.\n- Use concise docstrings that describe behavior, inputs, outputs, and tensor\n  shapes when relevant.\n- For dataclasses, document fields where they are declared.\n- Use logging/error helpers from `curobo/_src/util/logging.py` instead of raw\n  prints or ad hoc exceptions in library code.\n- Keep `_src` package initializers marker-only unless they intentionally build a\n  public API aggregation layer.\n- Public modules under `curobo/` should curate user-facing imports. Internal\n  code should import concrete implementation modules directly.\n\n## Naming\n\n- Internal implementation files under `curobo/_src/` should use the\n  category-first pattern from `.agent/file_naming.mdc`.\n- Public API modules under `curobo/` should use descriptive, user-friendly names.\n\n## Documentation\n\n- Prefer Markdown with MyST syntax for new Sphinx documentation.\n- Keep docs in the correct Diataxis category: tutorial, guide, concept, or\n  reference.\n- Write user-facing docs around the outcome and contract, not internal\n  implementation details.\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/NVlabs/curobo/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/NVlabs/curobo/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/NVlabs/curobo/HEAD/.cursor/mcp.json)\n</yakaai_skills>"}