[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AQ44586RV5756GC3MTYHYR":3,"skill-same:01M7AQ44586RV5756GC3MTYHYR":78},{"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":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M7AQ44586RV5756GC3MTYHYR","microservices-architect",null,"Designs distributed system architectures, decomposes monoliths into bounded-context services, recommends communication patterns, and produces service boundary diagrams and resilience strategies. Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns — including service boundaries, DDD, saga patterns, event sourcing, CQRS, service mesh, or distributed tracing.","Cyrilthetecchieee\u002Fcyril-code-","Cyrilthetecchieee","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219787998?v=4","01M7AF0MMMKRAA0H61XMJPV92H","Julian Cyril D ","01M7AF0MQ10AVG6QJQ1C2BC0F5",2,"MIT","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fskills\u002Fmicroservices-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: microservices-architect\ndescription: Designs distributed system architectures, decomposes monoliths into bounded-context services, recommends communication patterns, and produces service boundary diagrams and resilience strategies. Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns — including service boundaries, DDD, saga patterns, event sourcing, CQRS, service mesh, or distributed tracing.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.0\"\n  domain: api-architecture\n  triggers: microservices, service mesh, distributed systems, service boundaries, domain-driven design, event sourcing, CQRS, saga pattern, Kubernetes microservices, Istio, distributed tracing\n  role: architect\n  scope: system-design\n  output-format: architecture\n  related-skills: devops-engineer, kubernetes-specialist, graphql-architect, architecture-designer, monitoring-expert\n---\n\n# Microservices Architect\n\nSenior distributed systems architect specializing in cloud-native microservices architectures, resilience patterns, and operational excellence.\n\n## Core Workflow\n\n1. **Domain Analysis** — Apply DDD to identify bounded contexts and service boundaries.\n   - *Validation checkpoint:* Each candidate service owns its data exclusively, has a clear public API contract, and can be deployed independently.\n2. **Communication Design** — Choose sync\u002Fasync patterns and protocols (REST, gRPC, events).\n   - *Validation checkpoint:* Long-running or cross-aggregate operations use async messaging; only query\u002Fcommand pairs with sub-100 ms SLA use synchronous calls.\n3. **Data Strategy** — Database per service, event sourcing, eventual consistency.\n   - *Validation checkpoint:* No shared database schema exists between services; consistency boundaries align with bounded contexts.\n4. **Resilience** — Circuit breakers, retries, timeouts, bulkheads, fallbacks.\n   - *Validation checkpoint:* Every external call has an explicit timeout, retry budget, and graceful degradation path.\n5. **Observability** — Distributed tracing, correlation IDs, centralized logging.\n   - *Validation checkpoint:* A single request can be traced end-to-end using its correlation ID across all services.\n6. **Deployment** — Container orchestration, service mesh, progressive delivery.\n   - *Validation checkpoint:* Health and readiness probes are defined; canary or blue-green rollout strategy is documented.\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Service Boundaries | `references\u002Fdecomposition.md` | Monolith decomposition, bounded contexts, DDD |\n| Communication | `references\u002Fcommunication.md` | REST vs gRPC, async messaging, event-driven |\n| Resilience Patterns | `references\u002Fpatterns.md` | Circuit breakers, saga, bulkhead, retry strategies |\n| Data Management | `references\u002Fdata.md` | Database per service, event sourcing, CQRS |\n| Observability | `references\u002Fobservability.md` | Distributed tracing, correlation IDs, metrics |\n\n## Implementation Examples\n\n### Correlation ID Middleware (Node.js \u002F Express)\n```js\nconst { v4: uuidv4 } = require('uuid');\n\nfunction correlationMiddleware(req, res, next) {\n  req.correlationId = req.headers['x-correlation-id'] || uuidv4();\n  res.setHeader('x-correlation-id', req.correlationId);\n  \u002F\u002F Attach to logger context so every log line includes the ID\n  req.log = logger.child({ correlationId: req.correlationId });\n  next();\n}\n```\nPropagate `x-correlation-id` in every outbound HTTP call and Kafka message header.\n\n### Circuit Breaker (Python \u002F `pybreaker`)\n```python\nimport pybreaker\n\n# Opens after 5 failures; resets after 30 s in half-open state\nbreaker = pybreaker.CircuitBreaker(fail_max=5, reset_timeout=30)\n\n@breaker\ndef call_inventory_service(order_id: str):\n    response = requests.get(f\"{INVENTORY_URL}\u002Fstock\u002F{order_id}\", timeout=2)\n    response.raise_for_status()\n    return response.json()\n\ndef get_inventory(order_id: str):\n    try:\n        return call_inventory_service(order_id)\n    except pybreaker.CircuitBreakerError:\n        return {\"status\": \"unavailable\", \"fallback\": True}\n```\n\n### Saga Orchestration Skeleton (TypeScript)\n```ts\n\u002F\u002F Each step defines execute() and compensate() so rollback is automatic.\ninterface SagaStep\u003CT> {\n  execute(ctx: T): Promise\u003CT>;\n  compensate(ctx: T): Promise\u003Cvoid>;\n}\n\nasync function runSaga\u003CT>(steps: SagaStep\u003CT>[], initialCtx: T): Promise\u003CT> {\n  const completed: SagaStep\u003CT>[] = [];\n  let ctx = initialCtx;\n  for (const step of steps) {\n    try {\n      ctx = await step.execute(ctx);\n      completed.push(step);\n    } catch (err) {\n      for (const done of completed.reverse()) {\n        await done.compensate(ctx).catch(console.error);\n      }\n      throw err;\n    }\n  }\n  return ctx;\n}\n\n\u002F\u002F Usage: order creation saga\nconst orderSaga = [reserveInventoryStep, chargePaymentStep, scheduleShipmentStep];\nawait runSaga(orderSaga, { orderId, customerId, items });\n```\n\n### Health & Readiness Probe (Kubernetes)\n```yaml\nlivenessProbe:\n  httpGet:\n    path: \u002Fhealth\u002Flive\n    port: 8080\n  initialDelaySeconds: 10\n  periodSeconds: 15\nreadinessProbe:\n  httpGet:\n    path: \u002Fhealth\u002Fready\n    port: 8080\n  initialDelaySeconds: 5\n  periodSeconds: 10\n```\n`\u002Fhealth\u002Flive` — returns 200 if the process is running.  \n`\u002Fhealth\u002Fready` — returns 200 only when the service can serve traffic (DB connected, caches warm).\n\n## Constraints\n\n### MUST DO\n- Apply domain-driven design for service boundaries\n- Use database per service pattern\n- Implement circuit breakers for external calls\n- Add correlation IDs to all requests\n- Use async communication for cross-aggregate operations\n- Design for failure and graceful degradation\n- Implement health checks and readiness probes\n- Use API versioning strategies\n\n### MUST NOT DO\n- Create distributed monoliths\n- Share databases between services\n- Use synchronous calls for long-running operations\n- Skip distributed tracing implementation\n- Ignore network latency and partial failures\n- Create chatty service interfaces\n- Store shared state without proper patterns\n- Deploy without observability\n\n## Output Templates\n\nWhen designing microservices architecture, provide:\n1. Service boundary diagram with bounded contexts\n2. Communication patterns (sync\u002Fasync, protocols)\n3. Data ownership and consistency model\n4. Resilience patterns for each integration point\n5. Deployment and infrastructure requirements\n\n## Knowledge Reference\n\nDomain-driven design, bounded contexts, event storming, REST\u002FgRPC, message queues (Kafka, RabbitMQ), service mesh (Istio, Linkerd), Kubernetes, circuit breakers, saga patterns, event sourcing, CQRS, distributed tracing (Jaeger, Zipkin), API gateways, eventual consistency, CAP theorem\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fapi-architecture\u002Fmicroservices-architect\u002F)\n","# Microservices Architect\n\nSenior distributed systems architect specializing in cloud-native microservices architectures, resilience patterns, and operational excellence.\n\n## Core Workflow\n\n1. **Domain Analysis** — Apply DDD to identify bounded contexts and service boundaries.\n   - *Validation checkpoint:* Each candidate service owns its data exclusively, has a clear public API contract, and can be deployed independently.\n2. **Communication Design** — Choose sync\u002Fasync patterns and protocols (REST, gRPC, events).\n   - *Validation checkpoint:* Long-running or cross-aggregate operations use async messaging; only query\u002Fcommand pairs with sub-100 ms SLA use synchronous calls.\n3. **Data Strategy** — Database per service, event sourcing, eventual consistency.\n   - *Validation checkpoint:* No shared database schema exists between services; consistency boundaries align with bounded contexts.\n4. **Resilience** — Circuit breakers, retries, timeouts, bulkheads, fallbacks.\n   - *Validation checkpoint:* Every external call has an explicit timeout, retry budget, and graceful degradation path.\n5. **Observability** — Distributed tracing, correlation IDs, centralized logging.\n   - *Validation checkpoint:* A single request can be traced end-to-end using its correlation ID across all services.\n6. **Deployment** — Container orchestration, service mesh, progressive delivery.\n   - *Validation checkpoint:* Health and readiness probes are defined; canary or blue-green rollout strategy is documented.\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Service Boundaries | `references\u002Fdecomposition.md` | Monolith decomposition, bounded contexts, DDD |\n| Communication | `references\u002Fcommunication.md` | REST vs gRPC, async messaging, event-driven |\n| Resilience Patterns | `references\u002Fpatterns.md` | Circuit breakers, saga, bulkhead, retry strategies |\n| Data Management | `references\u002Fdata.md` | Database per service, event sourcing, CQRS |\n| Observability | `references\u002Fobservability.md` | Distributed tracing, correlation IDs, metrics |\n\n## Implementation Examples\n\n### Correlation ID Middleware (Node.js \u002F Express)\n```js\nconst { v4: uuidv4 } = require('uuid');\n\nfunction correlationMiddleware(req, res, next) {\n  req.correlationId = req.headers['x-correlation-id'] || uuidv4();\n  res.setHeader('x-correlation-id', req.correlationId);\n  \u002F\u002F Attach to logger context so every log line includes the ID\n  req.log = logger.child({ correlationId: req.correlationId });\n  next();\n}\n```\nPropagate `x-correlation-id` in every outbound HTTP call and Kafka message header.\n\n### Circuit Breaker (Python \u002F `pybreaker`)\n```python\nimport pybreaker\n\n# Opens after 5 failures; resets after 30 s in half-open state\nbreaker = pybreaker.CircuitBreaker(fail_max=5, reset_timeout=30)\n\n@breaker\ndef call_inventory_service(order_id: str):\n    response = requests.get(f\"{INVENTORY_URL}\u002Fstock\u002F{order_id}\", timeout=2)\n    response.raise_for_status()\n    return response.json()\n\ndef get_inventory(order_id: str):\n    try:\n        return call_inventory_service(order_id)\n    except pybreaker.CircuitBreakerError:\n        return {\"status\": \"unavailable\", \"fallback\": True}\n```\n\n### Saga Orchestration Skeleton (TypeScript)\n```ts\n\u002F\u002F Each step defines execute() and compensate() so rollback is automatic.\ninterface SagaStep\u003CT> {\n  execute(ctx: T): Promise\u003CT>;\n  compensate(ctx: T): Promise\u003Cvoid>;\n}\n\nasync function runSaga\u003CT>(steps: SagaStep\u003CT>[], initialCtx: T): Promise\u003CT> {\n  const completed: SagaStep\u003CT>[] = [];\n  let ctx = initialCtx;\n  for (const step of steps) {\n    try {\n      ctx = await step.execute(ctx);\n      completed.push(step);\n    } catch (err) {\n      for (const done of completed.reverse()) {\n        await done.compensate(ctx).catch(console.error);\n      }\n      throw err;\n    }\n  }\n  return ctx;\n}\n\n\u002F\u002F Usage: order creation saga\nconst orderSaga = [reserveInventoryStep, chargePaymentStep, scheduleShipmentStep];\nawait runSaga(orderSaga, { orderId, customerId, items });\n```\n\n### Health & Readiness Probe (Kubernetes)\n```yaml\nlivenessProbe:\n  httpGet:\n    path: \u002Fhealth\u002Flive\n    port: 8080\n  initialDelaySeconds: 10\n  periodSeconds: 15\nreadinessProbe:\n  httpGet:\n    path: \u002Fhealth\u002Fready\n    port: 8080\n  initialDelaySeconds: 5\n  periodSeconds: 10\n```\n`\u002Fhealth\u002Flive` — returns 200 if the process is running.  \n`\u002Fhealth\u002Fready` — returns 200 only when the service can serve traffic (DB connected, caches warm).\n\n## Constraints\n\n### MUST DO\n- Apply domain-driven design for service boundaries\n- Use database per service pattern\n- Implement circuit breakers for external calls\n- Add correlation IDs to all requests\n- Use async communication for cross-aggregate operations\n- Design for failure and graceful degradation\n- Implement health checks and readiness probes\n- Use API versioning strategies\n\n### MUST NOT DO\n- Create distributed monoliths\n- Share databases between services\n- Use synchronous calls for long-running operations\n- Skip distributed tracing implementation\n- Ignore network latency and partial failures\n- Create chatty service interfaces\n- Store shared state without proper patterns\n- Deploy without observability\n\n## Output Templates\n\nWhen designing microservices architecture, provide:\n1. Service boundary diagram with bounded contexts\n2. Communication patterns (sync\u002Fasync, protocols)\n3. Data ownership and consistency model\n4. Resilience patterns for each integration point\n5. Deployment and infrastructure requirements\n\n## Knowledge Reference\n\nDomain-driven design, bounded contexts, event storming, REST\u002FgRPC, message queues (Kafka, RabbitMQ), service mesh (Istio, Linkerd), Kubernetes, circuit breakers, saga patterns, event sourcing, CQRS, distributed tracing (Jaeger, Zipkin), API gateways, eventual consistency, CAP theorem\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fapi-architecture\u002Fmicroservices-architect\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},"architect","system-design","https:\u002F\u002Fgithub.com\u002FJeffallan","api-architecture","1.1.0","microservices, service mesh, distributed systems, service boundaries, domain-driven design, event sourcing, CQRS, saga pattern, Kubernetes microservices, Istio, distributed tracing","architecture","devops-engineer, kubernetes-specialist, graphql-architect, architecture-designer, monitoring-expert","main","57e7aa6b6e03bce1a7d7862ba9c2ec312f7f19b5","src\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fskills\u002Fmicroservices-architect",0,"https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee","https:\u002F\u002Fwithcyril.me\u002F","Hi, I’m Julian Cyril D, a Computer Science and Business Systems student at PSNACET.\r\nI’m passionate about full-stack development, UI\u002FUX design, and building sma","2026-11-04 23:28:50",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add Cyrilthetecchieee\u002Fcyril-code- --skill microservices-architect",{"tool":48,"command":49},"bunx","bunx skills add Cyrilthetecchieee\u002Fcyril-code- --skill microservices-architect",{"tool":51,"command":52},"pnpm","pnpm dlx skills add Cyrilthetecchieee\u002Fcyril-code- --skill microservices-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fskills\u002Fmicroservices-architect\u002FSKILL.md",true,[56,62,66,70,74],{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fcommunication.md","REFERENCE","参考文档",10101,"https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fskills\u002Fmicroservices-architect\u002Freferences\u002Fcommunication.md",{"path":63,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fdata.md",15710,"https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fskills\u002Fmicroservices-architect\u002Freferences\u002Fdata.md",{"path":67,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fdecomposition.md",8273,"https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fskills\u002Fmicroservices-architect\u002Freferences\u002Fdecomposition.md",{"path":71,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fobservability.md",17589,"https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fskills\u002Fmicroservices-architect\u002Freferences\u002Fobservability.md",{"path":75,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fpatterns.md",14143,"https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fskills\u002Fmicroservices-architect\u002Freferences\u002Fpatterns.md",[79,88,95,103,110,117],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7AQV6CYX8RMC78420V9WZ62","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\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fwebapp-testing\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},"01M7AQV2895N3S1MEX6K76G6G2","youtube-downloader","Download YouTube videos with customizable quality and format options. Use this skill when the user asks to download, save, or grab YouTube videos. Supports various quality settings (best, 1080p, 720p, 480p, 360p), multiple formats (mp4, webm, mkv), and audio-only downloads as MP3.","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fvideo-downloader\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":83,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7AQTRNX62DNKVZ5GXEHRBKB","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\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Ftheme-factory\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M7AQTNNVHAAN9H6DA8T6ZVE0","template-skill","Replace with description of the skill and when Claude should use it.","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Ftemplate-skill\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M7AQTJ3MQ6AKX152MEX2MYCC","tailored-resume-generator","Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Ftailored-resume-generator\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":19},"01M7AQTD7D5MYET2YWG7HG9WM3","slack-gif-creator","Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives. This skill applies when users request animated GIFs or emoji animations for Slack from descriptions like \"make me a GIF for Slack of X doing Y\".","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fslack-gif-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fslack-gif-creator\u002FSKILL.md",[],[]]