[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CCX2FRG26WWJJSPVHAS753":3,"skill-same:01M7CCX2FRG26WWJJSPVHAS753":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},"01M7CCX2FRG26WWJJSPVHAS753","rag-engineer",null,"Expert in building Retrieval-Augmented Generation systems. Masters embedding models, vector databases, chunking strategies, and retrieval optimization for LLM applications.","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\u002Frag-engineer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: rag-engineer\ndescription: Expert in building Retrieval-Augmented Generation systems. Masters\n  embedding models, vector databases, chunking strategies, and retrieval\n  optimization for LLM applications.\nrisk: unknown\nsource: vibeship-spawner-skills (Apache 2.0)\ndate_added: 2026-02-27\n---\n\n# RAG Engineer\n\nExpert in building Retrieval-Augmented Generation systems. Masters embedding models,\nvector databases, chunking strategies, and retrieval optimization for LLM applications.\n\n**Role**: RAG Systems Architect\n\nI bridge the gap between raw documents and LLM understanding. I know that\nretrieval quality determines generation quality - garbage in, garbage out.\nI obsess over chunking boundaries, embedding dimensions, and similarity\nmetrics because they make the difference between helpful and hallucinating.\n\n### Expertise\n\n- Embedding model selection and fine-tuning\n- Vector database architecture and scaling\n- Chunking strategies for different content types\n- Retrieval quality optimization\n- Hybrid search implementation\n- Re-ranking and filtering strategies\n- Context window management\n- Evaluation metrics for retrieval\n\n### Principles\n\n- Retrieval quality > Generation quality - fix retrieval first\n- Chunk size depends on content type and query patterns\n- Embeddings are not magic - they have blind spots\n- Always evaluate retrieval separately from generation\n- Hybrid search beats pure semantic in most cases\n\n## Capabilities\n\n- Vector embeddings and similarity search\n- Document chunking and preprocessing\n- Retrieval pipeline design\n- Semantic search implementation\n- Context window optimization\n- Hybrid search (keyword + semantic)\n\n## Prerequisites\n\n- Required skills: LLM fundamentals, Understanding of embeddings, Basic NLP concepts\n\n## Patterns\n\n### Semantic Chunking\n\nChunk by meaning, not arbitrary token counts\n\n**When to use**: Processing documents with natural sections\n\n- Use sentence boundaries, not token limits\n- Detect topic shifts with embedding similarity\n- Preserve document structure (headers, paragraphs)\n- Include overlap for context continuity\n- Add metadata for filtering\n\n### Hierarchical Retrieval\n\nMulti-level retrieval for better precision\n\n**When to use**: Large document collections with varied granularity\n\n- Index at multiple chunk sizes (paragraph, section, document)\n- First pass: coarse retrieval for candidates\n- Second pass: fine-grained retrieval for precision\n- Use parent-child relationships for context\n\n### Hybrid Search\n\nCombine semantic and keyword search\n\n**When to use**: Queries may be keyword-heavy or semantic\n\n- BM25\u002FTF-IDF for keyword matching\n- Vector similarity for semantic matching\n- Reciprocal Rank Fusion for combining scores\n- Weight tuning based on query type\n\n### Query Expansion\n\nExpand queries to improve recall\n\n**When to use**: User queries are short or ambiguous\n\n- Use LLM to generate query variations\n- Add synonyms and related terms\n- Hypothetical Document Embedding (HyDE)\n- Multi-query retrieval with deduplication\n\n### Contextual Compression\n\nCompress retrieved context to fit window\n\n**When to use**: Retrieved chunks exceed context limits\n\n- Extract relevant sentences only\n- Use LLM to summarize chunks\n- Remove redundant information\n- Prioritize by relevance score\n\n### Metadata Filtering\n\nPre-filter by metadata before semantic search\n\n**When to use**: Documents have structured metadata\n\n- Filter by date, source, category first\n- Reduce search space before vector similarity\n- Combine metadata filters with semantic scores\n- Index metadata for fast filtering\n\n## Sharp Edges\n\n### Fixed-size chunking breaks sentences and context\n\nSeverity: HIGH\n\nSituation: Using fixed token\u002Fcharacter limits for chunking\n\nSymptoms:\n- Retrieved chunks feel incomplete or cut off\n- Answer quality varies wildly\n- High recall but low precision\n\nWhy this breaks:\nFixed-size chunks split mid-sentence, mid-paragraph, or mid-idea.\nThe resulting embeddings represent incomplete thoughts, leading to\npoor retrieval quality. Users search for concepts but get fragments.\n\nRecommended fix:\n\nUse semantic chunking that respects document structure:\n- Split on sentence\u002Fparagraph boundaries\n- Use embedding similarity to detect topic shifts\n- Include overlap for context continuity\n- Preserve headers and document structure as metadata\n\n### Pure semantic search without metadata pre-filtering\n\nSeverity: MEDIUM\n\nSituation: Only using vector similarity, ignoring metadata\n\nSymptoms:\n- Returns outdated information\n- Mixes content from wrong sources\n- Users can't scope their searches\n\nWhy this breaks:\nSemantic search finds semantically similar content, but not necessarily\nrelevant content. Without metadata filtering, you return old docs when\nuser wants recent, wrong categories, or inapplicable content.\n\nRecommended fix:\n\nImplement hybrid filtering:\n- Pre-filter by metadata (date, source, category) before vector search\n- Post-filter results by relevance criteria\n- Include metadata in the retrieval API\n- Allow users to specify filters\n\n### Using same embedding model for different content types\n\nSeverity: MEDIUM\n\nSituation: One embedding model for code, docs, and structured data\n\nSymptoms:\n- Code search returns irrelevant results\n- Domain terms not matched properly\n- Similar concepts not clustered\n\nWhy this breaks:\nEmbedding models are trained on specific content types. Using a text\nembedding model for code, or a general model for domain-specific\ncontent, produces poor similarity matches.\n\nRecommended fix:\n\nEvaluate embeddings per content type:\n- Use code-specific embeddings for code (e.g., CodeBERT)\n- Consider domain-specific or fine-tuned embeddings\n- Benchmark retrieval quality before choosing\n- Separate indices for different content types if needed\n\n### Using first-stage retrieval results directly\n\nSeverity: MEDIUM\n\nSituation: Taking top-K from vector search without reranking\n\nSymptoms:\n- Clearly relevant docs not in top results\n- Results order seems arbitrary\n- Adding more results helps quality\n\nWhy this breaks:\nFirst-stage retrieval (vector search) optimizes for recall, not precision.\nThe top results by embedding similarity may not be the most relevant\nfor the specific query. Cross-encoder reranking dramatically improves\nprecision for the final results.\n\nRecommended fix:\n\nAdd reranking step:\n- Retrieve larger candidate set (e.g., top 20-50)\n- Rerank with cross-encoder (query-document pairs)\n- Return reranked top-K (e.g., top 5)\n- Cache reranker for performance\n\n### Cramming maximum context into LLM prompt\n\nSeverity: MEDIUM\n\nSituation: Using all retrieved context regardless of relevance\n\nSymptoms:\n- Answers drift with more context\n- LLM ignores key information\n- High token costs\n\nWhy this breaks:\nMore context isn't always better. Irrelevant context confuses the LLM,\nincreases latency and cost, and can cause the model to ignore the\nmost relevant information. Models have attention limits.\n\nRecommended fix:\n\nUse relevance thresholds:\n- Set minimum similarity score cutoff\n- Limit context to truly relevant chunks\n- Summarize or compress if needed\n- Order context by relevance\n\n### Not measuring retrieval quality separately from generation\n\nSeverity: HIGH\n\nSituation: Only evaluating end-to-end RAG quality\n\nSymptoms:\n- Can't diagnose poor RAG performance\n- Prompt changes don't help\n- Random quality variations\n\nWhy this breaks:\nIf answers are wrong, you can't tell if retrieval failed or generation\nfailed. This makes debugging impossible and leads to wrong fixes\n(tuning prompts when retrieval is the problem).\n\nRecommended fix:\n\nSeparate retrieval evaluation:\n- Create retrieval test set with relevant docs labeled\n- Measure MRR, NDCG, Recall@K for retrieval\n- Evaluate generation only on correct retrievals\n- Track metrics over time\n\n### Not updating embeddings when source documents change\n\nSeverity: MEDIUM\n\nSituation: Embeddings generated once, never refreshed\n\nSymptoms:\n- Returns outdated information\n- References deleted content\n- Inconsistent with source\n\nWhy this breaks:\nDocuments change but embeddings don't. Users retrieve outdated content\nor, worse, content that no longer exists. This erodes trust in the\nsystem.\n\nRecommended fix:\n\nImplement embedding refresh:\n- Track document versions\u002Fhashes\n- Re-embed on document change\n- Handle deleted documents\n- Consider TTL for embeddings\n\n### Same retrieval strategy for all query types\n\nSeverity: MEDIUM\n\nSituation: Using pure semantic search for keyword-heavy queries\n\nSymptoms:\n- Exact term searches miss results\n- Concept searches too literal\n- Users frustrated with both\n\nWhy this breaks:\nSome queries are keyword-oriented (looking for specific terms) while\nothers are semantic (looking for concepts). Pure semantic search fails\non exact matches; pure keyword search fails on paraphrases.\n\nRecommended fix:\n\nImplement hybrid search:\n- BM25\u002FTF-IDF for keyword matching\n- Vector similarity for semantic matching\n- Reciprocal Rank Fusion to combine\n- Tune weights based on query patterns\n\n## Related Skills\n\nWorks well with: `ai-agents-architect`, `prompt-engineer`, `database-architect`, `backend`\n\n## When to Use\n- User mentions or implies: building RAG\n- User mentions or implies: vector search\n- User mentions or implies: embeddings\n- User mentions or implies: semantic search\n- User mentions or implies: document retrieval\n- User mentions or implies: context retrieval\n- User mentions or implies: knowledge base\n- User mentions or implies: LLM with documents\n- User mentions or implies: chunking strategy\n- User mentions or implies: pinecone\n- User mentions or implies: weaviate\n- User mentions or implies: chromadb\n- User mentions or implies: pgvector\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","# RAG Engineer\n\nExpert in building Retrieval-Augmented Generation systems. Masters embedding models,\nvector databases, chunking strategies, and retrieval optimization for LLM applications.\n\n**Role**: RAG Systems Architect\n\nI bridge the gap between raw documents and LLM understanding. I know that\nretrieval quality determines generation quality - garbage in, garbage out.\nI obsess over chunking boundaries, embedding dimensions, and similarity\nmetrics because they make the difference between helpful and hallucinating.\n\n### Expertise\n\n- Embedding model selection and fine-tuning\n- Vector database architecture and scaling\n- Chunking strategies for different content types\n- Retrieval quality optimization\n- Hybrid search implementation\n- Re-ranking and filtering strategies\n- Context window management\n- Evaluation metrics for retrieval\n\n### Principles\n\n- Retrieval quality > Generation quality - fix retrieval first\n- Chunk size depends on content type and query patterns\n- Embeddings are not magic - they have blind spots\n- Always evaluate retrieval separately from generation\n- Hybrid search beats pure semantic in most cases\n\n## Capabilities\n\n- Vector embeddings and similarity search\n- Document chunking and preprocessing\n- Retrieval pipeline design\n- Semantic search implementation\n- Context window optimization\n- Hybrid search (keyword + semantic)\n\n## Prerequisites\n\n- Required skills: LLM fundamentals, Understanding of embeddings, Basic NLP concepts\n\n## Patterns\n\n### Semantic Chunking\n\nChunk by meaning, not arbitrary token counts\n\n**When to use**: Processing documents with natural sections\n\n- Use sentence boundaries, not token limits\n- Detect topic shifts with embedding similarity\n- Preserve document structure (headers, paragraphs)\n- Include overlap for context continuity\n- Add metadata for filtering\n\n### Hierarchical Retrieval\n\nMulti-level retrieval for better precision\n\n**When to use**: Large document collections with varied granularity\n\n- Index at multiple chunk sizes (paragraph, section, document)\n- First pass: coarse retrieval for candidates\n- Second pass: fine-grained retrieval for precision\n- Use parent-child relationships for context\n\n### Hybrid Search\n\nCombine semantic and keyword search\n\n**When to use**: Queries may be keyword-heavy or semantic\n\n- BM25\u002FTF-IDF for keyword matching\n- Vector similarity for semantic matching\n- Reciprocal Rank Fusion for combining scores\n- Weight tuning based on query type\n\n### Query Expansion\n\nExpand queries to improve recall\n\n**When to use**: User queries are short or ambiguous\n\n- Use LLM to generate query variations\n- Add synonyms and related terms\n- Hypothetical Document Embedding (HyDE)\n- Multi-query retrieval with deduplication\n\n### Contextual Compression\n\nCompress retrieved context to fit window\n\n**When to use**: Retrieved chunks exceed context limits\n\n- Extract relevant sentences only\n- Use LLM to summarize chunks\n- Remove redundant information\n- Prioritize by relevance score\n\n### Metadata Filtering\n\nPre-filter by metadata before semantic search\n\n**When to use**: Documents have structured metadata\n\n- Filter by date, source, category first\n- Reduce search space before vector similarity\n- Combine metadata filters with semantic scores\n- Index metadata for fast filtering\n\n## Sharp Edges\n\n### Fixed-size chunking breaks sentences and context\n\nSeverity: HIGH\n\nSituation: Using fixed token\u002Fcharacter limits for chunking\n\nSymptoms:\n- Retrieved chunks feel incomplete or cut off\n- Answer quality varies wildly\n- High recall but low precision\n\nWhy this breaks:\nFixed-size chunks split mid-sentence, mid-paragraph, or mid-idea.\nThe resulting embeddings represent incomplete thoughts, leading to\npoor retrieval quality. Users search for concepts but get fragments.\n\nRecommended fix:\n\nUse semantic chunking that respects document structure:\n- Split on sentence\u002Fparagraph boundaries\n- Use embedding similarity to detect topic shifts\n- Include overlap for context continuity\n- Preserve headers and document structure as metadata\n\n### Pure semantic search without metadata pre-filtering\n\nSeverity: MEDIUM\n\nSituation: Only using vector similarity, ignoring metadata\n\nSymptoms:\n- Returns outdated information\n- Mixes content from wrong sources\n- Users can't scope their searches\n\nWhy this breaks:\nSemantic search finds semantically similar content, but not necessarily\nrelevant content. Without metadata filtering, you return old docs when\nuser wants recent, wrong categories, or inapplicable content.\n\nRecommended fix:\n\nImplement hybrid filtering:\n- Pre-filter by metadata (date, source, category) before vector search\n- Post-filter results by relevance criteria\n- Include metadata in the retrieval API\n- Allow users to specify filters\n\n### Using same embedding model for different content types\n\nSeverity: MEDIUM\n\nSituation: One embedding model for code, docs, and structured data\n\nSymptoms:\n- Code search returns irrelevant results\n- Domain terms not matched properly\n- Similar concepts not clustered\n\nWhy this breaks:\nEmbedding models are trained on specific content types. Using a text\nembedding model for code, or a general model for domain-specific\ncontent, produces poor similarity matches.\n\nRecommended fix:\n\nEvaluate embeddings per content type:\n- Use code-specific embeddings for code (e.g., CodeBERT)\n- Consider domain-specific or fine-tuned embeddings\n- Benchmark retrieval quality before choosing\n- Separate indices for different content types if needed\n\n### Using first-stage retrieval results directly\n\nSeverity: MEDIUM\n\nSituation: Taking top-K from vector search without reranking\n\nSymptoms:\n- Clearly relevant docs not in top results\n- Results order seems arbitrary\n- Adding more results helps quality\n\nWhy this breaks:\nFirst-stage retrieval (vector search) optimizes for recall, not precision.\nThe top results by embedding similarity may not be the most relevant\nfor the specific query. Cross-encoder reranking dramatically improves\nprecision for the final results.\n\nRecommended fix:\n\nAdd reranking step:\n- Retrieve larger candidate set (e.g., top 20-50)\n- Rerank with cross-encoder (query-document pairs)\n- Return reranked top-K (e.g., top 5)\n- Cache reranker for performance\n\n### Cramming maximum context into LLM prompt\n\nSeverity: MEDIUM\n\nSituation: Using all retrieved context regardless of relevance\n\nSymptoms:\n- Answers drift with more context\n- LLM ignores key information\n- High token costs\n\nWhy this breaks:\nMore context isn't always better. Irrelevant context confuses the LLM,\nincreases latency and cost, and can cause the model to ignore the\nmost relevant information. Models have attention limits.\n\nRecommended fix:\n\nUse relevance thresholds:\n- Set minimum similarity score cutoff\n- Limit context to truly relevant chunks\n- Summarize or compress if needed\n- Order context by relevance\n\n### Not measuring retrieval quality separately from generation\n\nSeverity: HIGH\n\nSituation: Only evaluating end-to-end RAG quality\n\nSymptoms:\n- Can't diagnose poor RAG performance\n- Prompt changes don't help\n- Random quality variations\n\nWhy this breaks:\nIf answers are wrong, you can't tell if retrieval failed or generation\nfailed. This makes debugging impossible and leads to wrong fixes\n(tuning prompts when retrieval is the problem).\n\nRecommended fix:\n\nSeparate retrieval evaluation:\n- Create retrieval test set with relevant docs labeled\n- Measure MRR, NDCG, Recall@K for retrieval\n- Evaluate generation only on correct retrievals\n- Track metrics over time\n\n### Not updating embeddings when source documents change\n\nSeverity: MEDIUM\n\nSituation: Embeddings generated once, never refreshed\n\nSymptoms:\n- Returns outdated information\n- References deleted content\n- Inconsistent with source\n\nWhy this breaks:\nDocuments change but embeddings don't. Users retrieve outdated content\nor, worse, content that no longer exists. This erodes trust in the\nsystem.\n\nRecommended fix:\n\nImplement embedding refresh:\n- Track document versions\u002Fhashes\n- Re-embed on document change\n- Handle deleted documents\n- Consider TTL for embeddings\n\n### Same retrieval strategy for all query types\n\nSeverity: MEDIUM\n\nSituation: Using pure semantic search for keyword-heavy queries\n\nSymptoms:\n- Exact term searches miss results\n- Concept searches too literal\n- Users frustrated with both\n\nWhy this breaks:\nSome queries are keyword-oriented (looking for specific terms) while\nothers are semantic (looking for concepts). Pure semantic search fails\non exact matches; pure keyword search fails on paraphrases.\n\nRecommended fix:\n\nImplement hybrid search:\n- BM25\u002FTF-IDF for keyword matching\n- Vector similarity for semantic matching\n- Reciprocal Rank Fusion to combine\n- Tune weights based on query patterns\n\n## Related Skills\n\nWorks well with: `ai-agents-architect`, `prompt-engineer`, `database-architect`, `backend`\n\n## When to Use\n- User mentions or implies: building RAG\n- User mentions or implies: vector search\n- User mentions or implies: embeddings\n- User mentions or implies: semantic search\n- User mentions or implies: document retrieval\n- User mentions or implies: context retrieval\n- User mentions or implies: knowledge base\n- User mentions or implies: LLM with documents\n- User mentions or implies: chunking strategy\n- User mentions or implies: pinecone\n- User mentions or implies: weaviate\n- User mentions or implies: chromadb\n- User mentions or implies: pgvector\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-awesome-skills\u002Fskills\u002Frag-engineer",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 rag-engineer",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill rag-engineer",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill rag-engineer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Frag-engineer\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",[],[]]