[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PF1Q2P6MM4FASTGR7VPBHQ":3,"skill-same:01M6PF1Q2P6MM4FASTGR7VPBHQ":93},{"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":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M6PF1Q2P6MM4FASTGR7VPBHQ","validating-pci-dss-compliance",null,"This skill uses the pci-dss-validator plugin to assess codebases and infrastructure configurations for compliance with the Payment Card Industry Data Security Standard (PCI DSS). It identifies potential vulnerabilities and deviations from PCI DSS requirements. Use this skill when the user requests to \"validate PCI compliance\", \"check PCI DSS\", \"assess PCI security\", or \"review PCI standards\" for a given project or configuration. It helps ensure that systems handling cardholder data meet the necessary security controls.","sandraschi\u002Fdocumentation-mcp","sandraschi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F34750307?v=4","01M6C42H9WE5EC9CK3N5RGZP8S","Sandra Schipal","01M6PE1X2FZP8KR5GANPPFTHA8",2,"MIT","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fsecurity\u002Fpci-dss-validator\u002Fskills\u002Fpci-dss-validator\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"pci","compliance","pci dss compliance","Validating PCI DSS Compliance","dss","project","Meet","for","validator","assess","controls","card","review","pci compliance","standards","use","pci-dss","data","infrastructure","security","2026-11-10 10:12:30",false,"---\nname: validating-pci-dss-compliance\ndescription: |\n  This skill uses the pci-dss-validator plugin to assess codebases and infrastructure configurations for compliance with the Payment Card Industry Data Security Standard (PCI DSS). It identifies potential vulnerabilities and deviations from PCI DSS requirements. Use this skill when the user requests to \"validate PCI compliance\", \"check PCI DSS\", \"assess PCI security\", or \"review PCI standards\" for a given project or configuration. It helps ensure that systems handling cardholder data meet the necessary security controls.\n---\n\n## Overview\n\nThis skill streamlines PCI DSS compliance checks by automatically analyzing code and configurations. It flags potential issues, allowing for proactive remediation and improved security posture. It is particularly useful for developers, security engineers, and compliance officers.\n\n## How It Works\n\n1. **Analyze the Target**: The skill identifies the codebase, configuration files, or infrastructure resources to be evaluated.\n2. **Run PCI DSS Validation**: The pci-dss-validator plugin scans the target for potential PCI DSS violations.\n3. **Generate Report**: The skill compiles a report detailing any identified vulnerabilities or non-compliant configurations, along with remediation recommendations.\n\n## When to Use This Skill\n\nThis skill activates when you need to:\n- Evaluate a new application or system for PCI DSS compliance before deployment.\n- Periodically assess existing systems to maintain PCI DSS compliance.\n- Investigate potential security vulnerabilities related to PCI DSS.\n\n## Examples\n\n### Example 1: Validating a Web Application\n\nUser request: \"Validate PCI compliance for my e-commerce web application.\"\n\nThe skill will:\n1. Identify the source code repository for the web application.\n2. Run the pci-dss-validator plugin against the codebase.\n3. Generate a report highlighting any PCI DSS violations found in the code.\n\n### Example 2: Checking Infrastructure Configuration\n\nUser request: \"Check PCI DSS compliance of my AWS infrastructure.\"\n\nThe skill will:\n1. Access the AWS configuration files (e.g., Terraform, CloudFormation).\n2. Execute the pci-dss-validator plugin against the infrastructure configuration.\n3. Produce a report outlining any non-compliant configurations in the AWS environment.\n\n## Best Practices\n\n- **Scope Definition**: Clearly define the scope of the PCI DSS assessment to ensure accurate and relevant results.\n- **Regular Assessments**: Conduct regular PCI DSS assessments to maintain continuous compliance.\n- **Remediation Tracking**: Track and document all remediation efforts to demonstrate ongoing commitment to security.\n\n## Integration\n\nThis skill can be integrated with other security tools and plugins to provide a comprehensive security assessment. For example, it can be used in conjunction with static analysis tools to identify vulnerabilities in code before it is deployed. It can also be integrated with infrastructure-as-code tools to ensure that infrastructure is compliant with PCI DSS from the start.\n","## Overview\n\nThis skill streamlines PCI DSS compliance checks by automatically analyzing code and configurations. It flags potential issues, allowing for proactive remediation and improved security posture. It is particularly useful for developers, security engineers, and compliance officers.\n\n## How It Works\n\n1. **Analyze the Target**: The skill identifies the codebase, configuration files, or infrastructure resources to be evaluated.\n2. **Run PCI DSS Validation**: The pci-dss-validator plugin scans the target for potential PCI DSS violations.\n3. **Generate Report**: The skill compiles a report detailing any identified vulnerabilities or non-compliant configurations, along with remediation recommendations.\n\n## When to Use This Skill\n\nThis skill activates when you need to:\n- Evaluate a new application or system for PCI DSS compliance before deployment.\n- Periodically assess existing systems to maintain PCI DSS compliance.\n- Investigate potential security vulnerabilities related to PCI DSS.\n\n## Examples\n\n### Example 1: Validating a Web Application\n\nUser request: \"Validate PCI compliance for my e-commerce web application.\"\n\nThe skill will:\n1. Identify the source code repository for the web application.\n2. Run the pci-dss-validator plugin against the codebase.\n3. Generate a report highlighting any PCI DSS violations found in the code.\n\n### Example 2: Checking Infrastructure Configuration\n\nUser request: \"Check PCI DSS compliance of my AWS infrastructure.\"\n\nThe skill will:\n1. Access the AWS configuration files (e.g., Terraform, CloudFormation).\n2. Execute the pci-dss-validator plugin against the infrastructure configuration.\n3. Produce a report outlining any non-compliant configurations in the AWS environment.\n\n## Best Practices\n\n- **Scope Definition**: Clearly define the scope of the PCI DSS assessment to ensure accurate and relevant results.\n- **Regular Assessments**: Conduct regular PCI DSS assessments to maintain continuous compliance.\n- **Remediation Tracking**: Track and document all remediation efforts to demonstrate ongoing commitment to security.\n\n## Integration\n\nThis skill can be integrated with other security tools and plugins to provide a comprehensive security assessment. For example, it can be used in conjunction with static analysis tools to identify vulnerabilities in code before it is deployed. It can also be integrated with infrastructure-as-code tools to ensure that infrastructure is compliant with PCI DSS from the start.\n",{"name":5,"description":7},"master","be156301b65e301887f327d08190ed4f17ba08d2","docs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fsecurity\u002Fpci-dss-validator\u002Fskills\u002Fpci-dss-validator",0,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp","https:\u002F\u002Fgithub.com\u002Fsandraschi","2026-11-09 11:03:27",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add sandraschi\u002Fdocumentation-mcp --skill validating-pci-dss-compliance",{"tool":67,"command":68},"bunx","bunx skills add sandraschi\u002Fdocumentation-mcp --skill validating-pci-dss-compliance",{"tool":70,"command":71},"pnpm","pnpm dlx skills add sandraschi\u002Fdocumentation-mcp --skill validating-pci-dss-compliance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fsecurity\u002Fpci-dss-validator\u002Fskills\u002Fpci-dss-validator\u002FSKILL.md",true,[75,81,87],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"assets\u002FREADME.md","ASSET","资产文件",515,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fsecurity\u002Fpci-dss-validator\u002Fskills\u002Fpci-dss-validator\u002Fassets\u002FREADME.md",{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002FREADME.md","REFERENCE","参考文档",759,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fsecurity\u002Fpci-dss-validator\u002Fskills\u002Fpci-dss-validator\u002Freferences\u002FREADME.md",{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002FREADME.md","SCRIPT","脚本",628,"https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fnot-mcp-related\u002Fclaude-skills\u002Ftemp\u002Fcode-plugins\u002Fplugins\u002Fsecurity\u002Fpci-dss-validator\u002Fskills\u002Fpci-dss-validator\u002Fscripts\u002FREADME.md",[94,115,141,151,176,202],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":104,"publishedAt":49},"01M6PFAWAHEJJCKKVNXEWNK87W","Docs Research","Use MCP Central Docs server to search, ask, and retrieve documentation (FastMCP, standards, packaging).","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fsrc\u002Fdocs_mcp\u002Fskills\u002Fdocs-research\u002FSKILL.md",[100,103],{"categoryNo":101,"categoryName":102,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[105,106,107,43,44,108,109,110,111,112,113,114],"docs research","docs","research","packaging","ask","server","search","fastmcp","documentation","MCP",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":49},"01M6PFAN4DAENMY574Q7Q3CB3H","wrappee-drift","Read-only, single-repo audit of a repo's tool coverage against the software it wraps (its current real API\u002Fdocs, not training-data memory) and against comparable\u002Fcompeting wrappers. Trigger when the user says \"wrappee drift\" followed by a repo name, \"capability audit\" followed by a repo name, or asks whether a repo is missing features the wrapped software or a competitor now has. Always scoped to one named repo per invocation -- never trigger this fleet-wide or unprompted; that is explicitly against the SOP. Do NOT trigger for internal fleet-standard compliance (that is drift-scan) or strategic worth\u002Farchive decisions (that is quality-check) -- this is specifically about the gap between the repo's tool list and the wrapped software's\u002Fcompetitors' actual current capabilities.","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwrappee-drift\u002FSKILL.md",[],[122,123,124,46,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140],"drift","wrappee drift","api","audit","capabilities","training","memory","features","repo audit","competitors","fleet","now","software","tool list","only","never","coverage","list","read",{"skillNo":142,"name":143,"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":144,"categories":145,"keywords":150,"publishedAt":49},"01M6PFADA3X031SK3W3T6X0N6H","modules","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwindsurf-mcp-standards\u002Fmodules\u002FSKILL.md",[146,149],{"categoryNo":147,"categoryName":148,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[143],{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":161,"publishedAt":49},"01M6PFA8YA029N68TW0X31FB1W","mcp-standards","Use when developing MCP servers to access comprehensive standards for scaffolding, packaging, sampling, documentation, testing, error handling, monitoring, and CI\u002FCD workflows.","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwindsurf-mcp-standards\u002FSKILL.md",[157,160],{"categoryNo":158,"categoryName":159,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[162,114,43,44,163,164,165,166,167,168,36,169,170,171,172,173,113,174,175,108],"mcp standards","monitoring","sampling","scaffolding","servers","cd","error","CI\u002FCD","access","ci","mcp servers","error handling","workflows","testing",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":184,"publishedAt":49},"01M6PFA1XX344WX57B0DJZY94Q","webapp-cua-test","Run the pre-Tauri CUA click-through test (real browser, dev stack, OCR \"Connected\" wait, sidebar nav walk) for a fleet MCP server repo under D:\\Dev\\repos. Trigger when the user says \"cua webapp test\" or \"webapp clickthrough\" followed by a repo name, asks for an e2e click-through of a webapp, or asks whether a webapp boots and connects in a real browser. Not for the installed NSIS app (that is the nsis-build skill \u002F cua-nsis-test) and not for DOM assertions (Playwright), and not for hunting fake data or dead buttons (fakefind).","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fwebapp-cua-test\u002FSKILL.md",[182,183],{"categoryNo":158,"categoryName":159,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[185,186,187,188,189,114,190,191,192,36,193,194,195,196,197,198,199,200,110,201],"webapp","test","webapp cua test","playwright","mcp server","dev","dom","assertions","trigger","click","app","tauri","repo","stack","e2e","ocr","browser",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":209,"publishedAt":49},"01M6PF9WYF6NWJR7WVN38TT0WH","ship","Final release gate for a fleet MCP server repo under D:\\Dev\\repos -- run all quality gates, build the release artifact, verify it, commit, push, and cut a GitHub release. Trigger this whenever the user says \"ship it\", \"ship\" followed by a repo name, \"release\" followed by a repo name, or asks to finalize and publish work that's already been done in a repo. This is the terminal step after assfix\u002Fnsis-build, not a substitute for them -- if the repo hasn't been assessed recently, say so before shipping rather than shipping blind.","https:\u002F\u002Fgithub.com\u002Fsandraschi\u002Fdocumentation-mcp\u002Fblob\u002Fmaster\u002Fdocs\u002Fskills\u002Fship\u002FSKILL.md",[208],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[204,197,36,193,210,211,212,213,214,215,216,110,217,190,218,219,220,189,221,114],"gates","ship it","artifact","done","say","work","publish","push","shipping","quality gates","commit","github"]