[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EX7454STRXRBPE9F89B5QK":3,"skill-same:01M7EX7454STRXRBPE9F89B5QK":52},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M7EX7454STRXRBPE9F89B5QK","aws-cdk-development",null,"AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript\u002FPython.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Faws-cdk-development\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: aws-cdk-development\ndescription: \"AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript\u002FPython.\"\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fzxkane\u002Faws-skills\u002Ftree\u002Fmain\u002Fplugins\u002Faws-iac\u002Fskills\u002Faws-cdk-development\nsource_repo: zxkane\u002Faws-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fzxkane\u002Faws-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# AWS CDK Development\n\nThis skill provides comprehensive guidance for developing AWS infrastructure using the Cloud Development Kit (CDK), with integrated MCP servers for accessing latest AWS knowledge and CDK utilities.\n\n## AWS Documentation Requirement\n\nAlways verify AWS facts using MCP tools (`mcp__aws-mcp__*` or `mcp__*awsdocs*__*`) before answering. The `aws-mcp-setup` dependency is auto-loaded — if MCP tools are unavailable, guide the user through that skill's setup flow.\n\n## CDK-Specific MCP Guidance\n\nAWS Labs replaced the dedicated CDK MCP server (`awslabs.cdk-mcp-server`) with the broader `awslabs.aws-iac-mcp-server`, which covers CDK alongside CloudFormation and other AWS infrastructure-as-code workflows.\n\nFor CDK construct lookups, best-practice recommendations, and pattern guidance, install `awslabs.aws-iac-mcp-server`. It ships in the `deploy-on-aws` plugin from `awslabs\u002Fagent-plugins`, or can be registered directly with `claude mcp add aws-iac uvx awslabs.aws-iac-mcp-server@latest`.\n\n**When to reach for it**:\n- CDK construct recommendations and API lookups\n- CDK and CloudFormation best-practice patterns\n- Validation of synthesized templates\n- Cross-resource configuration guidance\n\n## When to Use This Skill\n\nUse this skill when:\n- Creating new CDK stacks or constructs\n- Refactoring existing CDK infrastructure\n- Implementing Lambda functions within CDK\n- Following AWS CDK best practices\n- Validating CDK stack configurations before deployment\n- Verifying AWS service capabilities and regional availability\n\n## Core CDK Principles\n\n### Resource Naming\n\n**CRITICAL**: Do NOT explicitly specify resource names when they are optional in CDK constructs.\n\n**Why**: CDK-generated names enable:\n- **Reusable patterns**: Deploy the same construct\u002Fpattern multiple times without conflicts\n- **Parallel deployments**: Multiple stacks can deploy simultaneously in the same region\n- **Cleaner shared logic**: Patterns and shared code can be initialized multiple times without name collision\n- **Stack isolation**: Each stack gets uniquely identified resources automatically\n\n**Pattern**: Let CDK generate unique names automatically using CloudFormation's naming mechanism.\n\n```typescript\n\u002F\u002F ❌ BAD - Explicit naming prevents reusability and parallel deployments\nnew lambda.Function(this, 'MyFunction', {\n  functionName: 'my-lambda',  \u002F\u002F Avoid this\n  \u002F\u002F ...\n});\n\n\u002F\u002F ✅ GOOD - Let CDK generate unique names\nnew lambda.Function(this, 'MyFunction', {\n  \u002F\u002F No functionName specified - CDK generates: StackName-MyFunctionXXXXXX\n  \u002F\u002F ...\n});\n```\n\n**Security Note**: For different environments (dev, staging, prod), follow AWS Security Pillar best practices by using separate AWS accounts rather than relying on resource naming within a single account. Account-level isolation provides stronger security boundaries.\n\n### Lambda Function Development\n\nUse the appropriate Lambda construct based on runtime:\n\n**TypeScript\u002FJavaScript**: Use `@aws-cdk\u002Faws-lambda-nodejs`\n```typescript\nimport { NodejsFunction } from 'aws-cdk-lib\u002Faws-lambda-nodejs';\n\nnew NodejsFunction(this, 'MyFunction', {\n  entry: 'lambda\u002Fhandler.ts',\n  handler: 'handler',\n  \u002F\u002F Automatically handles bundling, dependencies, and transpilation\n});\n```\n\n**Python**: Use `@aws-cdk\u002Faws-lambda-python`\n```typescript\nimport { PythonFunction } from '@aws-cdk\u002Faws-lambda-python-alpha';\n\nnew PythonFunction(this, 'MyFunction', {\n  entry: 'lambda',\n  index: 'handler.py',\n  handler: 'handler',\n  \u002F\u002F Automatically handles dependencies and packaging\n});\n```\n\n**Benefits**:\n- Automatic bundling and dependency management\n- Transpilation handled automatically\n- No manual packaging required\n- Consistent deployment patterns\n\n### Pre-Deployment Validation\n\nUse a **multi-layer validation strategy** for comprehensive CDK quality checks:\n\n#### Layer 1: Real-Time IDE Feedback (Recommended)\n\n**For TypeScript\u002FJavaScript projects**:\n\nInstall [cdk-nag](https:\u002F\u002Fgithub.com\u002Fcdklabs\u002Fcdk-nag) for synthesis-time validation:\n```bash\nnpm install --save-dev cdk-nag\n```\n\nAdd to your CDK app:\n```typescript\nimport { Aspects } from 'aws-cdk-lib';\nimport { AwsSolutionsChecks } from 'cdk-nag';\n\nconst app = new App();\nAspects.of(app).add(new AwsSolutionsChecks());\n```\n\n**Optional - VS Code users**: Install [CDK NAG Validator extension](https:\u002F\u002Fmarketplace.visualstudio.com\u002Fitems?itemName=alphacrack.cdk-nag-validator) for faster feedback on file save.\n\n**For Python\u002FJava\u002FC#\u002FGo projects**: cdk-nag is available in all CDK languages and provides the same synthesis-time validation.\n\n#### Layer 2: Synthesis-Time Validation (Required)\n\n1. **Synthesis with cdk-nag**: Validate stack with comprehensive rules\n   ```bash\n   cdk synth  # cdk-nag runs automatically via Aspects\n   ```\n\n2. **Suppress legitimate exceptions** with documented reasons:\n   ```typescript\n   import { NagSuppressions } from 'cdk-nag';\n\n   \u002F\u002F Document WHY the exception is needed\n   NagSuppressions.addResourceSuppressions(resource, [\n     {\n       id: 'AwsSolutions-L1',\n       reason: 'Lambda@Edge requires specific runtime for CloudFront compatibility'\n     }\n   ]);\n   ```\n\n#### Layer 3: Pre-Commit Safety Net\n\n1. **Build**: Ensure compilation succeeds\n   ```bash\n   npm run build  # or language-specific build command\n   ```\n\n2. **Tests**: Run unit and integration tests\n   ```bash\n   npm test  # or pytest, mvn test, etc.\n   ```\n\n3. **Validation Script**: Meta-level checks\n   ```bash\n   .\u002Fscripts\u002Fvalidate-stack.sh\n   ```\n\nThe validation script now focuses on:\n- Language detection\n- Template size and resource count analysis\n- Synthesis success verification\n- (Note: Detailed anti-pattern checks are handled by cdk-nag)\n\n## Workflow Guidelines\n\n### Development Workflow\n\n1. **Design**: Plan infrastructure resources and relationships\n2. **Verify AWS Services**: Use AWS Documentation MCP to confirm service availability and features\n   - Check regional availability for all required services\n   - Verify service limits and quotas\n   - Confirm latest API specifications\n3. **Implement**: Write CDK constructs following best practices\n   - Use CDK MCP server for construct recommendations\n   - Reference CDK best practices via MCP tools\n4. **Validate**: Run pre-deployment checks (see above)\n5. **Synthesize**: Generate CloudFormation templates\n6. **Review**: Examine synthesized templates for correctness\n7. **Deploy**: Deploy to target environment\n8. **Verify**: Confirm resources are created correctly\n\n### Stack Organization\n\n- Use nested stacks for complex applications\n- Separate concerns into logical construct boundaries\n- Export values that other stacks may need\n- Use CDK context for environment-specific configuration\n\n### Testing Strategy\n\n- Unit test individual constructs\n- Integration test stack synthesis\n- Snapshot test CloudFormation templates\n- Validate resource properties and relationships\n\n## Using MCP Servers Effectively\n\n### When to Use AWS Documentation MCP\n\n**Always verify before implementing**:\n- New AWS service features or configurations\n- Service availability in target regions\n- API parameter specifications\n- Service limits and quotas\n- Security best practices for AWS services\n\n**Example scenarios**:\n- \"Check if Lambda supports Python 3.13 runtime\"\n- \"Verify DynamoDB is available in eu-south-2\"\n- \"What are the current Lambda timeout limits?\"\n- \"Get latest S3 encryption options\"\n\n### When to Use CDK MCP Server\n\n**Leverage for CDK-specific guidance**:\n- CDK construct selection and usage\n- CDK API parameter options\n- CDK best practice patterns\n- Construct property configurations\n- CDK-specific optimizations\n\n**Example scenarios**:\n- \"What's the recommended CDK construct for API Gateway REST API?\"\n- \"How to configure NodejsFunction bundling options?\"\n- \"Best practices for CDK stack organization\"\n- \"CDK construct for DynamoDB with auto-scaling\"\n\n### MCP Usage Best Practices\n\n1. **Verify First**: Always check AWS Documentation MCP before implementing new features\n2. **Regional Validation**: Check service availability in target deployment regions\n3. **CDK Guidance**: Use CDK MCP for construct-specific recommendations\n4. **Stay Current**: MCP servers provide latest information beyond knowledge cutoff\n5. **Combine Sources**: Use both skill patterns and MCP servers for comprehensive guidance\n\n## CDK Patterns Reference\n\nFor detailed CDK patterns, anti-patterns, and architectural guidance, refer to the comprehensive reference:\n\n**File**: `references\u002Fcdk-patterns.md`\n\nThis reference includes:\n- Common CDK patterns and their use cases\n- Anti-patterns to avoid\n- Security best practices\n- Cost optimization strategies\n- Performance considerations\n\n## Additional Resources\n\n- **Validation Script**: `scripts\u002Fvalidate-stack.sh` - Pre-deployment validation\n- **CDK Patterns**: `references\u002Fcdk-patterns.md` - Detailed pattern library\n- **AWS Documentation MCP**: Integrated for latest AWS information\n- **CDK MCP Server**: Integrated for CDK-specific guidance\n\n## GitHub Actions Integration\n\nWhen GitHub Actions workflow files exist in the repository, ensure all checks defined in `.github\u002Fworkflows\u002F` pass before committing. This prevents CI\u002FCD failures and maintains code quality standards.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# AWS CDK Development\n\nThis skill provides comprehensive guidance for developing AWS infrastructure using the Cloud Development Kit (CDK), with integrated MCP servers for accessing latest AWS knowledge and CDK utilities.\n\n## AWS Documentation Requirement\n\nAlways verify AWS facts using MCP tools (`mcp__aws-mcp__*` or `mcp__*awsdocs*__*`) before answering. The `aws-mcp-setup` dependency is auto-loaded — if MCP tools are unavailable, guide the user through that skill's setup flow.\n\n## CDK-Specific MCP Guidance\n\nAWS Labs replaced the dedicated CDK MCP server (`awslabs.cdk-mcp-server`) with the broader `awslabs.aws-iac-mcp-server`, which covers CDK alongside CloudFormation and other AWS infrastructure-as-code workflows.\n\nFor CDK construct lookups, best-practice recommendations, and pattern guidance, install `awslabs.aws-iac-mcp-server`. It ships in the `deploy-on-aws` plugin from `awslabs\u002Fagent-plugins`, or can be registered directly with `claude mcp add aws-iac uvx awslabs.aws-iac-mcp-server@latest`.\n\n**When to reach for it**:\n- CDK construct recommendations and API lookups\n- CDK and CloudFormation best-practice patterns\n- Validation of synthesized templates\n- Cross-resource configuration guidance\n\n## When to Use This Skill\n\nUse this skill when:\n- Creating new CDK stacks or constructs\n- Refactoring existing CDK infrastructure\n- Implementing Lambda functions within CDK\n- Following AWS CDK best practices\n- Validating CDK stack configurations before deployment\n- Verifying AWS service capabilities and regional availability\n\n## Core CDK Principles\n\n### Resource Naming\n\n**CRITICAL**: Do NOT explicitly specify resource names when they are optional in CDK constructs.\n\n**Why**: CDK-generated names enable:\n- **Reusable patterns**: Deploy the same construct\u002Fpattern multiple times without conflicts\n- **Parallel deployments**: Multiple stacks can deploy simultaneously in the same region\n- **Cleaner shared logic**: Patterns and shared code can be initialized multiple times without name collision\n- **Stack isolation**: Each stack gets uniquely identified resources automatically\n\n**Pattern**: Let CDK generate unique names automatically using CloudFormation's naming mechanism.\n\n```typescript\n\u002F\u002F ❌ BAD - Explicit naming prevents reusability and parallel deployments\nnew lambda.Function(this, 'MyFunction', {\n  functionName: 'my-lambda',  \u002F\u002F Avoid this\n  \u002F\u002F ...\n});\n\n\u002F\u002F ✅ GOOD - Let CDK generate unique names\nnew lambda.Function(this, 'MyFunction', {\n  \u002F\u002F No functionName specified - CDK generates: StackName-MyFunctionXXXXXX\n  \u002F\u002F ...\n});\n```\n\n**Security Note**: For different environments (dev, staging, prod), follow AWS Security Pillar best practices by using separate AWS accounts rather than relying on resource naming within a single account. Account-level isolation provides stronger security boundaries.\n\n### Lambda Function Development\n\nUse the appropriate Lambda construct based on runtime:\n\n**TypeScript\u002FJavaScript**: Use `@aws-cdk\u002Faws-lambda-nodejs`\n```typescript\nimport { NodejsFunction } from 'aws-cdk-lib\u002Faws-lambda-nodejs';\n\nnew NodejsFunction(this, 'MyFunction', {\n  entry: 'lambda\u002Fhandler.ts',\n  handler: 'handler',\n  \u002F\u002F Automatically handles bundling, dependencies, and transpilation\n});\n```\n\n**Python**: Use `@aws-cdk\u002Faws-lambda-python`\n```typescript\nimport { PythonFunction } from '@aws-cdk\u002Faws-lambda-python-alpha';\n\nnew PythonFunction(this, 'MyFunction', {\n  entry: 'lambda',\n  index: 'handler.py',\n  handler: 'handler',\n  \u002F\u002F Automatically handles dependencies and packaging\n});\n```\n\n**Benefits**:\n- Automatic bundling and dependency management\n- Transpilation handled automatically\n- No manual packaging required\n- Consistent deployment patterns\n\n### Pre-Deployment Validation\n\nUse a **multi-layer validation strategy** for comprehensive CDK quality checks:\n\n#### Layer 1: Real-Time IDE Feedback (Recommended)\n\n**For TypeScript\u002FJavaScript projects**:\n\nInstall [cdk-nag](https:\u002F\u002Fgithub.com\u002Fcdklabs\u002Fcdk-nag) for synthesis-time validation:\n```bash\nnpm install --save-dev cdk-nag\n```\n\nAdd to your CDK app:\n```typescript\nimport { Aspects } from 'aws-cdk-lib';\nimport { AwsSolutionsChecks } from 'cdk-nag';\n\nconst app = new App();\nAspects.of(app).add(new AwsSolutionsChecks());\n```\n\n**Optional - VS Code users**: Install [CDK NAG Validator extension](https:\u002F\u002Fmarketplace.visualstudio.com\u002Fitems?itemName=alphacrack.cdk-nag-validator) for faster feedback on file save.\n\n**For Python\u002FJava\u002FC#\u002FGo projects**: cdk-nag is available in all CDK languages and provides the same synthesis-time validation.\n\n#### Layer 2: Synthesis-Time Validation (Required)\n\n1. **Synthesis with cdk-nag**: Validate stack with comprehensive rules\n   ```bash\n   cdk synth  # cdk-nag runs automatically via Aspects\n   ```\n\n2. **Suppress legitimate exceptions** with documented reasons:\n   ```typescript\n   import { NagSuppressions } from 'cdk-nag';\n\n   \u002F\u002F Document WHY the exception is needed\n   NagSuppressions.addResourceSuppressions(resource, [\n     {\n       id: 'AwsSolutions-L1',\n       reason: 'Lambda@Edge requires specific runtime for CloudFront compatibility'\n     }\n   ]);\n   ```\n\n#### Layer 3: Pre-Commit Safety Net\n\n1. **Build**: Ensure compilation succeeds\n   ```bash\n   npm run build  # or language-specific build command\n   ```\n\n2. **Tests**: Run unit and integration tests\n   ```bash\n   npm test  # or pytest, mvn test, etc.\n   ```\n\n3. **Validation Script**: Meta-level checks\n   ```bash\n   .\u002Fscripts\u002Fvalidate-stack.sh\n   ```\n\nThe validation script now focuses on:\n- Language detection\n- Template size and resource count analysis\n- Synthesis success verification\n- (Note: Detailed anti-pattern checks are handled by cdk-nag)\n\n## Workflow Guidelines\n\n### Development Workflow\n\n1. **Design**: Plan infrastructure resources and relationships\n2. **Verify AWS Services**: Use AWS Documentation MCP to confirm service availability and features\n   - Check regional availability for all required services\n   - Verify service limits and quotas\n   - Confirm latest API specifications\n3. **Implement**: Write CDK constructs following best practices\n   - Use CDK MCP server for construct recommendations\n   - Reference CDK best practices via MCP tools\n4. **Validate**: Run pre-deployment checks (see above)\n5. **Synthesize**: Generate CloudFormation templates\n6. **Review**: Examine synthesized templates for correctness\n7. **Deploy**: Deploy to target environment\n8. **Verify**: Confirm resources are created correctly\n\n### Stack Organization\n\n- Use nested stacks for complex applications\n- Separate concerns into logical construct boundaries\n- Export values that other stacks may need\n- Use CDK context for environment-specific configuration\n\n### Testing Strategy\n\n- Unit test individual constructs\n- Integration test stack synthesis\n- Snapshot test CloudFormation templates\n- Validate resource properties and relationships\n\n## Using MCP Servers Effectively\n\n### When to Use AWS Documentation MCP\n\n**Always verify before implementing**:\n- New AWS service features or configurations\n- Service availability in target regions\n- API parameter specifications\n- Service limits and quotas\n- Security best practices for AWS services\n\n**Example scenarios**:\n- \"Check if Lambda supports Python 3.13 runtime\"\n- \"Verify DynamoDB is available in eu-south-2\"\n- \"What are the current Lambda timeout limits?\"\n- \"Get latest S3 encryption options\"\n\n### When to Use CDK MCP Server\n\n**Leverage for CDK-specific guidance**:\n- CDK construct selection and usage\n- CDK API parameter options\n- CDK best practice patterns\n- Construct property configurations\n- CDK-specific optimizations\n\n**Example scenarios**:\n- \"What's the recommended CDK construct for API Gateway REST API?\"\n- \"How to configure NodejsFunction bundling options?\"\n- \"Best practices for CDK stack organization\"\n- \"CDK construct for DynamoDB with auto-scaling\"\n\n### MCP Usage Best Practices\n\n1. **Verify First**: Always check AWS Documentation MCP before implementing new features\n2. **Regional Validation**: Check service availability in target deployment regions\n3. **CDK Guidance**: Use CDK MCP for construct-specific recommendations\n4. **Stay Current**: MCP servers provide latest information beyond knowledge cutoff\n5. **Combine Sources**: Use both skill patterns and MCP servers for comprehensive guidance\n\n## CDK Patterns Reference\n\nFor detailed CDK patterns, anti-patterns, and architectural guidance, refer to the comprehensive reference:\n\n**File**: `references\u002Fcdk-patterns.md`\n\nThis reference includes:\n- Common CDK patterns and their use cases\n- Anti-patterns to avoid\n- Security best practices\n- Cost optimization strategies\n- Performance considerations\n\n## Additional Resources\n\n- **Validation Script**: `scripts\u002Fvalidate-stack.sh` - Pre-deployment validation\n- **CDK Patterns**: `references\u002Fcdk-patterns.md` - Detailed pattern library\n- **AWS Documentation MCP**: Integrated for latest AWS information\n- **CDK MCP Server**: Integrated for CDK-specific guidance\n\n## GitHub Actions Integration\n\nWhen GitHub Actions workflow files exist in the repository, ensure all checks defined in `.github\u002Fworkflows\u002F` pass before committing. This prevents CI\u002FCD failures and maintains code quality standards.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"critical","https:\u002F\u002Fgithub.com\u002Fzxkane\u002Faws-skills\u002Ftree\u002Fmain\u002Fplugins\u002Faws-iac\u002Fskills\u002Faws-cdk-development",1782864000000,"zxkane\u002Faws-skills","community","https:\u002F\u002Fgithub.com\u002Fzxkane\u002Faws-skills\u002Fblob\u002Fmain\u002FLICENSE","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Faws-cdk-development",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill aws-cdk-development",{"tool":44,"command":45},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill aws-cdk-development",{"tool":47,"command":48},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill aws-cdk-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Faws-cdk-development\u002FSKILL.md",true,[],[53,61,66,73,80,87],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":60},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":62,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":60},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":60},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":60},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":60},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":60},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]