{
  "schemaVersion": "1.0",
  "item": {
    "slug": "senior-architect",
    "name": "Senior Architect",
    "source": "tencent",
    "type": "skill",
    "category": "AI 智能",
    "sourceUrl": "https://clawhub.ai/alirezarezvani/senior-architect",
    "canonicalUrl": "https://clawhub.ai/alirezarezvani/senior-architect",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/senior-architect",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=senior-architect",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md",
      "references/architecture_patterns.md",
      "references/system_design_workflows.md",
      "references/tech_decision_guide.md",
      "scripts/architecture_diagram_generator.py",
      "scripts/dependency_analyzer.py"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-30T16:55:25.780Z",
      "expiresAt": "2026-05-07T16:55:25.780Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
        "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/senior-architect"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/senior-architect",
    "agentPageUrl": "https://openagent3.xyz/skills/senior-architect/agent",
    "manifestUrl": "https://openagent3.xyz/skills/senior-architect/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/senior-architect/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Senior Architect",
        "body": "Architecture design and analysis tools for making informed technical decisions."
      },
      {
        "title": "Table of Contents",
        "body": "Quick Start\nTools Overview\n\nArchitecture Diagram Generator\nDependency Analyzer\nProject Architect\n\n\nDecision Workflows\n\nDatabase Selection\nArchitecture Pattern Selection\nMonolith vs Microservices\n\n\nReference Documentation\nTech Stack Coverage\nCommon Commands"
      },
      {
        "title": "Quick Start",
        "body": "# Generate architecture diagram from project\npython scripts/architecture_diagram_generator.py ./my-project --format mermaid\n\n# Analyze dependencies for issues\npython scripts/dependency_analyzer.py ./my-project --output json\n\n# Get architecture assessment\npython scripts/project_architect.py ./my-project --verbose"
      },
      {
        "title": "1. Architecture Diagram Generator",
        "body": "Generates architecture diagrams from project structure in multiple formats.\n\nSolves: \"I need to visualize my system architecture for documentation or team discussion\"\n\nInput: Project directory path\nOutput: Diagram code (Mermaid, PlantUML, or ASCII)\n\nSupported diagram types:\n\ncomponent - Shows modules and their relationships\nlayer - Shows architectural layers (presentation, business, data)\ndeployment - Shows deployment topology\n\nUsage:\n\n# Mermaid format (default)\npython scripts/architecture_diagram_generator.py ./project --format mermaid --type component\n\n# PlantUML format\npython scripts/architecture_diagram_generator.py ./project --format plantuml --type layer\n\n# ASCII format (terminal-friendly)\npython scripts/architecture_diagram_generator.py ./project --format ascii\n\n# Save to file\npython scripts/architecture_diagram_generator.py ./project -o architecture.md\n\nExample output (Mermaid):\n\ngraph TD\n    A[API Gateway] --> B[Auth Service]\n    A --> C[User Service]\n    B --> D[(PostgreSQL)]\n    C --> D"
      },
      {
        "title": "2. Dependency Analyzer",
        "body": "Analyzes project dependencies for coupling, circular dependencies, and outdated packages.\n\nSolves: \"I need to understand my dependency tree and identify potential issues\"\n\nInput: Project directory path\nOutput: Analysis report (JSON or human-readable)\n\nAnalyzes:\n\nDependency tree (direct and transitive)\nCircular dependencies between modules\nCoupling score (0-100)\nOutdated packages\n\nSupported package managers:\n\nnpm/yarn (package.json)\nPython (requirements.txt, pyproject.toml)\nGo (go.mod)\nRust (Cargo.toml)\n\nUsage:\n\n# Human-readable report\npython scripts/dependency_analyzer.py ./project\n\n# JSON output for CI/CD integration\npython scripts/dependency_analyzer.py ./project --output json\n\n# Check only for circular dependencies\npython scripts/dependency_analyzer.py ./project --check circular\n\n# Verbose mode with recommendations\npython scripts/dependency_analyzer.py ./project --verbose\n\nExample output:\n\nDependency Analysis Report\n==========================\nTotal dependencies: 47 (32 direct, 15 transitive)\nCoupling score: 72/100 (moderate)\n\nIssues found:\n- CIRCULAR: auth → user → permissions → auth\n- OUTDATED: lodash 4.17.15 → 4.17.21 (security)\n\nRecommendations:\n1. Extract shared interface to break circular dependency\n2. Update lodash to fix CVE-2020-8203"
      },
      {
        "title": "3. Project Architect",
        "body": "Analyzes project structure and detects architectural patterns, code smells, and improvement opportunities.\n\nSolves: \"I want to understand the current architecture and identify areas for improvement\"\n\nInput: Project directory path\nOutput: Architecture assessment report\n\nDetects:\n\nArchitectural patterns (MVC, layered, hexagonal, microservices indicators)\nCode organization issues (god classes, mixed concerns)\nLayer violations\nMissing architectural components\n\nUsage:\n\n# Full assessment\npython scripts/project_architect.py ./project\n\n# Verbose with detailed recommendations\npython scripts/project_architect.py ./project --verbose\n\n# JSON output\npython scripts/project_architect.py ./project --output json\n\n# Check specific aspect\npython scripts/project_architect.py ./project --check layers\n\nExample output:\n\nArchitecture Assessment\n=======================\nDetected pattern: Layered Architecture (confidence: 85%)\n\nStructure analysis:\n  ✓ controllers/  - Presentation layer detected\n  ✓ services/     - Business logic layer detected\n  ✓ repositories/ - Data access layer detected\n  ⚠ models/       - Mixed domain and DTOs\n\nIssues:\n- LARGE FILE: UserService.ts (1,847 lines) - consider splitting\n- MIXED CONCERNS: PaymentController contains business logic\n\nRecommendations:\n1. Split UserService into focused services\n2. Move business logic from controllers to services\n3. Separate domain models from DTOs"
      },
      {
        "title": "Database Selection Workflow",
        "body": "Use when choosing a database for a new project or migrating existing data.\n\nStep 1: Identify data characteristics\n\nCharacteristicPoints to SQLPoints to NoSQLStructured with relationships✓ACID transactions required✓Flexible/evolving schema✓Document-oriented data✓Time-series data✓ (specialized)\n\nStep 2: Evaluate scale requirements\n\n<1M records, single region → PostgreSQL or MySQL\n1M-100M records, read-heavy → PostgreSQL with read replicas\n\n\n100M records, global distribution → CockroachDB, Spanner, or DynamoDB\n\n\nHigh write throughput (>10K/sec) → Cassandra or ScyllaDB\n\nStep 3: Check consistency requirements\n\nStrong consistency required → SQL or CockroachDB\nEventual consistency acceptable → DynamoDB, Cassandra, MongoDB\n\nStep 4: Document decision\nCreate an ADR (Architecture Decision Record) with:\n\nContext and requirements\nOptions considered\nDecision and rationale\nTrade-offs accepted\n\nQuick reference:\n\nPostgreSQL → Default choice for most applications\nMongoDB    → Document store, flexible schema\nRedis      → Caching, sessions, real-time features\nDynamoDB   → Serverless, auto-scaling, AWS-native\nTimescaleDB → Time-series data with SQL interface"
      },
      {
        "title": "Architecture Pattern Selection Workflow",
        "body": "Use when designing a new system or refactoring existing architecture.\n\nStep 1: Assess team and project size\n\nTeam SizeRecommended Starting Point1-3 developersModular monolith4-10 developersModular monolith or service-oriented10+ developersConsider microservices\n\nStep 2: Evaluate deployment requirements\n\nSingle deployment unit acceptable → Monolith\nIndependent scaling needed → Microservices\nMixed (some services scale differently) → Hybrid\n\nStep 3: Consider data boundaries\n\nShared database acceptable → Monolith or modular monolith\nStrict data isolation required → Microservices with separate DBs\nEvent-driven communication fits → Event-sourcing/CQRS\n\nStep 4: Match pattern to requirements\n\nRequirementRecommended PatternRapid MVP developmentModular MonolithIndependent team deploymentMicroservicesComplex domain logicDomain-Driven DesignHigh read/write ratio differenceCQRSAudit trail requiredEvent SourcingThird-party integrationsHexagonal/Ports & Adapters\n\nSee references/architecture_patterns.md for detailed pattern descriptions."
      },
      {
        "title": "Monolith vs Microservices Decision",
        "body": "Choose Monolith when:\n\nTeam is small (<10 developers)\n Domain boundaries are unclear\n Rapid iteration is priority\n Operational complexity must be minimized\n Shared database is acceptable\n\nChoose Microservices when:\n\nTeams can own services end-to-end\n Independent deployment is critical\n Different scaling requirements per component\n Technology diversity is needed\n Domain boundaries are well understood\n\nHybrid approach:\nStart with a modular monolith. Extract services only when:\n\nA module has significantly different scaling needs\nA team needs independent deployment\nTechnology constraints require separation"
      },
      {
        "title": "Reference Documentation",
        "body": "Load these files for detailed information:\n\nFileContainsLoad when user asks aboutreferences/architecture_patterns.md9 architecture patterns with trade-offs, code examples, and when to use\"which pattern?\", \"microservices vs monolith\", \"event-driven\", \"CQRS\"references/system_design_workflows.md6 step-by-step workflows for system design tasks\"how to design?\", \"capacity planning\", \"API design\", \"migration\"references/tech_decision_guide.mdDecision matrices for technology choices\"which database?\", \"which framework?\", \"which cloud?\", \"which cache?\""
      },
      {
        "title": "Tech Stack Coverage",
        "body": "Languages: TypeScript, JavaScript, Python, Go, Swift, Kotlin, Rust\nFrontend: React, Next.js, Vue, Angular, React Native, Flutter\nBackend: Node.js, Express, FastAPI, Go, GraphQL, REST\nDatabases: PostgreSQL, MySQL, MongoDB, Redis, DynamoDB, Cassandra\nInfrastructure: Docker, Kubernetes, Terraform, AWS, GCP, Azure\nCI/CD: GitHub Actions, GitLab CI, CircleCI, Jenkins"
      },
      {
        "title": "Common Commands",
        "body": "# Architecture visualization\npython scripts/architecture_diagram_generator.py . --format mermaid\npython scripts/architecture_diagram_generator.py . --format plantuml\npython scripts/architecture_diagram_generator.py . --format ascii\n\n# Dependency analysis\npython scripts/dependency_analyzer.py . --verbose\npython scripts/dependency_analyzer.py . --check circular\npython scripts/dependency_analyzer.py . --output json\n\n# Architecture assessment\npython scripts/project_architect.py . --verbose\npython scripts/project_architect.py . --check layers\npython scripts/project_architect.py . --output json"
      },
      {
        "title": "Getting Help",
        "body": "Run any script with --help for usage information\nCheck reference documentation for detailed patterns and workflows\nUse --verbose flag for detailed explanations and recommendations"
      }
    ],
    "body": "Senior Architect\n\nArchitecture design and analysis tools for making informed technical decisions.\n\nTable of Contents\nQuick Start\nTools Overview\nArchitecture Diagram Generator\nDependency Analyzer\nProject Architect\nDecision Workflows\nDatabase Selection\nArchitecture Pattern Selection\nMonolith vs Microservices\nReference Documentation\nTech Stack Coverage\nCommon Commands\nQuick Start\n# Generate architecture diagram from project\npython scripts/architecture_diagram_generator.py ./my-project --format mermaid\n\n# Analyze dependencies for issues\npython scripts/dependency_analyzer.py ./my-project --output json\n\n# Get architecture assessment\npython scripts/project_architect.py ./my-project --verbose\n\nTools Overview\n1. Architecture Diagram Generator\n\nGenerates architecture diagrams from project structure in multiple formats.\n\nSolves: \"I need to visualize my system architecture for documentation or team discussion\"\n\nInput: Project directory path Output: Diagram code (Mermaid, PlantUML, or ASCII)\n\nSupported diagram types:\n\ncomponent - Shows modules and their relationships\nlayer - Shows architectural layers (presentation, business, data)\ndeployment - Shows deployment topology\n\nUsage:\n\n# Mermaid format (default)\npython scripts/architecture_diagram_generator.py ./project --format mermaid --type component\n\n# PlantUML format\npython scripts/architecture_diagram_generator.py ./project --format plantuml --type layer\n\n# ASCII format (terminal-friendly)\npython scripts/architecture_diagram_generator.py ./project --format ascii\n\n# Save to file\npython scripts/architecture_diagram_generator.py ./project -o architecture.md\n\n\nExample output (Mermaid):\n\ngraph TD\n    A[API Gateway] --> B[Auth Service]\n    A --> C[User Service]\n    B --> D[(PostgreSQL)]\n    C --> D\n\n2. Dependency Analyzer\n\nAnalyzes project dependencies for coupling, circular dependencies, and outdated packages.\n\nSolves: \"I need to understand my dependency tree and identify potential issues\"\n\nInput: Project directory path Output: Analysis report (JSON or human-readable)\n\nAnalyzes:\n\nDependency tree (direct and transitive)\nCircular dependencies between modules\nCoupling score (0-100)\nOutdated packages\n\nSupported package managers:\n\nnpm/yarn (package.json)\nPython (requirements.txt, pyproject.toml)\nGo (go.mod)\nRust (Cargo.toml)\n\nUsage:\n\n# Human-readable report\npython scripts/dependency_analyzer.py ./project\n\n# JSON output for CI/CD integration\npython scripts/dependency_analyzer.py ./project --output json\n\n# Check only for circular dependencies\npython scripts/dependency_analyzer.py ./project --check circular\n\n# Verbose mode with recommendations\npython scripts/dependency_analyzer.py ./project --verbose\n\n\nExample output:\n\nDependency Analysis Report\n==========================\nTotal dependencies: 47 (32 direct, 15 transitive)\nCoupling score: 72/100 (moderate)\n\nIssues found:\n- CIRCULAR: auth → user → permissions → auth\n- OUTDATED: lodash 4.17.15 → 4.17.21 (security)\n\nRecommendations:\n1. Extract shared interface to break circular dependency\n2. Update lodash to fix CVE-2020-8203\n\n3. Project Architect\n\nAnalyzes project structure and detects architectural patterns, code smells, and improvement opportunities.\n\nSolves: \"I want to understand the current architecture and identify areas for improvement\"\n\nInput: Project directory path Output: Architecture assessment report\n\nDetects:\n\nArchitectural patterns (MVC, layered, hexagonal, microservices indicators)\nCode organization issues (god classes, mixed concerns)\nLayer violations\nMissing architectural components\n\nUsage:\n\n# Full assessment\npython scripts/project_architect.py ./project\n\n# Verbose with detailed recommendations\npython scripts/project_architect.py ./project --verbose\n\n# JSON output\npython scripts/project_architect.py ./project --output json\n\n# Check specific aspect\npython scripts/project_architect.py ./project --check layers\n\n\nExample output:\n\nArchitecture Assessment\n=======================\nDetected pattern: Layered Architecture (confidence: 85%)\n\nStructure analysis:\n  ✓ controllers/  - Presentation layer detected\n  ✓ services/     - Business logic layer detected\n  ✓ repositories/ - Data access layer detected\n  ⚠ models/       - Mixed domain and DTOs\n\nIssues:\n- LARGE FILE: UserService.ts (1,847 lines) - consider splitting\n- MIXED CONCERNS: PaymentController contains business logic\n\nRecommendations:\n1. Split UserService into focused services\n2. Move business logic from controllers to services\n3. Separate domain models from DTOs\n\nDecision Workflows\nDatabase Selection Workflow\n\nUse when choosing a database for a new project or migrating existing data.\n\nStep 1: Identify data characteristics\n\nCharacteristic\tPoints to SQL\tPoints to NoSQL\nStructured with relationships\t✓\t\nACID transactions required\t✓\t\nFlexible/evolving schema\t\t✓\nDocument-oriented data\t\t✓\nTime-series data\t\t✓ (specialized)\n\nStep 2: Evaluate scale requirements\n\n<1M records, single region → PostgreSQL or MySQL\n1M-100M records, read-heavy → PostgreSQL with read replicas\n\n100M records, global distribution → CockroachDB, Spanner, or DynamoDB\n\nHigh write throughput (>10K/sec) → Cassandra or ScyllaDB\n\nStep 3: Check consistency requirements\n\nStrong consistency required → SQL or CockroachDB\nEventual consistency acceptable → DynamoDB, Cassandra, MongoDB\n\nStep 4: Document decision Create an ADR (Architecture Decision Record) with:\n\nContext and requirements\nOptions considered\nDecision and rationale\nTrade-offs accepted\n\nQuick reference:\n\nPostgreSQL → Default choice for most applications\nMongoDB    → Document store, flexible schema\nRedis      → Caching, sessions, real-time features\nDynamoDB   → Serverless, auto-scaling, AWS-native\nTimescaleDB → Time-series data with SQL interface\n\nArchitecture Pattern Selection Workflow\n\nUse when designing a new system or refactoring existing architecture.\n\nStep 1: Assess team and project size\n\nTeam Size\tRecommended Starting Point\n1-3 developers\tModular monolith\n4-10 developers\tModular monolith or service-oriented\n10+ developers\tConsider microservices\n\nStep 2: Evaluate deployment requirements\n\nSingle deployment unit acceptable → Monolith\nIndependent scaling needed → Microservices\nMixed (some services scale differently) → Hybrid\n\nStep 3: Consider data boundaries\n\nShared database acceptable → Monolith or modular monolith\nStrict data isolation required → Microservices with separate DBs\nEvent-driven communication fits → Event-sourcing/CQRS\n\nStep 4: Match pattern to requirements\n\nRequirement\tRecommended Pattern\nRapid MVP development\tModular Monolith\nIndependent team deployment\tMicroservices\nComplex domain logic\tDomain-Driven Design\nHigh read/write ratio difference\tCQRS\nAudit trail required\tEvent Sourcing\nThird-party integrations\tHexagonal/Ports & Adapters\n\nSee references/architecture_patterns.md for detailed pattern descriptions.\n\nMonolith vs Microservices Decision\n\nChoose Monolith when:\n\n Team is small (<10 developers)\n Domain boundaries are unclear\n Rapid iteration is priority\n Operational complexity must be minimized\n Shared database is acceptable\n\nChoose Microservices when:\n\n Teams can own services end-to-end\n Independent deployment is critical\n Different scaling requirements per component\n Technology diversity is needed\n Domain boundaries are well understood\n\nHybrid approach: Start with a modular monolith. Extract services only when:\n\nA module has significantly different scaling needs\nA team needs independent deployment\nTechnology constraints require separation\nReference Documentation\n\nLoad these files for detailed information:\n\nFile\tContains\tLoad when user asks about\nreferences/architecture_patterns.md\t9 architecture patterns with trade-offs, code examples, and when to use\t\"which pattern?\", \"microservices vs monolith\", \"event-driven\", \"CQRS\"\nreferences/system_design_workflows.md\t6 step-by-step workflows for system design tasks\t\"how to design?\", \"capacity planning\", \"API design\", \"migration\"\nreferences/tech_decision_guide.md\tDecision matrices for technology choices\t\"which database?\", \"which framework?\", \"which cloud?\", \"which cache?\"\nTech Stack Coverage\n\nLanguages: TypeScript, JavaScript, Python, Go, Swift, Kotlin, Rust Frontend: React, Next.js, Vue, Angular, React Native, Flutter Backend: Node.js, Express, FastAPI, Go, GraphQL, REST Databases: PostgreSQL, MySQL, MongoDB, Redis, DynamoDB, Cassandra Infrastructure: Docker, Kubernetes, Terraform, AWS, GCP, Azure CI/CD: GitHub Actions, GitLab CI, CircleCI, Jenkins\n\nCommon Commands\n# Architecture visualization\npython scripts/architecture_diagram_generator.py . --format mermaid\npython scripts/architecture_diagram_generator.py . --format plantuml\npython scripts/architecture_diagram_generator.py . --format ascii\n\n# Dependency analysis\npython scripts/dependency_analyzer.py . --verbose\npython scripts/dependency_analyzer.py . --check circular\npython scripts/dependency_analyzer.py . --output json\n\n# Architecture assessment\npython scripts/project_architect.py . --verbose\npython scripts/project_architect.py . --check layers\npython scripts/project_architect.py . --output json\n\nGetting Help\nRun any script with --help for usage information\nCheck reference documentation for detailed patterns and workflows\nUse --verbose flag for detailed explanations and recommendations"
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/alirezarezvani/senior-architect",
    "publisherUrl": "https://clawhub.ai/alirezarezvani/senior-architect",
    "owner": "alirezarezvani",
    "version": "2.1.1",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/senior-architect",
    "downloadUrl": "https://openagent3.xyz/downloads/senior-architect",
    "agentUrl": "https://openagent3.xyz/skills/senior-architect/agent",
    "manifestUrl": "https://openagent3.xyz/skills/senior-architect/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/senior-architect/agent.md"
  }
}