[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MH2RQ4EWAVQWG761EE04P":3,"skill-same:01M71MH2RQ4EWAVQWG761EE04P":106},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":6,"updatedAt":64,"install":65,"resources":78},"01M71MH2RQ4EWAVQWG761EE04P","cloud-architecture",null,"Use when designing AWS, Azure or GCP architectures, planning migrations with the 6Rs, setting DR with RTO and RPO checks, or cutting cloud costs. Persona workflow with per-provider references and CLI validation steps; for pure cost work see cost-optimization.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcloud-architecture\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcloud-architecture\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"cloud architecture","cloud","architecture","for","planning","architectures","setting","architect","steps","rpo","rto","cli","work","references","gcp","migrate","workflow","when","persona","claude-skills","2026-11-10 10:56:23",false,"---\nname: cloud-architecture\ndescription: \"Use when designing AWS, Azure or GCP architectures, planning migrations with the 6Rs, setting DR with RTO and RPO checks, or cutting cloud costs. Persona workflow with per-provider references and CLI validation steps; for pure cost work see cost-optimization.\"\ntags: [\"devops\",\"engineering\",\"cloud\",\"architecture\",\"migrate\"]\ntools: []\nlicense: MIT\nsource: https:\u002F\u002Fgithub.com\u002FJeffallan\u002Fclaude-skills\nsource_path: \"skills\u002Fcloud-architect\"\nsource_commit: 882ef55e377dbf9a4dbe496bb41ac6ccd0e555cf\n---\n# Cloud Architect\n\n## Core Workflow\n\n1. **Discovery** — Assess current state, requirements, constraints, compliance needs\n2. **Design** — Select services, design topology, plan data architecture\n3. **Security** — Implement zero-trust, identity federation, encryption\n4. **Cost Model** — Right-size resources, reserved capacity, auto-scaling\n5. **Migration** — Apply 6Rs framework, define waves, validate connectivity before cutover\n6. **Operate** — Set up monitoring, automation, continuous optimization\n\n### Workflow Validation Checkpoints\n\n**After Design:** Confirm every component has a redundancy strategy and no single points of failure exist in the topology.\n\n**Before Migration cutover:** Validate VPC peering or connectivity is fully established:\n```bash\n# AWS: confirm peering connection is Active before proceeding\naws ec2 describe-vpc-peering-connections \\\n  --filters \"Name=status-code,Values=active\"\n\n# Azure: confirm VNet peering state\naz network vnet peering list \\\n  --resource-group myRG --vnet-name myVNet \\\n  --query \"[].{Name:name,State:peeringState}\"\n```\n\n**After Migration:** Verify application health and routing:\n```bash\n# AWS: check target group health in ALB\naws elbv2 describe-target-health \\\n  --target-group-arn arn:aws:elasticloadbalancing:...\n```\n\n**After DR test:** Confirm RTO\u002FRPO targets were met; document actual recovery times.\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| AWS Services | `references\u002Faws.md` | EC2, S3, Lambda, RDS, Well-Architected Framework |\n| Azure Services | `references\u002Fazure.md` | VMs, Storage, Functions, SQL, Cloud Adoption Framework |\n| GCP Services | `references\u002Fgcp.md` | Compute Engine, Cloud Storage, Cloud Functions, BigQuery |\n| Multi-Cloud | `references\u002Fmulti-cloud.md` | Abstraction layers, portability, vendor lock-in mitigation |\n| Cost Optimization | `references\u002Fcost.md` | Reserved instances, spot, right-sizing, FinOps practices |\n\n## Constraints\n\n### MUST DO\n- Design for high availability (99.9%+)\n- Implement security by design (zero-trust)\n- Use infrastructure as code (Terraform, CloudFormation)\n- Enable cost allocation tags and monitoring\n- Plan disaster recovery with defined RTO\u002FRPO\n- Implement multi-region for critical workloads\n- Use managed services when possible\n- Document architectural decisions\n\n### MUST NOT DO\n- Store credentials in code or public repos\n- Skip encryption (at rest and in transit)\n- Create single points of failure\n- Ignore cost optimization opportunities\n- Deploy without proper monitoring\n- Use overly complex architectures\n- Ignore compliance requirements\n- Skip disaster recovery testing\n\n## Common Patterns with Examples\n\n### Least-Privilege IAM (Zero-Trust)\n\nRather than broad policies, scope permissions to specific resources and actions:\n\n```bash\n# AWS: create a scoped role for an application\naws iam create-role \\\n  --role-name AppRole \\\n  --assume-role-policy-document file:\u002F\u002Ftrust-policy.json\n\naws iam put-role-policy \\\n  --role-name AppRole \\\n  --policy-name AppInlinePolicy \\\n  --policy-document '{\n    \"Version\": \"2012-10-17\",\n    \"Statement\": [{\n      \"Effect\": \"Allow\",\n      \"Action\": [\"s3:GetObject\", \"s3:PutObject\"],\n      \"Resource\": \"arn:aws:s3:::my-app-bucket\u002F*\"\n    }]\n  }'\n```\n\n```hcl\n# Terraform equivalent\nresource \"aws_iam_role\" \"app_role\" {\n  name               = \"AppRole\"\n  assume_role_policy = data.aws_iam_policy_document.trust.json\n}\n\nresource \"aws_iam_role_policy\" \"app_policy\" {\n  role = aws_iam_role.app_role.id\n  policy = jsonencode({\n    Version = \"2012-10-17\"\n    Statement = [{\n      Effect   = \"Allow\"\n      Action   = [\"s3:GetObject\", \"s3:PutObject\"]\n      Resource = \"${aws_s3_bucket.app.arn}\u002F*\"\n    }]\n  })\n}\n```\n\n### VPC with Public\u002FPrivate Subnets (Terraform)\n\n```hcl\nresource \"aws_vpc\" \"main\" {\n  cidr_block           = \"10.0.0.0\u002F16\"\n  enable_dns_hostnames = true\n  tags = { Name = \"main\", CostCenter = var.cost_center }\n}\n\nresource \"aws_subnet\" \"private\" {\n  count             = 2\n  vpc_id            = aws_vpc.main.id\n  cidr_block        = cidrsubnet(\"10.0.0.0\u002F16\", 8, count.index)\n  availability_zone = data.aws_availability_zones.available.names[count.index]\n}\n\nresource \"aws_subnet\" \"public\" {\n  count                   = 2\n  vpc_id                  = aws_vpc.main.id\n  cidr_block              = cidrsubnet(\"10.0.0.0\u002F16\", 8, count.index + 10)\n  availability_zone       = data.aws_availability_zones.available.names[count.index]\n  map_public_ip_on_launch = true\n}\n```\n\n### Auto-Scaling Group (Terraform)\n\n```hcl\nresource \"aws_autoscaling_group\" \"app\" {\n  desired_capacity    = 2\n  min_size            = 1\n  max_size            = 10\n  vpc_zone_identifier = aws_subnet.private[*].id\n\n  launch_template {\n    id      = aws_launch_template.app.id\n    version = \"$Latest\"\n  }\n\n  tag {\n    key                 = \"CostCenter\"\n    value               = var.cost_center\n    propagate_at_launch = true\n  }\n}\n\nresource \"aws_autoscaling_policy\" \"cpu_target\" {\n  autoscaling_group_name = aws_autoscaling_group.app.name\n  policy_type            = \"TargetTrackingScaling\"\n  target_tracking_configuration {\n    predefined_metric_specification {\n      predefined_metric_type = \"ASGAverageCPUUtilization\"\n    }\n    target_value = 60.0\n  }\n}\n```\n\n### Cost Analysis CLI\n\n```bash\n# AWS: identify top cost drivers for the last 30 days\naws ce get-cost-and-usage \\\n  --time-period Start=$(date -d '30 days ago' +%Y-%m-%d),End=$(date +%Y-%m-%d) \\\n  --granularity MONTHLY \\\n  --metrics \"UnblendedCost\" \\\n  --group-by Type=DIMENSION,Key=SERVICE \\\n  --query 'ResultsByTime[0].Groups[*].{Service:Keys[0],Cost:Metrics.UnblendedCost.Amount}' \\\n  --output table\n\n# Azure: review spend by resource group\naz consumption usage list \\\n  --start-date $(date -d '30 days ago' +%Y-%m-%d) \\\n  --end-date $(date +%Y-%m-%d) \\\n  --query \"[].{ResourceGroup:resourceGroup,Cost:pretaxCost,Currency:currency}\" \\\n  --output table\n```\n\n## Output Templates\n\nWhen designing cloud architecture, provide:\n1. Architecture diagram with services and data flow\n2. Service selection rationale (compute, storage, database, networking)\n3. Security architecture (IAM, network segmentation, encryption)\n4. Cost estimation and optimization strategy\n5. Deployment approach and rollback plan\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Finfrastructure\u002Fcloud-architect\u002F)\n","# Cloud Architect\n\n## Core Workflow\n\n1. **Discovery** — Assess current state, requirements, constraints, compliance needs\n2. **Design** — Select services, design topology, plan data architecture\n3. **Security** — Implement zero-trust, identity federation, encryption\n4. **Cost Model** — Right-size resources, reserved capacity, auto-scaling\n5. **Migration** — Apply 6Rs framework, define waves, validate connectivity before cutover\n6. **Operate** — Set up monitoring, automation, continuous optimization\n\n### Workflow Validation Checkpoints\n\n**After Design:** Confirm every component has a redundancy strategy and no single points of failure exist in the topology.\n\n**Before Migration cutover:** Validate VPC peering or connectivity is fully established:\n```bash\n# AWS: confirm peering connection is Active before proceeding\naws ec2 describe-vpc-peering-connections \\\n  --filters \"Name=status-code,Values=active\"\n\n# Azure: confirm VNet peering state\naz network vnet peering list \\\n  --resource-group myRG --vnet-name myVNet \\\n  --query \"[].{Name:name,State:peeringState}\"\n```\n\n**After Migration:** Verify application health and routing:\n```bash\n# AWS: check target group health in ALB\naws elbv2 describe-target-health \\\n  --target-group-arn arn:aws:elasticloadbalancing:...\n```\n\n**After DR test:** Confirm RTO\u002FRPO targets were met; document actual recovery times.\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| AWS Services | `references\u002Faws.md` | EC2, S3, Lambda, RDS, Well-Architected Framework |\n| Azure Services | `references\u002Fazure.md` | VMs, Storage, Functions, SQL, Cloud Adoption Framework |\n| GCP Services | `references\u002Fgcp.md` | Compute Engine, Cloud Storage, Cloud Functions, BigQuery |\n| Multi-Cloud | `references\u002Fmulti-cloud.md` | Abstraction layers, portability, vendor lock-in mitigation |\n| Cost Optimization | `references\u002Fcost.md` | Reserved instances, spot, right-sizing, FinOps practices |\n\n## Constraints\n\n### MUST DO\n- Design for high availability (99.9%+)\n- Implement security by design (zero-trust)\n- Use infrastructure as code (Terraform, CloudFormation)\n- Enable cost allocation tags and monitoring\n- Plan disaster recovery with defined RTO\u002FRPO\n- Implement multi-region for critical workloads\n- Use managed services when possible\n- Document architectural decisions\n\n### MUST NOT DO\n- Store credentials in code or public repos\n- Skip encryption (at rest and in transit)\n- Create single points of failure\n- Ignore cost optimization opportunities\n- Deploy without proper monitoring\n- Use overly complex architectures\n- Ignore compliance requirements\n- Skip disaster recovery testing\n\n## Common Patterns with Examples\n\n### Least-Privilege IAM (Zero-Trust)\n\nRather than broad policies, scope permissions to specific resources and actions:\n\n```bash\n# AWS: create a scoped role for an application\naws iam create-role \\\n  --role-name AppRole \\\n  --assume-role-policy-document file:\u002F\u002Ftrust-policy.json\n\naws iam put-role-policy \\\n  --role-name AppRole \\\n  --policy-name AppInlinePolicy \\\n  --policy-document '{\n    \"Version\": \"2012-10-17\",\n    \"Statement\": [{\n      \"Effect\": \"Allow\",\n      \"Action\": [\"s3:GetObject\", \"s3:PutObject\"],\n      \"Resource\": \"arn:aws:s3:::my-app-bucket\u002F*\"\n    }]\n  }'\n```\n\n```hcl\n# Terraform equivalent\nresource \"aws_iam_role\" \"app_role\" {\n  name               = \"AppRole\"\n  assume_role_policy = data.aws_iam_policy_document.trust.json\n}\n\nresource \"aws_iam_role_policy\" \"app_policy\" {\n  role = aws_iam_role.app_role.id\n  policy = jsonencode({\n    Version = \"2012-10-17\"\n    Statement = [{\n      Effect   = \"Allow\"\n      Action   = [\"s3:GetObject\", \"s3:PutObject\"]\n      Resource = \"${aws_s3_bucket.app.arn}\u002F*\"\n    }]\n  })\n}\n```\n\n### VPC with Public\u002FPrivate Subnets (Terraform)\n\n```hcl\nresource \"aws_vpc\" \"main\" {\n  cidr_block           = \"10.0.0.0\u002F16\"\n  enable_dns_hostnames = true\n  tags = { Name = \"main\", CostCenter = var.cost_center }\n}\n\nresource \"aws_subnet\" \"private\" {\n  count             = 2\n  vpc_id            = aws_vpc.main.id\n  cidr_block        = cidrsubnet(\"10.0.0.0\u002F16\", 8, count.index)\n  availability_zone = data.aws_availability_zones.available.names[count.index]\n}\n\nresource \"aws_subnet\" \"public\" {\n  count                   = 2\n  vpc_id                  = aws_vpc.main.id\n  cidr_block              = cidrsubnet(\"10.0.0.0\u002F16\", 8, count.index + 10)\n  availability_zone       = data.aws_availability_zones.available.names[count.index]\n  map_public_ip_on_launch = true\n}\n```\n\n### Auto-Scaling Group (Terraform)\n\n```hcl\nresource \"aws_autoscaling_group\" \"app\" {\n  desired_capacity    = 2\n  min_size            = 1\n  max_size            = 10\n  vpc_zone_identifier = aws_subnet.private[*].id\n\n  launch_template {\n    id      = aws_launch_template.app.id\n    version = \"$Latest\"\n  }\n\n  tag {\n    key                 = \"CostCenter\"\n    value               = var.cost_center\n    propagate_at_launch = true\n  }\n}\n\nresource \"aws_autoscaling_policy\" \"cpu_target\" {\n  autoscaling_group_name = aws_autoscaling_group.app.name\n  policy_type            = \"TargetTrackingScaling\"\n  target_tracking_configuration {\n    predefined_metric_specification {\n      predefined_metric_type = \"ASGAverageCPUUtilization\"\n    }\n    target_value = 60.0\n  }\n}\n```\n\n### Cost Analysis CLI\n\n```bash\n# AWS: identify top cost drivers for the last 30 days\naws ce get-cost-and-usage \\\n  --time-period Start=$(date -d '30 days ago' +%Y-%m-%d),End=$(date +%Y-%m-%d) \\\n  --granularity MONTHLY \\\n  --metrics \"UnblendedCost\" \\\n  --group-by Type=DIMENSION,Key=SERVICE \\\n  --query 'ResultsByTime[0].Groups[*].{Service:Keys[0],Cost:Metrics.UnblendedCost.Amount}' \\\n  --output table\n\n# Azure: review spend by resource group\naz consumption usage list \\\n  --start-date $(date -d '30 days ago' +%Y-%m-%d) \\\n  --end-date $(date +%Y-%m-%d) \\\n  --query \"[].{ResourceGroup:resourceGroup,Cost:pretaxCost,Currency:currency}\" \\\n  --output table\n```\n\n## Output Templates\n\nWhen designing cloud architecture, provide:\n1. Architecture diagram with services and data flow\n2. Service selection rationale (compute, storage, database, networking)\n3. Security architecture (IAM, network segmentation, encryption)\n4. Cost estimation and optimization strategy\n5. Deployment approach and rollback plan\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Finfrastructure\u002Fcloud-architect\u002F)\n",{"name":5,"tags":49,"tools":52,"source":53,"license":14,"description":7,"source_path":54,"source_commit":55},[50,51,25,26,39],"devops","engineering",[],"https:\u002F\u002Fgithub.com\u002FJeffallan\u002Fclaude-skills","skills\u002Fcloud-architect","882ef55e377dbf9a4dbe496bb41ac6ccd0e555cf","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcloud-architecture",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-14 03:30:52",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add monoes\u002Fmonomind --skill cloud-architecture",{"tool":71,"command":72},"bunx","bunx skills add monoes\u002Fmonomind --skill cloud-architecture",{"tool":74,"command":75},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill cloud-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcloud-architecture\u002FSKILL.md",true,[79,84,90,94,98,102],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",1056,{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Faws.md","REFERENCE","参考文档",11309,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcloud-architecture\u002Freferences\u002Faws.md",{"path":91,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fazure.md",14468,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcloud-architecture\u002Freferences\u002Fazure.md",{"path":95,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fcost.md",14289,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcloud-architecture\u002Freferences\u002Fcost.md",{"path":99,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fgcp.md",17222,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcloud-architecture\u002Freferences\u002Fgcp.md",{"path":103,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fmulti-cloud.md",11331,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fcloud-architecture\u002Freferences\u002Fmulti-cloud.md",[107,136,169,195,219,242],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":135},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","knowledge","impact","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":140,"sourceHtmlUrl":141,"categories":142,"keywords":151,"publishedAt":135},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[143,146],{"categoryNo":144,"categoryName":145,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":147,"categoryName":148,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[152,153,154,119,155,156,41,157,124,158,159,160,161,162,163,164,165,166,167,168],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":173,"sourceHtmlUrl":174,"categories":175,"keywords":179,"publishedAt":135},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[176],{"categoryNo":177,"categoryName":178,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000031","产品经理",[162,180,181,182,183,122,184,41,185,186,36,161,187,188,189,190,191,192,193,194],"write spec","spec","user request","problem","acceptance","ask","vague","request","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":199,"sourceHtmlUrl":200,"categories":201,"keywords":205,"publishedAt":135},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[202],{"categoryNo":203,"categoryName":204,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000033","数据分析师",[124,162,206,207,27,208,122,193,41,209,210,211,212,36,213,214,215,216,217,218],"write query","postgres","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":6,"sourceHtmlUrl":223,"categories":224,"keywords":229,"publishedAt":135},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[225,228],{"categoryNo":226,"categoryName":227,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[230,231,40,232,27,233,234,235,236,123,237,238,239,124,127,213,240,241,50,215],"Workflow Automation","automation","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency",{"skillNo":243,"name":244,"nameZh":6,"description":245,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":6,"sourceHtmlUrl":246,"categories":247,"keywords":249,"publishedAt":135},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[248],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[40,250,31,251,252,253,28,27,254,255,158,26,256,257,127,213,258,259,215,260],"workflow architect","trees","user journeys","branch","map","workflows","state","leadership","recovery","operations","systems"]