[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M797MKB7KVFVST89MB22V54J":3,"skill-same:01M797MKB7KVFVST89MB22V54J":92},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M797MKB7KVFVST89MB22V54J","scanning-infrastructure-with-nessus",null,"Tenable Nessus is the industry-leading vulnerability scanner used to identify security weaknesses across network infrastructure including servers, workstations, network devices, and operating systems.","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fscanning-infrastructure-with-nessus\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fscanning-infrastructure-with-nessus\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: scanning-infrastructure-with-nessus\ndescription: Tenable Nessus is the industry-leading vulnerability scanner used to identify security weaknesses across network infrastructure including servers, workstations, network devices, and operating systems.\ndomain: cybersecurity\nsubdomain: vulnerability-management\ntags: [vulnerability-management, cve, nessus, tenable, infrastructure-scanning, risk]\nversion: \"1.0\"\nauthor: mahipal\nlicense: Apache-2.0\n---\n# Scanning Infrastructure with Nessus\n\n## Overview\nTenable Nessus is the industry-leading vulnerability scanner used to identify security weaknesses across network infrastructure including servers, workstations, network devices, and operating systems. This skill covers configuring scan policies, running authenticated and unauthenticated scans, interpreting results, and integrating Nessus into continuous vulnerability management workflows.\n\n\n## When to Use\n\n- When conducting security assessments that involve scanning infrastructure with nessus\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n- Nessus Professional or Essentials license installed and activated\n- Network access to target systems (firewall rules allowing scanner IP)\n- Administrative credentials for authenticated scanning\n- Understanding of TCP\u002FIP networking and common services\n- Written authorization for scanning target environments\n\n## Core Concepts\n\n### Nessus Architecture\nNessus operates as a client-server application where the Nessus scanner engine runs as a service (nessusd) on the host system. It uses a plugin-based architecture with over 200,000 plugins updated weekly by Tenable's research team. Each plugin tests for a specific vulnerability, misconfiguration, or compliance check.\n\n### Scan Types\n1. **Host Discovery** - Identifies live hosts using ICMP, TCP, UDP, and ARP\n2. **Basic Network Scan** - Default policy covering common vulnerabilities\n3. **Advanced Scan** - Custom policy with granular plugin selection\n4. **Credentialed Patch Audit** - Authenticated scan checking installed patches\n5. **Web Application Tests** - Scans for web-specific vulnerabilities\n6. **Compliance Audit** - Checks against CIS, DISA STIG, PCI DSS benchmarks\n\n### Plugin Families\nNessus organizes plugins into families including:\n- **Operating Systems**: Windows, Linux, macOS, Solaris\n- **Network Devices**: Cisco, Juniper, Palo Alto, Fortinet\n- **Web Servers**: Apache, Nginx, IIS, Tomcat\n- **Databases**: Oracle, MySQL, PostgreSQL, MSSQL\n- **Services**: DNS, SMTP, FTP, SSH, SNMP\n\n## Workflow\n\n### Step 1: Initial Configuration\n```bash\n# Start Nessus service\nsudo systemctl start nessusd\nsudo systemctl enable nessusd\n\n# CLI management with nessuscli\n\u002Fopt\u002Fnessus\u002Fsbin\u002Fnessuscli update --all\n\u002Fopt\u002Fnessus\u002Fsbin\u002Fnessuscli fix --list\n\n# Verify plugin count\n\u002Fopt\u002Fnessus\u002Fsbin\u002Fnessuscli update --plugins-only\n```\n\n### Step 2: Create Scan Policy\nConfigure a custom scan policy through the Nessus web UI at https:\u002F\u002Flocalhost:8834:\n\n1. Navigate to Policies > New Policy > Advanced Scan\n2. Configure General settings: name, description, targets\n3. Set Discovery settings:\n   - Host Discovery: Ping methods (ICMP, TCP SYN on ports 22,80,443)\n   - Port Scanning: SYN scan on common ports or all 65535 ports\n   - Service Discovery: Probe all ports for services\n4. Configure Assessment settings:\n   - Accuracy: Override normal accuracy (reduce false positives)\n   - Web Applications: Enable if scanning web servers\n5. Select Plugin families relevant to target environment\n\n### Step 3: Configure Credentials\nFor authenticated scanning, configure credentials under the Credentials tab:\n- **SSH**: Username\u002Fpassword or SSH key pair\n- **Windows**: Domain credentials via SMB, WMI\n- **SNMP**: Community strings (v1\u002Fv2c) or USM credentials (v3)\n- **Database**: Oracle, MySQL, PostgreSQL connection strings\n- **VMware**: vCenter or ESXi credentials\n\n### Step 4: Run the Scan\n```\n# Using Nessus REST API via curl\n# Authenticate and get token\ncurl -k -X POST https:\u002F\u002Flocalhost:8834\u002Fsession \\\n  -d '{\"username\":\"admin\",\"password\":\"password\"}' \\\n  -H \"Content-Type: application\u002Fjson\"\n\n# Create scan\ncurl -k -X POST https:\u002F\u002Flocalhost:8834\u002Fscans \\\n  -H \"X-Cookie: token=\u003CTOKEN>\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"uuid\": \"\u003CTEMPLATE_UUID>\",\n    \"settings\": {\n      \"name\": \"Infrastructure Scan Q1\",\n      \"text_targets\": \"192.168.1.0\u002F24\",\n      \"enabled\": true,\n      \"launch\": \"ON_DEMAND\"\n    }\n  }'\n\n# Launch scan\ncurl -k -X POST https:\u002F\u002Flocalhost:8834\u002Fscans\u002F\u003CSCAN_ID>\u002Flaunch \\\n  -H \"X-Cookie: token=\u003CTOKEN>\"\n\n# Check scan status\ncurl -k -X GET https:\u002F\u002Flocalhost:8834\u002Fscans\u002F\u003CSCAN_ID> \\\n  -H \"X-Cookie: token=\u003CTOKEN>\"\n```\n\n### Step 5: Analyze Results\nNessus categorizes findings by severity:\n- **Critical (CVSS 9.0-10.0)**: Immediate remediation required\n- **High (CVSS 7.0-8.9)**: Remediate within 7-14 days\n- **Medium (CVSS 4.0-6.9)**: Remediate within 30 days\n- **Low (CVSS 0.1-3.9)**: Remediate during next maintenance window\n- **Informational**: No immediate action required\n\n### Step 6: Export and Report\n```bash\n# Export via REST API\ncurl -k -X POST \"https:\u002F\u002Flocalhost:8834\u002Fscans\u002F\u003CSCAN_ID>\u002Fexport\" \\\n  -H \"X-Cookie: token=\u003CTOKEN>\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"format\":\"nessus\"}'\n\n# Supported formats: nessus (XML), csv, html, pdf\n```\n\n## Best Practices\n1. Schedule scans during maintenance windows to minimize production impact\n2. Use authenticated scanning for 45-60% more vulnerability detection\n3. Exclude fragile systems (medical devices, legacy SCADA) from aggressive scans\n4. Maintain separate scan policies for different network segments\n5. Update plugins before every scan to catch recently disclosed CVEs\n6. Validate critical findings manually before escalating to remediation teams\n7. Implement scan result trending to track remediation progress over time\n8. Store scan results in Tenable.sc or Tenable.io for centralized management\n\n## Common Pitfalls\n- Running unauthenticated scans only (misses 45-60% of vulnerabilities)\n- Scanning without written authorization (legal and ethical violations)\n- Ignoring scan performance impact on production systems\n- Failing to tune plugins leading to excessive false positives\n- Not validating scanner network connectivity before launching scans\n- Using default scan policies without customization for the environment\n\n## Related Skills\n- performing-authenticated-vulnerability-scan\n- prioritizing-vulnerabilities-with-cvss-scoring\n- implementing-continuous-vulnerability-monitoring\n- performing-network-vulnerability-assessment\n","# Scanning Infrastructure with Nessus\n\n## Overview\nTenable Nessus is the industry-leading vulnerability scanner used to identify security weaknesses across network infrastructure including servers, workstations, network devices, and operating systems. This skill covers configuring scan policies, running authenticated and unauthenticated scans, interpreting results, and integrating Nessus into continuous vulnerability management workflows.\n\n\n## When to Use\n\n- When conducting security assessments that involve scanning infrastructure with nessus\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n- Nessus Professional or Essentials license installed and activated\n- Network access to target systems (firewall rules allowing scanner IP)\n- Administrative credentials for authenticated scanning\n- Understanding of TCP\u002FIP networking and common services\n- Written authorization for scanning target environments\n\n## Core Concepts\n\n### Nessus Architecture\nNessus operates as a client-server application where the Nessus scanner engine runs as a service (nessusd) on the host system. It uses a plugin-based architecture with over 200,000 plugins updated weekly by Tenable's research team. Each plugin tests for a specific vulnerability, misconfiguration, or compliance check.\n\n### Scan Types\n1. **Host Discovery** - Identifies live hosts using ICMP, TCP, UDP, and ARP\n2. **Basic Network Scan** - Default policy covering common vulnerabilities\n3. **Advanced Scan** - Custom policy with granular plugin selection\n4. **Credentialed Patch Audit** - Authenticated scan checking installed patches\n5. **Web Application Tests** - Scans for web-specific vulnerabilities\n6. **Compliance Audit** - Checks against CIS, DISA STIG, PCI DSS benchmarks\n\n### Plugin Families\nNessus organizes plugins into families including:\n- **Operating Systems**: Windows, Linux, macOS, Solaris\n- **Network Devices**: Cisco, Juniper, Palo Alto, Fortinet\n- **Web Servers**: Apache, Nginx, IIS, Tomcat\n- **Databases**: Oracle, MySQL, PostgreSQL, MSSQL\n- **Services**: DNS, SMTP, FTP, SSH, SNMP\n\n## Workflow\n\n### Step 1: Initial Configuration\n```bash\n# Start Nessus service\nsudo systemctl start nessusd\nsudo systemctl enable nessusd\n\n# CLI management with nessuscli\n\u002Fopt\u002Fnessus\u002Fsbin\u002Fnessuscli update --all\n\u002Fopt\u002Fnessus\u002Fsbin\u002Fnessuscli fix --list\n\n# Verify plugin count\n\u002Fopt\u002Fnessus\u002Fsbin\u002Fnessuscli update --plugins-only\n```\n\n### Step 2: Create Scan Policy\nConfigure a custom scan policy through the Nessus web UI at https:\u002F\u002Flocalhost:8834:\n\n1. Navigate to Policies > New Policy > Advanced Scan\n2. Configure General settings: name, description, targets\n3. Set Discovery settings:\n   - Host Discovery: Ping methods (ICMP, TCP SYN on ports 22,80,443)\n   - Port Scanning: SYN scan on common ports or all 65535 ports\n   - Service Discovery: Probe all ports for services\n4. Configure Assessment settings:\n   - Accuracy: Override normal accuracy (reduce false positives)\n   - Web Applications: Enable if scanning web servers\n5. Select Plugin families relevant to target environment\n\n### Step 3: Configure Credentials\nFor authenticated scanning, configure credentials under the Credentials tab:\n- **SSH**: Username\u002Fpassword or SSH key pair\n- **Windows**: Domain credentials via SMB, WMI\n- **SNMP**: Community strings (v1\u002Fv2c) or USM credentials (v3)\n- **Database**: Oracle, MySQL, PostgreSQL connection strings\n- **VMware**: vCenter or ESXi credentials\n\n### Step 4: Run the Scan\n```\n# Using Nessus REST API via curl\n# Authenticate and get token\ncurl -k -X POST https:\u002F\u002Flocalhost:8834\u002Fsession \\\n  -d '{\"username\":\"admin\",\"password\":\"password\"}' \\\n  -H \"Content-Type: application\u002Fjson\"\n\n# Create scan\ncurl -k -X POST https:\u002F\u002Flocalhost:8834\u002Fscans \\\n  -H \"X-Cookie: token=\u003CTOKEN>\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"uuid\": \"\u003CTEMPLATE_UUID>\",\n    \"settings\": {\n      \"name\": \"Infrastructure Scan Q1\",\n      \"text_targets\": \"192.168.1.0\u002F24\",\n      \"enabled\": true,\n      \"launch\": \"ON_DEMAND\"\n    }\n  }'\n\n# Launch scan\ncurl -k -X POST https:\u002F\u002Flocalhost:8834\u002Fscans\u002F\u003CSCAN_ID>\u002Flaunch \\\n  -H \"X-Cookie: token=\u003CTOKEN>\"\n\n# Check scan status\ncurl -k -X GET https:\u002F\u002Flocalhost:8834\u002Fscans\u002F\u003CSCAN_ID> \\\n  -H \"X-Cookie: token=\u003CTOKEN>\"\n```\n\n### Step 5: Analyze Results\nNessus categorizes findings by severity:\n- **Critical (CVSS 9.0-10.0)**: Immediate remediation required\n- **High (CVSS 7.0-8.9)**: Remediate within 7-14 days\n- **Medium (CVSS 4.0-6.9)**: Remediate within 30 days\n- **Low (CVSS 0.1-3.9)**: Remediate during next maintenance window\n- **Informational**: No immediate action required\n\n### Step 6: Export and Report\n```bash\n# Export via REST API\ncurl -k -X POST \"https:\u002F\u002Flocalhost:8834\u002Fscans\u002F\u003CSCAN_ID>\u002Fexport\" \\\n  -H \"X-Cookie: token=\u003CTOKEN>\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"format\":\"nessus\"}'\n\n# Supported formats: nessus (XML), csv, html, pdf\n```\n\n## Best Practices\n1. Schedule scans during maintenance windows to minimize production impact\n2. Use authenticated scanning for 45-60% more vulnerability detection\n3. Exclude fragile systems (medical devices, legacy SCADA) from aggressive scans\n4. Maintain separate scan policies for different network segments\n5. Update plugins before every scan to catch recently disclosed CVEs\n6. Validate critical findings manually before escalating to remediation teams\n7. Implement scan result trending to track remediation progress over time\n8. Store scan results in Tenable.sc or Tenable.io for centralized management\n\n## Common Pitfalls\n- Running unauthenticated scans only (misses 45-60% of vulnerabilities)\n- Scanning without written authorization (legal and ethical violations)\n- Ignoring scan performance impact on production systems\n- Failing to tune plugins leading to excessive false positives\n- Not validating scanner network connectivity before launching scans\n- Using default scan policies without customization for the environment\n\n## Related Skills\n- performing-authenticated-vulnerability-scan\n- prioritizing-vulnerabilities-with-cvss-scoring\n- implementing-continuous-vulnerability-monitoring\n- performing-network-vulnerability-assessment\n",{"name":5,"tags":25,"author":32,"domain":33,"license":15,"version":34,"subdomain":26,"description":7},[26,27,28,29,30,31],"vulnerability-management","cve","nessus","tenable","infrastructure-scanning","risk","mahipal","cybersecurity","1.0","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fscanning-infrastructure-with-nessus",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill scanning-infrastructure-with-nessus",{"tool":50,"command":51},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill scanning-infrastructure-with-nessus",{"tool":53,"command":54},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill scanning-infrastructure-with-nessus","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fscanning-infrastructure-with-nessus\u002FSKILL.md",true,[58,64,68,74,78,82,88],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"assets\u002Ftemplate.md","ASSET","资产文件",3695,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fscanning-infrastructure-with-nessus\u002Fassets\u002Ftemplate.md",{"path":65,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fapi-reference.md","REFERENCE","参考文档",1931,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fscanning-infrastructure-with-nessus\u002Freferences\u002Fapi-reference.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fstandards.md",1940,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fscanning-infrastructure-with-nessus\u002Freferences\u002Fstandards.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fworkflows.md",4515,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fscanning-infrastructure-with-nessus\u002Freferences\u002Fworkflows.md",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Fagent.py","SCRIPT","脚本",6251,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fscanning-infrastructure-with-nessus\u002Fscripts\u002Fagent.py",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Fprocess.py",21306,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fscanning-infrastructure-with-nessus\u002Fscripts\u002Fprocess.py",[93,101,108,115,122,130],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":20},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":20},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":20},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":20},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":20},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":20},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]