[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0D4KTES2BTAAH196QFCMG":3,"skill-same:01M7F0D4KTES2BTAAH196QFCMG":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7F0D4KTES2BTAAH196QFCMG","linkerd-patterns",null,"Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.","shotcowboystyle\u002Fag-skills","shotcowboystyle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62471?v=4","01M7EZTCFCZJ6K3MYW8BPM4X6R","Curtis Blanton","01M7EZTCG1S5M04J90A931X9BX",0,"MIT","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcloud-infrastructure\u002Fskills\u002Flinkerd-patterns\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: linkerd-patterns\ndescription: Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.\nlast_verified: 2026-10-27\n---\n\n# Linkerd Patterns\n\nProduction patterns for Linkerd service mesh - the lightweight, security-first service mesh for Kubernetes.\n\n## When to Use This Skill\n\n- Setting up a lightweight service mesh\n- Implementing automatic mTLS\n- Configuring weighted traffic splits for canary deployments\n- Per-route routing, retries and timeouts with Gateway API routes\n- Multi-cluster service mesh\n\n## Core Concepts\n\n### 1. Linkerd Architecture\n\n```\n┌─────────────────────────────────────────────┐\n│                Control Plane                │\n│ ┌───────────┐ ┌──────────┐ ┌────────────┐   │\n│ │destination│ │ identity │ │proxy-inject│   │\n│ └───────────┘ └──────────┘ └────────────┘   │\n└─────────────────────────────────────────────┘\n                      │\n┌─────────────────────────────────────────────┐\n│                 Data Plane                   │\n│  ┌─────┐    ┌─────┐    ┌─────┐             │\n│  │proxy│────│proxy│────│proxy│             │\n│  └─────┘    └─────┘    └─────┘             │\n│     │           │           │               │\n│  ┌──┴──┐    ┌──┴──┐    ┌──┴──┐            │\n│  │ app │    │ app │    │ app │            │\n│  └─────┘    └─────┘    └─────┘            │\n└─────────────────────────────────────────────┘\n```\n\n### 2. Key Resources\n\n| Resource                                     | Purpose                                                 |\n| -------------------------------------------- | ------------------------------------------------------- |\n| **HTTPRoute \u002F GRPCRoute** (Gateway API)      | Routing, weighted splits, retries and timeouts per route |\n| **Server**                                   | Names a port on a set of pods for policy                |\n| **AuthorizationPolicy**                      | Allows traffic to a Server, route or namespace          |\n| **MeshTLSAuthentication \u002F NetworkAuthentication** | Who the policy allows: mesh identities or CIDRs     |\n\nLinkerd's routing and policy features use the Kubernetes Gateway API types. SMI\n`TrafficSplit` (the SMI project is archived) and the `linkerd-smi` extension are\nnot used for new setups. ServiceProfiles still work, but new features land on\nHTTPRoute\u002FGRPCRoute, and a ServiceProfile on a Service overrides any route-level\nretry and timeout annotations.\n\n## Templates\n\n### Template 1: Mesh Installation\n\nThe Linkerd project publishes open-source *edge* releases (`edge-YY.M.N`);\nversioned stable releases come from vendors. Use a CLI version that matches the\ncontrol plane. The example uses Homebrew; for other systems, follow the\n[official installation guide](https:\u002F\u002Flinkerd.io\u002F2-edge\u002Fgetting-started\u002F).\n\n```bash\n# Install the CLI with Homebrew\nbrew install linkerd\nlinkerd version\n\n# Linkerd needs the Gateway API CRDs. Check whether they are already installed\n# (prints the bundle version) and that it is in Linkerd's compatibility table\nkubectl get crds\u002Fhttproutes.gateway.networking.k8s.io \\\n  -o \"jsonpath={.metadata.annotations.gateway\\.networking\\.k8s\\.io\u002Fbundle-version}\"\n# If not found, install a compatible version (1.5.1 at the time of writing)\nkubectl apply --server-side -f https:\u002F\u002Fgithub.com\u002Fkubernetes-sigs\u002Fgateway-api\u002Freleases\u002Fdownload\u002Fv1.5.1\u002Fstandard-install.yaml\n\n# Validate cluster\nlinkerd check --pre\n\n# Install CRDs\nlinkerd install --crds | kubectl apply -f -\n\n# Install control plane\nlinkerd install | kubectl apply -f -\n\n# Verify installation\nlinkerd check\n\n# Install viz extension (optional)\nlinkerd viz install | kubectl apply -f -\n```\n\n### Template 2: Inject Namespace\n\n```yaml\n# Automatic injection for namespace\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: my-app\n  annotations:\n    linkerd.io\u002Finject: enabled\n---\n# Or inject specific deployment\napiVersion: apps\u002Fv1\nkind: Deployment\nmetadata:\n  name: my-app\nspec:\n  selector:\n    matchLabels:\n      app: my-app\n  template:\n    metadata:\n      labels:\n        app: my-app\n      annotations:\n        linkerd.io\u002Finject: enabled # on the pod template, not the Deployment\n    spec:\n      containers:\n        - name: app\n          image: registry.example.com\u002Fmy-app:1.0.0\n```\n\n### Template 3: Retries and Timeouts on a Route\n\nRetries are opt-in and only safe for idempotent requests, so put them on a\nroute that matches only those requests.\n\n```yaml\napiVersion: gateway.networking.k8s.io\u002Fv1\nkind: HTTPRoute\nmetadata:\n  name: users-get\n  namespace: my-namespace\n  annotations:\n    retry.linkerd.io\u002Fhttp: 5xx\n    retry.linkerd.io\u002Flimit: \"2\"\n    retry.linkerd.io\u002Ftimeout: 300ms # per-attempt timeout\n    timeout.linkerd.io\u002Frequest: 5s # whole request, including retries\nspec:\n  parentRefs:\n    - name: my-service\n      kind: Service\n      group: \"\"\n      port: 8080\n  rules:\n    - matches:\n        - method: GET\n          path:\n            type: PathPrefix\n            value: \u002Fapi\u002Fusers\n      backendRefs:\n        - name: my-service\n          port: 8080\n```\n\nThe same annotations on the Service apply to every route of that Service.\n\n### Template 4: Weighted Traffic Split (Canary)\n\n```yaml\napiVersion: gateway.networking.k8s.io\u002Fv1\nkind: HTTPRoute\nmetadata:\n  name: my-service-canary\n  namespace: my-namespace\nspec:\n  parentRefs:\n    - name: my-service\n      kind: Service\n      group: \"\"\n      port: 8080\n  rules:\n    - backendRefs:\n        - name: my-service-stable\n          port: 8080\n          weight: 90\n        - name: my-service-canary\n          port: 8080\n          weight: 10\n```\n\nShift the weights step by step, or let Flagger or Argo Rollouts (Gateway API\nplugin) drive them.\n\n### More templates\n\n`references\u002Fdetails.md` covers header- and path-based routing with HTTPRoute,\nauthorization policy (Server, AuthorizationPolicy, MeshTLSAuthentication,\nNetworkAuthentication) and multi-cluster linking with `link-gen`.\n\n## Monitoring Commands\n\n```bash\n# Live traffic view\nlinkerd viz top deploy\u002Fmy-app\n\n# Per-route metrics (HTTPRoute\u002FGRPCRoute or ServiceProfile routes)\nlinkerd viz routes deploy\u002Fmy-app\n\n# Check proxy status\nlinkerd viz stat deploy -n my-namespace\n\n# View service dependencies\nlinkerd viz edges deploy -n my-namespace\n\n# Dashboard\nlinkerd viz dashboard\n```\n\n## Debugging\n\n```bash\n# Check injection status\nlinkerd check --proxy -n my-namespace\n\n# View proxy logs\nkubectl logs deploy\u002Fmy-app -c linkerd-proxy\n\n# Debug identity\u002FTLS\nlinkerd identity -n my-namespace\n\n# Tap traffic (live)\nlinkerd viz tap deploy\u002Fmy-app --to deploy\u002Fmy-backend\n```\n\n## Best Practices\n\n### Do's\n\n- **Enable mTLS everywhere** - It's automatic with Linkerd\n- **Use HTTPRoute\u002FGRPCRoute** - Per-route routing, retries and timeouts\n- **Limit retries** - Retry idempotent routes only, with `retry.linkerd.io\u002Flimit`\n- **Monitor golden metrics** - Success rate, latency, throughput\n\n### Don'ts\n\n- **Don't skip check** - Always run `linkerd check` after changes\n- **Don't over-configure** - Linkerd defaults are sensible\n- **Don't mix ServiceProfiles and route annotations** - A ServiceProfile overrides route-level retries and timeouts\n- **Don't forget timeouts** - Set appropriate values per route\n","# Linkerd Patterns\n\nProduction patterns for Linkerd service mesh - the lightweight, security-first service mesh for Kubernetes.\n\n## When to Use This Skill\n\n- Setting up a lightweight service mesh\n- Implementing automatic mTLS\n- Configuring weighted traffic splits for canary deployments\n- Per-route routing, retries and timeouts with Gateway API routes\n- Multi-cluster service mesh\n\n## Core Concepts\n\n### 1. Linkerd Architecture\n\n```\n┌─────────────────────────────────────────────┐\n│                Control Plane                │\n│ ┌───────────┐ ┌──────────┐ ┌────────────┐   │\n│ │destination│ │ identity │ │proxy-inject│   │\n│ └───────────┘ └──────────┘ └────────────┘   │\n└─────────────────────────────────────────────┘\n                      │\n┌─────────────────────────────────────────────┐\n│                 Data Plane                   │\n│  ┌─────┐    ┌─────┐    ┌─────┐             │\n│  │proxy│────│proxy│────│proxy│             │\n│  └─────┘    └─────┘    └─────┘             │\n│     │           │           │               │\n│  ┌──┴──┐    ┌──┴──┐    ┌──┴──┐            │\n│  │ app │    │ app │    │ app │            │\n│  └─────┘    └─────┘    └─────┘            │\n└─────────────────────────────────────────────┘\n```\n\n### 2. Key Resources\n\n| Resource                                     | Purpose                                                 |\n| -------------------------------------------- | ------------------------------------------------------- |\n| **HTTPRoute \u002F GRPCRoute** (Gateway API)      | Routing, weighted splits, retries and timeouts per route |\n| **Server**                                   | Names a port on a set of pods for policy                |\n| **AuthorizationPolicy**                      | Allows traffic to a Server, route or namespace          |\n| **MeshTLSAuthentication \u002F NetworkAuthentication** | Who the policy allows: mesh identities or CIDRs     |\n\nLinkerd's routing and policy features use the Kubernetes Gateway API types. SMI\n`TrafficSplit` (the SMI project is archived) and the `linkerd-smi` extension are\nnot used for new setups. ServiceProfiles still work, but new features land on\nHTTPRoute\u002FGRPCRoute, and a ServiceProfile on a Service overrides any route-level\nretry and timeout annotations.\n\n## Templates\n\n### Template 1: Mesh Installation\n\nThe Linkerd project publishes open-source *edge* releases (`edge-YY.M.N`);\nversioned stable releases come from vendors. Use a CLI version that matches the\ncontrol plane. The example uses Homebrew; for other systems, follow the\n[official installation guide](https:\u002F\u002Flinkerd.io\u002F2-edge\u002Fgetting-started\u002F).\n\n```bash\n# Install the CLI with Homebrew\nbrew install linkerd\nlinkerd version\n\n# Linkerd needs the Gateway API CRDs. Check whether they are already installed\n# (prints the bundle version) and that it is in Linkerd's compatibility table\nkubectl get crds\u002Fhttproutes.gateway.networking.k8s.io \\\n  -o \"jsonpath={.metadata.annotations.gateway\\.networking\\.k8s\\.io\u002Fbundle-version}\"\n# If not found, install a compatible version (1.5.1 at the time of writing)\nkubectl apply --server-side -f https:\u002F\u002Fgithub.com\u002Fkubernetes-sigs\u002Fgateway-api\u002Freleases\u002Fdownload\u002Fv1.5.1\u002Fstandard-install.yaml\n\n# Validate cluster\nlinkerd check --pre\n\n# Install CRDs\nlinkerd install --crds | kubectl apply -f -\n\n# Install control plane\nlinkerd install | kubectl apply -f -\n\n# Verify installation\nlinkerd check\n\n# Install viz extension (optional)\nlinkerd viz install | kubectl apply -f -\n```\n\n### Template 2: Inject Namespace\n\n```yaml\n# Automatic injection for namespace\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: my-app\n  annotations:\n    linkerd.io\u002Finject: enabled\n---\n# Or inject specific deployment\napiVersion: apps\u002Fv1\nkind: Deployment\nmetadata:\n  name: my-app\nspec:\n  selector:\n    matchLabels:\n      app: my-app\n  template:\n    metadata:\n      labels:\n        app: my-app\n      annotations:\n        linkerd.io\u002Finject: enabled # on the pod template, not the Deployment\n    spec:\n      containers:\n        - name: app\n          image: registry.example.com\u002Fmy-app:1.0.0\n```\n\n### Template 3: Retries and Timeouts on a Route\n\nRetries are opt-in and only safe for idempotent requests, so put them on a\nroute that matches only those requests.\n\n```yaml\napiVersion: gateway.networking.k8s.io\u002Fv1\nkind: HTTPRoute\nmetadata:\n  name: users-get\n  namespace: my-namespace\n  annotations:\n    retry.linkerd.io\u002Fhttp: 5xx\n    retry.linkerd.io\u002Flimit: \"2\"\n    retry.linkerd.io\u002Ftimeout: 300ms # per-attempt timeout\n    timeout.linkerd.io\u002Frequest: 5s # whole request, including retries\nspec:\n  parentRefs:\n    - name: my-service\n      kind: Service\n      group: \"\"\n      port: 8080\n  rules:\n    - matches:\n        - method: GET\n          path:\n            type: PathPrefix\n            value: \u002Fapi\u002Fusers\n      backendRefs:\n        - name: my-service\n          port: 8080\n```\n\nThe same annotations on the Service apply to every route of that Service.\n\n### Template 4: Weighted Traffic Split (Canary)\n\n```yaml\napiVersion: gateway.networking.k8s.io\u002Fv1\nkind: HTTPRoute\nmetadata:\n  name: my-service-canary\n  namespace: my-namespace\nspec:\n  parentRefs:\n    - name: my-service\n      kind: Service\n      group: \"\"\n      port: 8080\n  rules:\n    - backendRefs:\n        - name: my-service-stable\n          port: 8080\n          weight: 90\n        - name: my-service-canary\n          port: 8080\n          weight: 10\n```\n\nShift the weights step by step, or let Flagger or Argo Rollouts (Gateway API\nplugin) drive them.\n\n### More templates\n\n`references\u002Fdetails.md` covers header- and path-based routing with HTTPRoute,\nauthorization policy (Server, AuthorizationPolicy, MeshTLSAuthentication,\nNetworkAuthentication) and multi-cluster linking with `link-gen`.\n\n## Monitoring Commands\n\n```bash\n# Live traffic view\nlinkerd viz top deploy\u002Fmy-app\n\n# Per-route metrics (HTTPRoute\u002FGRPCRoute or ServiceProfile routes)\nlinkerd viz routes deploy\u002Fmy-app\n\n# Check proxy status\nlinkerd viz stat deploy -n my-namespace\n\n# View service dependencies\nlinkerd viz edges deploy -n my-namespace\n\n# Dashboard\nlinkerd viz dashboard\n```\n\n## Debugging\n\n```bash\n# Check injection status\nlinkerd check --proxy -n my-namespace\n\n# View proxy logs\nkubectl logs deploy\u002Fmy-app -c linkerd-proxy\n\n# Debug identity\u002FTLS\nlinkerd identity -n my-namespace\n\n# Tap traffic (live)\nlinkerd viz tap deploy\u002Fmy-app --to deploy\u002Fmy-backend\n```\n\n## Best Practices\n\n### Do's\n\n- **Enable mTLS everywhere** - It's automatic with Linkerd\n- **Use HTTPRoute\u002FGRPCRoute** - Per-route routing, retries and timeouts\n- **Limit retries** - Retry idempotent routes only, with `retry.linkerd.io\u002Flimit`\n- **Monitor golden metrics** - Success rate, latency, throughput\n\n### Don'ts\n\n- **Don't skip check** - Always run `linkerd check` after changes\n- **Don't over-configure** - Linkerd defaults are sensible\n- **Don't mix ServiceProfiles and route annotations** - A ServiceProfile overrides route-level retries and timeouts\n- **Don't forget timeouts** - Set appropriate values per route\n",{"name":5,"description":7,"last_verified":24},1793059200000,"main","f846d9a97082ff30d613b55a085cef425d822473","plugins\u002Fcloud-infrastructure\u002Fskills\u002Flinkerd-patterns","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle","https:\u002F\u002Fshotcowboystyle.github.io","Building smarter with AI, automation & modern tools. Exploring how far one person can go without a big team using today’s AI.","2026-11-10 04:58:27",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add shotcowboystyle\u002Fag-skills --skill linkerd-patterns",{"tool":39,"command":40},"bunx","bunx skills add shotcowboystyle\u002Fag-skills --skill linkerd-patterns",{"tool":42,"command":43},"pnpm","pnpm dlx skills add shotcowboystyle\u002Fag-skills --skill linkerd-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcloud-infrastructure\u002Fskills\u002Flinkerd-patterns\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fdetails.md","REFERENCE","参考文档",3242,"https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcloud-infrastructure\u002Fskills\u002Flinkerd-patterns\u002Freferences\u002Fdetails.md",[54,60,67,74,81,88],{"skillNo":55,"name":56,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7F1YRY5S5QRJ1V0BJS130QX","no-description","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fno-description\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7F1Y9BV2FJNQJ3NB32JS5CM","good-skill","Fixture skill that satisfies every rule.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fgood-skill\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7F1XXBQ3NQRXZSS0KAGAR9V","broken-link","Links to a reference file that does not exist.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbroken-link\u002FSKILL.md",[],[],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7F1XBX4R46NR9W0HXQ7XCDX","Bad_Name","Name violates the kebab-case rule and does not match the directory.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fbad-name\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7F1WNAF8WNEQ7S5HKT5VK0D","skill-authoring","Write, review, and validate portable agent skills in SKILL.md format. Use when creating a new skill, editing an existing one, or asked whether a skill follows the Agent Skills spec.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-authoring\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7F1W30TC0XFNSF7YBRGETK2","weigh-bags","Record scale readings for each bag — empty (tare), outbound, current, final — and reconcile them against the itemised inventory to find unaccounted weight. Use when the user gives a bag weight, says how heavy something is, weighs their luggage, or asks how close to the limit they are. Appends to bags.yaml and runs scripts\u002Freconcile.py.","https:\u002F\u002Fgithub.com\u002Fshotcowboystyle\u002Fag-skills\u002Fblob\u002Fmain\u002Fplugins\u002Ftravel-packing-assistant\u002Fskills\u002Fweigh-bags\u002FSKILL.md",[],[]]