[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C8T6C7PA26FBKBZDNFP5YN":3,"skill-same:01M7C8T6C7PA26FBKBZDNFP5YN":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},"01M7C8T6C7PA26FBKBZDNFP5YN","conductor-new-track",null,"Create a new track with specification and phased implementation plan","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\u002Fconductor-new-track\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: conductor-new-track\ndescription: \"Create a new track with specification and phased implementation plan\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# New Track\n\nCreate a new track (feature, bug fix, chore, or refactor) with a detailed specification and phased implementation plan.\n\n## Use this skill when\n\n- Working on new track tasks or workflows\n- Needing guidance, best practices, or checklists for new track\n\n## Do not use this skill when\n\n- The task is unrelated to new track\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\n## Pre-flight Checks\n\n1. Verify Conductor is initialized:\n   - Check `conductor\u002Fproduct.md` exists\n   - Check `conductor\u002Ftech-stack.md` exists\n   - Check `conductor\u002Fworkflow.md` exists\n   - If missing: Display error and suggest running `\u002Fconductor:setup` first\n\n2. Load context files:\n   - Read `conductor\u002Fproduct.md` for product context\n   - Read `conductor\u002Ftech-stack.md` for technical context\n   - Read `conductor\u002Fworkflow.md` for TDD\u002Fcommit preferences\n\n## Track Classification\n\nDetermine track type based on description or ask user:\n\n```\nWhat type of track is this?\n\n1. Feature - New functionality\n2. Bug - Fix for existing issue\n3. Chore - Maintenance, dependencies, config\n4. Refactor - Code improvement without behavior change\n```\n\n## Interactive Specification Gathering\n\n**CRITICAL RULES:**\n\n- Ask ONE question per turn\n- Wait for user response before proceeding\n- Tailor questions based on track type\n- Maximum 6 questions total\n\n### For Feature Tracks\n\n**Q1: Feature Summary**\n\n```\nDescribe the feature in 1-2 sentences.\n[If argument provided, confirm: \"You want to: {argument}. Is this correct?\"]\n```\n\n**Q2: User Story**\n\n```\nWho benefits and how?\n\nFormat: As a [user type], I want to [action] so that [benefit].\n```\n\n**Q3: Acceptance Criteria**\n\n```\nWhat must be true for this feature to be complete?\n\nList 3-5 acceptance criteria (one per line):\n```\n\n**Q4: Dependencies**\n\n```\nDoes this depend on any existing code, APIs, or other tracks?\n\n1. No dependencies\n2. Depends on existing code (specify)\n3. Depends on incomplete track (specify)\n```\n\n**Q5: Scope Boundaries**\n\n```\nWhat is explicitly OUT of scope for this track?\n(Helps prevent scope creep)\n```\n\n**Q6: Technical Considerations (optional)**\n\n```\nAny specific technical approach or constraints?\n(Press enter to skip)\n```\n\n### For Bug Tracks\n\n**Q1: Bug Summary**\n\n```\nWhat is broken?\n[If argument provided, confirm]\n```\n\n**Q2: Steps to Reproduce**\n\n```\nHow can this bug be reproduced?\nList steps:\n```\n\n**Q3: Expected vs Actual Behavior**\n\n```\nWhat should happen vs what actually happens?\n```\n\n**Q4: Affected Areas**\n\n```\nWhat parts of the system are affected?\n```\n\n**Q5: Root Cause Hypothesis (optional)**\n\n```\nAny hypothesis about the cause?\n(Press enter to skip)\n```\n\n### For Chore\u002FRefactor Tracks\n\n**Q1: Task Summary**\n\n```\nWhat needs to be done?\n[If argument provided, confirm]\n```\n\n**Q2: Motivation**\n\n```\nWhy is this work needed?\n```\n\n**Q3: Success Criteria**\n\n```\nHow will we know this is complete?\n```\n\n**Q4: Risk Assessment**\n\n```\nWhat could go wrong? Any risky changes?\n```\n\n## Track ID Generation\n\nGenerate track ID in format: `{shortname}_{YYYYMMDD}`\n\n- Extract shortname from feature\u002Fbug summary (2-3 words, lowercase, hyphenated)\n- Use current date\n- Example: `user-auth_20250115`, `nav-bug_20250115`\n\nValidate uniqueness:\n\n- Check `conductor\u002Ftracks.md` for existing IDs\n- If collision, append counter: `user-auth_20250115_2`\n\n## Specification Generation\n\nCreate `conductor\u002Ftracks\u002F{trackId}\u002Fspec.md`:\n\n```markdown\n# Specification: {Track Title}\n\n**Track ID:** {trackId}\n**Type:** {Feature|Bug|Chore|Refactor}\n**Created:** {YYYY-MM-DD}\n**Status:** Draft\n\n## Summary\n\n{1-2 sentence summary}\n\n## Context\n\n{Product context from product.md relevant to this track}\n\n## User Story (for features)\n\nAs a {user}, I want to {action} so that {benefit}.\n\n## Problem Description (for bugs)\n\n{Bug description, steps to reproduce}\n\n## Acceptance Criteria\n\n- [ ] {Criterion 1}\n- [ ] {Criterion 2}\n- [ ] {Criterion 3}\n\n## Dependencies\n\n{List dependencies or \"None\"}\n\n## Out of Scope\n\n{Explicit exclusions}\n\n## Technical Notes\n\n{Technical considerations or \"None specified\"}\n\n---\n\n_Generated by Conductor. Review and edit as needed._\n```\n\n## User Review of Spec\n\nDisplay the generated spec and ask:\n\n```\nHere is the specification I've generated:\n\n{spec content}\n\nIs this specification correct?\n1. Yes, proceed to plan generation\n2. No, let me edit (opens for inline edits)\n3. Start over with different inputs\n```\n\n## Plan Generation\n\nAfter spec approval, generate `conductor\u002Ftracks\u002F{trackId}\u002Fplan.md`:\n\n### Plan Structure\n\n```markdown\n# Implementation Plan: {Track Title}\n\n**Track ID:** {trackId}\n**Spec:** spec.md\n**Created:** {YYYY-MM-DD}\n**Status:** [ ] Not Started\n\n## Overview\n\n{Brief summary of implementation approach}\n\n## Phase 1: {Phase Name}\n\n{Phase description}\n\n### Tasks\n\n- [ ] Task 1.1: {Description}\n- [ ] Task 1.2: {Description}\n- [ ] Task 1.3: {Description}\n\n### Verification\n\n- [ ] {Verification step for phase 1}\n\n## Phase 2: {Phase Name}\n\n{Phase description}\n\n### Tasks\n\n- [ ] Task 2.1: {Description}\n- [ ] Task 2.2: {Description}\n\n### Verification\n\n- [ ] {Verification step for phase 2}\n\n## Phase 3: {Phase Name} (if needed)\n\n...\n\n## Final Verification\n\n- [ ] All acceptance criteria met\n- [ ] Tests passing\n- [ ] Documentation updated (if applicable)\n- [ ] Ready for review\n\n---\n\n_Generated by Conductor. Tasks will be marked [~] in progress and [x] complete._\n```\n\n### Phase Guidelines\n\n- Group related tasks into logical phases\n- Each phase should be independently verifiable\n- Include verification task after each phase\n- TDD tracks: Include test writing tasks before implementation tasks\n- Typical structure:\n  1. **Setup\u002FFoundation** - Initial scaffolding, interfaces\n  2. **Core Implementation** - Main functionality\n  3. **Integration** - Connect with existing system\n  4. **Polish** - Error handling, edge cases, docs\n\n## User Review of Plan\n\nDisplay the generated plan and ask:\n\n```\nHere is the implementation plan:\n\n{plan content}\n\nIs this plan correct?\n1. Yes, create the track\n2. No, let me edit (opens for inline edits)\n3. Add more phases\u002Ftasks\n4. Start over\n```\n\n## Track Creation\n\nAfter plan approval:\n\n1. Create directory structure:\n\n   ```\n   conductor\u002Ftracks\u002F{trackId}\u002F\n   ├── spec.md\n   ├── plan.md\n   ├── metadata.json\n   └── index.md\n   ```\n\n2. Create `metadata.json`:\n\n   ```json\n   {\n     \"id\": \"{trackId}\",\n     \"title\": \"{Track Title}\",\n     \"type\": \"feature|bug|chore|refactor\",\n     \"status\": \"pending\",\n     \"created\": \"ISO_TIMESTAMP\",\n     \"updated\": \"ISO_TIMESTAMP\",\n     \"phases\": {\n       \"total\": N,\n       \"completed\": 0\n     },\n     \"tasks\": {\n       \"total\": M,\n       \"completed\": 0\n     }\n   }\n   ```\n\n3. Create `index.md`:\n\n   ```markdown\n   # Track: {Track Title}\n\n   **ID:** {trackId}\n   **Status:** Pending\n\n   ## Documents\n\n   - Specification\n   - Implementation Plan\n\n   ## Progress\n\n   - Phases: 0\u002F{N} complete\n   - Tasks: 0\u002F{M} complete\n\n   ## Quick Links\n\n   - Back to Tracks\n   - Product Context\n   ```\n\n4. Register in `conductor\u002Ftracks.md`:\n   - Add row to tracks table\n   - Format: `| [ ] | {trackId} | {title} | {created} | {created} |`\n\n5. Update `conductor\u002Findex.md`:\n   - Add track to \"Active Tracks\" section\n\n## Completion Message\n\n```\nTrack created successfully!\n\nTrack ID: {trackId}\nLocation: conductor\u002Ftracks\u002F{trackId}\u002F\n\nFiles created:\n- spec.md - Requirements specification\n- plan.md - Phased implementation plan\n- metadata.json - Track metadata\n- index.md - Track navigation\n\nNext steps:\n1. Review spec.md and plan.md, make any edits\n2. Run \u002Fconductor:implement {trackId} to start implementation\n3. Run \u002Fconductor:status to see project progress\n```\n\n## Error Handling\n\n- If directory creation fails: Halt and report, do not register in tracks.md\n- If any file write fails: Clean up partial track, report error\n- If tracks.md update fails: Warn user to manually register track\n","# New Track\n\nCreate a new track (feature, bug fix, chore, or refactor) with a detailed specification and phased implementation plan.\n\n## Use this skill when\n\n- Working on new track tasks or workflows\n- Needing guidance, best practices, or checklists for new track\n\n## Do not use this skill when\n\n- The task is unrelated to new track\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\n## Pre-flight Checks\n\n1. Verify Conductor is initialized:\n   - Check `conductor\u002Fproduct.md` exists\n   - Check `conductor\u002Ftech-stack.md` exists\n   - Check `conductor\u002Fworkflow.md` exists\n   - If missing: Display error and suggest running `\u002Fconductor:setup` first\n\n2. Load context files:\n   - Read `conductor\u002Fproduct.md` for product context\n   - Read `conductor\u002Ftech-stack.md` for technical context\n   - Read `conductor\u002Fworkflow.md` for TDD\u002Fcommit preferences\n\n## Track Classification\n\nDetermine track type based on description or ask user:\n\n```\nWhat type of track is this?\n\n1. Feature - New functionality\n2. Bug - Fix for existing issue\n3. Chore - Maintenance, dependencies, config\n4. Refactor - Code improvement without behavior change\n```\n\n## Interactive Specification Gathering\n\n**CRITICAL RULES:**\n\n- Ask ONE question per turn\n- Wait for user response before proceeding\n- Tailor questions based on track type\n- Maximum 6 questions total\n\n### For Feature Tracks\n\n**Q1: Feature Summary**\n\n```\nDescribe the feature in 1-2 sentences.\n[If argument provided, confirm: \"You want to: {argument}. Is this correct?\"]\n```\n\n**Q2: User Story**\n\n```\nWho benefits and how?\n\nFormat: As a [user type], I want to [action] so that [benefit].\n```\n\n**Q3: Acceptance Criteria**\n\n```\nWhat must be true for this feature to be complete?\n\nList 3-5 acceptance criteria (one per line):\n```\n\n**Q4: Dependencies**\n\n```\nDoes this depend on any existing code, APIs, or other tracks?\n\n1. No dependencies\n2. Depends on existing code (specify)\n3. Depends on incomplete track (specify)\n```\n\n**Q5: Scope Boundaries**\n\n```\nWhat is explicitly OUT of scope for this track?\n(Helps prevent scope creep)\n```\n\n**Q6: Technical Considerations (optional)**\n\n```\nAny specific technical approach or constraints?\n(Press enter to skip)\n```\n\n### For Bug Tracks\n\n**Q1: Bug Summary**\n\n```\nWhat is broken?\n[If argument provided, confirm]\n```\n\n**Q2: Steps to Reproduce**\n\n```\nHow can this bug be reproduced?\nList steps:\n```\n\n**Q3: Expected vs Actual Behavior**\n\n```\nWhat should happen vs what actually happens?\n```\n\n**Q4: Affected Areas**\n\n```\nWhat parts of the system are affected?\n```\n\n**Q5: Root Cause Hypothesis (optional)**\n\n```\nAny hypothesis about the cause?\n(Press enter to skip)\n```\n\n### For Chore\u002FRefactor Tracks\n\n**Q1: Task Summary**\n\n```\nWhat needs to be done?\n[If argument provided, confirm]\n```\n\n**Q2: Motivation**\n\n```\nWhy is this work needed?\n```\n\n**Q3: Success Criteria**\n\n```\nHow will we know this is complete?\n```\n\n**Q4: Risk Assessment**\n\n```\nWhat could go wrong? Any risky changes?\n```\n\n## Track ID Generation\n\nGenerate track ID in format: `{shortname}_{YYYYMMDD}`\n\n- Extract shortname from feature\u002Fbug summary (2-3 words, lowercase, hyphenated)\n- Use current date\n- Example: `user-auth_20250115`, `nav-bug_20250115`\n\nValidate uniqueness:\n\n- Check `conductor\u002Ftracks.md` for existing IDs\n- If collision, append counter: `user-auth_20250115_2`\n\n## Specification Generation\n\nCreate `conductor\u002Ftracks\u002F{trackId}\u002Fspec.md`:\n\n```markdown\n# Specification: {Track Title}\n\n**Track ID:** {trackId}\n**Type:** {Feature|Bug|Chore|Refactor}\n**Created:** {YYYY-MM-DD}\n**Status:** Draft\n\n## Summary\n\n{1-2 sentence summary}\n\n## Context\n\n{Product context from product.md relevant to this track}\n\n## User Story (for features)\n\nAs a {user}, I want to {action} so that {benefit}.\n\n## Problem Description (for bugs)\n\n{Bug description, steps to reproduce}\n\n## Acceptance Criteria\n\n- [ ] {Criterion 1}\n- [ ] {Criterion 2}\n- [ ] {Criterion 3}\n\n## Dependencies\n\n{List dependencies or \"None\"}\n\n## Out of Scope\n\n{Explicit exclusions}\n\n## Technical Notes\n\n{Technical considerations or \"None specified\"}\n\n---\n\n_Generated by Conductor. Review and edit as needed._\n```\n\n## User Review of Spec\n\nDisplay the generated spec and ask:\n\n```\nHere is the specification I've generated:\n\n{spec content}\n\nIs this specification correct?\n1. Yes, proceed to plan generation\n2. No, let me edit (opens for inline edits)\n3. Start over with different inputs\n```\n\n## Plan Generation\n\nAfter spec approval, generate `conductor\u002Ftracks\u002F{trackId}\u002Fplan.md`:\n\n### Plan Structure\n\n```markdown\n# Implementation Plan: {Track Title}\n\n**Track ID:** {trackId}\n**Spec:** spec.md\n**Created:** {YYYY-MM-DD}\n**Status:** [ ] Not Started\n\n## Overview\n\n{Brief summary of implementation approach}\n\n## Phase 1: {Phase Name}\n\n{Phase description}\n\n### Tasks\n\n- [ ] Task 1.1: {Description}\n- [ ] Task 1.2: {Description}\n- [ ] Task 1.3: {Description}\n\n### Verification\n\n- [ ] {Verification step for phase 1}\n\n## Phase 2: {Phase Name}\n\n{Phase description}\n\n### Tasks\n\n- [ ] Task 2.1: {Description}\n- [ ] Task 2.2: {Description}\n\n### Verification\n\n- [ ] {Verification step for phase 2}\n\n## Phase 3: {Phase Name} (if needed)\n\n...\n\n## Final Verification\n\n- [ ] All acceptance criteria met\n- [ ] Tests passing\n- [ ] Documentation updated (if applicable)\n- [ ] Ready for review\n\n---\n\n_Generated by Conductor. Tasks will be marked [~] in progress and [x] complete._\n```\n\n### Phase Guidelines\n\n- Group related tasks into logical phases\n- Each phase should be independently verifiable\n- Include verification task after each phase\n- TDD tracks: Include test writing tasks before implementation tasks\n- Typical structure:\n  1. **Setup\u002FFoundation** - Initial scaffolding, interfaces\n  2. **Core Implementation** - Main functionality\n  3. **Integration** - Connect with existing system\n  4. **Polish** - Error handling, edge cases, docs\n\n## User Review of Plan\n\nDisplay the generated plan and ask:\n\n```\nHere is the implementation plan:\n\n{plan content}\n\nIs this plan correct?\n1. Yes, create the track\n2. No, let me edit (opens for inline edits)\n3. Add more phases\u002Ftasks\n4. Start over\n```\n\n## Track Creation\n\nAfter plan approval:\n\n1. Create directory structure:\n\n   ```\n   conductor\u002Ftracks\u002F{trackId}\u002F\n   ├── spec.md\n   ├── plan.md\n   ├── metadata.json\n   └── index.md\n   ```\n\n2. Create `metadata.json`:\n\n   ```json\n   {\n     \"id\": \"{trackId}\",\n     \"title\": \"{Track Title}\",\n     \"type\": \"feature|bug|chore|refactor\",\n     \"status\": \"pending\",\n     \"created\": \"ISO_TIMESTAMP\",\n     \"updated\": \"ISO_TIMESTAMP\",\n     \"phases\": {\n       \"total\": N,\n       \"completed\": 0\n     },\n     \"tasks\": {\n       \"total\": M,\n       \"completed\": 0\n     }\n   }\n   ```\n\n3. Create `index.md`:\n\n   ```markdown\n   # Track: {Track Title}\n\n   **ID:** {trackId}\n   **Status:** Pending\n\n   ## Documents\n\n   - Specification\n   - Implementation Plan\n\n   ## Progress\n\n   - Phases: 0\u002F{N} complete\n   - Tasks: 0\u002F{M} complete\n\n   ## Quick Links\n\n   - Back to Tracks\n   - Product Context\n   ```\n\n4. Register in `conductor\u002Ftracks.md`:\n   - Add row to tracks table\n   - Format: `| [ ] | {trackId} | {title} | {created} | {created} |`\n\n5. Update `conductor\u002Findex.md`:\n   - Add track to \"Active Tracks\" section\n\n## Completion Message\n\n```\nTrack created successfully!\n\nTrack ID: {trackId}\nLocation: conductor\u002Ftracks\u002F{trackId}\u002F\n\nFiles created:\n- spec.md - Requirements specification\n- plan.md - Phased implementation plan\n- metadata.json - Track metadata\n- index.md - Track navigation\n\nNext steps:\n1. Review spec.md and plan.md, make any edits\n2. Run \u002Fconductor:implement {trackId} to start implementation\n3. Run \u002Fconductor:status to see project progress\n```\n\n## Error Handling\n\n- If directory creation fails: Halt and report, do not register in tracks.md\n- If any file write fails: Clean up partial track, report error\n- If tracks.md update fails: Warn user to manually register track\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"unknown","community","2026-02-27","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fconductor-new-track",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 conductor-new-track",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill conductor-new-track",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill conductor-new-track","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fconductor-new-track\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",[],[]]