[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79FGGC7W0954RCDTSFAW1DT":3,"skill-same:01M79FGGC7W0954RCDTSFAW1DT":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M79FGGC7W0954RCDTSFAW1DT","pentest-checklist",null,"This skill should be used when the user asks to \"plan a penetration test\", \"create a security assessment checklist\", \"prepare for penetration testing\", \"define pentest scope\", \"follow security testing best practices\", or needs a structured methodology for penetration testing engagements.","sharepointoscar\u002Fagent-workflow-skills","sharepointoscar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1544014?v=4","01M79DYNNSWKW6C81A3C9QF0FQ","Oscar Medina","01M79DYNPDXTKQ5RFX4071RBM8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-security\u002Fskills\u002Fpentest-checklist\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pentest-checklist\ndescription: This skill should be used when the user asks to \"plan a penetration test\", \"create a security assessment checklist\", \"prepare for penetration testing\", \"define pentest scope\", \"follow security testing best practices\", or needs a structured methodology for penetration testing engagements.\nmetadata:\n  author: zebbern\n  version: \"1.1\"\n---\n\n# Pentest Checklist\n\n## Purpose\n\nProvide a comprehensive checklist for planning, executing, and following up on penetration tests. Ensure thorough preparation, proper scoping, and effective remediation of discovered vulnerabilities.\n\n## Inputs\u002FPrerequisites\n\n- Clear business objectives for testing\n- Target environment information\n- Budget and timeline constraints\n- Stakeholder contacts and authorization\n- Legal agreements and scope documents\n\n## Outputs\u002FDeliverables\n\n- Defined pentest scope and objectives\n- Prepared testing environment\n- Security monitoring data\n- Vulnerability findings report\n- Remediation plan and verification\n\n## Core Workflow\n\n### Phase 1: Scope Definition\n\n#### Define Objectives\n\n- [ ] **Clarify testing purpose** - Determine goals (find vulnerabilities, compliance, customer assurance)\n- [ ] **Validate pentest necessity** - Ensure penetration test is the right solution\n- [ ] **Align outcomes with objectives** - Define success criteria\n\n**Reference Questions:**\n- Why are you doing this pentest?\n- What specific outcomes do you expect?\n- What will you do with the findings?\n\n#### Know Your Test Types\n\n| Type | Purpose | Scope |\n|------|---------|-------|\n| External Pentest | Assess external attack surface | Public-facing systems |\n| Internal Pentest | Assess insider threat risk | Internal network |\n| Web Application | Find application vulnerabilities | Specific applications |\n| Social Engineering | Test human security | Employees, processes |\n| Red Team | Full adversary simulation | Entire organization |\n\n#### Enumerate Likely Threats\n\n- [ ] **Identify high-risk areas** - Where could damage occur?\n- [ ] **Assess data sensitivity** - What data could be compromised?\n- [ ] **Review legacy systems** - Old systems often have vulnerabilities\n- [ ] **Map critical assets** - Prioritize testing targets\n\n#### Define Scope\n\n- [ ] **List in-scope systems** - IPs, domains, applications\n- [ ] **Define out-of-scope items** - Systems to avoid\n- [ ] **Set testing boundaries** - What techniques are allowed?\n- [ ] **Document exclusions** - Third-party systems, production data\n\n#### Budget Planning\n\n| Factor | Consideration |\n|--------|---------------|\n| Asset Value | Higher value = higher investment |\n| Complexity | More systems = more time |\n| Depth Required | Thorough testing costs more |\n| Reputation Value | Brand-name firms cost more |\n\n**Budget Reality Check:**\n- Cheap pentests often produce poor results\n- Align budget with asset criticality\n- Consider ongoing vs. one-time testing\n\n### Phase 2: Environment Preparation\n\n#### Prepare Test Environment\n\n- [ ] **Production vs. staging decision** - Determine where to test\n- [ ] **Set testing limits** - No DoS on production\n- [ ] **Schedule testing window** - Minimize business impact\n- [ ] **Create test accounts** - Provide appropriate access levels\n\n**Environment Options:**\n```\nProduction  - Realistic but risky\nStaging     - Safer but may differ from production\nClone       - Ideal but resource-intensive\n```\n\n#### Run Preliminary Scans\n\n- [ ] **Execute vulnerability scanners** - Find known issues first\n- [ ] **Fix obvious vulnerabilities** - Don't waste pentest time\n- [ ] **Document existing issues** - Share with testers\n\n**Common Pre-Scan Tools:**\n```bash\n# Network vulnerability scan\nnmap -sV --script vuln TARGET\n\n# Web vulnerability scan\nnikto -h http:\u002F\u002FTARGET\n```\n\n#### Review Security Policy\n\n- [ ] **Verify compliance requirements** - GDPR, PCI-DSS, HIPAA\n- [ ] **Document data handling rules** - Sensitive data procedures\n- [ ] **Confirm legal authorization** - Get written permission\n\n#### Notify Hosting Provider\n\n- [ ] **Check provider policies** - What testing is allowed?\n- [ ] **Submit authorization requests** - AWS, Azure, GCP requirements\n- [ ] **Document approvals** - Keep records\n\n**Cloud Provider Policies:**\n- AWS: https:\u002F\u002Faws.amazon.com\u002Fsecurity\u002Fpenetration-testing\u002F\n- Azure: https:\u002F\u002Fdocs.microsoft.com\u002Fsecurity\u002Fpentest\n- GCP: https:\u002F\u002Fcloud.google.com\u002Fsecurity\u002Foverview\n\n#### Freeze Developments\n\n- [ ] **Stop deployments during testing** - Maintain consistent environment\n- [ ] **Document current versions** - Record system states\n- [ ] **Avoid critical patches** - Unless security emergency\n\n### Phase 3: Expertise Selection\n\n#### Find Qualified Pentesters\n\n- [ ] **Seek recommendations** - Ask trusted sources\n- [ ] **Verify credentials** - OSCP, GPEN, CEH, CREST\n- [ ] **Check references** - Talk to previous clients\n- [ ] **Match expertise to scope** - Web, network, mobile specialists\n\n**Evaluation Criteria:**\n\n| Factor | Questions to Ask |\n|--------|------------------|\n| Experience | Years in field, similar projects |\n| Methodology | OWASP, PTES, custom approach |\n| Reporting | Sample reports, detail level |\n| Communication | Availability, update frequency |\n\n#### Define Methodology\n\n- [ ] **Select testing standard** - PTES, OWASP, NIST\n- [ ] **Determine access level** - Black box, gray box, white box\n- [ ] **Agree on techniques** - Manual vs. automated testing\n- [ ] **Set communication schedule** - Updates and escalation\n\n**Testing Approaches:**\n\n| Type | Access Level | Simulates |\n|------|-------------|-----------|\n| Black Box | No information | External attacker |\n| Gray Box | Partial access | Insider with limited access |\n| White Box | Full access | Insider\u002Fdetailed audit |\n\n#### Define Report Format\n\n- [ ] **Review sample reports** - Ensure quality meets needs\n- [ ] **Specify required sections** - Executive summary, technical details\n- [ ] **Request machine-readable output** - CSV, XML for tracking\n- [ ] **Agree on risk ratings** - CVSS, custom scale\n\n**Report Should Include:**\n- Executive summary for management\n- Technical findings with evidence\n- Risk ratings and prioritization\n- Remediation recommendations\n- Retesting guidance\n\n### Phase 4: Monitoring\n\n#### Implement Security Monitoring\n\n- [ ] **Deploy IDS\u002FIPS** - Intrusion detection systems\n- [ ] **Enable logging** - Comprehensive audit trails\n- [ ] **Configure SIEM** - Centralized log analysis\n- [ ] **Set up alerting** - Real-time notifications\n\n**Monitoring Tools:**\n```bash\n# Check security logs\ntail -f \u002Fvar\u002Flog\u002Fauth.log\ntail -f \u002Fvar\u002Flog\u002Fapache2\u002Faccess.log\n\n# Monitor network\ntcpdump -i eth0 -w capture.pcap\n```\n\n#### Configure Logging\n\n- [ ] **Centralize logs** - Aggregate from all systems\n- [ ] **Set retention periods** - Keep logs for analysis\n- [ ] **Enable detailed logging** - Application and system level\n- [ ] **Test log collection** - Verify all sources working\n\n**Key Logs to Monitor:**\n- Authentication events\n- Application errors\n- Network connections\n- File access\n- System changes\n\n#### Monitor Exception Tools\n\n- [ ] **Track error rates** - Unusual spikes indicate testing\n- [ ] **Brief operations team** - Distinguish testing from attacks\n- [ ] **Document baseline** - Normal vs. pentest activity\n\n#### Watch Security Tools\n\n- [ ] **Review IDS alerts** - Separate pentest from real attacks\n- [ ] **Monitor WAF logs** - Track blocked attempts\n- [ ] **Check endpoint protection** - Antivirus detections\n\n### Phase 5: Remediation\n\n#### Ensure Backups\n\n- [ ] **Verify backup integrity** - Test restoration\n- [ ] **Document recovery procedures** - Know how to restore\n- [ ] **Separate backup access** - Protect from testing\n\n#### Reserve Remediation Time\n\n- [ ] **Allocate team availability** - Post-pentest analysis\n- [ ] **Schedule fix implementation** - Address findings\n- [ ] **Plan verification testing** - Confirm fixes work\n\n#### Patch During Testing Policy\n\n- [ ] **Generally avoid patching** - Maintain consistent environment\n- [ ] **Exception for critical issues** - Security emergencies only\n- [ ] **Communicate changes** - Inform pentesters of any changes\n\n#### Cleanup Procedure\n\n- [ ] **Remove test artifacts** - Backdoors, scripts, files\n- [ ] **Delete test accounts** - Remove pentester access\n- [ ] **Restore configurations** - Return to original state\n- [ ] **Verify cleanup complete** - Audit all changes\n\n#### Schedule Next Pentest\n\n- [ ] **Determine frequency** - Annual, quarterly, after changes\n- [ ] **Consider continuous testing** - Bug bounty, ongoing assessments\n- [ ] **Budget for future tests** - Plan ahead\n\n**Testing Frequency Factors:**\n- Release frequency\n- Regulatory requirements\n- Risk tolerance\n- Past findings severity\n\n## Quick Reference\n\n### Pre-Pentest Checklist\n\n```\n□ Scope defined and documented\n□ Authorization obtained\n□ Environment prepared\n□ Hosting provider notified\n□ Team briefed\n□ Monitoring enabled\n□ Backups verified\n```\n\n### Post-Pentest Checklist\n\n```\n□ Report received and reviewed\n□ Findings prioritized\n□ Remediation assigned\n□ Fixes implemented\n□ Verification testing scheduled\n□ Environment cleaned up\n□ Next test scheduled\n```\n\n## Constraints\n\n- Production testing carries inherent risks\n- Budget limitations affect thoroughness\n- Time constraints may limit coverage\n- Tester expertise varies significantly\n- Findings become stale quickly\n\n## Examples\n\n### Example 1: Quick Scope Definition\n\n```markdown\n**Target:** Corporate web application (app.company.com)\n**Type:** Gray box web application pentest\n**Duration:** 5 business days\n**Excluded:** DoS testing, production database access\n**Access:** Standard user account provided\n```\n\n### Example 2: Monitoring Setup\n\n```bash\n# Enable comprehensive logging\nsudo systemctl restart rsyslog\nsudo systemctl restart auditd\n\n# Start packet capture\ntcpdump -i eth0 -w \u002Ftmp\u002Fpentest_capture.pcap &\n```\n\n## Troubleshooting\n\n| Issue | Solution |\n|-------|----------|\n| Scope creep | Document and require change approval |\n| Testing impacts production | Schedule off-hours, use staging |\n| Findings disputed | Provide detailed evidence, retest |\n| Remediation delayed | Prioritize by risk, set deadlines |\n| Budget exceeded | Define clear scope, fixed-price contracts |\n","# Pentest Checklist\n\n## Purpose\n\nProvide a comprehensive checklist for planning, executing, and following up on penetration tests. Ensure thorough preparation, proper scoping, and effective remediation of discovered vulnerabilities.\n\n## Inputs\u002FPrerequisites\n\n- Clear business objectives for testing\n- Target environment information\n- Budget and timeline constraints\n- Stakeholder contacts and authorization\n- Legal agreements and scope documents\n\n## Outputs\u002FDeliverables\n\n- Defined pentest scope and objectives\n- Prepared testing environment\n- Security monitoring data\n- Vulnerability findings report\n- Remediation plan and verification\n\n## Core Workflow\n\n### Phase 1: Scope Definition\n\n#### Define Objectives\n\n- [ ] **Clarify testing purpose** - Determine goals (find vulnerabilities, compliance, customer assurance)\n- [ ] **Validate pentest necessity** - Ensure penetration test is the right solution\n- [ ] **Align outcomes with objectives** - Define success criteria\n\n**Reference Questions:**\n- Why are you doing this pentest?\n- What specific outcomes do you expect?\n- What will you do with the findings?\n\n#### Know Your Test Types\n\n| Type | Purpose | Scope |\n|------|---------|-------|\n| External Pentest | Assess external attack surface | Public-facing systems |\n| Internal Pentest | Assess insider threat risk | Internal network |\n| Web Application | Find application vulnerabilities | Specific applications |\n| Social Engineering | Test human security | Employees, processes |\n| Red Team | Full adversary simulation | Entire organization |\n\n#### Enumerate Likely Threats\n\n- [ ] **Identify high-risk areas** - Where could damage occur?\n- [ ] **Assess data sensitivity** - What data could be compromised?\n- [ ] **Review legacy systems** - Old systems often have vulnerabilities\n- [ ] **Map critical assets** - Prioritize testing targets\n\n#### Define Scope\n\n- [ ] **List in-scope systems** - IPs, domains, applications\n- [ ] **Define out-of-scope items** - Systems to avoid\n- [ ] **Set testing boundaries** - What techniques are allowed?\n- [ ] **Document exclusions** - Third-party systems, production data\n\n#### Budget Planning\n\n| Factor | Consideration |\n|--------|---------------|\n| Asset Value | Higher value = higher investment |\n| Complexity | More systems = more time |\n| Depth Required | Thorough testing costs more |\n| Reputation Value | Brand-name firms cost more |\n\n**Budget Reality Check:**\n- Cheap pentests often produce poor results\n- Align budget with asset criticality\n- Consider ongoing vs. one-time testing\n\n### Phase 2: Environment Preparation\n\n#### Prepare Test Environment\n\n- [ ] **Production vs. staging decision** - Determine where to test\n- [ ] **Set testing limits** - No DoS on production\n- [ ] **Schedule testing window** - Minimize business impact\n- [ ] **Create test accounts** - Provide appropriate access levels\n\n**Environment Options:**\n```\nProduction  - Realistic but risky\nStaging     - Safer but may differ from production\nClone       - Ideal but resource-intensive\n```\n\n#### Run Preliminary Scans\n\n- [ ] **Execute vulnerability scanners** - Find known issues first\n- [ ] **Fix obvious vulnerabilities** - Don't waste pentest time\n- [ ] **Document existing issues** - Share with testers\n\n**Common Pre-Scan Tools:**\n```bash\n# Network vulnerability scan\nnmap -sV --script vuln TARGET\n\n# Web vulnerability scan\nnikto -h http:\u002F\u002FTARGET\n```\n\n#### Review Security Policy\n\n- [ ] **Verify compliance requirements** - GDPR, PCI-DSS, HIPAA\n- [ ] **Document data handling rules** - Sensitive data procedures\n- [ ] **Confirm legal authorization** - Get written permission\n\n#### Notify Hosting Provider\n\n- [ ] **Check provider policies** - What testing is allowed?\n- [ ] **Submit authorization requests** - AWS, Azure, GCP requirements\n- [ ] **Document approvals** - Keep records\n\n**Cloud Provider Policies:**\n- AWS: https:\u002F\u002Faws.amazon.com\u002Fsecurity\u002Fpenetration-testing\u002F\n- Azure: https:\u002F\u002Fdocs.microsoft.com\u002Fsecurity\u002Fpentest\n- GCP: https:\u002F\u002Fcloud.google.com\u002Fsecurity\u002Foverview\n\n#### Freeze Developments\n\n- [ ] **Stop deployments during testing** - Maintain consistent environment\n- [ ] **Document current versions** - Record system states\n- [ ] **Avoid critical patches** - Unless security emergency\n\n### Phase 3: Expertise Selection\n\n#### Find Qualified Pentesters\n\n- [ ] **Seek recommendations** - Ask trusted sources\n- [ ] **Verify credentials** - OSCP, GPEN, CEH, CREST\n- [ ] **Check references** - Talk to previous clients\n- [ ] **Match expertise to scope** - Web, network, mobile specialists\n\n**Evaluation Criteria:**\n\n| Factor | Questions to Ask |\n|--------|------------------|\n| Experience | Years in field, similar projects |\n| Methodology | OWASP, PTES, custom approach |\n| Reporting | Sample reports, detail level |\n| Communication | Availability, update frequency |\n\n#### Define Methodology\n\n- [ ] **Select testing standard** - PTES, OWASP, NIST\n- [ ] **Determine access level** - Black box, gray box, white box\n- [ ] **Agree on techniques** - Manual vs. automated testing\n- [ ] **Set communication schedule** - Updates and escalation\n\n**Testing Approaches:**\n\n| Type | Access Level | Simulates |\n|------|-------------|-----------|\n| Black Box | No information | External attacker |\n| Gray Box | Partial access | Insider with limited access |\n| White Box | Full access | Insider\u002Fdetailed audit |\n\n#### Define Report Format\n\n- [ ] **Review sample reports** - Ensure quality meets needs\n- [ ] **Specify required sections** - Executive summary, technical details\n- [ ] **Request machine-readable output** - CSV, XML for tracking\n- [ ] **Agree on risk ratings** - CVSS, custom scale\n\n**Report Should Include:**\n- Executive summary for management\n- Technical findings with evidence\n- Risk ratings and prioritization\n- Remediation recommendations\n- Retesting guidance\n\n### Phase 4: Monitoring\n\n#### Implement Security Monitoring\n\n- [ ] **Deploy IDS\u002FIPS** - Intrusion detection systems\n- [ ] **Enable logging** - Comprehensive audit trails\n- [ ] **Configure SIEM** - Centralized log analysis\n- [ ] **Set up alerting** - Real-time notifications\n\n**Monitoring Tools:**\n```bash\n# Check security logs\ntail -f \u002Fvar\u002Flog\u002Fauth.log\ntail -f \u002Fvar\u002Flog\u002Fapache2\u002Faccess.log\n\n# Monitor network\ntcpdump -i eth0 -w capture.pcap\n```\n\n#### Configure Logging\n\n- [ ] **Centralize logs** - Aggregate from all systems\n- [ ] **Set retention periods** - Keep logs for analysis\n- [ ] **Enable detailed logging** - Application and system level\n- [ ] **Test log collection** - Verify all sources working\n\n**Key Logs to Monitor:**\n- Authentication events\n- Application errors\n- Network connections\n- File access\n- System changes\n\n#### Monitor Exception Tools\n\n- [ ] **Track error rates** - Unusual spikes indicate testing\n- [ ] **Brief operations team** - Distinguish testing from attacks\n- [ ] **Document baseline** - Normal vs. pentest activity\n\n#### Watch Security Tools\n\n- [ ] **Review IDS alerts** - Separate pentest from real attacks\n- [ ] **Monitor WAF logs** - Track blocked attempts\n- [ ] **Check endpoint protection** - Antivirus detections\n\n### Phase 5: Remediation\n\n#### Ensure Backups\n\n- [ ] **Verify backup integrity** - Test restoration\n- [ ] **Document recovery procedures** - Know how to restore\n- [ ] **Separate backup access** - Protect from testing\n\n#### Reserve Remediation Time\n\n- [ ] **Allocate team availability** - Post-pentest analysis\n- [ ] **Schedule fix implementation** - Address findings\n- [ ] **Plan verification testing** - Confirm fixes work\n\n#### Patch During Testing Policy\n\n- [ ] **Generally avoid patching** - Maintain consistent environment\n- [ ] **Exception for critical issues** - Security emergencies only\n- [ ] **Communicate changes** - Inform pentesters of any changes\n\n#### Cleanup Procedure\n\n- [ ] **Remove test artifacts** - Backdoors, scripts, files\n- [ ] **Delete test accounts** - Remove pentester access\n- [ ] **Restore configurations** - Return to original state\n- [ ] **Verify cleanup complete** - Audit all changes\n\n#### Schedule Next Pentest\n\n- [ ] **Determine frequency** - Annual, quarterly, after changes\n- [ ] **Consider continuous testing** - Bug bounty, ongoing assessments\n- [ ] **Budget for future tests** - Plan ahead\n\n**Testing Frequency Factors:**\n- Release frequency\n- Regulatory requirements\n- Risk tolerance\n- Past findings severity\n\n## Quick Reference\n\n### Pre-Pentest Checklist\n\n```\n□ Scope defined and documented\n□ Authorization obtained\n□ Environment prepared\n□ Hosting provider notified\n□ Team briefed\n□ Monitoring enabled\n□ Backups verified\n```\n\n### Post-Pentest Checklist\n\n```\n□ Report received and reviewed\n□ Findings prioritized\n□ Remediation assigned\n□ Fixes implemented\n□ Verification testing scheduled\n□ Environment cleaned up\n□ Next test scheduled\n```\n\n## Constraints\n\n- Production testing carries inherent risks\n- Budget limitations affect thoroughness\n- Time constraints may limit coverage\n- Tester expertise varies significantly\n- Findings become stale quickly\n\n## Examples\n\n### Example 1: Quick Scope Definition\n\n```markdown\n**Target:** Corporate web application (app.company.com)\n**Type:** Gray box web application pentest\n**Duration:** 5 business days\n**Excluded:** DoS testing, production database access\n**Access:** Standard user account provided\n```\n\n### Example 2: Monitoring Setup\n\n```bash\n# Enable comprehensive logging\nsudo systemctl restart rsyslog\nsudo systemctl restart auditd\n\n# Start packet capture\ntcpdump -i eth0 -w \u002Ftmp\u002Fpentest_capture.pcap &\n```\n\n## Troubleshooting\n\n| Issue | Solution |\n|-------|----------|\n| Scope creep | Document and require change approval |\n| Testing impacts production | Schedule off-hours, use staging |\n| Findings disputed | Provide detailed evidence, retest |\n| Remediation delayed | Prioritize by risk, set deadlines |\n| Budget exceeded | Define clear scope, fixed-price contracts |\n",{"name":5,"metadata":24,"description":7},{"author":25,"version":26},"zebbern","1.1","main","f27dd0e6c87efa56cfdea304aa3e89e63c02711b","plugins\u002Fskills-security\u002Fskills\u002Fpentest-checklist","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills","https:\u002F\u002Fgithub.com\u002Fsharepointoscar","Author | DevOps Practitioner | Docker | Terraform | Kubernetes | Jenkins X  | AWS | GCP | Azure and SP Veteran (since code-name Tahoe)","2026-11-11 12:44:52",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add sharepointoscar\u002Fagent-workflow-skills --skill pentest-checklist",{"tool":40,"command":41},"bunx","bunx skills add sharepointoscar\u002Fagent-workflow-skills --skill pentest-checklist",{"tool":43,"command":44},"pnpm","pnpm dlx skills add sharepointoscar\u002Fagent-workflow-skills --skill pentest-checklist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-security\u002Fskills\u002Fpentest-checklist\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M79FQNYDNR7TYQAM5061GVKR","web-performance-optimization","Optimize website and web application performance including loading speed, Core Web Vitals, bundle size, caching strategies, and runtime performance","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fweb-performance-optimization\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M79FQK396EEGX40QA7B9S404","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M79FQFK4GJCG8HVRG8JQF4QH","wcag-audit-patterns","Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fwcag-audit-patterns\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"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":76,"publishedAt":19},"01M79FQ7WRQXC4D20Q2HTBMDG7","ui-ux-pro-max","UI\u002FUX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn\u002Fui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI\u002FUX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn\u002Fui MCP for component search and examples.","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fui-ux-pro-max\u002FSKILL.md",[],[],{"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":83,"publishedAt":19},"01M79FPZC11BPBWDCVK2TER0RC","stitch-ui-design","Expert guide for creating effective prompts for Google Stitch AI UI design tool. Use when user wants to design UI\u002FUX in Stitch, create app interfaces, generate mobile\u002Fweb designs, or needs help crafting Stitch prompts. Covers prompt structure, specificity techniques, iteration strategies, and design-to-code workflows for Stitch by Google.","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fstitch-ui-design\u002FSKILL.md",[],[],{"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":19},"01M79FPTMMM3C57JN25RTRX2HR","scroll-experience","Expert in building immersive scroll-driven experiences - parallax storytelling, scroll animations, interactive narratives, and cinematic web experiences. Like NY Times interactives, Apple product pages, and award-winning web experiences. Makes websites feel like experiences, not just pages. Use when: scroll animation, parallax, scroll storytelling, interactive story, cinematic website.","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fscroll-experience\u002FSKILL.md",[],[]]