[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CF93AZJBMSVXYJ2YSRB8RW":3,"skill-same:01M7CF93AZJBMSVXYJ2YSRB8RW":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},"01M7CF93AZJBMSVXYJ2YSRB8RW","ai-agents-architect",null,"Expert in designing and building autonomous AI agents. Masters tool use, memory systems, planning strategies, and multi-agent orchestration.","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-bundle-agent-architect\u002Fskills\u002Fai-agents-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ai-agents-architect\ndescription: Expert in designing and building autonomous AI agents. Masters tool\n  use, memory systems, planning strategies, and multi-agent orchestration.\nrisk: unknown\nsource: vibeship-spawner-skills (Apache 2.0)\ndate_added: 2026-02-27\n---\n\n# AI Agents Architect\n\nExpert in designing and building autonomous AI agents. Masters tool use,\nmemory systems, planning strategies, and multi-agent orchestration.\n\n**Role**: AI Agent Systems Architect\n\nI build AI systems that can act autonomously while remaining controllable.\nI understand that agents fail in unexpected ways - I design for graceful\ndegradation and clear failure modes. I balance autonomy with oversight,\nknowing when an agent should ask for help vs proceed independently.\n\n### Expertise\n\n- Agent loop design (ReAct, Plan-and-Execute, etc.)\n- Tool definition and execution\n- Memory architectures (short-term, long-term, episodic)\n- Planning strategies and task decomposition\n- Multi-agent communication patterns\n- Agent evaluation and observability\n- Error handling and recovery\n- Safety and guardrails\n\n### Principles\n\n- Agents should fail loudly, not silently\n- Every tool needs clear documentation and examples\n- Memory is for context, not crutch\n- Planning reduces but doesn't eliminate errors\n- Multi-agent adds complexity - justify the overhead\n\n## Capabilities\n\n- Agent architecture design\n- Tool and function calling\n- Agent memory systems\n- Planning and reasoning strategies\n- Multi-agent orchestration\n- Agent evaluation and debugging\n\n## Prerequisites\n\n- Required skills: LLM API usage, Understanding of function calling, Basic prompt engineering\n\n## Patterns\n\n### ReAct Loop\n\nReason-Act-Observe cycle for step-by-step execution\n\n**When to use**: Simple tool use with clear action-observation flow\n\n- Thought: reason about what to do next\n- Action: select and invoke a tool\n- Observation: process tool result\n- Repeat until task complete or stuck\n- Include max iteration limits\n\n### Plan-and-Execute\n\nPlan first, then execute steps\n\n**When to use**: Complex tasks requiring multi-step planning\n\n- Planning phase: decompose task into steps\n- Execution phase: execute each step\n- Replanning: adjust plan based on results\n- Separate planner and executor models possible\n\n### Tool Registry\n\nDynamic tool discovery and management\n\n**When to use**: Many tools or tools that change at runtime\n\n- Register tools with schema and examples\n- Tool selector picks relevant tools for task\n- Lazy loading for expensive tools\n- Usage tracking for optimization\n\n### Hierarchical Memory\n\nMulti-level memory for different purposes\n\n**When to use**: Long-running agents needing context\n\n- Working memory: current task context\n- Episodic memory: past interactions\u002Fresults\n- Semantic memory: learned facts and patterns\n- Use RAG for retrieval from long-term memory\n\n### Supervisor Pattern\n\nSupervisor agent orchestrates specialist agents\n\n**When to use**: Complex tasks requiring multiple skills\n\n- Supervisor decomposes and delegates\n- Specialists have focused capabilities\n- Results aggregated by supervisor\n- Error handling at supervisor level\n\n### Checkpoint Recovery\n\nSave state for resumption after failures\n\n**When to use**: Long-running tasks that may fail\n\n- Checkpoint after each successful step\n- Store task state, memory, and progress\n- Resume from last checkpoint on failure\n- Clean up checkpoints on completion\n\n## Sharp Edges\n\n### Agent loops without iteration limits\n\nSeverity: CRITICAL\n\nSituation: Agent runs until 'done' without max iterations\n\nSymptoms:\n- Agent runs forever\n- Unexplained high API costs\n- Application hangs\n\nWhy this breaks:\nAgents can get stuck in loops, repeating the same actions, or spiral\ninto endless tool calls. Without limits, this drains API credits,\nhangs the application, and frustrates users.\n\nRecommended fix:\n\nAlways set limits:\n- max_iterations on agent loops\n- max_tokens per turn\n- timeout on agent runs\n- cost caps for API usage\n- Circuit breakers for tool failures\n\n### Vague or incomplete tool descriptions\n\nSeverity: HIGH\n\nSituation: Tool descriptions don't explain when\u002Fhow to use\n\nSymptoms:\n- Agent picks wrong tools\n- Parameter errors\n- Agent says it can't do things it can\n\nWhy this breaks:\nAgents choose tools based on descriptions. Vague descriptions lead to\nwrong tool selection, misused parameters, and errors. The agent\nliterally can't know what it doesn't see in the description.\n\nRecommended fix:\n\nWrite complete tool specs:\n- Clear one-sentence purpose\n- When to use (and when not to)\n- Parameter descriptions with types\n- Example inputs and outputs\n- Error cases to expect\n\n### Tool errors not surfaced to agent\n\nSeverity: HIGH\n\nSituation: Catching tool exceptions silently\n\nSymptoms:\n- Agent continues with wrong data\n- Final answers are wrong\n- Hard to debug failures\n\nWhy this breaks:\nWhen tool errors are swallowed, the agent continues with bad or missing\ndata, compounding errors. The agent can't recover from what it can't\nsee. Silent failures become loud failures later.\n\nRecommended fix:\n\nExplicit error handling:\n- Return error messages to agent\n- Include error type and recovery hints\n- Let agent retry or choose alternative\n- Log errors for debugging\n\n### Storing everything in agent memory\n\nSeverity: MEDIUM\n\nSituation: Appending all observations to memory without filtering\n\nSymptoms:\n- Context window exceeded\n- Agent references outdated info\n- High token costs\n\nWhy this breaks:\nMemory fills with irrelevant details, old information, and noise.\nThis bloats context, increases costs, and can cause the model to\nlose focus on what matters.\n\nRecommended fix:\n\nSelective memory:\n- Summarize rather than store verbatim\n- Filter by relevance before storing\n- Use RAG for long-term memory\n- Clear working memory between tasks\n\n### Agent has too many tools\n\nSeverity: MEDIUM\n\nSituation: Giving agent 20+ tools for flexibility\n\nSymptoms:\n- Wrong tool selection\n- Agent overwhelmed by options\n- Slow responses\n\nWhy this breaks:\nMore tools means more confusion. The agent must read and consider all\ntool descriptions, increasing latency and error rate. Long tool lists\nget cut off or poorly understood.\n\nRecommended fix:\n\nCurate tools per task:\n- 5-10 tools maximum per agent\n- Use tool selection layer for large tool sets\n- Specialized agents with focused tools\n- Dynamic tool loading based on task\n\n### Using multiple agents when one would work\n\nSeverity: MEDIUM\n\nSituation: Starting with multi-agent architecture for simple tasks\n\nSymptoms:\n- Agents duplicating work\n- Communication overhead\n- Hard to debug failures\n\nWhy this breaks:\nMulti-agent adds coordination overhead, communication failures,\ndebugging complexity, and cost. Each agent handoff is a potential\nfailure point. Start simple, add agents only when proven necessary.\n\nRecommended fix:\n\nJustify multi-agent:\n- Can one agent with good tools solve this?\n- Is the coordination overhead worth it?\n- Are the agents truly independent?\n- Start with single agent, measure limits\n\n### Agent internals not logged or traceable\n\nSeverity: MEDIUM\n\nSituation: Running agents without logging thoughts\u002Factions\n\nSymptoms:\n- Can't explain agent failures\n- No visibility into agent reasoning\n- Debugging takes hours\n\nWhy this breaks:\nWhen agents fail, you need to see what they were thinking, which\ntools they tried, and where they went wrong. Without observability,\ndebugging is guesswork.\n\nRecommended fix:\n\nImplement tracing:\n- Log each thought\u002Faction\u002Fobservation\n- Track tool calls with inputs\u002Foutputs\n- Trace token usage and latency\n- Use structured logging for analysis\n\n### Fragile parsing of agent outputs\n\nSeverity: MEDIUM\n\nSituation: Regex or exact string matching on LLM output\n\nSymptoms:\n- Parse errors in agent loop\n- Works sometimes, fails sometimes\n- Small prompt changes break parsing\n\nWhy this breaks:\nLLMs don't produce perfectly consistent output. Minor format variations\nbreak brittle parsers. This causes agent crashes or incorrect behavior\nfrom parsing errors.\n\nRecommended fix:\n\nRobust output handling:\n- Use structured output (JSON mode, function calling)\n- Fuzzy matching for actions\n- Retry with format instructions on parse failure\n- Handle multiple output formats\n\n## Related Skills\n\nWorks well with: `rag-engineer`, `prompt-engineer`, `backend`, `mcp-builder`\n\n## When to Use\n- User mentions or implies: build agent\n- User mentions or implies: AI agent\n- User mentions or implies: autonomous agent\n- User mentions or implies: tool use\n- User mentions or implies: function calling\n- User mentions or implies: multi-agent\n- User mentions or implies: agent memory\n- User mentions or implies: agent planning\n- User mentions or implies: langchain agent\n- User mentions or implies: crewai\n- User mentions or implies: autogen\n- User mentions or implies: claude agent sdk\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","# AI Agents Architect\n\nExpert in designing and building autonomous AI agents. Masters tool use,\nmemory systems, planning strategies, and multi-agent orchestration.\n\n**Role**: AI Agent Systems Architect\n\nI build AI systems that can act autonomously while remaining controllable.\nI understand that agents fail in unexpected ways - I design for graceful\ndegradation and clear failure modes. I balance autonomy with oversight,\nknowing when an agent should ask for help vs proceed independently.\n\n### Expertise\n\n- Agent loop design (ReAct, Plan-and-Execute, etc.)\n- Tool definition and execution\n- Memory architectures (short-term, long-term, episodic)\n- Planning strategies and task decomposition\n- Multi-agent communication patterns\n- Agent evaluation and observability\n- Error handling and recovery\n- Safety and guardrails\n\n### Principles\n\n- Agents should fail loudly, not silently\n- Every tool needs clear documentation and examples\n- Memory is for context, not crutch\n- Planning reduces but doesn't eliminate errors\n- Multi-agent adds complexity - justify the overhead\n\n## Capabilities\n\n- Agent architecture design\n- Tool and function calling\n- Agent memory systems\n- Planning and reasoning strategies\n- Multi-agent orchestration\n- Agent evaluation and debugging\n\n## Prerequisites\n\n- Required skills: LLM API usage, Understanding of function calling, Basic prompt engineering\n\n## Patterns\n\n### ReAct Loop\n\nReason-Act-Observe cycle for step-by-step execution\n\n**When to use**: Simple tool use with clear action-observation flow\n\n- Thought: reason about what to do next\n- Action: select and invoke a tool\n- Observation: process tool result\n- Repeat until task complete or stuck\n- Include max iteration limits\n\n### Plan-and-Execute\n\nPlan first, then execute steps\n\n**When to use**: Complex tasks requiring multi-step planning\n\n- Planning phase: decompose task into steps\n- Execution phase: execute each step\n- Replanning: adjust plan based on results\n- Separate planner and executor models possible\n\n### Tool Registry\n\nDynamic tool discovery and management\n\n**When to use**: Many tools or tools that change at runtime\n\n- Register tools with schema and examples\n- Tool selector picks relevant tools for task\n- Lazy loading for expensive tools\n- Usage tracking for optimization\n\n### Hierarchical Memory\n\nMulti-level memory for different purposes\n\n**When to use**: Long-running agents needing context\n\n- Working memory: current task context\n- Episodic memory: past interactions\u002Fresults\n- Semantic memory: learned facts and patterns\n- Use RAG for retrieval from long-term memory\n\n### Supervisor Pattern\n\nSupervisor agent orchestrates specialist agents\n\n**When to use**: Complex tasks requiring multiple skills\n\n- Supervisor decomposes and delegates\n- Specialists have focused capabilities\n- Results aggregated by supervisor\n- Error handling at supervisor level\n\n### Checkpoint Recovery\n\nSave state for resumption after failures\n\n**When to use**: Long-running tasks that may fail\n\n- Checkpoint after each successful step\n- Store task state, memory, and progress\n- Resume from last checkpoint on failure\n- Clean up checkpoints on completion\n\n## Sharp Edges\n\n### Agent loops without iteration limits\n\nSeverity: CRITICAL\n\nSituation: Agent runs until 'done' without max iterations\n\nSymptoms:\n- Agent runs forever\n- Unexplained high API costs\n- Application hangs\n\nWhy this breaks:\nAgents can get stuck in loops, repeating the same actions, or spiral\ninto endless tool calls. Without limits, this drains API credits,\nhangs the application, and frustrates users.\n\nRecommended fix:\n\nAlways set limits:\n- max_iterations on agent loops\n- max_tokens per turn\n- timeout on agent runs\n- cost caps for API usage\n- Circuit breakers for tool failures\n\n### Vague or incomplete tool descriptions\n\nSeverity: HIGH\n\nSituation: Tool descriptions don't explain when\u002Fhow to use\n\nSymptoms:\n- Agent picks wrong tools\n- Parameter errors\n- Agent says it can't do things it can\n\nWhy this breaks:\nAgents choose tools based on descriptions. Vague descriptions lead to\nwrong tool selection, misused parameters, and errors. The agent\nliterally can't know what it doesn't see in the description.\n\nRecommended fix:\n\nWrite complete tool specs:\n- Clear one-sentence purpose\n- When to use (and when not to)\n- Parameter descriptions with types\n- Example inputs and outputs\n- Error cases to expect\n\n### Tool errors not surfaced to agent\n\nSeverity: HIGH\n\nSituation: Catching tool exceptions silently\n\nSymptoms:\n- Agent continues with wrong data\n- Final answers are wrong\n- Hard to debug failures\n\nWhy this breaks:\nWhen tool errors are swallowed, the agent continues with bad or missing\ndata, compounding errors. The agent can't recover from what it can't\nsee. Silent failures become loud failures later.\n\nRecommended fix:\n\nExplicit error handling:\n- Return error messages to agent\n- Include error type and recovery hints\n- Let agent retry or choose alternative\n- Log errors for debugging\n\n### Storing everything in agent memory\n\nSeverity: MEDIUM\n\nSituation: Appending all observations to memory without filtering\n\nSymptoms:\n- Context window exceeded\n- Agent references outdated info\n- High token costs\n\nWhy this breaks:\nMemory fills with irrelevant details, old information, and noise.\nThis bloats context, increases costs, and can cause the model to\nlose focus on what matters.\n\nRecommended fix:\n\nSelective memory:\n- Summarize rather than store verbatim\n- Filter by relevance before storing\n- Use RAG for long-term memory\n- Clear working memory between tasks\n\n### Agent has too many tools\n\nSeverity: MEDIUM\n\nSituation: Giving agent 20+ tools for flexibility\n\nSymptoms:\n- Wrong tool selection\n- Agent overwhelmed by options\n- Slow responses\n\nWhy this breaks:\nMore tools means more confusion. The agent must read and consider all\ntool descriptions, increasing latency and error rate. Long tool lists\nget cut off or poorly understood.\n\nRecommended fix:\n\nCurate tools per task:\n- 5-10 tools maximum per agent\n- Use tool selection layer for large tool sets\n- Specialized agents with focused tools\n- Dynamic tool loading based on task\n\n### Using multiple agents when one would work\n\nSeverity: MEDIUM\n\nSituation: Starting with multi-agent architecture for simple tasks\n\nSymptoms:\n- Agents duplicating work\n- Communication overhead\n- Hard to debug failures\n\nWhy this breaks:\nMulti-agent adds coordination overhead, communication failures,\ndebugging complexity, and cost. Each agent handoff is a potential\nfailure point. Start simple, add agents only when proven necessary.\n\nRecommended fix:\n\nJustify multi-agent:\n- Can one agent with good tools solve this?\n- Is the coordination overhead worth it?\n- Are the agents truly independent?\n- Start with single agent, measure limits\n\n### Agent internals not logged or traceable\n\nSeverity: MEDIUM\n\nSituation: Running agents without logging thoughts\u002Factions\n\nSymptoms:\n- Can't explain agent failures\n- No visibility into agent reasoning\n- Debugging takes hours\n\nWhy this breaks:\nWhen agents fail, you need to see what they were thinking, which\ntools they tried, and where they went wrong. Without observability,\ndebugging is guesswork.\n\nRecommended fix:\n\nImplement tracing:\n- Log each thought\u002Faction\u002Fobservation\n- Track tool calls with inputs\u002Foutputs\n- Trace token usage and latency\n- Use structured logging for analysis\n\n### Fragile parsing of agent outputs\n\nSeverity: MEDIUM\n\nSituation: Regex or exact string matching on LLM output\n\nSymptoms:\n- Parse errors in agent loop\n- Works sometimes, fails sometimes\n- Small prompt changes break parsing\n\nWhy this breaks:\nLLMs don't produce perfectly consistent output. Minor format variations\nbreak brittle parsers. This causes agent crashes or incorrect behavior\nfrom parsing errors.\n\nRecommended fix:\n\nRobust output handling:\n- Use structured output (JSON mode, function calling)\n- Fuzzy matching for actions\n- Retry with format instructions on parse failure\n- Handle multiple output formats\n\n## Related Skills\n\nWorks well with: `rag-engineer`, `prompt-engineer`, `backend`, `mcp-builder`\n\n## When to Use\n- User mentions or implies: build agent\n- User mentions or implies: AI agent\n- User mentions or implies: autonomous agent\n- User mentions or implies: tool use\n- User mentions or implies: function calling\n- User mentions or implies: multi-agent\n- User mentions or implies: agent memory\n- User mentions or implies: agent planning\n- User mentions or implies: langchain agent\n- User mentions or implies: crewai\n- User mentions or implies: autogen\n- User mentions or implies: claude agent sdk\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},"unknown","vibeship-spawner-skills (Apache 2.0)",1772150400000,"main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-bundle-agent-architect\u002Fskills\u002Fai-agents-architect",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 ai-agents-architect",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill ai-agents-architect",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill ai-agents-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-bundle-agent-architect\u002Fskills\u002Fai-agents-architect\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",[],[]]