[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CVTC4MWTF9HK2XVGXFWD4W":3,"skill-same:01M6CVTC4MWTF9HK2XVGXFWD4W":76},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6CVTC4MWTF9HK2XVGXFWD4W","skill-scanner",null,"Scan agent skills for security issues before adoption. Detects prompt injection, malicious code, excessive permissions, secret exposure, and supply chain risks.","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\u002Fskill-scanner\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"skill scanner","scanner","prompt injection","malicious","security","code","permissions","issues","adoption","injection","prompt","community","scan","supply chain","2026-11-10 10:12:30",false,"---\nname: skill-scanner\ndescription: \"Scan agent skills for security issues before adoption. Detects prompt injection, malicious code, excessive permissions, secret exposure, and supply chain risks.\"\nrisk: unknown\nsource: community\n---\n\n# Skill Security Scanner\n\nScan agent skills for security issues before adoption. Detects prompt injection, malicious code, excessive permissions, secret exposure, and supply chain risks.\n\n**Important**: Run all scripts from the repository root using the full path via `${CLAUDE_SKILL_ROOT}`.\n\n## When to Use\n\n- You need to evaluate a skill for prompt injection, malicious code, over-broad permissions, or supply-chain risk before adopting it.\n- You want a static scan plus manual review workflow for a skill directory.\n- The task is to decide whether a skill is safe enough to trust in an agent environment.\n\n## Bundled Script\n\n### `scripts\u002Fscan_skill.py`\n\nStatic analysis scanner that detects deterministic patterns. Outputs structured JSON.\n\n```bash\nuv run ${CLAUDE_SKILL_ROOT}\u002Fscripts\u002Fscan_skill.py \u003Cskill-directory>\n```\n\nReturns JSON with findings, URLs, structure info, and severity counts. The script catches patterns mechanically — your job is to evaluate intent and filter false positives.\n\n## Workflow\n\n### Phase 1: Input & Discovery\n\nDetermine the scan target:\n\n- If the user provides a skill directory path, use it directly\n- If the user names a skill, look for it under `plugins\u002F*\u002Fskills\u002F\u003Cname>\u002F` or `.claude\u002Fskills\u002F\u003Cname>\u002F`\n- If the user says \"scan all skills\", discover all `*\u002FSKILL.md` files and scan each\n\nValidate the target contains a `SKILL.md` file. List the skill structure:\n\n```bash\nls -la \u003Cskill-directory>\u002F\nls \u003Cskill-directory>\u002Freferences\u002F 2>\u002Fdev\u002Fnull\nls \u003Cskill-directory>\u002Fscripts\u002F 2>\u002Fdev\u002Fnull\n```\n\n### Phase 2: Automated Static Scan\n\nRun the bundled scanner:\n\n```bash\nuv run ${CLAUDE_SKILL_ROOT}\u002Fscripts\u002Fscan_skill.py \u003Cskill-directory>\n```\n\nParse the JSON output. The script produces findings with severity levels, URL analysis, and structure information. Use these as leads for deeper analysis.\n\n**Fallback**: If the script fails, proceed with manual analysis using Grep patterns from the reference files.\n\n### Phase 3: Frontmatter Validation\n\nRead the SKILL.md and check:\n\n- **Required fields**: `name` and `description` must be present\n- **Name consistency**: `name` field should match the directory name\n- **Tool assessment**: Review `allowed-tools` — is Bash justified? Are tools unrestricted (`*`)?\n- **Model override**: Is a specific model forced? Why?\n- **Description quality**: Does the description accurately represent what the skill does?\n\n### Phase 4: Prompt Injection Analysis\n\nLoad `${CLAUDE_SKILL_ROOT}\u002Freferences\u002Fprompt-injection-patterns.md` for context.\n\nReview scanner findings in the \"Prompt Injection\" category. For each finding:\n\n1. Read the surrounding context in the file\n2. Determine if the pattern is **performing** injection (malicious) or **discussing\u002Fdetecting** injection (legitimate)\n3. Skills about security, testing, or education commonly reference injection patterns — this is expected\n\n**Critical distinction**: A security review skill that lists injection patterns in its references is documenting threats, not attacking. Only flag patterns that would execute against the agent running the skill.\n\n### Phase 5: Behavioral Analysis\n\nThis phase is agent-only — no pattern matching. Read the full SKILL.md instructions and evaluate:\n\n**Description vs. instructions alignment**:\n- Does the description match what the instructions actually tell the agent to do?\n- A skill described as \"code formatter\" that instructs the agent to read ~\u002F.ssh is misaligned\n\n**Config\u002Fmemory poisoning**:\n- Instructions to modify `CLAUDE.md`, `MEMORY.md`, `settings.json`, `.mcp.json`, or hook configurations\n- Instructions to add itself to allowlists or auto-approve permissions\n- Writing to `~\u002F.claude\u002F` or any agent configuration directory\n\n**Scope creep**:\n- Instructions that exceed the skill's stated purpose\n- Unnecessary data gathering (reading files unrelated to the skill's function)\n- Instructions to install other skills, plugins, or dependencies not mentioned in the description\n\n**Information gathering**:\n- Reading environment variables beyond what's needed\n- Listing directory contents outside the skill's scope\n- Accessing git history, credentials, or user data unnecessarily\n\n### Phase 6: Script Analysis\n\nIf the skill has a `scripts\u002F` directory:\n\n1. Load `${CLAUDE_SKILL_ROOT}\u002Freferences\u002Fdangerous-code-patterns.md` for context\n2. Read each script file fully (do not skip any)\n3. Check scanner findings in the \"Malicious Code\" category\n4. For each finding, evaluate:\n   - **Data exfiltration**: Does the script send data to external URLs? What data?\n   - **Reverse shells**: Socket connections with redirected I\u002FO\n   - **Credential theft**: Reading SSH keys, .env files, tokens from environment\n   - **Dangerous execution**: eval\u002Fexec with dynamic input, shell=True with interpolation\n   - **Config modification**: Writing to agent settings, shell configs, git hooks\n5. Check PEP 723 `dependencies` — are they legitimate, well-known packages?\n6. Verify the script's behavior matches the SKILL.md description of what it does\n\n**Legitimate patterns**: `gh` CLI calls, `git` commands, reading project files, JSON output to stdout are normal for skill scripts.\n\n### Phase 7: Supply Chain Assessment\n\nReview URLs from the scanner output and any additional URLs found in scripts:\n\n- **Trusted domains**: GitHub, PyPI, official docs — normal\n- **Untrusted domains**: Unknown domains, personal sites, URL shorteners — flag for review\n- **Remote instruction loading**: Any URL that fetches content to be executed or interpreted as instructions is high risk\n- **Dependency downloads**: Scripts that download and execute binaries or code at runtime\n- **Unverifiable sources**: References to packages or tools not on standard registries\n\n### Phase 8: Permission Analysis\n\nLoad `${CLAUDE_SKILL_ROOT}\u002Freferences\u002Fpermission-analysis.md` for the tool risk matrix.\n\nEvaluate:\n\n- **Least privilege**: Are all granted tools actually used in the skill instructions?\n- **Tool justification**: Does the skill body reference operations that require each tool?\n- **Risk level**: Rate the overall permission profile using the tier system from the reference\n\nExample assessments:\n- `Read Grep Glob` — Low risk, read-only analysis skill\n- `Read Grep Glob Bash` — Medium risk, needs Bash justification (e.g., running bundled scripts)\n- `Read Grep Glob Bash Write Edit WebFetch Task` — High risk, near-full access\n\n## Confidence Levels\n\n| Level | Criteria | Action |\n|-------|----------|--------|\n| **HIGH** | Pattern confirmed + malicious intent evident | Report with severity |\n| **MEDIUM** | Suspicious pattern, intent unclear | Note as \"Needs verification\" |\n| **LOW** | Theoretical, best practice only | Do not report |\n\n**False positive awareness is critical.** The biggest risk is flagging legitimate security skills as malicious because they reference attack patterns. Always evaluate intent before reporting.\n\n## Output Format\n\n```markdown\n## Skill Security Scan: [Skill Name]\n\n### Summary\n- **Findings**: X (Y Critical, Z High, ...)\n- **Risk Level**: Critical \u002F High \u002F Medium \u002F Low \u002F Clean\n- **Skill Structure**: SKILL.md only \u002F +references \u002F +scripts \u002F full\n\n### Findings\n\n#### [SKILL-SEC-001] [Finding Type] (Severity)\n- **Location**: `SKILL.md:42` or `scripts\u002Ftool.py:15`\n- **Confidence**: High\n- **Category**: Prompt Injection \u002F Malicious Code \u002F Excessive Permissions \u002F Secret Exposure \u002F Supply Chain \u002F Validation\n- **Issue**: [What was found]\n- **Evidence**: [code snippet]\n- **Risk**: [What could happen]\n- **Remediation**: [How to fix]\n\n### Needs Verification\n[Medium-confidence items needing human review]\n\n### Assessment\n[Safe to install \u002F Install with caution \u002F Do not install]\n[Brief justification for the assessment]\n```\n\n**Risk level determination**:\n- **Critical**: Any high-confidence critical finding (prompt injection, credential theft, data exfiltration)\n- **High**: High-confidence high-severity findings or multiple medium findings\n- **Medium**: Medium-confidence findings or minor permission concerns\n- **Low**: Only best-practice suggestions\n- **Clean**: No findings after thorough analysis\n\n## Reference Files\n\n| File | Purpose |\n|------|---------|\n| `references\u002Fprompt-injection-patterns.md` | Injection patterns, jailbreaks, obfuscation techniques, false positive guide |\n| `references\u002Fdangerous-code-patterns.md` | Script security patterns: exfiltration, shells, credential theft, eval\u002Fexec |\n| `references\u002Fpermission-analysis.md` | Tool risk tiers, least privilege methodology, common skill permission profiles |\n","# Skill Security Scanner\n\nScan agent skills for security issues before adoption. Detects prompt injection, malicious code, excessive permissions, secret exposure, and supply chain risks.\n\n**Important**: Run all scripts from the repository root using the full path via `${CLAUDE_SKILL_ROOT}`.\n\n## When to Use\n\n- You need to evaluate a skill for prompt injection, malicious code, over-broad permissions, or supply-chain risk before adopting it.\n- You want a static scan plus manual review workflow for a skill directory.\n- The task is to decide whether a skill is safe enough to trust in an agent environment.\n\n## Bundled Script\n\n### `scripts\u002Fscan_skill.py`\n\nStatic analysis scanner that detects deterministic patterns. Outputs structured JSON.\n\n```bash\nuv run ${CLAUDE_SKILL_ROOT}\u002Fscripts\u002Fscan_skill.py \u003Cskill-directory>\n```\n\nReturns JSON with findings, URLs, structure info, and severity counts. The script catches patterns mechanically — your job is to evaluate intent and filter false positives.\n\n## Workflow\n\n### Phase 1: Input & Discovery\n\nDetermine the scan target:\n\n- If the user provides a skill directory path, use it directly\n- If the user names a skill, look for it under `plugins\u002F*\u002Fskills\u002F\u003Cname>\u002F` or `.claude\u002Fskills\u002F\u003Cname>\u002F`\n- If the user says \"scan all skills\", discover all `*\u002FSKILL.md` files and scan each\n\nValidate the target contains a `SKILL.md` file. List the skill structure:\n\n```bash\nls -la \u003Cskill-directory>\u002F\nls \u003Cskill-directory>\u002Freferences\u002F 2>\u002Fdev\u002Fnull\nls \u003Cskill-directory>\u002Fscripts\u002F 2>\u002Fdev\u002Fnull\n```\n\n### Phase 2: Automated Static Scan\n\nRun the bundled scanner:\n\n```bash\nuv run ${CLAUDE_SKILL_ROOT}\u002Fscripts\u002Fscan_skill.py \u003Cskill-directory>\n```\n\nParse the JSON output. The script produces findings with severity levels, URL analysis, and structure information. Use these as leads for deeper analysis.\n\n**Fallback**: If the script fails, proceed with manual analysis using Grep patterns from the reference files.\n\n### Phase 3: Frontmatter Validation\n\nRead the SKILL.md and check:\n\n- **Required fields**: `name` and `description` must be present\n- **Name consistency**: `name` field should match the directory name\n- **Tool assessment**: Review `allowed-tools` — is Bash justified? Are tools unrestricted (`*`)?\n- **Model override**: Is a specific model forced? Why?\n- **Description quality**: Does the description accurately represent what the skill does?\n\n### Phase 4: Prompt Injection Analysis\n\nLoad `${CLAUDE_SKILL_ROOT}\u002Freferences\u002Fprompt-injection-patterns.md` for context.\n\nReview scanner findings in the \"Prompt Injection\" category. For each finding:\n\n1. Read the surrounding context in the file\n2. Determine if the pattern is **performing** injection (malicious) or **discussing\u002Fdetecting** injection (legitimate)\n3. Skills about security, testing, or education commonly reference injection patterns — this is expected\n\n**Critical distinction**: A security review skill that lists injection patterns in its references is documenting threats, not attacking. Only flag patterns that would execute against the agent running the skill.\n\n### Phase 5: Behavioral Analysis\n\nThis phase is agent-only — no pattern matching. Read the full SKILL.md instructions and evaluate:\n\n**Description vs. instructions alignment**:\n- Does the description match what the instructions actually tell the agent to do?\n- A skill described as \"code formatter\" that instructs the agent to read ~\u002F.ssh is misaligned\n\n**Config\u002Fmemory poisoning**:\n- Instructions to modify `CLAUDE.md`, `MEMORY.md`, `settings.json`, `.mcp.json`, or hook configurations\n- Instructions to add itself to allowlists or auto-approve permissions\n- Writing to `~\u002F.claude\u002F` or any agent configuration directory\n\n**Scope creep**:\n- Instructions that exceed the skill's stated purpose\n- Unnecessary data gathering (reading files unrelated to the skill's function)\n- Instructions to install other skills, plugins, or dependencies not mentioned in the description\n\n**Information gathering**:\n- Reading environment variables beyond what's needed\n- Listing directory contents outside the skill's scope\n- Accessing git history, credentials, or user data unnecessarily\n\n### Phase 6: Script Analysis\n\nIf the skill has a `scripts\u002F` directory:\n\n1. Load `${CLAUDE_SKILL_ROOT}\u002Freferences\u002Fdangerous-code-patterns.md` for context\n2. Read each script file fully (do not skip any)\n3. Check scanner findings in the \"Malicious Code\" category\n4. For each finding, evaluate:\n   - **Data exfiltration**: Does the script send data to external URLs? What data?\n   - **Reverse shells**: Socket connections with redirected I\u002FO\n   - **Credential theft**: Reading SSH keys, .env files, tokens from environment\n   - **Dangerous execution**: eval\u002Fexec with dynamic input, shell=True with interpolation\n   - **Config modification**: Writing to agent settings, shell configs, git hooks\n5. Check PEP 723 `dependencies` — are they legitimate, well-known packages?\n6. Verify the script's behavior matches the SKILL.md description of what it does\n\n**Legitimate patterns**: `gh` CLI calls, `git` commands, reading project files, JSON output to stdout are normal for skill scripts.\n\n### Phase 7: Supply Chain Assessment\n\nReview URLs from the scanner output and any additional URLs found in scripts:\n\n- **Trusted domains**: GitHub, PyPI, official docs — normal\n- **Untrusted domains**: Unknown domains, personal sites, URL shorteners — flag for review\n- **Remote instruction loading**: Any URL that fetches content to be executed or interpreted as instructions is high risk\n- **Dependency downloads**: Scripts that download and execute binaries or code at runtime\n- **Unverifiable sources**: References to packages or tools not on standard registries\n\n### Phase 8: Permission Analysis\n\nLoad `${CLAUDE_SKILL_ROOT}\u002Freferences\u002Fpermission-analysis.md` for the tool risk matrix.\n\nEvaluate:\n\n- **Least privilege**: Are all granted tools actually used in the skill instructions?\n- **Tool justification**: Does the skill body reference operations that require each tool?\n- **Risk level**: Rate the overall permission profile using the tier system from the reference\n\nExample assessments:\n- `Read Grep Glob` — Low risk, read-only analysis skill\n- `Read Grep Glob Bash` — Medium risk, needs Bash justification (e.g., running bundled scripts)\n- `Read Grep Glob Bash Write Edit WebFetch Task` — High risk, near-full access\n\n## Confidence Levels\n\n| Level | Criteria | Action |\n|-------|----------|--------|\n| **HIGH** | Pattern confirmed + malicious intent evident | Report with severity |\n| **MEDIUM** | Suspicious pattern, intent unclear | Note as \"Needs verification\" |\n| **LOW** | Theoretical, best practice only | Do not report |\n\n**False positive awareness is critical.** The biggest risk is flagging legitimate security skills as malicious because they reference attack patterns. Always evaluate intent before reporting.\n\n## Output Format\n\n```markdown\n## Skill Security Scan: [Skill Name]\n\n### Summary\n- **Findings**: X (Y Critical, Z High, ...)\n- **Risk Level**: Critical \u002F High \u002F Medium \u002F Low \u002F Clean\n- **Skill Structure**: SKILL.md only \u002F +references \u002F +scripts \u002F full\n\n### Findings\n\n#### [SKILL-SEC-001] [Finding Type] (Severity)\n- **Location**: `SKILL.md:42` or `scripts\u002Ftool.py:15`\n- **Confidence**: High\n- **Category**: Prompt Injection \u002F Malicious Code \u002F Excessive Permissions \u002F Secret Exposure \u002F Supply Chain \u002F Validation\n- **Issue**: [What was found]\n- **Evidence**: [code snippet]\n- **Risk**: [What could happen]\n- **Remediation**: [How to fix]\n\n### Needs Verification\n[Medium-confidence items needing human review]\n\n### Assessment\n[Safe to install \u002F Install with caution \u002F Do not install]\n[Brief justification for the assessment]\n```\n\n**Risk level determination**:\n- **Critical**: Any high-confidence critical finding (prompt injection, credential theft, data exfiltration)\n- **High**: High-confidence high-severity findings or multiple medium findings\n- **Medium**: Medium-confidence findings or minor permission concerns\n- **Low**: Only best-practice suggestions\n- **Clean**: No findings after thorough analysis\n\n## Reference Files\n\n| File | Purpose |\n|------|---------|\n| `references\u002Fprompt-injection-patterns.md` | Injection patterns, jailbreaks, obfuscation techniques, false positive guide |\n| `references\u002Fdangerous-code-patterns.md` | Script security patterns: exfiltration, shells, credential theft, eval\u002Fexec |\n| `references\u002Fpermission-analysis.md` | Tool risk tiers, least privilege methodology, common skill permission profiles |\n",{"name":5,"risk":43,"source":35,"description":7},"unknown","main","a50a3aa6b39fb0e1b7db88bef1bfc9c93606e126","modules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fskill-scanner",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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add Sam-06060\u002Fjarvis-assistant --skill skill-scanner",{"tool":58,"command":59},"bunx","bunx skills add Sam-06060\u002Fjarvis-assistant --skill skill-scanner",{"tool":61,"command":62},"pnpm","pnpm dlx skills add Sam-06060\u002Fjarvis-assistant --skill skill-scanner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fskill-scanner\u002FSKILL.md",true,[66,72],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"metadata.json","REFERENCE","参考文档",1948,"https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fisraeli-insurance-comparator\u002Fmetadata.json",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"SKILL_HE.md",21377,"https:\u002F\u002Fgithub.com\u002FFDU-INS\u002FInsurance-Skills\u002Fblob\u002Fmain\u002FSkills\u002Fisraeli-insurance-comparator\u002FSKILL_HE.md",[77,88,104,129,148,175],{"skillNo":78,"name":79,"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":80,"categories":81,"keywords":85,"publishedAt":38},"01M6GDRVS6FXX3ESH0C9DW01C0","test_skill","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fscratch\u002Ftest_skill\u002FSKILL.md",[82],{"categoryNo":83,"categoryName":84,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[86,87],"Test Skill","test",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":38},"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",[],[95,96,97,98,99,100,101,35,102,103],"zustand store ts","zustand","store","with","types","middleware","patterns","create","typescript",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":111,"publishedAt":38},"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",[110],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[112,113,114,115,116,117,118,119,120,121,122,123,124,125,35,126,127,128],"automation","zoom automation","zoom","first","Tools","search","MCP","via","meeting","automate","critical","creation","webinars","composio","recordings","management","tracking",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":136,"publishedAt":38},"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",[135],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[137,112,138,139,140,141,142,35,117,143,125,144,122,121,116,145,102,146,118,147],"crm automation","zoho crm","crm","zoho crm automation","zoho","leads","contacts","records","update","tasks","manage",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":157,"publishedAt":38},"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",[154],{"categoryNo":155,"categoryName":156,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[158,159,160,161,162,103,163,164,165,166,167,168,98,169,170,171,172,35,173,174],"expert","zod","zod validation expert","validation","react","safe","parsing","errors","schema validation","react hook form","hook","trpc","form","type","next","schema","Next.js",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":182,"publishedAt":38},"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",[181],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[183,184,185,186,187,188,189,190,35,191,192,193,194,195,196,197,198,29,199,118],"zeroize audit","audit","write","passwords","get","project","c++","activate","assembly","read","Bash","secrets","analysis","data","flow","verification","rust"]