[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H4YHGYABW2JS1TWXFJ3PD6":3,"skill-same:01M6H4YHGYABW2JS1TWXFJ3PD6":100},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M6H4YHGYABW2JS1TWXFJ3PD6","managing-database-replication",null,"Process use when you need to work with database scalability.\nThis skill provides replication and sharding with comprehensive guidance and automation.\nTrigger with phrases like \"set up replication\", \"implement sharding\",\nor \"scale database\".","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fdatabase\u002Fdatabase-replication-manager\u002Fskills\u002Fmanaging-database-replication\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"database","replication","Managing Database Replication","use","you","Sharding","with","trigger","io","scalability","up","codex","process","work","Bash","SET","mysql","code","automation","implement","2026-11-10 10:12:30",false,"---\nname: managing-database-replication\ndescription: |\n  Process use when you need to work with database scalability.\n  This skill provides replication and sharding with comprehensive guidance and automation.\n  Trigger with phrases like \"set up replication\", \"implement sharding\",\n  or \"scale database\".\n\nallowed-tools: Read, Write, Edit, Grep, Glob, Bash(psql:*), Bash(mysql:*), Bash(mongosh:*)\nversion: 1.0.0\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\nlicense: MIT\ncompatible-with: claude-code, codex, openclaw\n---\n# Database Replication Manager\n\n## Overview\n\nConfigure and manage database replication topologies for PostgreSQL (streaming replication, logical replication), MySQL (source-replica, group replication), and MongoDB (replica sets). This skill covers primary-replica setup, read scaling through replica routing, failover automation, replication lag monitoring, and conflict resolution for multi-primary configurations.\n\n## Prerequisites\n\n- Superuser or replication-role credentials on primary and replica servers\n- Network connectivity between all replication nodes (verify with `pg_isready` or `mysqladmin ping`)\n- `psql`, `mysql`, or `mongosh` CLI tools installed on all nodes\n- Matching major database versions across all replication nodes\n- Sufficient disk space on replicas (equal to or greater than primary)\n- SSH access to replica servers for initial base backup transfer\n\n## Instructions\n\n1. Choose the replication topology based on requirements:\n   - **Single primary + read replicas**: Best for read-heavy workloads. All writes go to primary; reads distributed across replicas.\n   - **Multi-primary (active-active)**: Best for geographic distribution. Requires conflict resolution. Use PostgreSQL logical replication or MySQL Group Replication.\n   - **Cascading replication**: Replica A replicates from primary, Replica B replicates from Replica A. Reduces primary load for many replicas.\n\n2. For PostgreSQL streaming replication, configure the primary:\n   - Set `wal_level = replica`, `max_wal_senders = 10`, `max_replication_slots = 10`\n   - Create replication user: `CREATE ROLE replicator WITH REPLICATION LOGIN PASSWORD 'secure_password'`\n   - Add replication entry to `pg_hba.conf`: `host replication replicator replica_ip\u002F32 scram-sha-256`\n   - Reload configuration: `SELECT pg_reload_conf()`\n\n3. Initialize the replica with a base backup: `pg_basebackup -h primary_host -U replicator -D \u002Fvar\u002Flib\u002Fpostgresql\u002Fdata -Fp -Xs -P -R`. The `-R` flag creates `standby.signal` and configures `primary_conninfo` automatically.\n\n4. For MySQL source-replica replication, configure the source:\n   - Set `server-id = 1`, `log_bin = mysql-bin`, `binlog_format = ROW`\n   - Create replication user: `CREATE USER 'replicator'@'replica_ip' IDENTIFIED BY 'secure_password'; GRANT REPLICATION SLAVE ON *.* TO 'replicator'@'replica_ip'`\n   - Record binary log position: `SHOW MASTER STATUS`\n\n5. Configure the MySQL replica: `CHANGE REPLICATION SOURCE TO SOURCE_HOST='primary_host', SOURCE_USER='replicator', SOURCE_PASSWORD='...', SOURCE_LOG_FILE='mysql-bin.000001', SOURCE_LOG_POS=154; START REPLICA`.\n\n6. For MongoDB replica sets: initialize with `rs.initiate({_id: \"rs0\", members: [{_id: 0, host: \"node1:27017\"}, {_id: 1, host: \"node2:27017\"}, {_id: 2, host: \"node3:27017\"}]})`. MongoDB handles leader election and failover automatically.\n\n7. Monitor replication lag continuously:\n   - PostgreSQL: `SELECT client_addr, state, sent_lsn, write_lsn, flush_lsn, replay_lsn, (sent_lsn - replay_lsn) AS lag_bytes FROM pg_stat_replication`\n   - MySQL: `SHOW REPLICA STATUS\\G` (check `Seconds_Behind_Source`)\n   - MongoDB: `rs.printReplicationInfo()` and `rs.printSecondaryReplicationInfo()`\n\n8. Configure application-level read routing: direct write queries to the primary connection and read queries to a load-balanced replica pool. Use connection poolers (PgBouncer, ProxySQL) or application middleware for automatic routing.\n\n9. Set up automated failover using Patroni (PostgreSQL), MySQL InnoDB Cluster + MySQL Router, or MongoDB's built-in election mechanism. Test failover by stopping the primary and verifying the replica promotes automatically within the target RTO.\n\n10. Configure alerting for replication lag exceeding 10 seconds, replication slot inactive for more than 1 hour, and replica connection drops. Stale replication slots in PostgreSQL cause WAL accumulation and can fill the disk.\n\n## Output\n\n- **Replication configuration files** for primary and replica nodes\n- **Base backup and initialization scripts** for setting up new replicas\n- **Replication monitoring queries** with lag measurement and health checks\n- **Failover runbook** with manual and automated promotion procedures\n- **Read routing configuration** for application or connection pooler\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|---------|\n| Replication lag increasing steadily | Replica cannot keep up with primary write volume | Check replica I\u002FO and CPU; increase `max_parallel_workers` on replica; consider upgrading replica hardware; reduce write-heavy batch operations on primary |\n| `replication slot is inactive` warning | Replica disconnected or paused, WAL accumulating on primary | Reconnect replica; if permanently removed, drop the slot with `SELECT pg_drop_replication_slot('slot_name')` to prevent disk fill |\n| `could not connect to primary` on replica | Network partition, primary down, or authentication failure | Verify network connectivity; check `pg_hba.conf` entries; confirm replication user credentials; check primary process status |\n| Replica has diverged from primary | Split-brain after failed failover or manual writes to replica | Re-initialize replica from fresh base backup; for PostgreSQL, use `pg_rewind` if timeline divergence is small |\n| Conflict in logical replication | Same row modified on both publisher and subscriber | Configure conflict resolution policy; use `UPDATE` conflict handler; design schema to avoid cross-node writes to same rows |\n\n## Examples\n\n**Setting up PostgreSQL read replicas for a web application**: A primary database handles 2,000 writes\u002Fsecond but read traffic is 10x higher. Two streaming replicas are added with PgBouncer routing read queries to replicas in round-robin. Result: primary CPU drops from 90% to 40%, read latency improves by 60%.\n\n**Automated failover with Patroni**: A 3-node PostgreSQL cluster managed by Patroni with etcd for consensus. When the primary fails, Patroni promotes the most up-to-date replica within 10 seconds. Application reconnects automatically through the Patroni-managed VIP or DNS endpoint.\n\n**Cross-region logical replication for compliance**: EU customer data must stay in EU region. Logical replication publishes only non-PII tables to the US region replica. EU application reads locally; US analytics queries use the replicated subset. Publication filter: `CREATE PUBLICATION us_analytics FOR TABLE orders, products, categories`.\n\n## Resources\n\n- PostgreSQL streaming replication: https:\u002F\u002Fwww.postgresql.org\u002Fdocs\u002Fcurrent\u002Fwarm-standby.html\n- PostgreSQL logical replication: https:\u002F\u002Fwww.postgresql.org\u002Fdocs\u002Fcurrent\u002Flogical-replication.html\n- MySQL replication: https:\u002F\u002Fdev.mysql.com\u002Fdoc\u002Frefman\u002F8.0\u002Fen\u002Freplication.html\n- Patroni (PostgreSQL HA): https:\u002F\u002Fpatroni.readthedocs.io\u002F\n- MongoDB replica sets: https:\u002F\u002Fwww.mongodb.com\u002Fdocs\u002Fmanual\u002Freplication\u002F","# Database Replication Manager\n\n## Overview\n\nConfigure and manage database replication topologies for PostgreSQL (streaming replication, logical replication), MySQL (source-replica, group replication), and MongoDB (replica sets). This skill covers primary-replica setup, read scaling through replica routing, failover automation, replication lag monitoring, and conflict resolution for multi-primary configurations.\n\n## Prerequisites\n\n- Superuser or replication-role credentials on primary and replica servers\n- Network connectivity between all replication nodes (verify with `pg_isready` or `mysqladmin ping`)\n- `psql`, `mysql`, or `mongosh` CLI tools installed on all nodes\n- Matching major database versions across all replication nodes\n- Sufficient disk space on replicas (equal to or greater than primary)\n- SSH access to replica servers for initial base backup transfer\n\n## Instructions\n\n1. Choose the replication topology based on requirements:\n   - **Single primary + read replicas**: Best for read-heavy workloads. All writes go to primary; reads distributed across replicas.\n   - **Multi-primary (active-active)**: Best for geographic distribution. Requires conflict resolution. Use PostgreSQL logical replication or MySQL Group Replication.\n   - **Cascading replication**: Replica A replicates from primary, Replica B replicates from Replica A. Reduces primary load for many replicas.\n\n2. For PostgreSQL streaming replication, configure the primary:\n   - Set `wal_level = replica`, `max_wal_senders = 10`, `max_replication_slots = 10`\n   - Create replication user: `CREATE ROLE replicator WITH REPLICATION LOGIN PASSWORD 'secure_password'`\n   - Add replication entry to `pg_hba.conf`: `host replication replicator replica_ip\u002F32 scram-sha-256`\n   - Reload configuration: `SELECT pg_reload_conf()`\n\n3. Initialize the replica with a base backup: `pg_basebackup -h primary_host -U replicator -D \u002Fvar\u002Flib\u002Fpostgresql\u002Fdata -Fp -Xs -P -R`. The `-R` flag creates `standby.signal` and configures `primary_conninfo` automatically.\n\n4. For MySQL source-replica replication, configure the source:\n   - Set `server-id = 1`, `log_bin = mysql-bin`, `binlog_format = ROW`\n   - Create replication user: `CREATE USER 'replicator'@'replica_ip' IDENTIFIED BY 'secure_password'; GRANT REPLICATION SLAVE ON *.* TO 'replicator'@'replica_ip'`\n   - Record binary log position: `SHOW MASTER STATUS`\n\n5. Configure the MySQL replica: `CHANGE REPLICATION SOURCE TO SOURCE_HOST='primary_host', SOURCE_USER='replicator', SOURCE_PASSWORD='...', SOURCE_LOG_FILE='mysql-bin.000001', SOURCE_LOG_POS=154; START REPLICA`.\n\n6. For MongoDB replica sets: initialize with `rs.initiate({_id: \"rs0\", members: [{_id: 0, host: \"node1:27017\"}, {_id: 1, host: \"node2:27017\"}, {_id: 2, host: \"node3:27017\"}]})`. MongoDB handles leader election and failover automatically.\n\n7. Monitor replication lag continuously:\n   - PostgreSQL: `SELECT client_addr, state, sent_lsn, write_lsn, flush_lsn, replay_lsn, (sent_lsn - replay_lsn) AS lag_bytes FROM pg_stat_replication`\n   - MySQL: `SHOW REPLICA STATUS\\G` (check `Seconds_Behind_Source`)\n   - MongoDB: `rs.printReplicationInfo()` and `rs.printSecondaryReplicationInfo()`\n\n8. Configure application-level read routing: direct write queries to the primary connection and read queries to a load-balanced replica pool. Use connection poolers (PgBouncer, ProxySQL) or application middleware for automatic routing.\n\n9. Set up automated failover using Patroni (PostgreSQL), MySQL InnoDB Cluster + MySQL Router, or MongoDB's built-in election mechanism. Test failover by stopping the primary and verifying the replica promotes automatically within the target RTO.\n\n10. Configure alerting for replication lag exceeding 10 seconds, replication slot inactive for more than 1 hour, and replica connection drops. Stale replication slots in PostgreSQL cause WAL accumulation and can fill the disk.\n\n## Output\n\n- **Replication configuration files** for primary and replica nodes\n- **Base backup and initialization scripts** for setting up new replicas\n- **Replication monitoring queries** with lag measurement and health checks\n- **Failover runbook** with manual and automated promotion procedures\n- **Read routing configuration** for application or connection pooler\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|---------|\n| Replication lag increasing steadily | Replica cannot keep up with primary write volume | Check replica I\u002FO and CPU; increase `max_parallel_workers` on replica; consider upgrading replica hardware; reduce write-heavy batch operations on primary |\n| `replication slot is inactive` warning | Replica disconnected or paused, WAL accumulating on primary | Reconnect replica; if permanently removed, drop the slot with `SELECT pg_drop_replication_slot('slot_name')` to prevent disk fill |\n| `could not connect to primary` on replica | Network partition, primary down, or authentication failure | Verify network connectivity; check `pg_hba.conf` entries; confirm replication user credentials; check primary process status |\n| Replica has diverged from primary | Split-brain after failed failover or manual writes to replica | Re-initialize replica from fresh base backup; for PostgreSQL, use `pg_rewind` if timeline divergence is small |\n| Conflict in logical replication | Same row modified on both publisher and subscriber | Configure conflict resolution policy; use `UPDATE` conflict handler; design schema to avoid cross-node writes to same rows |\n\n## Examples\n\n**Setting up PostgreSQL read replicas for a web application**: A primary database handles 2,000 writes\u002Fsecond but read traffic is 10x higher. Two streaming replicas are added with PgBouncer routing read queries to replicas in round-robin. Result: primary CPU drops from 90% to 40%, read latency improves by 60%.\n\n**Automated failover with Patroni**: A 3-node PostgreSQL cluster managed by Patroni with etcd for consensus. When the primary fails, Patroni promotes the most up-to-date replica within 10 seconds. Application reconnects automatically through the Patroni-managed VIP or DNS endpoint.\n\n**Cross-region logical replication for compliance**: EU customer data must stay in EU region. Logical replication publishes only non-PII tables to the US region replica. EU application reads locally; US analytics queries use the replicated subset. Publication filter: `CREATE PUBLICATION us_analytics FOR TABLE orders, products, categories`.\n\n## Resources\n\n- PostgreSQL streaming replication: https:\u002F\u002Fwww.postgresql.org\u002Fdocs\u002Fcurrent\u002Fwarm-standby.html\n- PostgreSQL logical replication: https:\u002F\u002Fwww.postgresql.org\u002Fdocs\u002Fcurrent\u002Flogical-replication.html\n- MySQL replication: https:\u002F\u002Fdev.mysql.com\u002Fdoc\u002Frefman\u002F8.0\u002Fen\u002Freplication.html\n- Patroni (PostgreSQL HA): https:\u002F\u002Fpatroni.readthedocs.io\u002F\n- MongoDB replica sets: https:\u002F\u002Fwww.mongodb.com\u002Fdocs\u002Fmanual\u002Freplication\u002F",{"name":5,"author":48,"license":14,"version":49,"description":50,"allowed-tools":51,"compatible-with":52},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Process use when you need to work with database scalability.\nThis skill provides replication and sharding with comprehensive guidance and automation.\nTrigger with phrases like \"set up replication\", \"implement sharding\",\nor \"scale database\".\n","Read, Write, Edit, Grep, Glob, Bash(psql:*), Bash(mysql:*), Bash(mongosh:*)","claude-code, codex, openclaw","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fdatabase\u002Fdatabase-replication-manager\u002Fskills\u002Fmanaging-database-replication",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add micsapp\u002Fmicstec-skills --skill managing-database-replication",{"tool":66,"command":67},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill managing-database-replication",{"tool":69,"command":70},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill managing-database-replication","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fdatabase\u002Fdatabase-replication-manager\u002Fskills\u002Fmanaging-database-replication\u002FSKILL.md",true,[74,80,86,92,96],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"assets\u002FREADME.md","ASSET","资产文件",157,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fdatabase\u002Fdatabase-replication-manager\u002Fskills\u002Fmanaging-database-replication\u002Fassets\u002FREADME.md",{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002FREADME.md","REFERENCE","参考文档",72,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fdatabase\u002Fdatabase-replication-manager\u002Fskills\u002Fmanaging-database-replication\u002Freferences\u002FREADME.md",{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Ffailover.sh","SCRIPT","脚本",2887,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fdatabase\u002Fdatabase-replication-manager\u002Fskills\u002Fmanaging-database-replication\u002Fscripts\u002Ffailover.sh",{"path":93,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":94,"sourceHtmlUrl":95},"scripts\u002FREADME.md",393,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fdatabase\u002Fdatabase-replication-manager\u002Fskills\u002Fmanaging-database-replication\u002Fscripts\u002FREADME.md",{"path":97,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":98,"sourceHtmlUrl":99},"scripts\u002Fsetup_replication.sh",2659,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fdatabase\u002Fdatabase-replication-manager\u002Fskills\u002Fmanaging-database-replication\u002Fscripts\u002Fsetup_replication.sh",[101,134,163,183,203,227],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":113,"publishedAt":43},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[107,108],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","api","team","environment","multi-environment","workspaces","instances","selection","strategies","azure api management","mode","for",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":148,"publishedAt":43},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[140,141,144,147],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":142,"categoryName":143,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":145,"categoryName":146,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},[149,150,151,152,115,153,40,154,155,156,157,158,123,124,130,159,160,131,161,162],"deployment","apiops deployment","workflows","azure devops","infrastructure","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD","implementing",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":170,"publishedAt":43},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[169],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[171,172,173,174,115,118,123,124,175,26,176,177,178,179,180,131,181,182,162,133],"policy","authoring","apim policy authoring","security","access","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":191,"publishedAt":43},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[189,190],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},[192,174,193,123,177,194,115,149,195,196,197,198,124,199,131,200,201,202,132,133],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":209,"publishedAt":43},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[210,211,212,151,213,214,215,216,123,217,36,218,219,220,221,222,223,224,225,226],"cli","jira","jira cli","init","tasks","create","issues","common","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":228,"name":229,"nameZh":6,"description":230,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":231,"categories":232,"keywords":233,"publishedAt":43},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[229,234,235,236,237,238,239,26,240,241],"npm","js","calculate","node","math","user","compute","errors"]