[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C93JSADGF84DNRGSKHZXH9":3,"skill-same:01M7C93JSADGF84DNRGSKHZXH9":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7C93JSADGF84DNRGSKHZXH9","data-structure-protocol",null,"Give agents persistent structural memory of a codebase — navigate dependencies, track public APIs, and understand why connections exist without re-reading the whole repo.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fdata-structure-protocol\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: data-structure-protocol\ndescription: \"Give agents persistent structural memory of a codebase — navigate dependencies, track public APIs, and understand why connections exist without re-reading the whole repo.\"\nrisk: safe\nsource: \"https:\u002F\u002Fgithub.com\u002Fk-kolomeitsev\u002Fdata-structure-protocol\"\ndate_added: \"2026-02-27\"\n---\n\n# Data Structure Protocol (DSP)\n\nLLM coding agents lose context between tasks. On large codebases they spend most of their tokens on \"orientation\" — figuring out where things live, what depends on what, and what is safe to change. DSP solves this by externalizing the project's structural map into a persistent, queryable graph stored in a `.dsp\u002F` directory next to the code.\n\nDSP is NOT documentation for humans and NOT an AST dump. It captures three things: **meaning** (why an entity exists), **boundaries** (what it imports and exposes), and **reasons** (why each connection exists). This is enough for an agent to navigate, refactor, and generate code without loading the entire source tree into the context window.\n\n## When to Use\nUse this skill when:\n- The project has a `.dsp\u002F` directory (DSP is already set up)\n- The user asks to set up DSP, bootstrap, or map a project's structure\n- Creating, modifying, or deleting code files in a DSP-tracked project (to keep the graph updated)\n- Navigating project structure, understanding dependencies, or finding specific modules\n- The user mentions DSP, dsp-cli, `.dsp`, or structure mapping\n- Performing impact analysis before a refactor or dependency replacement\n\n## Core Concepts\n\n### Code = graph\n\nDSP models the codebase as a directed graph. Nodes are **entities**, edges are **imports** and **shared\u002Fexports**.\n\nTwo entity kinds exist:\n- **Object**: any \"thing\" that isn't a function (module\u002Ffile\u002Fclass\u002Fconfig\u002Fresource\u002Fexternal dependency)\n- **Function**: an exported function\u002Fmethod\u002Fhandler\u002Fpipeline\n\n### Identity by UID, not by file path\n\nEvery entity gets a stable UID: `obj-\u003C8hex>` for objects, `func-\u003C8hex>` for functions. File paths are attributes that can change; UIDs survive renames, moves, and reformatting.\n\nFor entities inside a file, the UID is anchored with a comment marker in source code:\n\n```js\n\u002F\u002F @dsp func-7f3a9c12\nexport function calculateTotal(items) { ... }\n```\n\n```python\n# @dsp obj-e5f6g7h8\nclass UserService:\n```\n\n### Every connection has a \"why\"\n\nWhen an import is recorded, DSP stores a short reason explaining *why* that dependency exists. This lives in the `exports\u002F` reverse index of the imported entity. A dependency graph without reasons tells you *what imports what*; reasons tell you **what is safe to change and who will break**.\n\n### Storage format\n\nEach entity gets a small directory under `.dsp\u002F`:\n\n```\n.dsp\u002F\n├── TOC                        # ordered list of all entity UIDs from root\n├── obj-a1b2c3d4\u002F\n│   ├── description            # source path, kind, purpose (1-3 sentences)\n│   ├── imports                # UIDs this entity depends on (one per line)\n│   ├── shared                 # UIDs of public API \u002F exported entities\n│   └── exports\u002F               # reverse index: who imports this and why\n│       ├── \u003Cimporter_uid>     # file content = \"why\" text\n│       └── \u003Cshared_uid>\u002F\n│           ├── description    # what is exported\n│           └── \u003Cimporter_uid> # why this specific export is imported\n└── func-7f3a9c12\u002F\n    ├── description\n    ├── imports\n    └── exports\u002F\n```\n\nEverything is plain text. Diffable. Reviewable. No database needed.\n\n### Full import coverage\n\nEvery file or artifact that is imported anywhere must be represented in `.dsp` as an Object — code, images, styles, configs, JSON, wasm, everything. External dependencies (npm packages, stdlib, etc.) are recorded as `kind: external` but their internals are never analyzed.\n\n## How It Works\n\n### Initial Setup\n\nThe skill relies on a standalone Python CLI script `dsp-cli.py`. If it is missing from the project, download it:\n\n```bash\ncurl -O https:\u002F\u002Fraw.githubusercontent.com\u002Fk-kolomeitsev\u002Fdata-structure-protocol\u002Fmain\u002Fskills\u002Fdata-structure-protocol\u002Fscripts\u002Fdsp-cli.py\n```\n\nRequires **Python 3.10+**. All commands use `python dsp-cli.py --root \u003Cproject-root> \u003Ccommand>`.\n\n### Bootstrap (initial mapping)\n\nIf `.dsp\u002F` is empty, traverse the project from root entrypoint(s) via DFS on imports:\n\n1. Identify root entrypoints (`package.json` main, framework entry, `main.py`, etc.)\n2. Document the root file: `create-object`, `create-function` for each export, `create-shared`, `add-import` for all dependencies\n3. Take the first non-external import, document it fully, descend into its imports\n4. Backtrack when no unvisited local imports remain; continue until all reachable files are documented\n5. External dependencies: `create-object --kind external`, add to TOC, but never descend into `node_modules`\u002F`site-packages`\u002Fetc.\n\n### Workflow Rules\n\n- **Before changing code**: Find affected entities via `search`, `find-by-source`, or `read-toc`. Read their `description` and `imports` to understand context.\n- **When creating a file\u002Fmodule**: Call `create-object`. For each exported function — `create-function` (with `--owner`). Register exports via `create-shared`.\n- **When adding an import**: Call `add-import` with a brief `why`. For external deps — first `create-object --kind external` if the entity doesn't exist.\n- **When removing import\u002Fexport\u002Ffile**: Call `remove-import`, `remove-shared`, `remove-entity`. Cascade cleanup is automatic.\n- **When renaming\u002Fmoving a file**: Call `move-entity`. UID does not change.\n- **Don't touch DSP** if only internal implementation changed without affecting purpose or dependencies.\n\n### Key Commands\n\n| Category | Commands |\n|----------|----------|\n| **Create** | `init`, `create-object`, `create-function`, `create-shared`, `add-import` |\n| **Update** | `update-description`, `update-import-why`, `move-entity` |\n| **Delete** | `remove-import`, `remove-shared`, `remove-entity` |\n| **Navigate** | `get-entity`, `get-children --depth N`, `get-parents --depth N`, `get-path`, `get-recipients`, `read-toc` |\n| **Search** | `search \u003Cquery>`, `find-by-source \u003Cpath>` |\n| **Diagnostics** | `detect-cycles`, `get-orphans`, `get-stats` |\n\n### When to Update DSP\n\n| Code Change | DSP Action |\n|---|---|\n| New file\u002Fmodule | `create-object` + `create-function` + `create-shared` + `add-import` |\n| New import added | `add-import` (+ `create-object --kind external` if new dep) |\n| Import removed | `remove-import` |\n| Export added | `create-shared` (+ `create-function` if new) |\n| Export removed | `remove-shared` |\n| File renamed\u002Fmoved | `move-entity` |\n| File deleted | `remove-entity` |\n| Purpose changed | `update-description` |\n| Internal-only change | **No DSP update needed** |\n\n## Examples\n\n### Example 1: Setting up DSP and documenting a module\n\n```bash\npython dsp-cli.py --root . init\n\npython dsp-cli.py --root . create-object \"src\u002Fapp.ts\" \"Main application entrypoint\"\n# Output: obj-a1b2c3d4\n\npython dsp-cli.py --root . create-function \"src\u002Fapp.ts#start\" \"Starts the HTTP server\" --owner obj-a1b2c3d4\n# Output: func-7f3a9c12\n\npython dsp-cli.py --root . create-shared obj-a1b2c3d4 func-7f3a9c12\n\npython dsp-cli.py --root . add-import obj-a1b2c3d4 obj-deadbeef \"HTTP routing\"\n```\n\n### Example 2: Navigating the graph before making changes\n\n```bash\npython dsp-cli.py --root . search \"authentication\"\npython dsp-cli.py --root . get-entity obj-a1b2c3d4\npython dsp-cli.py --root . get-children obj-a1b2c3d4 --depth 2\npython dsp-cli.py --root . get-recipients obj-a1b2c3d4\npython dsp-cli.py --root . get-path obj-a1b2c3d4 func-7f3a9c12\n```\n\n### Example 3: Impact analysis before replacing a library\n\n```bash\npython dsp-cli.py --root . find-by-source \"lodash\"\n# Output: obj-11223344\n\npython dsp-cli.py --root . get-recipients obj-11223344\n# Shows every module that imports lodash and WHY — lets you systematically replace it\n```\n\n## Best Practices\n\n- ✅ **Do:** Update DSP immediately when creating new files, adding imports, or changing public APIs\n- ✅ **Do:** Always add a meaningful `why` reason when recording an import — this is where most of DSP's value lives\n- ✅ **Do:** Use `kind: external` for third-party libraries without analyzing their internals\n- ✅ **Do:** Keep descriptions minimal (1-3 sentences about purpose, not implementation)\n- ✅ **Do:** Treat `.dsp\u002F` diffs like code diffs — review them, keep them accurate\n- ❌ **Don't:** Touch `.dsp\u002F` for internal-only changes that don't affect purpose or dependencies\n- ❌ **Don't:** Change an entity's UID on rename\u002Fmove (use `move-entity` instead)\n- ❌ **Don't:** Create UIDs for every local variable or helper — only file-level Objects and public\u002Fshared entities\n\n## Integration\n\nThis skill connects naturally to:\n- **context-compression** — DSP reduces the need for compression by providing targeted retrieval instead of loading everything\n- **context-optimization** — DSP is a structural optimization: agents pull minimal \"context bundles\" instead of raw source\n- **architecture** — DSP captures architectural boundaries (imports\u002Fexports) that feed system design decisions\n\n## References\n\n- **Full architecture specification**: [ARCHITECTURE.md](https:\u002F\u002Fgithub.com\u002Fk-kolomeitsev\u002Fdata-structure-protocol\u002Fblob\u002Fmain\u002FARCHITECTURE.md)\n- **CLI source + reference docs**: [skills\u002Fdata-structure-protocol](https:\u002F\u002Fgithub.com\u002Fk-kolomeitsev\u002Fdata-structure-protocol\u002Ftree\u002Fmain\u002Fskills\u002Fdata-structure-protocol)\n- **Introduction article**: [article.md](https:\u002F\u002Fgithub.com\u002Fk-kolomeitsev\u002Fdata-structure-protocol\u002Fblob\u002Fmain\u002Farticle.md)\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# Data Structure Protocol (DSP)\n\nLLM coding agents lose context between tasks. On large codebases they spend most of their tokens on \"orientation\" — figuring out where things live, what depends on what, and what is safe to change. DSP solves this by externalizing the project's structural map into a persistent, queryable graph stored in a `.dsp\u002F` directory next to the code.\n\nDSP is NOT documentation for humans and NOT an AST dump. It captures three things: **meaning** (why an entity exists), **boundaries** (what it imports and exposes), and **reasons** (why each connection exists). This is enough for an agent to navigate, refactor, and generate code without loading the entire source tree into the context window.\n\n## When to Use\nUse this skill when:\n- The project has a `.dsp\u002F` directory (DSP is already set up)\n- The user asks to set up DSP, bootstrap, or map a project's structure\n- Creating, modifying, or deleting code files in a DSP-tracked project (to keep the graph updated)\n- Navigating project structure, understanding dependencies, or finding specific modules\n- The user mentions DSP, dsp-cli, `.dsp`, or structure mapping\n- Performing impact analysis before a refactor or dependency replacement\n\n## Core Concepts\n\n### Code = graph\n\nDSP models the codebase as a directed graph. Nodes are **entities**, edges are **imports** and **shared\u002Fexports**.\n\nTwo entity kinds exist:\n- **Object**: any \"thing\" that isn't a function (module\u002Ffile\u002Fclass\u002Fconfig\u002Fresource\u002Fexternal dependency)\n- **Function**: an exported function\u002Fmethod\u002Fhandler\u002Fpipeline\n\n### Identity by UID, not by file path\n\nEvery entity gets a stable UID: `obj-\u003C8hex>` for objects, `func-\u003C8hex>` for functions. File paths are attributes that can change; UIDs survive renames, moves, and reformatting.\n\nFor entities inside a file, the UID is anchored with a comment marker in source code:\n\n```js\n\u002F\u002F @dsp func-7f3a9c12\nexport function calculateTotal(items) { ... }\n```\n\n```python\n# @dsp obj-e5f6g7h8\nclass UserService:\n```\n\n### Every connection has a \"why\"\n\nWhen an import is recorded, DSP stores a short reason explaining *why* that dependency exists. This lives in the `exports\u002F` reverse index of the imported entity. A dependency graph without reasons tells you *what imports what*; reasons tell you **what is safe to change and who will break**.\n\n### Storage format\n\nEach entity gets a small directory under `.dsp\u002F`:\n\n```\n.dsp\u002F\n├── TOC                        # ordered list of all entity UIDs from root\n├── obj-a1b2c3d4\u002F\n│   ├── description            # source path, kind, purpose (1-3 sentences)\n│   ├── imports                # UIDs this entity depends on (one per line)\n│   ├── shared                 # UIDs of public API \u002F exported entities\n│   └── exports\u002F               # reverse index: who imports this and why\n│       ├── \u003Cimporter_uid>     # file content = \"why\" text\n│       └── \u003Cshared_uid>\u002F\n│           ├── description    # what is exported\n│           └── \u003Cimporter_uid> # why this specific export is imported\n└── func-7f3a9c12\u002F\n    ├── description\n    ├── imports\n    └── exports\u002F\n```\n\nEverything is plain text. Diffable. Reviewable. No database needed.\n\n### Full import coverage\n\nEvery file or artifact that is imported anywhere must be represented in `.dsp` as an Object — code, images, styles, configs, JSON, wasm, everything. External dependencies (npm packages, stdlib, etc.) are recorded as `kind: external` but their internals are never analyzed.\n\n## How It Works\n\n### Initial Setup\n\nThe skill relies on a standalone Python CLI script `dsp-cli.py`. If it is missing from the project, download it:\n\n```bash\ncurl -O https:\u002F\u002Fraw.githubusercontent.com\u002Fk-kolomeitsev\u002Fdata-structure-protocol\u002Fmain\u002Fskills\u002Fdata-structure-protocol\u002Fscripts\u002Fdsp-cli.py\n```\n\nRequires **Python 3.10+**. All commands use `python dsp-cli.py --root \u003Cproject-root> \u003Ccommand>`.\n\n### Bootstrap (initial mapping)\n\nIf `.dsp\u002F` is empty, traverse the project from root entrypoint(s) via DFS on imports:\n\n1. Identify root entrypoints (`package.json` main, framework entry, `main.py`, etc.)\n2. Document the root file: `create-object`, `create-function` for each export, `create-shared`, `add-import` for all dependencies\n3. Take the first non-external import, document it fully, descend into its imports\n4. Backtrack when no unvisited local imports remain; continue until all reachable files are documented\n5. External dependencies: `create-object --kind external`, add to TOC, but never descend into `node_modules`\u002F`site-packages`\u002Fetc.\n\n### Workflow Rules\n\n- **Before changing code**: Find affected entities via `search`, `find-by-source`, or `read-toc`. Read their `description` and `imports` to understand context.\n- **When creating a file\u002Fmodule**: Call `create-object`. For each exported function — `create-function` (with `--owner`). Register exports via `create-shared`.\n- **When adding an import**: Call `add-import` with a brief `why`. For external deps — first `create-object --kind external` if the entity doesn't exist.\n- **When removing import\u002Fexport\u002Ffile**: Call `remove-import`, `remove-shared`, `remove-entity`. Cascade cleanup is automatic.\n- **When renaming\u002Fmoving a file**: Call `move-entity`. UID does not change.\n- **Don't touch DSP** if only internal implementation changed without affecting purpose or dependencies.\n\n### Key Commands\n\n| Category | Commands |\n|----------|----------|\n| **Create** | `init`, `create-object`, `create-function`, `create-shared`, `add-import` |\n| **Update** | `update-description`, `update-import-why`, `move-entity` |\n| **Delete** | `remove-import`, `remove-shared`, `remove-entity` |\n| **Navigate** | `get-entity`, `get-children --depth N`, `get-parents --depth N`, `get-path`, `get-recipients`, `read-toc` |\n| **Search** | `search \u003Cquery>`, `find-by-source \u003Cpath>` |\n| **Diagnostics** | `detect-cycles`, `get-orphans`, `get-stats` |\n\n### When to Update DSP\n\n| Code Change | DSP Action |\n|---|---|\n| New file\u002Fmodule | `create-object` + `create-function` + `create-shared` + `add-import` |\n| New import added | `add-import` (+ `create-object --kind external` if new dep) |\n| Import removed | `remove-import` |\n| Export added | `create-shared` (+ `create-function` if new) |\n| Export removed | `remove-shared` |\n| File renamed\u002Fmoved | `move-entity` |\n| File deleted | `remove-entity` |\n| Purpose changed | `update-description` |\n| Internal-only change | **No DSP update needed** |\n\n## Examples\n\n### Example 1: Setting up DSP and documenting a module\n\n```bash\npython dsp-cli.py --root . init\n\npython dsp-cli.py --root . create-object \"src\u002Fapp.ts\" \"Main application entrypoint\"\n# Output: obj-a1b2c3d4\n\npython dsp-cli.py --root . create-function \"src\u002Fapp.ts#start\" \"Starts the HTTP server\" --owner obj-a1b2c3d4\n# Output: func-7f3a9c12\n\npython dsp-cli.py --root . create-shared obj-a1b2c3d4 func-7f3a9c12\n\npython dsp-cli.py --root . add-import obj-a1b2c3d4 obj-deadbeef \"HTTP routing\"\n```\n\n### Example 2: Navigating the graph before making changes\n\n```bash\npython dsp-cli.py --root . search \"authentication\"\npython dsp-cli.py --root . get-entity obj-a1b2c3d4\npython dsp-cli.py --root . get-children obj-a1b2c3d4 --depth 2\npython dsp-cli.py --root . get-recipients obj-a1b2c3d4\npython dsp-cli.py --root . get-path obj-a1b2c3d4 func-7f3a9c12\n```\n\n### Example 3: Impact analysis before replacing a library\n\n```bash\npython dsp-cli.py --root . find-by-source \"lodash\"\n# Output: obj-11223344\n\npython dsp-cli.py --root . get-recipients obj-11223344\n# Shows every module that imports lodash and WHY — lets you systematically replace it\n```\n\n## Best Practices\n\n- ✅ **Do:** Update DSP immediately when creating new files, adding imports, or changing public APIs\n- ✅ **Do:** Always add a meaningful `why` reason when recording an import — this is where most of DSP's value lives\n- ✅ **Do:** Use `kind: external` for third-party libraries without analyzing their internals\n- ✅ **Do:** Keep descriptions minimal (1-3 sentences about purpose, not implementation)\n- ✅ **Do:** Treat `.dsp\u002F` diffs like code diffs — review them, keep them accurate\n- ❌ **Don't:** Touch `.dsp\u002F` for internal-only changes that don't affect purpose or dependencies\n- ❌ **Don't:** Change an entity's UID on rename\u002Fmove (use `move-entity` instead)\n- ❌ **Don't:** Create UIDs for every local variable or helper — only file-level Objects and public\u002Fshared entities\n\n## Integration\n\nThis skill connects naturally to:\n- **context-compression** — DSP reduces the need for compression by providing targeted retrieval instead of loading everything\n- **context-optimization** — DSP is a structural optimization: agents pull minimal \"context bundles\" instead of raw source\n- **architecture** — DSP captures architectural boundaries (imports\u002Fexports) that feed system design decisions\n\n## References\n\n- **Full architecture specification**: [ARCHITECTURE.md](https:\u002F\u002Fgithub.com\u002Fk-kolomeitsev\u002Fdata-structure-protocol\u002Fblob\u002Fmain\u002FARCHITECTURE.md)\n- **CLI source + reference docs**: [skills\u002Fdata-structure-protocol](https:\u002F\u002Fgithub.com\u002Fk-kolomeitsev\u002Fdata-structure-protocol\u002Ftree\u002Fmain\u002Fskills\u002Fdata-structure-protocol)\n- **Introduction article**: [article.md](https:\u002F\u002Fgithub.com\u002Fk-kolomeitsev\u002Fdata-structure-protocol\u002Fblob\u002Fmain\u002Farticle.md)\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"safe","https:\u002F\u002Fgithub.com\u002Fk-kolomeitsev\u002Fdata-structure-protocol","2026-02-27","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fdata-structure-protocol",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill data-structure-protocol",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill data-structure-protocol",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill data-structure-protocol","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fdata-structure-protocol\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]