[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C2DPWC4EZGKGXQB21EYDAC":3,"skill-same:01M6C2DPWC4EZGKGXQB21EYDAC":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":28,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6C2DPWC4EZGKGXQB21EYDAC","troubleshooting-guide",null,"Generate troubleshooting documentation","jmagly\u002Faiwg","jmagly","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1159087?v=4","01M6C10AK8N2WCSQN11FYGTJWN","Joseph Magly","01M6C10AQ8A2RMED1Y1BSVY7NF",229,"MIT","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fskills\u002Ftroubleshooting-guide\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40],"troubleshooting","guide","troubleshooting guide","architecture","documentation","generate","system","text","interactive","overview","guidance","system overview","2026-11-10 10:12:30",false,"---\nnamespace: aiwg\nname: troubleshooting-guide\nplatforms: [all]\ndescription: Generate troubleshooting documentation\ncommandHint:\n  argumentHint: 1. **System Overview and Architecture** [--interactive] [--guidance \"text\"]\n  category: documentation-changelogs\n---\n\n# Troubleshooting Guide Generator Command\n\nGenerate troubleshooting documentation\n\n## Instructions\n\nFollow this systematic approach to create troubleshooting guides: **$ARGUMENTS**\n\n1. **System Overview and Architecture**\n   - Document the system architecture and components\n   - Map out dependencies and integrations\n   - Identify critical paths and failure points\n   - Create system topology diagrams\n   - Document data flow and communication patterns\n\n2. **Common Issues Identification**\n   - Collect historical support tickets and issues\n   - Interview team members about frequent problems\n   - Analyze error logs and monitoring data\n   - Review user feedback and complaints\n   - Identify patterns in system failures\n\n3. **Troubleshooting Framework**\n   - Establish systematic diagnostic procedures\n   - Create problem isolation methodologies\n   - Document escalation paths and procedures\n   - Set up logging and monitoring checkpoints\n   - Define severity levels and response times\n\n4. **Diagnostic Tools and Commands**\n   \n   ```markdown\n   ## Essential Diagnostic Commands\n   \n   ### System Health\n   ```bash\n   # Check system resources\n   top                    # CPU and memory usage\n   df -h                 # Disk space\n   free -m               # Memory usage\n   netstat -tuln         # Network connections\n   \n   # Application logs\n   tail -f \u002Fvar\u002Flog\u002Fapp.log\n   journalctl -u service-name -f\n   \n   # Database connectivity\n   mysql -u user -p -e \"SELECT 1\"\n   psql -h host -U user -d db -c \"SELECT 1\"\n   ```\n   ```\n\n5. **Issue Categories and Solutions**\n\n   **Performance Issues:**\n   ```markdown\n   ### Slow Response Times\n   \n   **Symptoms:**\n   - API responses > 5 seconds\n   - User interface freezing\n   - Database timeouts\n   \n   **Diagnostic Steps:**\n   1. Check system resources (CPU, memory, disk)\n   2. Review application logs for errors\n   3. Analyze database query performance\n   4. Check network connectivity and latency\n   \n   **Common Causes:**\n   - Database connection pool exhaustion\n   - Inefficient database queries\n   - Memory leaks in application\n   - Network bandwidth limitations\n   \n   **Solutions:**\n   - Restart application services\n   - Optimize database queries\n   - Increase connection pool size\n   - Scale infrastructure resources\n   ```\n\n6. **Error Code Documentation**\n   \n   ```markdown\n   ## Error Code Reference\n   \n   ### HTTP Status Codes\n   - **500 Internal Server Error**\n     - Check application logs for stack traces\n     - Verify database connectivity\n     - Check environment variables\n   \n   - **404 Not Found**\n     - Verify URL routing configuration\n     - Check if resources exist\n     - Review API endpoint documentation\n   \n   - **503 Service Unavailable**\n     - Check service health status\n     - Verify load balancer configuration\n     - Check for maintenance mode\n   ```\n\n7. **Environment-Specific Issues**\n   - Document development environment problems\n   - Address staging\u002Ftesting environment issues\n   - Cover production-specific troubleshooting\n   - Include local development setup problems\n\n8. **Database Troubleshooting**\n   \n   ```markdown\n   ### Database Connection Issues\n   \n   **Symptoms:**\n   - \"Connection refused\" errors\n   - \"Too many connections\" errors\n   - Slow query performance\n   \n   **Diagnostic Commands:**\n   ```sql\n   -- Check active connections\n   SHOW PROCESSLIST;\n   \n   -- Check database size\n   SELECT table_schema, \n          ROUND(SUM(data_length + index_length) \u002F 1024 \u002F 1024, 1) AS 'DB Size in MB' \n   FROM information_schema.tables \n   GROUP BY table_schema;\n   \n   -- Check slow queries\n   SHOW VARIABLES LIKE 'slow_query_log';\n   ```\n   ```\n\n9. **Network and Connectivity Issues**\n   \n   ```markdown\n   ### Network Troubleshooting\n   \n   **Basic Connectivity:**\n   ```bash\n   # Test basic connectivity\n   ping example.com\n   telnet host port\n   curl -v https:\u002F\u002Fapi.example.com\u002Fhealth\n   \n   # DNS resolution\n   nslookup example.com\n   dig example.com\n   \n   # Network routing\n   traceroute example.com\n   ```\n   \n   **SSL\u002FTLS Issues:**\n   ```bash\n   # Check SSL certificate\n   openssl s_client -connect example.com:443\n   curl -vI https:\u002F\u002Fexample.com\n   ```\n   ```\n\n10. **Application-Specific Troubleshooting**\n    \n    **Memory Issues:**\n    ```markdown\n    ### Out of Memory Errors\n    \n    **Java Applications:**\n    ```bash\n    # Check heap usage\n    jstat -gc [PID]\n    jmap -dump:format=b,file=heapdump.hprof [PID]\n    \n    # Analyze heap dump\n    jhat heapdump.hprof\n    ```\n    \n    **Node.js Applications:**\n    ```bash\n    # Monitor memory usage\n    node --inspect app.js\n    # Use Chrome DevTools for memory profiling\n    ```\n    ```\n\n11. **Security and Authentication Issues**\n    \n    ```markdown\n    ### Authentication Failures\n    \n    **Symptoms:**\n    - 401 Unauthorized responses\n    - Token validation errors\n    - Session timeout issues\n    \n    **Diagnostic Steps:**\n    1. Verify credentials and tokens\n    2. Check token expiration\n    3. Validate authentication service\n    4. Review CORS configuration\n    \n    **Common Solutions:**\n    - Refresh authentication tokens\n    - Clear browser cookies\u002Fcache\n    - Verify CORS headers\n    - Check API key permissions\n    ```\n\n12. **Deployment and Configuration Issues**\n    \n    ```markdown\n    ### Deployment Failures\n    \n    **Container Issues:**\n    ```bash\n    # Check container status\n    docker ps -a\n    docker logs container-name\n    \n    # Check resource limits\n    docker stats\n    \n    # Debug container\n    docker exec -it container-name \u002Fbin\u002Fbash\n    ```\n    \n    **Kubernetes Issues:**\n    ```bash\n    # Check pod status\n    kubectl get pods\n    kubectl describe pod pod-name\n    kubectl logs pod-name\n    \n    # Check service connectivity\n    kubectl get svc\n    kubectl port-forward pod-name 8080:8080\n    ```\n    ```\n\n13. **Monitoring and Alerting Setup**\n    - Configure health checks and monitoring\n    - Set up log aggregation and analysis\n    - Implement alerting for critical issues\n    - Create dashboards for system metrics\n    - Document monitoring thresholds\n\n14. **Escalation Procedures**\n    \n    ```markdown\n    ## Escalation Matrix\n    \n    ### Severity Levels\n    \n    **Critical (P1):** System down, data loss\n    - Immediate response required\n    - Escalate to on-call engineer\n    - Notify management within 30 minutes\n    \n    **High (P2):** Major functionality impaired\n    - Response within 2 hours\n    - Escalate to senior engineer\n    - Provide hourly updates\n    \n    **Medium (P3):** Minor functionality issues\n    - Response within 8 hours\n    - Assign to appropriate team member\n    - Provide daily updates\n    ```\n\n15. **Recovery Procedures**\n    - Document system recovery steps\n    - Create data backup and restore procedures\n    - Establish rollback procedures for deployments\n    - Document disaster recovery processes\n    - Test recovery procedures regularly\n\n16. **Preventive Measures**\n    - Implement monitoring and alerting\n    - Set up automated health checks\n    - Create deployment validation procedures\n    - Establish code review processes\n    - Document maintenance procedures\n\n17. **Knowledge Base Integration**\n    - Link to relevant documentation\n    - Reference API documentation\n    - Include links to monitoring dashboards\n    - Connect to team communication channels\n    - Integrate with ticketing systems\n\n18. **Team Communication**\n    \n    ```markdown\n    ## Communication Channels\n    \n    ### Immediate Response\n    - Slack: #incidents channel\n    - Phone: On-call rotation\n    - Email: alerts@company.com\n    \n    ### Status Updates\n    - Status page: status.company.com\n    - Twitter: @company_status\n    - Internal wiki: troubleshooting section\n    ```\n\n19. **Documentation Maintenance**\n    - Regular review and updates\n    - Version control for troubleshooting guides\n    - Feedback collection from users\n    - Integration with incident post-mortems\n    - Continuous improvement processes\n\n20. **Self-Service Tools**\n    - Create diagnostic scripts and tools\n    - Build automated recovery procedures\n    - Implement self-healing systems\n    - Provide user-friendly diagnostic interfaces\n    - Create chatbot integration for common issues\n\n**Advanced Troubleshooting Techniques:**\n\n**Log Analysis:**\n```bash\n# Search for specific errors\ngrep -i \"error\" \u002Fvar\u002Flog\u002Fapp.log | tail -50\n\n# Analyze log patterns\nawk '{print $1}' access.log | sort | uniq -c | sort -nr\n\n# Monitor logs in real-time\ntail -f \u002Fvar\u002Flog\u002Fapp.log | grep -i \"exception\"\n```\n\n**Performance Profiling:**\n```bash\n# System performance\niostat -x 1\nsar -u 1 10\nvmstat 1 10\n\n# Application profiling\nstrace -p [PID]\nperf record -p [PID]\n```\n\nRemember to:\n- Keep troubleshooting guides up-to-date\n- Test all documented procedures regularly\n- Collect feedback from users and improve guides\n- Include screenshots and visual aids where helpful\n- Make guides searchable and well-organized\n\n## References\n\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002FREADME.md — SDLC framework context and documentation standards\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Faddons\u002Faiwg-utils\u002Frules\u002Fresearch-before-decision.md — Research-first for root cause analysis\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Faddons\u002Faiwg-utils\u002Frules\u002Fdiagram-generation.md — System topology and architecture diagram standards\n- @$AIWG_ROOT\u002Fdocs\u002Fcli-reference.md — CLI reference","# Troubleshooting Guide Generator Command\n\nGenerate troubleshooting documentation\n\n## Instructions\n\nFollow this systematic approach to create troubleshooting guides: **$ARGUMENTS**\n\n1. **System Overview and Architecture**\n   - Document the system architecture and components\n   - Map out dependencies and integrations\n   - Identify critical paths and failure points\n   - Create system topology diagrams\n   - Document data flow and communication patterns\n\n2. **Common Issues Identification**\n   - Collect historical support tickets and issues\n   - Interview team members about frequent problems\n   - Analyze error logs and monitoring data\n   - Review user feedback and complaints\n   - Identify patterns in system failures\n\n3. **Troubleshooting Framework**\n   - Establish systematic diagnostic procedures\n   - Create problem isolation methodologies\n   - Document escalation paths and procedures\n   - Set up logging and monitoring checkpoints\n   - Define severity levels and response times\n\n4. **Diagnostic Tools and Commands**\n   \n   ```markdown\n   ## Essential Diagnostic Commands\n   \n   ### System Health\n   ```bash\n   # Check system resources\n   top                    # CPU and memory usage\n   df -h                 # Disk space\n   free -m               # Memory usage\n   netstat -tuln         # Network connections\n   \n   # Application logs\n   tail -f \u002Fvar\u002Flog\u002Fapp.log\n   journalctl -u service-name -f\n   \n   # Database connectivity\n   mysql -u user -p -e \"SELECT 1\"\n   psql -h host -U user -d db -c \"SELECT 1\"\n   ```\n   ```\n\n5. **Issue Categories and Solutions**\n\n   **Performance Issues:**\n   ```markdown\n   ### Slow Response Times\n   \n   **Symptoms:**\n   - API responses > 5 seconds\n   - User interface freezing\n   - Database timeouts\n   \n   **Diagnostic Steps:**\n   1. Check system resources (CPU, memory, disk)\n   2. Review application logs for errors\n   3. Analyze database query performance\n   4. Check network connectivity and latency\n   \n   **Common Causes:**\n   - Database connection pool exhaustion\n   - Inefficient database queries\n   - Memory leaks in application\n   - Network bandwidth limitations\n   \n   **Solutions:**\n   - Restart application services\n   - Optimize database queries\n   - Increase connection pool size\n   - Scale infrastructure resources\n   ```\n\n6. **Error Code Documentation**\n   \n   ```markdown\n   ## Error Code Reference\n   \n   ### HTTP Status Codes\n   - **500 Internal Server Error**\n     - Check application logs for stack traces\n     - Verify database connectivity\n     - Check environment variables\n   \n   - **404 Not Found**\n     - Verify URL routing configuration\n     - Check if resources exist\n     - Review API endpoint documentation\n   \n   - **503 Service Unavailable**\n     - Check service health status\n     - Verify load balancer configuration\n     - Check for maintenance mode\n   ```\n\n7. **Environment-Specific Issues**\n   - Document development environment problems\n   - Address staging\u002Ftesting environment issues\n   - Cover production-specific troubleshooting\n   - Include local development setup problems\n\n8. **Database Troubleshooting**\n   \n   ```markdown\n   ### Database Connection Issues\n   \n   **Symptoms:**\n   - \"Connection refused\" errors\n   - \"Too many connections\" errors\n   - Slow query performance\n   \n   **Diagnostic Commands:**\n   ```sql\n   -- Check active connections\n   SHOW PROCESSLIST;\n   \n   -- Check database size\n   SELECT table_schema, \n          ROUND(SUM(data_length + index_length) \u002F 1024 \u002F 1024, 1) AS 'DB Size in MB' \n   FROM information_schema.tables \n   GROUP BY table_schema;\n   \n   -- Check slow queries\n   SHOW VARIABLES LIKE 'slow_query_log';\n   ```\n   ```\n\n9. **Network and Connectivity Issues**\n   \n   ```markdown\n   ### Network Troubleshooting\n   \n   **Basic Connectivity:**\n   ```bash\n   # Test basic connectivity\n   ping example.com\n   telnet host port\n   curl -v https:\u002F\u002Fapi.example.com\u002Fhealth\n   \n   # DNS resolution\n   nslookup example.com\n   dig example.com\n   \n   # Network routing\n   traceroute example.com\n   ```\n   \n   **SSL\u002FTLS Issues:**\n   ```bash\n   # Check SSL certificate\n   openssl s_client -connect example.com:443\n   curl -vI https:\u002F\u002Fexample.com\n   ```\n   ```\n\n10. **Application-Specific Troubleshooting**\n    \n    **Memory Issues:**\n    ```markdown\n    ### Out of Memory Errors\n    \n    **Java Applications:**\n    ```bash\n    # Check heap usage\n    jstat -gc [PID]\n    jmap -dump:format=b,file=heapdump.hprof [PID]\n    \n    # Analyze heap dump\n    jhat heapdump.hprof\n    ```\n    \n    **Node.js Applications:**\n    ```bash\n    # Monitor memory usage\n    node --inspect app.js\n    # Use Chrome DevTools for memory profiling\n    ```\n    ```\n\n11. **Security and Authentication Issues**\n    \n    ```markdown\n    ### Authentication Failures\n    \n    **Symptoms:**\n    - 401 Unauthorized responses\n    - Token validation errors\n    - Session timeout issues\n    \n    **Diagnostic Steps:**\n    1. Verify credentials and tokens\n    2. Check token expiration\n    3. Validate authentication service\n    4. Review CORS configuration\n    \n    **Common Solutions:**\n    - Refresh authentication tokens\n    - Clear browser cookies\u002Fcache\n    - Verify CORS headers\n    - Check API key permissions\n    ```\n\n12. **Deployment and Configuration Issues**\n    \n    ```markdown\n    ### Deployment Failures\n    \n    **Container Issues:**\n    ```bash\n    # Check container status\n    docker ps -a\n    docker logs container-name\n    \n    # Check resource limits\n    docker stats\n    \n    # Debug container\n    docker exec -it container-name \u002Fbin\u002Fbash\n    ```\n    \n    **Kubernetes Issues:**\n    ```bash\n    # Check pod status\n    kubectl get pods\n    kubectl describe pod pod-name\n    kubectl logs pod-name\n    \n    # Check service connectivity\n    kubectl get svc\n    kubectl port-forward pod-name 8080:8080\n    ```\n    ```\n\n13. **Monitoring and Alerting Setup**\n    - Configure health checks and monitoring\n    - Set up log aggregation and analysis\n    - Implement alerting for critical issues\n    - Create dashboards for system metrics\n    - Document monitoring thresholds\n\n14. **Escalation Procedures**\n    \n    ```markdown\n    ## Escalation Matrix\n    \n    ### Severity Levels\n    \n    **Critical (P1):** System down, data loss\n    - Immediate response required\n    - Escalate to on-call engineer\n    - Notify management within 30 minutes\n    \n    **High (P2):** Major functionality impaired\n    - Response within 2 hours\n    - Escalate to senior engineer\n    - Provide hourly updates\n    \n    **Medium (P3):** Minor functionality issues\n    - Response within 8 hours\n    - Assign to appropriate team member\n    - Provide daily updates\n    ```\n\n15. **Recovery Procedures**\n    - Document system recovery steps\n    - Create data backup and restore procedures\n    - Establish rollback procedures for deployments\n    - Document disaster recovery processes\n    - Test recovery procedures regularly\n\n16. **Preventive Measures**\n    - Implement monitoring and alerting\n    - Set up automated health checks\n    - Create deployment validation procedures\n    - Establish code review processes\n    - Document maintenance procedures\n\n17. **Knowledge Base Integration**\n    - Link to relevant documentation\n    - Reference API documentation\n    - Include links to monitoring dashboards\n    - Connect to team communication channels\n    - Integrate with ticketing systems\n\n18. **Team Communication**\n    \n    ```markdown\n    ## Communication Channels\n    \n    ### Immediate Response\n    - Slack: #incidents channel\n    - Phone: On-call rotation\n    - Email: alerts@company.com\n    \n    ### Status Updates\n    - Status page: status.company.com\n    - Twitter: @company_status\n    - Internal wiki: troubleshooting section\n    ```\n\n19. **Documentation Maintenance**\n    - Regular review and updates\n    - Version control for troubleshooting guides\n    - Feedback collection from users\n    - Integration with incident post-mortems\n    - Continuous improvement processes\n\n20. **Self-Service Tools**\n    - Create diagnostic scripts and tools\n    - Build automated recovery procedures\n    - Implement self-healing systems\n    - Provide user-friendly diagnostic interfaces\n    - Create chatbot integration for common issues\n\n**Advanced Troubleshooting Techniques:**\n\n**Log Analysis:**\n```bash\n# Search for specific errors\ngrep -i \"error\" \u002Fvar\u002Flog\u002Fapp.log | tail -50\n\n# Analyze log patterns\nawk '{print $1}' access.log | sort | uniq -c | sort -nr\n\n# Monitor logs in real-time\ntail -f \u002Fvar\u002Flog\u002Fapp.log | grep -i \"exception\"\n```\n\n**Performance Profiling:**\n```bash\n# System performance\niostat -x 1\nsar -u 1 10\nvmstat 1 10\n\n# Application profiling\nstrace -p [PID]\nperf record -p [PID]\n```\n\nRemember to:\n- Keep troubleshooting guides up-to-date\n- Test all documented procedures regularly\n- Collect feedback from users and improve guides\n- Include screenshots and visual aids where helpful\n- Make guides searchable and well-organized\n\n## References\n\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002FREADME.md — SDLC framework context and documentation standards\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Faddons\u002Faiwg-utils\u002Frules\u002Fresearch-before-decision.md — Research-first for root cause analysis\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Faddons\u002Faiwg-utils\u002Frules\u002Fdiagram-generation.md — System topology and architecture diagram standards\n- @$AIWG_ROOT\u002Fdocs\u002Fcli-reference.md — CLI reference",{"name":5,"namespace":46,"platforms":47,"commandHint":49,"description":7},"aiwg",[48],"all",{"category":50,"argumentHint":51},"documentation-changelogs","1. **System Overview and Architecture** [--interactive] [--guidance \"text\"]","main","6754967c344ccb087a8de06972f55a41067b291b","agentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fskills\u002Ftroubleshooting-guide",36,"https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg","https:\u002F\u002Faiwg.io","https:\u002F\u002Fgithub.com\u002Fjmagly","https:\u002F\u002Fintegrolabs.io","ml\u002Fai, industrial automation, safety\u002Fsecurity, ssi\r\n\r\nmagly.net\r\nintegrolabs.io\r\naiwg.io\r\nfortemi.com\r\npagenary.com\r\nbytecask.com","2026-11-12 00:33:10",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add jmagly\u002Faiwg --skill troubleshooting-guide",{"tool":68,"command":69},"bunx","bunx skills add jmagly\u002Faiwg --skill troubleshooting-guide",{"tool":71,"command":72},"pnpm","pnpm dlx skills add jmagly\u002Faiwg --skill troubleshooting-guide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fskills\u002Ftroubleshooting-guide\u002FSKILL.md",true,[],[77,105,129,135,142,156],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":84,"publishedAt":41},"01M70QA0BSYJ49EES9V4RE8QH1","host-hardening","Read-only system hardening baseline and plan-first host hardening recommendations for SSH, Docker bind addresses, firewall persistence, datastores, exporters and audit retention.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[83],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104],"host","host hardening","hardening","read","re","recommendations","remediation","plan","port","verification","Bash","access","only","retention","audit","never","firewall","bind","secrets","request",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":115,"publishedAt":41},"01M70PNT2Z4HMZPRBTAF6073NN","exposure-analysis","Read-only firewall analysis and effective host exposure reconstruction for Docker published ports, UFW bypass, stale rules, CDN scope, IPv6 asymmetry and external probe allowlists.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fforensics\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[111,114],{"categoryNo":112,"categoryName":113,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[116,117,118,88,119,93,120,121,95,122,85,123,97,124,125,100,101,126,127,128],"exposure analysis","analysis","unknown","credentials","collection","ufw","ports","internet","local","scope","reconstruction","operator","write",{"skillNo":130,"name":79,"nameZh":6,"description":80,"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},"01M70P8QATMPKA78E4FT5D2TNA","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[133],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[87,85,86,96,88,104,91,90,99,92,93,94,95,103,97,98,89,100,101,102],{"skillNo":136,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":141,"publishedAt":41},"01M70NMPVJ5H0JH131P60FW4R8","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[139,140],{"categoryNo":112,"categoryName":113,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[117,116,100,119,93,120,95,118,85,123,97,124,125,88,101,122,121,126,127,128],{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":149,"publishedAt":41},"01M6CB4DDR0B4NNCFK7ZK7449H","fixture-skill","Exercise rule delivery.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Frule-delivery\u002Fskills\u002Ffixture-skill\u002FSKILL.md",[148],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[150,151,152,153,154,155],"fixture skill","fixture","rule","delivery","true","exercise",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":163,"publishedAt":41},"01M6CB4AVK1W76MFMPP0JP32CJ","pi-local","Pi-local duplicate-precedence fixture.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fproviders\u002Fpi\u002Fproject\u002F.pi\u002Fskills\u002Fpi-local\u002FSKILL.md",[162],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[164,165,124,166,151],"pi","pi local","duplicate"]