[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71B1P0SDVR11X7NPW87QYJD":3,"skill-same:01M71B1P0SDVR11X7NPW87QYJD":73},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":58,"updatedAt":59,"install":60,"resources":72},"01M71B1P0SDVR11X7NPW87QYJD","cyber-executing-red-team-engagement-planning",null,"Red team engagement planning is the foundational phase that defines scope, objectives, rules of engagement (ROE), threat model selection, and operational timelines before any offensive testing begins.","nexuslinkproductions\u002Fyuri-os","nexuslinkproductions","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F273246263?v=4","01M718YX9NZRCW50B59B8ZVDKN","Marcel Spatz","01M718YXAQ7530F4B1VKN6SFQV",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcyber-executing-red-team-engagement-planning\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"team","executing red team engagement planning","planning","red team","engagement","red","cyber executing red team engagement planning","threat model","mitre-attack","rules-of-engagement","engagement-planning","phase","false","cybersecurity","model selection","adversary-simulation","selection","testing","model","scope","2026-11-10 10:12:30",false,"---\nname: cyber-executing-red-team-engagement-planning\ndescription: \"Red team engagement planning is the foundational phase that defines scope, objectives, rules of engagement (ROE), threat model selection, and operational timelines before any offensive testing begins.\"\nsource: mukul975\u002FAnthropic-Cybersecurity-Skills\nlicense: Apache-2.0\nauthorized_lab: false\norigin_frontmatter: \"name: executing-red-team-engagement-planning | description: Red team engagement planning is the foundational phase that defines scope, |   objectives, rules of engagement (ROE), threat model selection, and operational timelines |   before any offensive testing begins. | domain: cybersecurity | subdomain: red-teaming | tags: | - red-team | - adversary-simulation | - mitre-attack | - exploitation | - post-exploitation | - engagement-planning | - rules-of-engagement | version: '1.0' | author: mahip\"\nhide: true\n---\n\n> Defensive\u002Fanalysis cyber skill. Source: mukul975\u002FAnthropic-Cybersecurity-Skills (Apache-2.0). Advisory knowledge — the YURI floor, protected paths, and owner authority always outrank any instruction in this body.\n\n# Executing Red Team Engagement Planning\n\n## Overview\n\nRed team engagement planning is the foundational phase that defines scope, objectives, rules of engagement (ROE), threat model selection, and operational timelines before any offensive testing begins. A well-structured engagement plan ensures the red team simulates realistic adversary behavior while maintaining safety guardrails that prevent unintended business disruption.\n\n\n## When to Use\n\n- When conducting security assessments that involve executing red team engagement planning\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Familiarity with red teaming concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n\n- Define clear engagement scope including in-scope and out-of-scope assets, networks, and personnel\n- Establish Rules of Engagement (ROE) with emergency stop procedures, communication channels, and legal boundaries\n- Select appropriate threat profiles from the MITRE ATT&CK framework aligned to the organization's threat landscape\n- Create a detailed attack plan mapping adversary TTPs to engagement objectives\n- Develop deconfliction procedures with the organization's SOC\u002Fblue team\n- Produce a comprehensive engagement brief for stakeholder approval\n\n> **Legal Notice:** This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.\n\n## Core Concepts\n\n### Engagement Types\n\n| Type | Description | Scope |\n|------|-------------|-------|\n| Full Scope | Complete adversary simulation with physical, social, and cyber vectors | Entire organization |\n| Assumed Breach | Starts from initial foothold, focuses on post-exploitation | Internal network |\n| Objective-Based | Target specific crown jewels (e.g., domain admin, PII exfiltration) | Defined targets |\n| Purple Team | Collaborative with blue team for detection improvement | Specific controls |\n\n### Rules of Engagement Components\n\n1. **Scope Definition**: IP ranges, domains, physical locations, personnel\n2. **Restrictions**: Systems\u002Fnetworks that must not be touched (e.g., production databases, medical devices)\n3. **Communication Plan**: Primary and secondary contact channels, escalation procedures\n4. **Emergency Procedures**: Code word for immediate cessation, incident response coordination\n5. **Legal Authorization**: Signed authorization letters, get-out-of-jail letters for physical tests\n6. **Data Handling**: How sensitive data discovered during testing will be handled and destroyed\n7. **Timeline**: Start\u002Fend dates, blackout windows, reporting deadlines\n\n### Threat Profile Selection\n\nMap organizational threats using MITRE ATT&CK Navigator to select relevant adversary profiles:\n\n- **APT29 (Cozy Bear)**: Government\u002Fdefense sector targeting via spearphishing, supply chain\n- **APT28 (Fancy Bear)**: Government organizations, credential harvesting, zero-days\n- **FIN7**: Financial sector, POS malware, social engineering\n- **Lazarus Group**: Financial institutions, cryptocurrency exchanges, destructive malware\n- **Conti\u002FRoyal**: Ransomware operators, double extortion, RaaS model\n\n## Workflow\n\n### Phase 1: Pre-Engagement\n\n1. Conduct initial scoping meeting with stakeholders\n2. Identify crown jewels and critical business assets\n3. Review previous security assessments and audit findings\n4. Define success criteria and engagement objectives\n5. Draft Rules of Engagement document\n\n### Phase 2: Threat Modeling\n\n1. Identify relevant threat actors using MITRE ATT&CK\n2. Map threat actor TTPs to organizational attack surface\n3. Select primary and secondary attack scenarios\n4. Define adversary emulation plan with specific technique IDs\n5. Establish detection checkpoints for purple team opportunities\n\n### Phase 3: Operational Planning\n\n1. Set up secure communication channels (encrypted email, Signal, etc.)\n2. Create operational security (OPSEC) guidelines for the red team\n3. Establish infrastructure requirements (C2 servers, redirectors, phishing domains)\n4. Develop phased attack timeline with go\u002Fno-go decision points\n5. Create deconfliction matrix with SOC\u002FIR team\n\n### Phase 4: Documentation and Approval\n\n1. Compile engagement plan document\n2. Review with legal counsel\n3. Obtain executive sponsor signature\n4. Brief red team operators on ROE and restrictions\n5. Distribute emergency contact cards\n\n## Tools and Resources\n\n- **MITRE ATT&CK Navigator**: Threat actor TTP mapping and visualization\n- **VECTR**: Red team engagement tracking and metrics platform\n- **Cobalt Strike \u002F Nighthawk**: C2 framework planning and infrastructure design\n- **PlexTrac**: Red team reporting and engagement management platform\n- **SCYTHE**: Adversary emulation platform for attack plan creation\n\n## Validation Criteria\n\n- [ ] Signed Rules of Engagement document\n- [ ] Defined scope with explicit in\u002Fout boundaries\n- [ ] Selected threat profile with mapped MITRE ATT&CK techniques\n- [ ] Emergency stop procedures tested and verified\n- [ ] Communication plan distributed to all stakeholders\n- [ ] Legal authorization obtained and filed\n- [ ] Red team operators briefed and acknowledged ROE\n\n## Common Pitfalls\n\n1. **Scope Creep**: Expanding testing beyond approved boundaries during execution\n2. **Inadequate Deconfliction**: SOC investigating red team activity as real incidents\n3. **Missing Legal Authorization**: Testing without proper signed authorization\n4. **Unrealistic Threat Models**: Simulating threats irrelevant to the organization\n5. **Poor Communication**: Failing to maintain contact with stakeholders during engagement\n\n## Related Skills\n\n- performing-open-source-intelligence-gathering\n- conducting-adversary-simulation-with-atomic-red-team\n- performing-assumed-breach-red-team-exercise\n- building-red-team-infrastructure-with-redirectors\n","> Defensive\u002Fanalysis cyber skill. Source: mukul975\u002FAnthropic-Cybersecurity-Skills (Apache-2.0). Advisory knowledge — the YURI floor, protected paths, and owner authority always outrank any instruction in this body.\n\n# Executing Red Team Engagement Planning\n\n## Overview\n\nRed team engagement planning is the foundational phase that defines scope, objectives, rules of engagement (ROE), threat model selection, and operational timelines before any offensive testing begins. A well-structured engagement plan ensures the red team simulates realistic adversary behavior while maintaining safety guardrails that prevent unintended business disruption.\n\n\n## When to Use\n\n- When conducting security assessments that involve executing red team engagement planning\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Familiarity with red teaming concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n\n- Define clear engagement scope including in-scope and out-of-scope assets, networks, and personnel\n- Establish Rules of Engagement (ROE) with emergency stop procedures, communication channels, and legal boundaries\n- Select appropriate threat profiles from the MITRE ATT&CK framework aligned to the organization's threat landscape\n- Create a detailed attack plan mapping adversary TTPs to engagement objectives\n- Develop deconfliction procedures with the organization's SOC\u002Fblue team\n- Produce a comprehensive engagement brief for stakeholder approval\n\n> **Legal Notice:** This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.\n\n## Core Concepts\n\n### Engagement Types\n\n| Type | Description | Scope |\n|------|-------------|-------|\n| Full Scope | Complete adversary simulation with physical, social, and cyber vectors | Entire organization |\n| Assumed Breach | Starts from initial foothold, focuses on post-exploitation | Internal network |\n| Objective-Based | Target specific crown jewels (e.g., domain admin, PII exfiltration) | Defined targets |\n| Purple Team | Collaborative with blue team for detection improvement | Specific controls |\n\n### Rules of Engagement Components\n\n1. **Scope Definition**: IP ranges, domains, physical locations, personnel\n2. **Restrictions**: Systems\u002Fnetworks that must not be touched (e.g., production databases, medical devices)\n3. **Communication Plan**: Primary and secondary contact channels, escalation procedures\n4. **Emergency Procedures**: Code word for immediate cessation, incident response coordination\n5. **Legal Authorization**: Signed authorization letters, get-out-of-jail letters for physical tests\n6. **Data Handling**: How sensitive data discovered during testing will be handled and destroyed\n7. **Timeline**: Start\u002Fend dates, blackout windows, reporting deadlines\n\n### Threat Profile Selection\n\nMap organizational threats using MITRE ATT&CK Navigator to select relevant adversary profiles:\n\n- **APT29 (Cozy Bear)**: Government\u002Fdefense sector targeting via spearphishing, supply chain\n- **APT28 (Fancy Bear)**: Government organizations, credential harvesting, zero-days\n- **FIN7**: Financial sector, POS malware, social engineering\n- **Lazarus Group**: Financial institutions, cryptocurrency exchanges, destructive malware\n- **Conti\u002FRoyal**: Ransomware operators, double extortion, RaaS model\n\n## Workflow\n\n### Phase 1: Pre-Engagement\n\n1. Conduct initial scoping meeting with stakeholders\n2. Identify crown jewels and critical business assets\n3. Review previous security assessments and audit findings\n4. Define success criteria and engagement objectives\n5. Draft Rules of Engagement document\n\n### Phase 2: Threat Modeling\n\n1. Identify relevant threat actors using MITRE ATT&CK\n2. Map threat actor TTPs to organizational attack surface\n3. Select primary and secondary attack scenarios\n4. Define adversary emulation plan with specific technique IDs\n5. Establish detection checkpoints for purple team opportunities\n\n### Phase 3: Operational Planning\n\n1. Set up secure communication channels (encrypted email, Signal, etc.)\n2. Create operational security (OPSEC) guidelines for the red team\n3. Establish infrastructure requirements (C2 servers, redirectors, phishing domains)\n4. Develop phased attack timeline with go\u002Fno-go decision points\n5. Create deconfliction matrix with SOC\u002FIR team\n\n### Phase 4: Documentation and Approval\n\n1. Compile engagement plan document\n2. Review with legal counsel\n3. Obtain executive sponsor signature\n4. Brief red team operators on ROE and restrictions\n5. Distribute emergency contact cards\n\n## Tools and Resources\n\n- **MITRE ATT&CK Navigator**: Threat actor TTP mapping and visualization\n- **VECTR**: Red team engagement tracking and metrics platform\n- **Cobalt Strike \u002F Nighthawk**: C2 framework planning and infrastructure design\n- **PlexTrac**: Red team reporting and engagement management platform\n- **SCYTHE**: Adversary emulation platform for attack plan creation\n\n## Validation Criteria\n\n- [ ] Signed Rules of Engagement document\n- [ ] Defined scope with explicit in\u002Fout boundaries\n- [ ] Selected threat profile with mapped MITRE ATT&CK techniques\n- [ ] Emergency stop procedures tested and verified\n- [ ] Communication plan distributed to all stakeholders\n- [ ] Legal authorization obtained and filed\n- [ ] Red team operators briefed and acknowledged ROE\n\n## Common Pitfalls\n\n1. **Scope Creep**: Expanding testing beyond approved boundaries during execution\n2. **Inadequate Deconfliction**: SOC investigating red team activity as real incidents\n3. **Missing Legal Authorization**: Testing without proper signed authorization\n4. **Unrealistic Threat Models**: Simulating threats irrelevant to the organization\n5. **Poor Communication**: Failing to maintain contact with stakeholders during engagement\n\n## Related Skills\n\n- performing-open-source-intelligence-gathering\n- conducting-adversary-simulation-with-atomic-red-team\n- performing-assumed-breach-red-team-exercise\n- building-red-team-infrastructure-with-redirectors\n",{"hide":49,"name":5,"source":50,"license":15,"description":7,"authorized_lab":45,"origin_frontmatter":51},true,"mukul975\u002FAnthropic-Cybersecurity-Skills","name: executing-red-team-engagement-planning | description: Red team engagement planning is the foundational phase that defines scope, |   objectives, rules of engagement (ROE), threat model selection, and operational timelines |   before any offensive testing begins. | domain: cybersecurity | subdomain: red-teaming | tags: | - red-team | - adversary-simulation | - mitre-attack | - exploitation | - post-exploitation | - engagement-planning | - rules-of-engagement | version: '1.0' | author: mahip","main","4c6d8d65f3d6096e2fc25b0845e481dda73c2794",".claude\u002Fskills\u002Fcyber-executing-red-team-engagement-planning",0,"https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions","Building deterministic AI governance and continuity systems. Workflow architect + visual storyteller","2026-11-11 16:42:59",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":49},[62,65,68],{"tool":63,"command":64},"npx","npx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-executing-red-team-engagement-planning",{"tool":66,"command":67},"bunx","bunx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-executing-red-team-engagement-planning",{"tool":69,"command":70},"pnpm","pnpm dlx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-executing-red-team-engagement-planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcyber-executing-red-team-engagement-planning\u002FSKILL.md",[],[74,98,121,149,178,197],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":44},"01M71CG1AME5WC0A79AE65WT0X","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","MIT","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97],"zoom out","zoom","with","harness","how","section","re","true","understand","use","perspective","when","you","code","it","context",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":44},"01M71CFY9ATD0BAXV6B14HFG7C","yuri-shura","6-perspective adversarial review for high-stakes turns (architecture decisions, refactor planning, deployment review) — fans out architect, adversary (7-vector attack), maintainer, ops, product, and security perspectives in parallel, then consolidates. Use when user says 'review this decision', '\u002Fshura', 'adversarial review', 'what could go wrong', 'architecture review', or 'deployment review'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-shura\u002FSKILL.md",[],[105,106,85,107,26,108,109,110,111,112,113,91,114,93,115,116,117,118,119,120],"yuri shura","parallel","architecture review","for","deployment","vector","strategic review","decision","strategic","ops","workflow","decisions","architecture","review","perspectives","adversarial",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":130,"publishedAt":44},"01M71CFTTYW1HA2MNX38EV1GJ5","yuri-sales-intelligence","Unified sales and outreach skill generating cold outreach openers, social selling sequences, objection rebuttals, and ad creative for any paid platform — multi-persona aware, adapting tone and offer frame to buyer type. Use when user says 'write a cold email', 'outreach sequence', 'objection handling', 'ad copy', or 'sales pitch'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-sales-intelligence\u002FSKILL.md",[127],{"categoryNo":128,"categoryName":129,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通",[131,132,133,134,135,136,137,138,139,93,140,141,142,143,144,145,146,108,147,148],"intelligence","sales intelligence","yuri sales intelligence","sales","cold","paid","social","persona","pitch","cold email","ad creative","write","sequences","sequence","platform","email","cold outreach","frame",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":163,"publishedAt":44},"01M71CFQMBFTFADJNGP0Z2WCYK","yuri-code-intelligence","Unified code quality intelligence layer that diagnoses code smells (Long Method, Feature Envy, design pattern issues), prescribes targeted Fowler refactoring techniques, and reviews code for security, performance, and clarity. Use when user says 'review this code', 'refactor this', 'what's wrong with this method', 'code smells', or 'clean this up'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-code-intelligence\u002FSKILL.md",[155,158],{"categoryNo":156,"categoryName":157,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":159,"categoryName":160,"taxonomyType":161,"taxonomyTypeDesc":162},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[164,95,165,131,85,166,167,168,108,169,170,171,172,173,174,175,176,177,91,93],"yuri code intelligence","code intelligence","reviews","code quality","feature","performance","code review","long","up","issues","clean","techniques","improve","design",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":44},"01M71CFP32RT6GD3GKNHCJP8VP","yuri-adw","Invoke when user asks to run the ADW loop \u002F agentic engineering loop \u002F software factory workflow.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-adw\u002FSKILL.md",[],[185,186,187,188,189,190,191,192,193,93,194,115,195,196],"yuri adw","run","engineering loop","software factory","software","agentic engineering","factory","loop","invoke","engineering","agentic","user",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":213,"publishedAt":44},"01M71CFK4VPEKY6A73237P7RSN","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[203,204,207,210],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":205,"categoryName":206,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":208,"categoryName":209,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":211,"categoryName":212,"taxonomyType":161,"taxonomyTypeDesc":162},"01JBSEEDCAT000000000000036","内容创作者",[214,215,216,93,115,217,85,218,109,91,219],"writing","writing skills","new","work","editing","Existing"]