{"owner":"unit8co","repo":"darts","hasSkills":true,"totalSkillsCount":4,"totalTokensCount":1804,"categories":["root-instruction","mcp-config","marketplace","plugin-manifest"],"hasMcp":true,"mcpConfig":{"mcpServers":{"darts":{"command":"npx","args":["-y","@modelcontextprotocol/server-darts"]}}},"found":["AGENTS.md",".cursor/mcp.json",".claude-plugin/marketplace.json",".claude-plugin/plugin.json"],"skills":{"AGENTS.md":"# Instructions for AI Agents\n\nThis file gives AI coding agents (Claude Code, Codex, Cursor, Copilot, Devin, etc.) the rules they must follow when contributing to [Darts](https://github.com/unit8co/darts). It complements [CONTRIBUTING.md](CONTRIBUTING.md), which remains the source of truth for humans. Agents must respect every rule there as well.\n\nIf a rule here conflicts with `CONTRIBUTING.md`, follow `CONTRIBUTING.md` and flag the discrepancy in the PR description.\n\n## MUST READ FIRST — CONTRIBUTION GATE (DO NOT SKIP)\n\n**STOP. Do not open or draft a PR until this gate is satisfied.**\n\nFor any contribution that might become a PR, verify with the human user:\n\n1. **Issue link:** What is the GitHub issue number for this work? If none exists, the human must open one first.\n2. **Maintainer approval:** Does that issue have the **`ok`** label applied by a maintainer? If not, the human must comment on the issue and wait for maintainer triage. Do not start implementation for merge-bound work until the label is present.\n3. **PR linkage:** The PR description must reference the issue with a recognized keyword (e.g. `Fixes #123` when completing the issue, or `Addresses #123` / `Refs #123` for partial work). Sidebar-only links do not satisfy automation.\n\nThis gate is mandatory for all agents **unless the user has write access to the repository** (maintainer bypass below).\n\n### Maintainer bypass\n\nIf the authenticated user has **write**, **maintain**, or **admin** access to `unit8co/darts`, they may skip the contribution gate for their own work. Team members manage their own priorities and do not need to wait for `ok` labeling on internal PRs.\n\n## Zero-spam and PR authorization\n\n- **Require an issue:** Do not create a pull request unless there is an existing, open issue with the **`ok`** label that covers this work. Drive-by PRs, speculative refactors, typo-only PRs, and unsolicited features are not accepted.\n- **Respect claimed work:** If someone is assigned to an issue or has stated they are working on it, do not open a competing PR without coordinating in the issue thread.\n- **Stay inside scope:** Implement only what the approved issue (or approved sub-issue) describes. Open separate issues for unrelated findings.\n- **Multiple PRs per issue:** Allowed when each PR states its slice of the work. Use `Addresses`/`Refs`/`Part of` for partial PRs; use `Fixes`/`Closes` only on the PR that finishes the issue (or on a sub-issue).\n- **One PR, one focus:** Do not bundle multiple unrelated issues into one PR without maintainer agreement in the issue.\n- **No duplicate bot chores:** Dependency bumps and similar housekeeping belong to existing automation; do not duplicate that work.\n\n## Darts development principles\n\nFollow [CONTRIBUTING.md — Main Development Principles](CONTRIBUTING.md#main-development-principles). In short:\n\n- Simple, clear API; `TimeSeries` as the user-facing data type; avoid future leakage and user foot-guns.\n- Clear code over clever code; PEP-8; type hints; docstrings on public API; unit tests for changes.\n- Use `uv`, pre-commit/ruff, and `uv run pytest` as described in `CONTRIBUTING.md`.\n\n## AI-assisted contributions\n\nAI assistance is allowed only when a **human** drives the contribution and takes responsibility:\n\n- The human must understand, verify, and be able to explain every change in review.\n- Disclose AI use in the PR description (tool name and what it was used for, e.g. tests, docs, refactor).\n- Fully automated PRs submitted without meaningful human review may be closed.\n- AI-generated code must meet the same bar as any other contribution (CI, style, tests, Darts conventions).\n\n## Technical procedure\n\nSee [CONTRIBUTING.md — Technical Procedure](CONTRIBUTING.md#technical-procedure): fork, branch from **master** with `feature/`, `fix/`, or `refactor/` prefixes, changelog under **Unreleased**, PR into **master**.\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/unit8co/darts/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/unit8co/darts/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/unit8co/darts/HEAD/.claude-plugin/plugin.json)"},"files":{"AGENTS.md":"# Instructions for AI Agents\n\nThis file gives AI coding agents (Claude Code, Codex, Cursor, Copilot, Devin, etc.) the rules they must follow when contributing to [Darts](https://github.com/unit8co/darts). It complements [CONTRIBUTING.md](CONTRIBUTING.md), which remains the source of truth for humans. Agents must respect every rule there as well.\n\nIf a rule here conflicts with `CONTRIBUTING.md`, follow `CONTRIBUTING.md` and flag the discrepancy in the PR description.\n\n## MUST READ FIRST — CONTRIBUTION GATE (DO NOT SKIP)\n\n**STOP. Do not open or draft a PR until this gate is satisfied.**\n\nFor any contribution that might become a PR, verify with the human user:\n\n1. **Issue link:** What is the GitHub issue number for this work? If none exists, the human must open one first.\n2. **Maintainer approval:** Does that issue have the **`ok`** label applied by a maintainer? If not, the human must comment on the issue and wait for maintainer triage. Do not start implementation for merge-bound work until the label is present.\n3. **PR linkage:** The PR description must reference the issue with a recognized keyword (e.g. `Fixes #123` when completing the issue, or `Addresses #123` / `Refs #123` for partial work). Sidebar-only links do not satisfy automation.\n\nThis gate is mandatory for all agents **unless the user has write access to the repository** (maintainer bypass below).\n\n### Maintainer bypass\n\nIf the authenticated user has **write**, **maintain**, or **admin** access to `unit8co/darts`, they may skip the contribution gate for their own work. Team members manage their own priorities and do not need to wait for `ok` labeling on internal PRs.\n\n## Zero-spam and PR authorization\n\n- **Require an issue:** Do not create a pull request unless there is an existing, open issue with the **`ok`** label that covers this work. Drive-by PRs, speculative refactors, typo-only PRs, and unsolicited features are not accepted.\n- **Respect claimed work:** If someone is assigned to an issue or has stated they are working on it, do not open a competing PR without coordinating in the issue thread.\n- **Stay inside scope:** Implement only what the approved issue (or approved sub-issue) describes. Open separate issues for unrelated findings.\n- **Multiple PRs per issue:** Allowed when each PR states its slice of the work. Use `Addresses`/`Refs`/`Part of` for partial PRs; use `Fixes`/`Closes` only on the PR that finishes the issue (or on a sub-issue).\n- **One PR, one focus:** Do not bundle multiple unrelated issues into one PR without maintainer agreement in the issue.\n- **No duplicate bot chores:** Dependency bumps and similar housekeeping belong to existing automation; do not duplicate that work.\n\n## Darts development principles\n\nFollow [CONTRIBUTING.md — Main Development Principles](CONTRIBUTING.md#main-development-principles). In short:\n\n- Simple, clear API; `TimeSeries` as the user-facing data type; avoid future leakage and user foot-guns.\n- Clear code over clever code; PEP-8; type hints; docstrings on public API; unit tests for changes.\n- Use `uv`, pre-commit/ruff, and `uv run pytest` as described in `CONTRIBUTING.md`.\n\n## AI-assisted contributions\n\nAI assistance is allowed only when a **human** drives the contribution and takes responsibility:\n\n- The human must understand, verify, and be able to explain every change in review.\n- Disclose AI use in the PR description (tool name and what it was used for, e.g. tests, docs, refactor).\n- Fully automated PRs submitted without meaningful human review may be closed.\n- AI-generated code must meet the same bar as any other contribution (CI, style, tests, Darts conventions).\n\n## Technical procedure\n\nSee [CONTRIBUTING.md — Technical Procedure](CONTRIBUTING.md#technical-procedure): fork, branch from **master** with `feature/`, `fix/`, or `refactor/` prefixes, changelog under **Unreleased**, PR into **master**.\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/unit8co/darts/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/unit8co/darts/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/unit8co/darts/HEAD/.claude-plugin/plugin.json)"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","rawUrl":"https://raw.githubusercontent.com/unit8co/darts/HEAD/AGENTS.md","title":"AI Agent Protocol & Instructions","category":"root-instruction","format":"markdown","content":"# Instructions for AI Agents\n\nThis file gives AI coding agents (Claude Code, Codex, Cursor, Copilot, Devin, etc.) the rules they must follow when contributing to [Darts](https://github.com/unit8co/darts). It complements [CONTRIBUTING.md](CONTRIBUTING.md), which remains the source of truth for humans. Agents must respect every rule there as well.\n\nIf a rule here conflicts with `CONTRIBUTING.md`, follow `CONTRIBUTING.md` and flag the discrepancy in the PR description.\n\n## MUST READ FIRST — CONTRIBUTION GATE (DO NOT SKIP)\n\n**STOP. Do not open or draft a PR until this gate is satisfied.**\n\nFor any contribution that might become a PR, verify with the human user:\n\n1. **Issue link:** What is the GitHub issue number for this work? If none exists, the human must open one first.\n2. **Maintainer approval:** Does that issue have the **`ok`** label applied by a maintainer? If not, the human must comment on the issue and wait for maintainer triage. Do not start implementation for merge-bound work until the label is present.\n3. **PR linkage:** The PR description must reference the issue with a recognized keyword (e.g. `Fixes #123` when completing the issue, or `Addresses #123` / `Refs #123` for partial work). Sidebar-only links do not satisfy automation.\n\nThis gate is mandatory for all agents **unless the user has write access to the repository** (maintainer bypass below).\n\n### Maintainer bypass\n\nIf the authenticated user has **write**, **maintain**, or **admin** access to `unit8co/darts`, they may skip the contribution gate for their own work. Team members manage their own priorities and do not need to wait for `ok` labeling on internal PRs.\n\n## Zero-spam and PR authorization\n\n- **Require an issue:** Do not create a pull request unless there is an existing, open issue with the **`ok`** label that covers this work. Drive-by PRs, speculative refactors, typo-only PRs, and unsolicited features are not accepted.\n- **Respect claimed work:** If someone is assigned to an issue or has stated they are working on it, do not open a competing PR without coordinating in the issue thread.\n- **Stay inside scope:** Implement only what the approved issue (or approved sub-issue) describes. Open separate issues for unrelated findings.\n- **Multiple PRs per issue:** Allowed when each PR states its slice of the work. Use `Addresses`/`Refs`/`Part of` for partial PRs; use `Fixes`/`Closes` only on the PR that finishes the issue (or on a sub-issue).\n- **One PR, one focus:** Do not bundle multiple unrelated issues into one PR without maintainer agreement in the issue.\n- **No duplicate bot chores:** Dependency bumps and similar housekeeping belong to existing automation; do not duplicate that work.\n\n## Darts development principles\n\nFollow [CONTRIBUTING.md — Main Development Principles](CONTRIBUTING.md#main-development-principles). In short:\n\n- Simple, clear API; `TimeSeries` as the user-facing data type; avoid future leakage and user foot-guns.\n- Clear code over clever code; PEP-8; type hints; docstrings on public API; unit tests for changes.\n- Use `uv`, pre-commit/ruff, and `uv run pytest` as described in `CONTRIBUTING.md`.\n\n## AI-assisted contributions\n\nAI assistance is allowed only when a **human** drives the contribution and takes responsibility:\n\n- The human must understand, verify, and be able to explain every change in review.\n- Disclose AI use in the PR description (tool name and what it was used for, e.g. tests, docs, refactor).\n- Fully automated PRs submitted without meaningful human review may be closed.\n- AI-generated code must meet the same bar as any other contribution (CI, style, tests, Darts conventions).\n\n## Technical procedure\n\nSee [CONTRIBUTING.md — Technical Procedure](CONTRIBUTING.md#technical-procedure): fork, branch from **master** with `feature/`, `fix/`, or `refactor/` prefixes, changelog under **Unreleased**, PR into **master**.\n","isInternal":false,"tokens":904,"sizeBytes":3890},{"name":"marketplace.json","path":".claude-plugin/marketplace.json","rawUrl":"https://raw.githubusercontent.com/unit8co/darts/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/unit8co/darts/HEAD/.claude-plugin/marketplace.json)","tokens":300,"sizeBytes":192},{"name":"plugin.json","path":".claude-plugin/plugin.json","rawUrl":"https://raw.githubusercontent.com/unit8co/darts/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/unit8co/darts/HEAD/.claude-plugin/plugin.json)","tokens":300,"sizeBytes":178},{"name":"mcp.json","path":".cursor/mcp.json","rawUrl":"https://raw.githubusercontent.com/unit8co/darts/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/unit8co/darts/HEAD/.cursor/mcp.json)","tokens":300,"sizeBytes":171}],"systemPromptSnippet":"<yakaai_skills repo=\"unit8co/darts\">\n<!-- File: AGENTS.md (Tokens: ~904 | Category: root-instruction) -->\n# Instructions for AI Agents\n\nThis file gives AI coding agents (Claude Code, Codex, Cursor, Copilot, Devin, etc.) the rules they must follow when contributing to [Darts](https://github.com/unit8co/darts). It complements [CONTRIBUTING.md](CONTRIBUTING.md), which remains the source of truth for humans. Agents must respect every rule there as well.\n\nIf a rule here conflicts with `CONTRIBUTING.md`, follow `CONTRIBUTING.md` and flag the discrepancy in the PR description.\n\n## MUST READ FIRST — CONTRIBUTION GATE (DO NOT SKIP)\n\n**STOP. Do not open or draft a PR until this gate is satisfied.**\n\nFor any contribution that might become a PR, verify with the human user:\n\n1. **Issue link:** What is the GitHub issue number for this work? If none exists, the human must open one first.\n2. **Maintainer approval:** Does that issue have the **`ok`** label applied by a maintainer? If not, the human must comment on the issue and wait for maintainer triage. Do not start implementation for merge-bound work until the label is present.\n3. **PR linkage:** The PR description must reference the issue with a recognized keyword (e.g. `Fixes #123` when completing the issue, or `Addresses #123` / `Refs #123` for partial work). Sidebar-only links do not satisfy automation.\n\nThis gate is mandatory for all agents **unless the user has write access to the repository** (maintainer bypass below).\n\n### Maintainer bypass\n\nIf the authenticated user has **write**, **maintain**, or **admin** access to `unit8co/darts`, they may skip the contribution gate for their own work. Team members manage their own priorities and do not need to wait for `ok` labeling on internal PRs.\n\n## Zero-spam and PR authorization\n\n- **Require an issue:** Do not create a pull request unless there is an existing, open issue with the **`ok`** label that covers this work. Drive-by PRs, speculative refactors, typo-only PRs, and unsolicited features are not accepted.\n- **Respect claimed work:** If someone is assigned to an issue or has stated they are working on it, do not open a competing PR without coordinating in the issue thread.\n- **Stay inside scope:** Implement only what the approved issue (or approved sub-issue) describes. Open separate issues for unrelated findings.\n- **Multiple PRs per issue:** Allowed when each PR states its slice of the work. Use `Addresses`/`Refs`/`Part of` for partial PRs; use `Fixes`/`Closes` only on the PR that finishes the issue (or on a sub-issue).\n- **One PR, one focus:** Do not bundle multiple unrelated issues into one PR without maintainer agreement in the issue.\n- **No duplicate bot chores:** Dependency bumps and similar housekeeping belong to existing automation; do not duplicate that work.\n\n## Darts development principles\n\nFollow [CONTRIBUTING.md — Main Development Principles](CONTRIBUTING.md#main-development-principles). In short:\n\n- Simple, clear API; `TimeSeries` as the user-facing data type; avoid future leakage and user foot-guns.\n- Clear code over clever code; PEP-8; type hints; docstrings on public API; unit tests for changes.\n- Use `uv`, pre-commit/ruff, and `uv run pytest` as described in `CONTRIBUTING.md`.\n\n## AI-assisted contributions\n\nAI assistance is allowed only when a **human** drives the contribution and takes responsibility:\n\n- The human must understand, verify, and be able to explain every change in review.\n- Disclose AI use in the PR description (tool name and what it was used for, e.g. tests, docs, refactor).\n- Fully automated PRs submitted without meaningful human review may be closed.\n- AI-generated code must meet the same bar as any other contribution (CI, style, tests, Darts conventions).\n\n## Technical procedure\n\nSee [CONTRIBUTING.md — Technical Procedure](CONTRIBUTING.md#technical-procedure): fork, branch from **master** with `feature/`, `fix/`, or `refactor/` prefixes, changelog under **Unreleased**, PR into **master**.\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/unit8co/darts/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/unit8co/darts/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/unit8co/darts/HEAD/.cursor/mcp.json)\n</yakaai_skills>"}