[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79V79GSCTG634471XT0M6WK":3,"skill-same:01M79V79GSCTG634471XT0M6WK":79},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":38,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M79V79GSCTG634471XT0M6WK","chaos-engineer",null,"Designs chaos experiments, creates failure injection frameworks, and facilitates game day exercises for distributed systems — producing runbooks, experiment manifests, rollback procedures, and post-mortem templates. Use when designing chaos experiments, implementing failure injection frameworks, or conducting game day exercises. Invoke for chaos experiments, resilience testing, blast radius control, game days, antifragile systems, fault injection, Chaos Monkey, Litmus Chaos.","Vishwajeetsrk\u002FJARVIS-AI-OS","Vishwajeetsrk","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F83073825?v=4","01M79V4YAYQ35CPZPBS1RQ6VEX","VishwaJeet","01M79V4YBP8A6PPPZ91229KVHN",11,"MIT","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fchaos-engineer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: chaos-engineer\ndescription: Designs chaos experiments, creates failure injection frameworks, and facilitates game day exercises for distributed systems — producing runbooks, experiment manifests, rollback procedures, and post-mortem templates. Use when designing chaos experiments, implementing failure injection frameworks, or conducting game day exercises. Invoke for chaos experiments, resilience testing, blast radius control, game days, antifragile systems, fault injection, Chaos Monkey, Litmus Chaos.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.0\"\n  domain: devops\n  triggers: chaos engineering, resilience testing, failure injection, game day, blast radius, chaos experiment, fault injection, Chaos Monkey, Litmus Chaos, antifragile\n  role: specialist\n  scope: implementation\n  output-format: code\n  related-skills: sre-engineer, devops-engineer, kubernetes-specialist\n---\n\n# Chaos Engineer\n\n## When to Use This Skill\n\n- Designing and executing chaos experiments\n- Implementing failure injection frameworks (Chaos Monkey, Litmus, etc.)\n- Planning and conducting game day exercises\n- Building blast radius controls and safety mechanisms\n- Setting up continuous chaos testing in CI\u002FCD\n- Improving system resilience based on experiment findings\n\n## Core Workflow\n\n1. **System Analysis** - Map architecture, dependencies, critical paths, and failure modes\n2. **Experiment Design** - Define hypothesis, steady state, blast radius, and safety controls\n3. **Execute Chaos** - Run controlled experiments with monitoring and quick rollback\n4. **Learn & Improve** - Document findings, implement fixes, enhance monitoring\n5. **Automate** - Integrate chaos testing into CI\u002FCD for continuous resilience\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Experiments | `references\u002Fexperiment-design.md` | Designing hypothesis, blast radius, rollback |\n| Infrastructure | `references\u002Finfrastructure-chaos.md` | Server, network, zone, region failures |\n| Kubernetes | `references\u002Fkubernetes-chaos.md` | Pod, node, Litmus, chaos mesh experiments |\n| Tools & Automation | `references\u002Fchaos-tools.md` | Chaos Monkey, Gremlin, Pumba, CI\u002FCD integration |\n| Game Days | `references\u002Fgame-days.md` | Planning, executing, learning from game days |\n\n## Safety Checklist\n\nNon-obvious constraints that must be enforced on every experiment:\n\n- **Steady state first** — define and verify baseline metrics before injecting any failure\n- **Blast radius cap** — start with the smallest possible impact scope; expand only after validation\n- **Automated rollback ≤ 30 seconds** — abort path must be scripted and tested before the experiment begins\n- **Single variable** — change only one failure condition at a time until behaviour is well understood\n- **No production without safety nets** — customer-facing environments require circuit breakers, feature flags, or canary isolation\n- **Close the loop** — every experiment must produce a written learning summary and at least one tracked improvement\n\n## Output Templates\n\nWhen implementing chaos engineering, provide:\n1. Experiment design document (hypothesis, metrics, blast radius)\n2. Implementation code (failure injection scripts\u002Fmanifests)\n3. Monitoring setup and alert configuration\n4. Rollback procedures and safety controls\n5. Learning summary and improvement recommendations\n\n## Concrete Example: Pod Failure Experiment (Litmus Chaos)\n\nThe following shows a complete experiment — from hypothesis to rollback — using Litmus Chaos on Kubernetes.\n\n### Step 1 — Define steady state and apply the experiment\n\n```bash\n# Verify baseline: p99 latency \u003C 200ms, error rate \u003C 0.1%\nkubectl get deploy my-service -n production\nkubectl top pods -n production -l app=my-service\n```\n\n### Step 2 — Create and apply a Litmus ChaosEngine manifest\n\n```yaml\n# chaos-pod-delete.yaml\napiVersion: litmuschaos.io\u002Fv1alpha1\nkind: ChaosEngine\nmetadata:\n  name: my-service-pod-delete\n  namespace: production\nspec:\n  appinfo:\n    appns: production\n    applabel: \"app=my-service\"\n    appkind: deployment\n  # Limit blast radius: only 1 replica at a time\n  engineState: active\n  chaosServiceAccount: litmus-admin\n  experiments:\n    - name: pod-delete\n      spec:\n        components:\n          env:\n            - name: TOTAL_CHAOS_DURATION\n              value: \"60\"          # seconds\n            - name: CHAOS_INTERVAL\n              value: \"20\"          # delete one pod every 20s\n            - name: FORCE\n              value: \"false\"\n            - name: PODS_AFFECTED_PERC\n              value: \"33\"          # max 33% of replicas affected\n```\n\n```bash\n# Apply the experiment\nkubectl apply -f chaos-pod-delete.yaml\n\n# Watch experiment status\nkubectl describe chaosengine my-service-pod-delete -n production\nkubectl get chaosresult my-service-pod-delete-pod-delete -n production -w\n```\n\n### Step 3 — Monitor during the experiment\n\n```bash\n# Tail application logs for errors\nkubectl logs -l app=my-service -n production --since=2m -f\n\n# Check ChaosResult verdict when complete\nkubectl get chaosresult my-service-pod-delete-pod-delete \\\n  -n production -o jsonpath='{.status.experimentStatus.verdict}'\n```\n\n### Step 4 — Rollback \u002F abort if steady state is violated\n\n```bash\n# Immediately stop the experiment\nkubectl patch chaosengine my-service-pod-delete \\\n  -n production --type merge -p '{\"spec\":{\"engineState\":\"stop\"}}'\n\n# Confirm all pods are healthy\nkubectl rollout status deployment\u002Fmy-service -n production\n```\n\n## Concrete Example: Network Latency with toxiproxy\n\n```bash\n# Install toxiproxy CLI\nbrew install toxiproxy   # macOS; use the binary release on Linux\n\n# Start toxiproxy server (runs alongside your service)\ntoxiproxy-server &\n\n# Create a proxy for your downstream dependency\ntoxiproxy-cli create -l 0.0.0.0:22222 -u downstream-db:5432 db-proxy\n\n# Inject 300ms latency with 10% jitter — blast radius: this proxy only\ntoxiproxy-cli toxic add db-proxy -t latency -a latency=300 -a jitter=30\n\n# Run your load test \u002F observe metrics here ...\n\n# Remove the toxic to restore normal behaviour\ntoxiproxy-cli toxic remove db-proxy -n latency_downstream\n```\n\n## Concrete Example: Chaos Monkey (Spinnaker \u002F standalone)\n\n```bash\n# chaos-monkey-config.yml — restrict to a single ASG\ndeployment:\n  enabled: true\n  regionIndependence: false\nchaos:\n  enabled: true\n  meanTimeBetweenKillsInWorkDays: 2\n  minTimeBetweenKillsInWorkDays: 1\n  grouping: APP           # kill one instance per app, not per cluster\n  exceptions:\n    - account: production\n      region: us-east-1\n      detail: \"*-canary\"  # never kill canary instances\n\n# Apply and trigger a manual kill for testing\nchaos-monkey --app my-service --account staging --dry-run false\n```\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fdevops\u002Fchaos-engineer\u002F)\n","# Chaos Engineer\n\n## When to Use This Skill\n\n- Designing and executing chaos experiments\n- Implementing failure injection frameworks (Chaos Monkey, Litmus, etc.)\n- Planning and conducting game day exercises\n- Building blast radius controls and safety mechanisms\n- Setting up continuous chaos testing in CI\u002FCD\n- Improving system resilience based on experiment findings\n\n## Core Workflow\n\n1. **System Analysis** - Map architecture, dependencies, critical paths, and failure modes\n2. **Experiment Design** - Define hypothesis, steady state, blast radius, and safety controls\n3. **Execute Chaos** - Run controlled experiments with monitoring and quick rollback\n4. **Learn & Improve** - Document findings, implement fixes, enhance monitoring\n5. **Automate** - Integrate chaos testing into CI\u002FCD for continuous resilience\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Experiments | `references\u002Fexperiment-design.md` | Designing hypothesis, blast radius, rollback |\n| Infrastructure | `references\u002Finfrastructure-chaos.md` | Server, network, zone, region failures |\n| Kubernetes | `references\u002Fkubernetes-chaos.md` | Pod, node, Litmus, chaos mesh experiments |\n| Tools & Automation | `references\u002Fchaos-tools.md` | Chaos Monkey, Gremlin, Pumba, CI\u002FCD integration |\n| Game Days | `references\u002Fgame-days.md` | Planning, executing, learning from game days |\n\n## Safety Checklist\n\nNon-obvious constraints that must be enforced on every experiment:\n\n- **Steady state first** — define and verify baseline metrics before injecting any failure\n- **Blast radius cap** — start with the smallest possible impact scope; expand only after validation\n- **Automated rollback ≤ 30 seconds** — abort path must be scripted and tested before the experiment begins\n- **Single variable** — change only one failure condition at a time until behaviour is well understood\n- **No production without safety nets** — customer-facing environments require circuit breakers, feature flags, or canary isolation\n- **Close the loop** — every experiment must produce a written learning summary and at least one tracked improvement\n\n## Output Templates\n\nWhen implementing chaos engineering, provide:\n1. Experiment design document (hypothesis, metrics, blast radius)\n2. Implementation code (failure injection scripts\u002Fmanifests)\n3. Monitoring setup and alert configuration\n4. Rollback procedures and safety controls\n5. Learning summary and improvement recommendations\n\n## Concrete Example: Pod Failure Experiment (Litmus Chaos)\n\nThe following shows a complete experiment — from hypothesis to rollback — using Litmus Chaos on Kubernetes.\n\n### Step 1 — Define steady state and apply the experiment\n\n```bash\n# Verify baseline: p99 latency \u003C 200ms, error rate \u003C 0.1%\nkubectl get deploy my-service -n production\nkubectl top pods -n production -l app=my-service\n```\n\n### Step 2 — Create and apply a Litmus ChaosEngine manifest\n\n```yaml\n# chaos-pod-delete.yaml\napiVersion: litmuschaos.io\u002Fv1alpha1\nkind: ChaosEngine\nmetadata:\n  name: my-service-pod-delete\n  namespace: production\nspec:\n  appinfo:\n    appns: production\n    applabel: \"app=my-service\"\n    appkind: deployment\n  # Limit blast radius: only 1 replica at a time\n  engineState: active\n  chaosServiceAccount: litmus-admin\n  experiments:\n    - name: pod-delete\n      spec:\n        components:\n          env:\n            - name: TOTAL_CHAOS_DURATION\n              value: \"60\"          # seconds\n            - name: CHAOS_INTERVAL\n              value: \"20\"          # delete one pod every 20s\n            - name: FORCE\n              value: \"false\"\n            - name: PODS_AFFECTED_PERC\n              value: \"33\"          # max 33% of replicas affected\n```\n\n```bash\n# Apply the experiment\nkubectl apply -f chaos-pod-delete.yaml\n\n# Watch experiment status\nkubectl describe chaosengine my-service-pod-delete -n production\nkubectl get chaosresult my-service-pod-delete-pod-delete -n production -w\n```\n\n### Step 3 — Monitor during the experiment\n\n```bash\n# Tail application logs for errors\nkubectl logs -l app=my-service -n production --since=2m -f\n\n# Check ChaosResult verdict when complete\nkubectl get chaosresult my-service-pod-delete-pod-delete \\\n  -n production -o jsonpath='{.status.experimentStatus.verdict}'\n```\n\n### Step 4 — Rollback \u002F abort if steady state is violated\n\n```bash\n# Immediately stop the experiment\nkubectl patch chaosengine my-service-pod-delete \\\n  -n production --type merge -p '{\"spec\":{\"engineState\":\"stop\"}}'\n\n# Confirm all pods are healthy\nkubectl rollout status deployment\u002Fmy-service -n production\n```\n\n## Concrete Example: Network Latency with toxiproxy\n\n```bash\n# Install toxiproxy CLI\nbrew install toxiproxy   # macOS; use the binary release on Linux\n\n# Start toxiproxy server (runs alongside your service)\ntoxiproxy-server &\n\n# Create a proxy for your downstream dependency\ntoxiproxy-cli create -l 0.0.0.0:22222 -u downstream-db:5432 db-proxy\n\n# Inject 300ms latency with 10% jitter — blast radius: this proxy only\ntoxiproxy-cli toxic add db-proxy -t latency -a latency=300 -a jitter=30\n\n# Run your load test \u002F observe metrics here ...\n\n# Remove the toxic to restore normal behaviour\ntoxiproxy-cli toxic remove db-proxy -n latency_downstream\n```\n\n## Concrete Example: Chaos Monkey (Spinnaker \u002F standalone)\n\n```bash\n# chaos-monkey-config.yml — restrict to a single ASG\ndeployment:\n  enabled: true\n  regionIndependence: false\nchaos:\n  enabled: true\n  meanTimeBetweenKillsInWorkDays: 2\n  minTimeBetweenKillsInWorkDays: 1\n  grouping: APP           # kill one instance per app, not per cluster\n  exceptions:\n    - account: production\n      region: us-east-1\n      detail: \"*-canary\"  # never kill canary instances\n\n# Apply and trigger a manual kill for testing\nchaos-monkey --app my-service --account staging --dry-run false\n```\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fdevops\u002Fchaos-engineer\u002F)\n",{"name":5,"license":15,"metadata":24,"description":7},{"role":25,"scope":26,"author":27,"domain":28,"version":29,"triggers":30,"output-format":31,"related-skills":32},"specialist","implementation","https:\u002F\u002Fgithub.com\u002FJeffallan","devops","1.1.0","chaos engineering, resilience testing, failure injection, game day, blast radius, chaos experiment, fault injection, Chaos Monkey, Litmus Chaos, antifragile","code","sre-engineer, devops-engineer, kubernetes-specialist","main","87476a719bbe41680362bb9bfacf884c53784783",".agents\u002Fskills\u002Fchaos-engineer",3,"https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS","https:\u002F\u002Fjarvisaios.vercel.app","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk","https:\u002F\u002Flearnifyaitool.vercel.app\u002F","🎉 Welcome to my profile! I'm a BCA student with a passion for technology and innovation. As a frontend developer.","2026-09-01 14:20:58",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add Vishwajeetsrk\u002FJARVIS-AI-OS --skill chaos-engineer",{"tool":49,"command":50},"bunx","bunx skills add Vishwajeetsrk\u002FJARVIS-AI-OS --skill chaos-engineer",{"tool":52,"command":53},"pnpm","pnpm dlx skills add Vishwajeetsrk\u002FJARVIS-AI-OS --skill chaos-engineer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fchaos-engineer\u002FSKILL.md",true,[57,63,67,71,75],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fchaos-tools.md","REFERENCE","参考文档",14217,"https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fchaos-engineer\u002Freferences\u002Fchaos-tools.md",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fexperiment-design.md",7031,"https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fchaos-engineer\u002Freferences\u002Fexperiment-design.md",{"path":68,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fgame-days.md",12355,"https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fchaos-engineer\u002Freferences\u002Fgame-days.md",{"path":72,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Finfrastructure-chaos.md",10035,"https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fchaos-engineer\u002Freferences\u002Finfrastructure-chaos.md",{"path":76,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fkubernetes-chaos.md",10785,"https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fchaos-engineer\u002Freferences\u002Fkubernetes-chaos.md",[80,86,95,103,109,117],{"skillNo":81,"name":82,"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":83,"categories":84,"keywords":85,"publishedAt":19},"01M79VY332PY7B4KCWMN3FM430","workspace-agent","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002Fskills\u002Fworkspace-agent\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M79VXZK9MKMYDV57N8VJDPYW","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M79VXR975D5MQTW5VMFTKWGG","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"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":106,"categories":107,"keywords":108,"publishedAt":19},"01M79VXMF2JMWE9GETMJFRM4B9","ui-ux-expert","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002Fskills\u002Fui-ux-expert\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M79VXGG2RRFF3EH79CDYVE0K","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002Fskills\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002Fskills\u002Ftheme-factory\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"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":120,"categories":121,"keywords":122,"publishedAt":19},"01M79VXCR3A6QMYT131RFKNTWT","test-agent","https:\u002F\u002Fgithub.com\u002FVishwajeetsrk\u002FJARVIS-AI-OS\u002Fblob\u002Fmain\u002Fskills\u002Ftest-agent\u002FSKILL.md",[],[]]