[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BJS5CVJX8YEA3AF88G4429":3,"skill-same:01M7BJS5CVJX8YEA3AF88G4429":53},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BJS5CVJX8YEA3AF88G4429","requirements-clarity",null,"Clarify ambiguous requirements through focused dialogue before implementation. Use when requirements are unclear, features are complex (>2 days), or involve cross-team coordination. Ask two core questions - Why? (YAGNI check) and Simpler? (KISS check) - to ensure clarity before coding.","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-AI-应用工具\u002FYYC3-AI-应用工具-claude-code-templates-main\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Frequirements-clarity\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: requirements-clarity\ndescription: Clarify ambiguous requirements through focused dialogue before implementation. Use when requirements are unclear, features are complex (>2 days), or involve cross-team coordination. Ask two core questions - Why? (YAGNI check) and Simpler? (KISS check) - to ensure clarity before coding.\n---\n\n# Requirements Clarity Skill\n\n## Description\n\nAutomatically transforms vague requirements into actionable PRDs through systematic clarification with a 100-point scoring system.\n\n\n## Instructions\n\nWhen invoked, detect vague requirements:\n\n1. **Vague Feature Requests**\n   - User says: \"add login feature\", \"implement payment\", \"create dashboard\"\n   - Missing: How, with what technology, what constraints?\n\n2. **Missing Technical Context**\n   - No technology stack mentioned\n   - No integration points identified\n   - No performance\u002Fsecurity constraints\n\n3. **Incomplete Specifications**\n   - No acceptance criteria\n   - No success metrics\n   - No edge cases considered\n   - No error handling mentioned\n\n4. **Ambiguous Scope**\n   - Unclear boundaries (\"user management\" - what exactly?)\n   - No distinction between MVP and future enhancements\n   - Missing \"what's NOT included\"\n\n**Do NOT activate when**:\n- Specific file paths mentioned (e.g., \"auth.go:45\")\n- Code snippets included\n- Existing functions\u002Fclasses referenced\n- Bug fixes with clear reproduction steps\n\n## Core Principles\n\n1. **Systematic Questioning**\n   - Ask focused, specific questions\n   - One category at a time (2-3 questions per round)\n   - Build on previous answers\n   - Avoid overwhelming users\n\n2. **Quality-Driven Iteration**\n   - Continuously assess clarity score (0-100)\n   - Identify gaps systematically\n   - Iterate until ≥ 90 points\n   - Document all clarification rounds\n\n3. **Actionable Output**\n   - Generate concrete specifications\n   - Include measurable acceptance criteria\n   - Provide executable phases\n   - Enable direct implementation\n\n## Clarification Process\n\n### Step 1: Initial Requirement Analysis\n\n**Input**: User's requirement description\n\n**Tasks**:\n1. Parse and understand core requirement\n2. Generate feature name (kebab-case format)\n3. Determine document version (default `1.0` unless user specifies otherwise)\n4. Ensure `.\u002Fdocs\u002Fprds\u002F` exists for PRD output\n5. Perform initial clarity assessment (0-100)\n\n**Assessment Rubric**:\n```\nFunctional Clarity: \u002F30 points\n- Clear inputs\u002Foutputs: 10 pts\n- User interaction defined: 10 pts\n- Success criteria stated: 10 pts\n\nTechnical Specificity: \u002F25 points\n- Technology stack mentioned: 8 pts\n- Integration points identified: 8 pts\n- Constraints specified: 9 pts\n\nImplementation Completeness: \u002F25 points\n- Edge cases considered: 8 pts\n- Error handling mentioned: 9 pts\n- Data validation specified: 8 pts\n\nBusiness Context: \u002F20 points\n- Problem statement clear: 7 pts\n- Target users identified: 7 pts\n- Success metrics defined: 6 pts\n```\n\n**Initial Response Format**:\n```markdown\nI understand your requirement. Let me help you refine this specification.\n\n**Current Clarity Score**: X\u002F100\n\n**Clear Aspects**:\n- [List what's clear]\n\n**Needs Clarification**:\n- [List gaps]\n\nLet me systematically clarify these points...\n```\n\n### Step 2: Gap Analysis\n\nIdentify missing information across four dimensions:\n\n**1. Functional Scope**\n- What is the core functionality?\n- What are the boundaries?\n- What is out of scope?\n- What are edge cases?\n\n**2. User Interaction**\n- How do users interact?\n- What are the inputs?\n- What are the outputs?\n- What are success\u002Ffailure scenarios?\n\n**3. Technical Constraints**\n- Performance requirements?\n- Compatibility requirements?\n- Security considerations?\n- Scalability needs?\n\n**4. Business Value**\n- What problem does this solve?\n- Who are the target users?\n- What are success metrics?\n- What is the priority?\n\n### Step 3: Interactive Clarification\n\n**Question Strategy**:\n1. Start with highest-impact gaps\n2. Ask 2-3 questions per round\n3. Build context progressively\n4. Use user's language\n5. Provide examples when helpful\n\n**Question Format**:\n```markdown\nI need to clarify the following points to complete the requirements document:\n\n1. **[Category]**: [Specific question]?\n   - For example: [Example if helpful]\n\n2. **[Category]**: [Specific question]?\n\n3. **[Category]**: [Specific question]?\n\nPlease provide your answers, and I'll continue refining the PRD.\n```\n\n**After Each User Response**:\n1. Update clarity score\n2. Capture new information in the working PRD outline\n3. Identify remaining gaps\n4. If score \u003C 90: Continue with next round of questions\n5. If score ≥ 90: Proceed to PRD generation\n\n**Score Update Format**:\n```markdown\nThank you for the additional information!\n\n**Clarity Score Update**: X\u002F100 → Y\u002F100\n\n**New Clarified Content**:\n- [Summarize new information]\n\n**Remaining Points to Clarify**:\n- [List remaining gaps if score \u003C 90]\n\n[If score \u003C 90: Continue with next round of questions]\n[If score ≥ 90: \"Perfect! I will now generate the complete PRD document...\"]\n```\n\n### Step 4: PRD Generation\n\nOnce clarity score ≥ 90, generate comprehensive PRD.\n\n**Output File**:\n\n1. **Final PRD**: `.\u002Fdocs\u002Fprds\u002F{feature_name}-v{version}-prd.md`\n\nUse the `Write` tool to create or update this file. Derive `{version}` from the document version recorded in the PRD (default `1.0`).\n\n## PRD Document Structure\n\n```markdown\n# {Feature Name} - Product Requirements Document (PRD)\n\n## Requirements Description\n\n### Background\n- **Business Problem**: [Describe the business problem to solve]\n- **Target Users**: [Target user groups]\n- **Value Proposition**: [Value this feature brings]\n\n### Feature Overview\n- **Core Features**: [List of main features]\n- **Feature Boundaries**: [What is and isn't included]\n- **User Scenarios**: [Typical usage scenarios]\n\n### Detailed Requirements\n- **Input\u002FOutput**: [Specific input\u002Foutput specifications]\n- **User Interaction**: [User operation flow]\n- **Data Requirements**: [Data structures and validation rules]\n- **Edge Cases**: [Edge case handling]\n\n## Design Decisions\n\n### Technical Approach\n- **Architecture Choice**: [Technical architecture decisions and rationale]\n- **Key Components**: [List of main technical components]\n- **Data Storage**: [Data models and storage solutions]\n- **Interface Design**: [API\u002Finterface specifications]\n\n### Constraints\n- **Performance Requirements**: [Response time, throughput, etc.]\n- **Compatibility**: [System compatibility requirements]\n- **Security**: [Security considerations]\n- **Scalability**: [Future expansion considerations]\n\n### Risk Assessment\n- **Technical Risks**: [Potential technical risks and mitigation plans]\n- **Dependency Risks**: [External dependencies and alternatives]\n- **Schedule Risks**: [Timeline risks and response strategies]\n\n## Acceptance Criteria\n\n### Functional Acceptance\n- [ ] Feature 1: [Specific acceptance conditions]\n- [ ] Feature 2: [Specific acceptance conditions]\n- [ ] Feature 3: [Specific acceptance conditions]\n\n### Quality Standards\n- [ ] Code Quality: [Code standards and review requirements]\n- [ ] Test Coverage: [Testing requirements and coverage]\n- [ ] Performance Metrics: [Performance test pass criteria]\n- [ ] Security Review: [Security review requirements]\n\n### User Acceptance\n- [ ] User Experience: [UX acceptance criteria]\n- [ ] Documentation: [Documentation delivery requirements]\n- [ ] Training Materials: [If needed, training material requirements]\n\n## Execution Phases\n\n### Phase 1: Preparation\n**Goal**: Environment preparation and technical validation\n- [ ] Task 1: [Specific task description]\n- [ ] Task 2: [Specific task description]\n- **Deliverables**: [Phase deliverables]\n- **Time**: [Estimated time]\n\n### Phase 2: Core Development\n**Goal**: Implement core functionality\n- [ ] Task 1: [Specific task description]\n- [ ] Task 2: [Specific task description]\n- **Deliverables**: [Phase deliverables]\n- **Time**: [Estimated time]\n\n### Phase 3: Integration & Testing\n**Goal**: Integration and quality assurance\n- [ ] Task 1: [Specific task description]\n- [ ] Task 2: [Specific task description]\n- **Deliverables**: [Phase deliverables]\n- **Time**: [Estimated time]\n\n### Phase 4: Deployment\n**Goal**: Release and monitoring\n- [ ] Task 1: [Specific task description]\n- [ ] Task 2: [Specific task description]\n- **Deliverables**: [Phase deliverables]\n- **Time**: [Estimated time]\n\n---\n\n**Document Version**: 1.0\n**Created**: {timestamp}\n**Clarification Rounds**: {clarification_rounds}\n**Quality Score**: {quality_score}\u002F100\n```\n\n## Behavioral Guidelines\n\n### DO\n- Ask specific, targeted questions\n- Build on previous answers\n- Provide examples to guide users\n- Maintain conversational tone\n- Summarize clarification rounds within the PRD\n- Use clear, professional English\n- Generate concrete specifications\n- Stay in clarification mode until score ≥ 90\n\n### DON'T\n- Ask all questions at once\n- Make assumptions without confirmation\n- Generate PRD before 90+ score\n- Skip any required sections\n- Use vague or abstract language\n- Proceed without user responses\n- Exit skill mode prematurely\n\n## Success Criteria\n\n- Clarity score ≥ 90\u002F100\n- All PRD sections complete with substance\n- Acceptance criteria checklistable (using `- [ ]` format)\n- Execution phases actionable with concrete tasks\n- User approves final PRD\n- Ready for development handoff\n","# Requirements Clarity Skill\n\n## Description\n\nAutomatically transforms vague requirements into actionable PRDs through systematic clarification with a 100-point scoring system.\n\n\n## Instructions\n\nWhen invoked, detect vague requirements:\n\n1. **Vague Feature Requests**\n   - User says: \"add login feature\", \"implement payment\", \"create dashboard\"\n   - Missing: How, with what technology, what constraints?\n\n2. **Missing Technical Context**\n   - No technology stack mentioned\n   - No integration points identified\n   - No performance\u002Fsecurity constraints\n\n3. **Incomplete Specifications**\n   - No acceptance criteria\n   - No success metrics\n   - No edge cases considered\n   - No error handling mentioned\n\n4. **Ambiguous Scope**\n   - Unclear boundaries (\"user management\" - what exactly?)\n   - No distinction between MVP and future enhancements\n   - Missing \"what's NOT included\"\n\n**Do NOT activate when**:\n- Specific file paths mentioned (e.g., \"auth.go:45\")\n- Code snippets included\n- Existing functions\u002Fclasses referenced\n- Bug fixes with clear reproduction steps\n\n## Core Principles\n\n1. **Systematic Questioning**\n   - Ask focused, specific questions\n   - One category at a time (2-3 questions per round)\n   - Build on previous answers\n   - Avoid overwhelming users\n\n2. **Quality-Driven Iteration**\n   - Continuously assess clarity score (0-100)\n   - Identify gaps systematically\n   - Iterate until ≥ 90 points\n   - Document all clarification rounds\n\n3. **Actionable Output**\n   - Generate concrete specifications\n   - Include measurable acceptance criteria\n   - Provide executable phases\n   - Enable direct implementation\n\n## Clarification Process\n\n### Step 1: Initial Requirement Analysis\n\n**Input**: User's requirement description\n\n**Tasks**:\n1. Parse and understand core requirement\n2. Generate feature name (kebab-case format)\n3. Determine document version (default `1.0` unless user specifies otherwise)\n4. Ensure `.\u002Fdocs\u002Fprds\u002F` exists for PRD output\n5. Perform initial clarity assessment (0-100)\n\n**Assessment Rubric**:\n```\nFunctional Clarity: \u002F30 points\n- Clear inputs\u002Foutputs: 10 pts\n- User interaction defined: 10 pts\n- Success criteria stated: 10 pts\n\nTechnical Specificity: \u002F25 points\n- Technology stack mentioned: 8 pts\n- Integration points identified: 8 pts\n- Constraints specified: 9 pts\n\nImplementation Completeness: \u002F25 points\n- Edge cases considered: 8 pts\n- Error handling mentioned: 9 pts\n- Data validation specified: 8 pts\n\nBusiness Context: \u002F20 points\n- Problem statement clear: 7 pts\n- Target users identified: 7 pts\n- Success metrics defined: 6 pts\n```\n\n**Initial Response Format**:\n```markdown\nI understand your requirement. Let me help you refine this specification.\n\n**Current Clarity Score**: X\u002F100\n\n**Clear Aspects**:\n- [List what's clear]\n\n**Needs Clarification**:\n- [List gaps]\n\nLet me systematically clarify these points...\n```\n\n### Step 2: Gap Analysis\n\nIdentify missing information across four dimensions:\n\n**1. Functional Scope**\n- What is the core functionality?\n- What are the boundaries?\n- What is out of scope?\n- What are edge cases?\n\n**2. User Interaction**\n- How do users interact?\n- What are the inputs?\n- What are the outputs?\n- What are success\u002Ffailure scenarios?\n\n**3. Technical Constraints**\n- Performance requirements?\n- Compatibility requirements?\n- Security considerations?\n- Scalability needs?\n\n**4. Business Value**\n- What problem does this solve?\n- Who are the target users?\n- What are success metrics?\n- What is the priority?\n\n### Step 3: Interactive Clarification\n\n**Question Strategy**:\n1. Start with highest-impact gaps\n2. Ask 2-3 questions per round\n3. Build context progressively\n4. Use user's language\n5. Provide examples when helpful\n\n**Question Format**:\n```markdown\nI need to clarify the following points to complete the requirements document:\n\n1. **[Category]**: [Specific question]?\n   - For example: [Example if helpful]\n\n2. **[Category]**: [Specific question]?\n\n3. **[Category]**: [Specific question]?\n\nPlease provide your answers, and I'll continue refining the PRD.\n```\n\n**After Each User Response**:\n1. Update clarity score\n2. Capture new information in the working PRD outline\n3. Identify remaining gaps\n4. If score \u003C 90: Continue with next round of questions\n5. If score ≥ 90: Proceed to PRD generation\n\n**Score Update Format**:\n```markdown\nThank you for the additional information!\n\n**Clarity Score Update**: X\u002F100 → Y\u002F100\n\n**New Clarified Content**:\n- [Summarize new information]\n\n**Remaining Points to Clarify**:\n- [List remaining gaps if score \u003C 90]\n\n[If score \u003C 90: Continue with next round of questions]\n[If score ≥ 90: \"Perfect! I will now generate the complete PRD document...\"]\n```\n\n### Step 4: PRD Generation\n\nOnce clarity score ≥ 90, generate comprehensive PRD.\n\n**Output File**:\n\n1. **Final PRD**: `.\u002Fdocs\u002Fprds\u002F{feature_name}-v{version}-prd.md`\n\nUse the `Write` tool to create or update this file. Derive `{version}` from the document version recorded in the PRD (default `1.0`).\n\n## PRD Document Structure\n\n```markdown\n# {Feature Name} - Product Requirements Document (PRD)\n\n## Requirements Description\n\n### Background\n- **Business Problem**: [Describe the business problem to solve]\n- **Target Users**: [Target user groups]\n- **Value Proposition**: [Value this feature brings]\n\n### Feature Overview\n- **Core Features**: [List of main features]\n- **Feature Boundaries**: [What is and isn't included]\n- **User Scenarios**: [Typical usage scenarios]\n\n### Detailed Requirements\n- **Input\u002FOutput**: [Specific input\u002Foutput specifications]\n- **User Interaction**: [User operation flow]\n- **Data Requirements**: [Data structures and validation rules]\n- **Edge Cases**: [Edge case handling]\n\n## Design Decisions\n\n### Technical Approach\n- **Architecture Choice**: [Technical architecture decisions and rationale]\n- **Key Components**: [List of main technical components]\n- **Data Storage**: [Data models and storage solutions]\n- **Interface Design**: [API\u002Finterface specifications]\n\n### Constraints\n- **Performance Requirements**: [Response time, throughput, etc.]\n- **Compatibility**: [System compatibility requirements]\n- **Security**: [Security considerations]\n- **Scalability**: [Future expansion considerations]\n\n### Risk Assessment\n- **Technical Risks**: [Potential technical risks and mitigation plans]\n- **Dependency Risks**: [External dependencies and alternatives]\n- **Schedule Risks**: [Timeline risks and response strategies]\n\n## Acceptance Criteria\n\n### Functional Acceptance\n- [ ] Feature 1: [Specific acceptance conditions]\n- [ ] Feature 2: [Specific acceptance conditions]\n- [ ] Feature 3: [Specific acceptance conditions]\n\n### Quality Standards\n- [ ] Code Quality: [Code standards and review requirements]\n- [ ] Test Coverage: [Testing requirements and coverage]\n- [ ] Performance Metrics: [Performance test pass criteria]\n- [ ] Security Review: [Security review requirements]\n\n### User Acceptance\n- [ ] User Experience: [UX acceptance criteria]\n- [ ] Documentation: [Documentation delivery requirements]\n- [ ] Training Materials: [If needed, training material requirements]\n\n## Execution Phases\n\n### Phase 1: Preparation\n**Goal**: Environment preparation and technical validation\n- [ ] Task 1: [Specific task description]\n- [ ] Task 2: [Specific task description]\n- **Deliverables**: [Phase deliverables]\n- **Time**: [Estimated time]\n\n### Phase 2: Core Development\n**Goal**: Implement core functionality\n- [ ] Task 1: [Specific task description]\n- [ ] Task 2: [Specific task description]\n- **Deliverables**: [Phase deliverables]\n- **Time**: [Estimated time]\n\n### Phase 3: Integration & Testing\n**Goal**: Integration and quality assurance\n- [ ] Task 1: [Specific task description]\n- [ ] Task 2: [Specific task description]\n- **Deliverables**: [Phase deliverables]\n- **Time**: [Estimated time]\n\n### Phase 4: Deployment\n**Goal**: Release and monitoring\n- [ ] Task 1: [Specific task description]\n- [ ] Task 2: [Specific task description]\n- **Deliverables**: [Phase deliverables]\n- **Time**: [Estimated time]\n\n---\n\n**Document Version**: 1.0\n**Created**: {timestamp}\n**Clarification Rounds**: {clarification_rounds}\n**Quality Score**: {quality_score}\u002F100\n```\n\n## Behavioral Guidelines\n\n### DO\n- Ask specific, targeted questions\n- Build on previous answers\n- Provide examples to guide users\n- Maintain conversational tone\n- Summarize clarification rounds within the PRD\n- Use clear, professional English\n- Generate concrete specifications\n- Stay in clarification mode until score ≥ 90\n\n### DON'T\n- Ask all questions at once\n- Make assumptions without confirmation\n- Generate PRD before 90+ score\n- Skip any required sections\n- Use vague or abstract language\n- Proceed without user responses\n- Exit skill mode prematurely\n\n## Success Criteria\n\n- Clarity score ≥ 90\u002F100\n- All PRD sections complete with substance\n- Acceptance criteria checklistable (using `- [ ]` format)\n- Execution phases actionable with concrete tasks\n- User approves final PRD\n- Ready for development handoff\n",{"name":5,"description":7},"main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-AI-应用工具\u002FYYC3-AI-应用工具-claude-code-templates-main\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Frequirements-clarity",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":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill requirements-clarity",{"tool":39,"command":40},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill requirements-clarity",{"tool":42,"command":43},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill requirements-clarity","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-应用工具\u002FYYC3-AI-应用工具-claude-code-templates-main\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Frequirements-clarity\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"README.md","REFERENCE","参考文档",9297,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-应用工具\u002FYYC3-AI-应用工具-claude-code-templates-main\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Frequirements-clarity\u002FREADME.md",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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",[],[]]