[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GDKPSV19AK72MVCVBH6KW9":3,"skill-same:01M6GDKPSV19AK72MVCVBH6KW9":70},{"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":23,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6GDKPSV19AK72MVCVBH6KW9","wiki-onboarding",null,"Generate two complementary onboarding documents that together give any engineer — from newcomer to principal — a complete understanding of a codebase. Use when user asks for onboarding docs or getting-started guides, user runs \u002Fdeep-wiki, or user wants to help new team members understand a codebase.","Sam-06060\u002Fjarvis-assistant","Sam-06060","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F208600848?v=4","01M6CRKT7C7FXD21V6HXF293S0","Samson Frank Ganta","01M6CRKTBEKYFD8YX5Z1GT99EE",6,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fwiki-onboarding\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"wiki onboarding","onboarding","wiki","user","understand","getting-started","guides","complete","deep","community","engineer","use","docs","team","help","generate","documents","2026-11-10 10:12:30",false,"---\nname: wiki-onboarding\ndescription: \"Generate two complementary onboarding documents that together give any engineer — from newcomer to principal — a complete understanding of a codebase. Use when user asks for onboarding docs or getting-started guides, user runs \u002Fdeep-wiki, or user wants to help new team members understand a codebase.\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Wiki Onboarding Guide Generator\n\nGenerate two complementary onboarding documents that together give any engineer — from newcomer to principal — a complete understanding of a codebase.\n\n## When to Use\n- User asks for onboarding docs or getting-started guides\n- User runs `\u002Fdeep-wiki:onboard` command\n- User wants to help new team members understand a codebase\n\n## Language Detection\n\nScan the repository for build files to determine the primary language for code examples:\n- `package.json` \u002F `tsconfig.json` → TypeScript\u002FJavaScript\n- `*.csproj` \u002F `*.sln` → C# \u002F .NET\n- `Cargo.toml` → Rust\n- `pyproject.toml` \u002F `setup.py` \u002F `requirements.txt` → Python\n- `go.mod` → Go\n- `pom.xml` \u002F `build.gradle` → Java\n\n## Guide 1: Principal-Level Onboarding\n\n**Audience**: Senior\u002Fstaff+ engineers who need the \"why\" behind decisions.\n\n### Required Sections\n\n1. **System Philosophy & Design Principles** — What invariants does the system maintain? What were the key design choices and why?\n2. **Architecture Overview** — Component map with Mermaid diagram. What owns what, communication patterns.\n3. **Key Abstractions & Interfaces** — The load-bearing abstractions everything depends on\n4. **Decision Log** — Major architectural decisions with context, alternatives considered, trade-offs\n5. **Dependency Rationale** — Why each major dependency was chosen, what it replaced\n6. **Data Flow & State** — How data moves through the system (traced from actual code, not guessed)\n7. **Failure Modes & Error Handling** — What breaks, how errors propagate, recovery patterns\n8. **Performance Characteristics** — Bottlenecks, scaling limits, hot paths\n9. **Security Model** — Auth, authorization, trust boundaries, data sensitivity\n10. **Testing Strategy** — What's tested, what isn't, testing philosophy\n11. **Operational Concerns** — Deployment, monitoring, feature flags, configuration\n12. **Known Technical Debt** — Honest assessment of shortcuts and their risks\n\n### Rules\n- Every claim backed by `(file_path:line_number)` citation\n- Minimum 3 Mermaid diagrams (architecture, data flow, dependency graph)\n- All Mermaid diagrams use dark-mode colors (see wiki-vitepress skill)\n- Focus on WHY decisions were made, not just WHAT exists\n\n## Guide 2: Zero-to-Hero Contributor Guide\n\n**Audience**: New contributors who need step-by-step practical guidance.\n\n### Required Sections\n\n1. **What This Project Does** — 2-3 sentence elevator pitch\n2. **Prerequisites** — Tools, versions, accounts needed\n3. **Environment Setup** — Step-by-step with exact commands, expected output at each step\n4. **Project Structure** — Annotated directory tree (what lives where and why)\n5. **Your First Task** — End-to-end walkthrough of adding a simple feature\n6. **Development Workflow** — Branch strategy, commit conventions, PR process\n7. **Running Tests** — How to run tests, what to test, how to add a test\n8. **Debugging Guide** — Common issues and how to diagnose them\n9. **Key Concepts** — Domain-specific terminology explained with code examples\n10. **Code Patterns** — \"If you want to add X, follow this pattern\" templates\n11. **Common Pitfalls** — Mistakes every new contributor makes and how to avoid them\n12. **Where to Get Help** — Communication channels, documentation, key contacts\n13. **Glossary** — Terms used in the codebase that aren't obvious\n14. **Quick Reference Card** — Cheat sheet of most-used commands and patterns\n\n### Rules\n- All code examples in the detected primary language\n- Every command must be copy-pasteable\n- Include expected output for verification steps\n- Use Mermaid for workflow diagrams (dark-mode colors)\n- Ground all claims in actual code — cite `(file_path:line_number)`\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Wiki Onboarding Guide Generator\n\nGenerate two complementary onboarding documents that together give any engineer — from newcomer to principal — a complete understanding of a codebase.\n\n## When to Use\n- User asks for onboarding docs or getting-started guides\n- User runs `\u002Fdeep-wiki:onboard` command\n- User wants to help new team members understand a codebase\n\n## Language Detection\n\nScan the repository for build files to determine the primary language for code examples:\n- `package.json` \u002F `tsconfig.json` → TypeScript\u002FJavaScript\n- `*.csproj` \u002F `*.sln` → C# \u002F .NET\n- `Cargo.toml` → Rust\n- `pyproject.toml` \u002F `setup.py` \u002F `requirements.txt` → Python\n- `go.mod` → Go\n- `pom.xml` \u002F `build.gradle` → Java\n\n## Guide 1: Principal-Level Onboarding\n\n**Audience**: Senior\u002Fstaff+ engineers who need the \"why\" behind decisions.\n\n### Required Sections\n\n1. **System Philosophy & Design Principles** — What invariants does the system maintain? What were the key design choices and why?\n2. **Architecture Overview** — Component map with Mermaid diagram. What owns what, communication patterns.\n3. **Key Abstractions & Interfaces** — The load-bearing abstractions everything depends on\n4. **Decision Log** — Major architectural decisions with context, alternatives considered, trade-offs\n5. **Dependency Rationale** — Why each major dependency was chosen, what it replaced\n6. **Data Flow & State** — How data moves through the system (traced from actual code, not guessed)\n7. **Failure Modes & Error Handling** — What breaks, how errors propagate, recovery patterns\n8. **Performance Characteristics** — Bottlenecks, scaling limits, hot paths\n9. **Security Model** — Auth, authorization, trust boundaries, data sensitivity\n10. **Testing Strategy** — What's tested, what isn't, testing philosophy\n11. **Operational Concerns** — Deployment, monitoring, feature flags, configuration\n12. **Known Technical Debt** — Honest assessment of shortcuts and their risks\n\n### Rules\n- Every claim backed by `(file_path:line_number)` citation\n- Minimum 3 Mermaid diagrams (architecture, data flow, dependency graph)\n- All Mermaid diagrams use dark-mode colors (see wiki-vitepress skill)\n- Focus on WHY decisions were made, not just WHAT exists\n\n## Guide 2: Zero-to-Hero Contributor Guide\n\n**Audience**: New contributors who need step-by-step practical guidance.\n\n### Required Sections\n\n1. **What This Project Does** — 2-3 sentence elevator pitch\n2. **Prerequisites** — Tools, versions, accounts needed\n3. **Environment Setup** — Step-by-step with exact commands, expected output at each step\n4. **Project Structure** — Annotated directory tree (what lives where and why)\n5. **Your First Task** — End-to-end walkthrough of adding a simple feature\n6. **Development Workflow** — Branch strategy, commit conventions, PR process\n7. **Running Tests** — How to run tests, what to test, how to add a test\n8. **Debugging Guide** — Common issues and how to diagnose them\n9. **Key Concepts** — Domain-specific terminology explained with code examples\n10. **Code Patterns** — \"If you want to add X, follow this pattern\" templates\n11. **Common Pitfalls** — Mistakes every new contributor makes and how to avoid them\n12. **Where to Get Help** — Communication channels, documentation, key contacts\n13. **Glossary** — Terms used in the codebase that aren't obvious\n14. **Quick Reference Card** — Cheat sheet of most-used commands and patterns\n\n### Rules\n- All code examples in the detected primary language\n- Every command must be copy-pasteable\n- Include expected output for verification steps\n- Use Mermaid for workflow diagrams (dark-mode colors)\n- Ground all claims in actual code — cite `(file_path:line_number)`\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":46,"source":33,"date_added":47,"description":7},"unknown","2026-02-27","main","a50a3aa6b39fb0e1b7db88bef1bfc9c93606e126","modules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fwiki-onboarding",0,"https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant","https:\u002F\u002Fgithub.com\u002FSam-06060","Mobile Application Developer | Kotlin | Flutter, KMP, Swfit, Android,Swift UI | Building at Saar It Resources | Creator of Jarvis (AI Assistant)","2026-06-23 05:13:38",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add Sam-06060\u002Fjarvis-assistant --skill wiki-onboarding",{"tool":62,"command":63},"bunx","bunx skills add Sam-06060\u002Fjarvis-assistant --skill wiki-onboarding",{"tool":65,"command":66},"pnpm","pnpm dlx skills add Sam-06060\u002Fjarvis-assistant --skill wiki-onboarding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fwiki-onboarding\u002FSKILL.md",true,[],[71,84,100,127,146,173],{"skillNo":72,"name":73,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":81,"publishedAt":41},"01M6GDRVS6FXX3ESH0C9DW01C0","test_skill","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fscratch\u002Ftest_skill\u002FSKILL.md",[76],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[82,83],"Test Skill","test",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":41},"01M6GDRQ40HX22MA6XWC31RHHK","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzustand-store-ts\u002FSKILL.md",[],[91,92,93,94,95,96,97,33,98,99],"zustand store ts","zustand","store","with","types","middleware","patterns","create","typescript",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":109,"publishedAt":41},"01M6GDRKEA0WE670SPFWX5GKCN","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoom-automation\u002FSKILL.md",[106],{"categoryNo":107,"categoryName":108,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000023","Skill与智能体开发",[110,111,112,113,114,115,116,117,118,119,120,121,122,123,33,124,125,126],"automation","zoom automation","zoom","first","Tools","search","MCP","via","meeting","automate","critical","creation","webinars","composio","recordings","management","tracking",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":134,"publishedAt":41},"01M6GDRFS1452PC71JQ38S24HR","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoho-crm-automation\u002FSKILL.md",[133],{"categoryNo":107,"categoryName":108,"taxonomyType":79,"taxonomyTypeDesc":80},[135,110,136,137,138,139,140,33,115,141,123,142,120,119,114,143,98,144,116,145],"crm automation","zoho crm","crm","zoho crm automation","zoho","leads","contacts","records","update","tasks","manage",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":155,"publishedAt":41},"01M6GDRCKQBAVTGHX5XBH26KPZ","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzod-validation-expert\u002FSKILL.md",[152],{"categoryNo":153,"categoryName":154,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000009","前端开发",[156,157,158,159,160,99,161,162,163,164,165,166,94,167,168,169,170,33,171,172],"expert","zod","zod validation expert","validation","react","safe","parsing","errors","schema validation","react hook form","hook","trpc","form","type","next","schema","Next.js",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":180,"publishedAt":41},"01M6GDR658B08K4MY0RWD4A6EH","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzeroize-audit\u002FSKILL.md",[179],{"categoryNo":107,"categoryName":108,"taxonomyType":79,"taxonomyTypeDesc":80},[181,182,183,184,185,186,187,188,33,189,190,191,192,193,194,195,196,197,198,116],"zeroize audit","audit","write","passwords","get","project","c++","activate","assembly","read","Bash","secrets","analysis","data","flow","verification","code","rust"]