[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NPKS6XCARHSTK6JYN4J6Z0":3,"skill-same:01M6NPKS6XCARHSTK6JYN4J6Z0":83},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":14,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M6NPKS6XCARHSTK6JYN4J6Z0","container-orchestration",null,"Docker Compose patterns for multi-service apps — health checks, networking, volumes, dependencies. Use when writing or editing docker-compose files, designing multi-service architectures, debugging container networking, or managing volumes and service dependencies.","projectious-work\u002Fprocesskit","projectious-work","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263889726?v=4","01M6N97TJJ118WQ35CHRV8RD0E","projectious.work","01M6N97TPWJPF0BMKYQ4PBY5W8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdevops\u002Fcontainer-orchestration\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"orchestration","container orchestration","container","docker compose patterns","writing","for","multi","architectures","apps","docker-compose","files","compose","devops","use","editing","work","health","debugging","docker compose","docker","2026-11-10 10:12:30",false,"---\nname: container-orchestration\ndescription: |\n  Docker Compose patterns for multi-service apps — health checks, networking, volumes, dependencies. Use when writing or editing docker-compose files, designing multi-service architectures, debugging container networking, or managing volumes and service dependencies.\nmetadata:\n  processkit:\n    apiVersion: processkit.projectious.work\u002Fv2\n    id: SKILL-container-orchestration\n    version: \"1.1.0\"\n    created: 2026-04-06T00:00:00Z\n    category: devops\n---\n\n# Container Orchestration\n\n## Intro\n\nDocker Compose stitches multiple containers into a single declarative\nstack: services, networks, and volumes described in one YAML file. Get\nhealth checks, dependency conditions, and named volumes right and\neverything else follows.\n\n## Overview\n\n### Compose file structure\n\nDefine services, networks, and volumes at the top level. Prefer named\nvolumes for persistent data and explicit networks for inter-service\ncommunication:\n\n```yaml\nservices:\n  app:\n    build: .\n    networks:\n      - backend\n    volumes:\n      - app-data:\u002Fdata\n\nnetworks:\n  backend:\n\nvolumes:\n  app-data:\n```\n\n### Build vs image\n\nUse `build` for services you develop and `image` for third-party\nservices. Combine both to tag locally built images:\n\n```yaml\nservices:\n  api:\n    build:\n      context: .\u002Fapi\n      dockerfile: Dockerfile\n      args:\n        PYTHON_VERSION: \"3.12\"\n    image: myproject\u002Fapi:dev\n  redis:\n    image: redis:7-alpine\n```\n\n### Health checks and dependencies\n\nAlways define health checks on services that other services depend on.\nWithout them, `depends_on` only waits for the container to start — not\nfor the service inside to be ready:\n\n```yaml\nservices:\n  db:\n    image: postgres:16-alpine\n    environment:\n      POSTGRES_PASSWORD: ${DB_PASSWORD}\n    healthcheck:\n      test: [\"CMD-SHELL\", \"pg_isready -U postgres\"]\n      interval: 5s\n      timeout: 3s\n      retries: 5\n      start_period: 10s\n  app:\n    build: .\n    depends_on:\n      db:\n        condition: service_healthy\n```\n\n### Networking\n\nCompose creates a default network per project. Use custom networks to\nisolate traffic:\n\n```yaml\nservices:\n  web:\n    networks: [frontend, backend]\n  api:\n    networks: [backend]\n  db:\n    networks: [backend]\n\nnetworks:\n  frontend:\n  backend:\n```\n\nServices resolve each other by service name. Only expose ports to the\nhost when necessary — inter-service traffic uses the container port\ndirectly. Use `expose` for documentation, `ports` for host binding.\n\n### Volume strategies\n\n- **Named volumes** — persistent data managed by Docker; survives\n  `docker compose down`\n- **Bind mounts** — map host paths for development (live reload)\n- **tmpfs** — in-memory; for sensitive data or caches\n\n```yaml\nvolumes:\n  - pg-data:\u002Fvar\u002Flib\u002Fpostgresql\u002Fdata    # named volume\n  - .\u002Fsrc:\u002Fapp\u002Fsrc                       # bind mount\n  - type: tmpfs\n    target: \u002Ftmp\n```\n\n`docker compose down -v` removes named volumes (destructive). Back up\nvolume data with a one-off `docker run` using a bind mount.\n\n### Environment management\n\nUse `.env` files for defaults and override per environment:\n\n```yaml\nservices:\n  app:\n    env_file:\n      - .env\n      - .env.local    # overrides, git-ignored\n    environment:\n      - NODE_ENV=production   # explicit override\n```\n\nNever put secrets directly in `docker-compose.yml`. Use `env_file` with\ngit-ignored files or Docker secrets in swarm mode.\n\n### Profiles\n\nUse profiles to make services optional:\n\n```yaml\nservices:\n  app:\n    build: .\n  mailhog:\n    image: mailhog\u002Fmailhog\n    profiles: [debug]\n```\n\nStart with `docker compose --profile debug up` to include debug\nservices. Services without a profile always start.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **`depends_on` without health checks.** `depends_on: [db]` only waits for the database container to start — not for PostgreSQL to finish initializing and accept connections. If the app starts before the database is ready, it will fail on the first connection attempt. Always add a `healthcheck` to the dependency and use `condition: service_healthy` in `depends_on`.\n- **Hardcoded secrets in `docker-compose.yml`.** A `docker-compose.yml` checked into version control with secrets in `environment:` keys means every person who clones the repo has production credentials. Use `env_file:` pointing to a git-ignored `.env.local`, or inject via CI environment variables.\n- **`latest` tags for third-party images.** `image: postgres:latest` will silently pick up a major version bump the next time the image is pulled, changing behavior without any visible config change. Pin to a specific version tag (`postgres:16-alpine`) and update intentionally.\n- **Bind-mounting `.` (the entire project root) into a production container.** A bind mount of the full working directory replaces the built image's content with the host filesystem, including `.git`, local credentials, and development artifacts. Bind mounts are for development live-reload; production services should use the built image content only.\n- **Missing `restart:` policy.** The default restart policy is `no`, meaning a crashed container stays down indefinitely until someone notices and manually restarts it. Set `restart: unless-stopped` for long-running services so they recover automatically from crashes and host reboots.\n- **All services on a single default network.** Without explicit network definitions, every service can reach every other service by name. A compromised web container can reach the database directly. Define separate `frontend` and `backend` networks and attach each service only to the networks it legitimately needs.\n- **`docker compose down -v` in a recovery procedure.** The `-v` flag removes all named volumes, which means all database data, uploaded files, and other persistent state is permanently deleted. In a recovery or restart scenario this is a data loss event. Never include `-v` in runbooks or scripts unless data deletion is explicitly the intent.\n\n## Full reference\n\n### Common commands\n\n```bash\ndocker compose up -d              # start all services detached\ndocker compose up -d --build      # rebuild images before starting\ndocker compose ps                 # list running services\ndocker compose logs -f app        # follow logs for a service\ndocker compose exec app sh        # shell into running container\ndocker compose down               # stop and remove containers\u002Fnetworks\ndocker compose down -v            # also remove volumes (destructive)\ndocker compose config             # validate and display resolved config\n```\n\n### Debugging workflow: service cannot reach the database\n\n```bash\n# 1. Check both services are on the same network\ndocker compose ps\ndocker network inspect $(docker compose config --format json | jq -r '.networks | keys[0]')\n# 2. Verify the db is healthy\ndocker compose exec db pg_isready -U postgres\n# 3. Test connectivity from the app container\ndocker compose exec app ping db\ndocker compose exec app nc -zv db 5432\n# 4. Check environment variables\ndocker compose exec app env | grep DB\n```\n\n### Adding a service with zero-downtime restart\n\n```bash\n# 1. Add the service to docker-compose.yml\n# 2. Validate the config\ndocker compose config --quiet\n# 3. Start only the new service\ndocker compose up -d new-service\n# 4. Verify health\ndocker compose ps new-service\ndocker compose logs new-service\n```\n\n### One-off commands in a service context\n\n```bash\n# Database migration\ndocker compose run --rm app python manage.py migrate\n# Interactive database shell\ndocker compose exec db psql -U postgres\n# Run tests with the full service stack\ndocker compose run --rm app pytest\n```\n\n### Reference architectures\n\nThe complete YAML examples live in `references\u002Fcompose-patterns.md`.\nThe key patterns, in increasing complexity:\n\n- **Web + database** — the baseline production stack: app service with\n  health-checked postgres, named volume for data, `restart:\n  unless-stopped` on both. Always wire `depends_on` with\n  `condition: service_healthy`.\n- **Web + database + cache** — add redis with `--appendonly yes` and\n  an `allkeys-lru` memory cap. The web service waits on both\n  dependencies.\n- **Worker queue** — web enqueues jobs, celery workers process them via\n  RabbitMQ. Scale workers with `deploy.replicas`. Both web and worker\n  depend on the broker AND the database being healthy.\n- **Reverse proxy** — nginx or Traefik in front of application services\n  for TLS termination, load balancing, and static assets. Proxy lives\n  on the `frontend` network; app straddles `frontend` and `backend`;\n  db is `backend`-only.\n\n### Anti-patterns\n\n- **`depends_on` without health checks** — the dependent service will\n  race its dependency\n- **Hardcoded secrets in `docker-compose.yml`** — use `env_file` with a\n  git-ignored local file\n- **`latest` tags for third-party images** — pin to a specific version\n  so builds are reproducible\n- **Bind-mounting `.` into the container in production** — bind mounts\n  are for development; production should use the built image\n- **Missing `restart:` policy** — default is `no`, which means a crashed\n  service stays down until you notice\n","# Container Orchestration\n\n## Intro\n\nDocker Compose stitches multiple containers into a single declarative\nstack: services, networks, and volumes described in one YAML file. Get\nhealth checks, dependency conditions, and named volumes right and\neverything else follows.\n\n## Overview\n\n### Compose file structure\n\nDefine services, networks, and volumes at the top level. Prefer named\nvolumes for persistent data and explicit networks for inter-service\ncommunication:\n\n```yaml\nservices:\n  app:\n    build: .\n    networks:\n      - backend\n    volumes:\n      - app-data:\u002Fdata\n\nnetworks:\n  backend:\n\nvolumes:\n  app-data:\n```\n\n### Build vs image\n\nUse `build` for services you develop and `image` for third-party\nservices. Combine both to tag locally built images:\n\n```yaml\nservices:\n  api:\n    build:\n      context: .\u002Fapi\n      dockerfile: Dockerfile\n      args:\n        PYTHON_VERSION: \"3.12\"\n    image: myproject\u002Fapi:dev\n  redis:\n    image: redis:7-alpine\n```\n\n### Health checks and dependencies\n\nAlways define health checks on services that other services depend on.\nWithout them, `depends_on` only waits for the container to start — not\nfor the service inside to be ready:\n\n```yaml\nservices:\n  db:\n    image: postgres:16-alpine\n    environment:\n      POSTGRES_PASSWORD: ${DB_PASSWORD}\n    healthcheck:\n      test: [\"CMD-SHELL\", \"pg_isready -U postgres\"]\n      interval: 5s\n      timeout: 3s\n      retries: 5\n      start_period: 10s\n  app:\n    build: .\n    depends_on:\n      db:\n        condition: service_healthy\n```\n\n### Networking\n\nCompose creates a default network per project. Use custom networks to\nisolate traffic:\n\n```yaml\nservices:\n  web:\n    networks: [frontend, backend]\n  api:\n    networks: [backend]\n  db:\n    networks: [backend]\n\nnetworks:\n  frontend:\n  backend:\n```\n\nServices resolve each other by service name. Only expose ports to the\nhost when necessary — inter-service traffic uses the container port\ndirectly. Use `expose` for documentation, `ports` for host binding.\n\n### Volume strategies\n\n- **Named volumes** — persistent data managed by Docker; survives\n  `docker compose down`\n- **Bind mounts** — map host paths for development (live reload)\n- **tmpfs** — in-memory; for sensitive data or caches\n\n```yaml\nvolumes:\n  - pg-data:\u002Fvar\u002Flib\u002Fpostgresql\u002Fdata    # named volume\n  - .\u002Fsrc:\u002Fapp\u002Fsrc                       # bind mount\n  - type: tmpfs\n    target: \u002Ftmp\n```\n\n`docker compose down -v` removes named volumes (destructive). Back up\nvolume data with a one-off `docker run` using a bind mount.\n\n### Environment management\n\nUse `.env` files for defaults and override per environment:\n\n```yaml\nservices:\n  app:\n    env_file:\n      - .env\n      - .env.local    # overrides, git-ignored\n    environment:\n      - NODE_ENV=production   # explicit override\n```\n\nNever put secrets directly in `docker-compose.yml`. Use `env_file` with\ngit-ignored files or Docker secrets in swarm mode.\n\n### Profiles\n\nUse profiles to make services optional:\n\n```yaml\nservices:\n  app:\n    build: .\n  mailhog:\n    image: mailhog\u002Fmailhog\n    profiles: [debug]\n```\n\nStart with `docker compose --profile debug up` to include debug\nservices. Services without a profile always start.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **`depends_on` without health checks.** `depends_on: [db]` only waits for the database container to start — not for PostgreSQL to finish initializing and accept connections. If the app starts before the database is ready, it will fail on the first connection attempt. Always add a `healthcheck` to the dependency and use `condition: service_healthy` in `depends_on`.\n- **Hardcoded secrets in `docker-compose.yml`.** A `docker-compose.yml` checked into version control with secrets in `environment:` keys means every person who clones the repo has production credentials. Use `env_file:` pointing to a git-ignored `.env.local`, or inject via CI environment variables.\n- **`latest` tags for third-party images.** `image: postgres:latest` will silently pick up a major version bump the next time the image is pulled, changing behavior without any visible config change. Pin to a specific version tag (`postgres:16-alpine`) and update intentionally.\n- **Bind-mounting `.` (the entire project root) into a production container.** A bind mount of the full working directory replaces the built image's content with the host filesystem, including `.git`, local credentials, and development artifacts. Bind mounts are for development live-reload; production services should use the built image content only.\n- **Missing `restart:` policy.** The default restart policy is `no`, meaning a crashed container stays down indefinitely until someone notices and manually restarts it. Set `restart: unless-stopped` for long-running services so they recover automatically from crashes and host reboots.\n- **All services on a single default network.** Without explicit network definitions, every service can reach every other service by name. A compromised web container can reach the database directly. Define separate `frontend` and `backend` networks and attach each service only to the networks it legitimately needs.\n- **`docker compose down -v` in a recovery procedure.** The `-v` flag removes all named volumes, which means all database data, uploaded files, and other persistent state is permanently deleted. In a recovery or restart scenario this is a data loss event. Never include `-v` in runbooks or scripts unless data deletion is explicitly the intent.\n\n## Full reference\n\n### Common commands\n\n```bash\ndocker compose up -d              # start all services detached\ndocker compose up -d --build      # rebuild images before starting\ndocker compose ps                 # list running services\ndocker compose logs -f app        # follow logs for a service\ndocker compose exec app sh        # shell into running container\ndocker compose down               # stop and remove containers\u002Fnetworks\ndocker compose down -v            # also remove volumes (destructive)\ndocker compose config             # validate and display resolved config\n```\n\n### Debugging workflow: service cannot reach the database\n\n```bash\n# 1. Check both services are on the same network\ndocker compose ps\ndocker network inspect $(docker compose config --format json | jq -r '.networks | keys[0]')\n# 2. Verify the db is healthy\ndocker compose exec db pg_isready -U postgres\n# 3. Test connectivity from the app container\ndocker compose exec app ping db\ndocker compose exec app nc -zv db 5432\n# 4. Check environment variables\ndocker compose exec app env | grep DB\n```\n\n### Adding a service with zero-downtime restart\n\n```bash\n# 1. Add the service to docker-compose.yml\n# 2. Validate the config\ndocker compose config --quiet\n# 3. Start only the new service\ndocker compose up -d new-service\n# 4. Verify health\ndocker compose ps new-service\ndocker compose logs new-service\n```\n\n### One-off commands in a service context\n\n```bash\n# Database migration\ndocker compose run --rm app python manage.py migrate\n# Interactive database shell\ndocker compose exec db psql -U postgres\n# Run tests with the full service stack\ndocker compose run --rm app pytest\n```\n\n### Reference architectures\n\nThe complete YAML examples live in `references\u002Fcompose-patterns.md`.\nThe key patterns, in increasing complexity:\n\n- **Web + database** — the baseline production stack: app service with\n  health-checked postgres, named volume for data, `restart:\n  unless-stopped` on both. Always wire `depends_on` with\n  `condition: service_healthy`.\n- **Web + database + cache** — add redis with `--appendonly yes` and\n  an `allkeys-lru` memory cap. The web service waits on both\n  dependencies.\n- **Worker queue** — web enqueues jobs, celery workers process them via\n  RabbitMQ. Scale workers with `deploy.replicas`. Both web and worker\n  depend on the broker AND the database being healthy.\n- **Reverse proxy** — nginx or Traefik in front of application services\n  for TLS termination, load balancing, and static assets. Proxy lives\n  on the `frontend` network; app straddles `frontend` and `backend`;\n  db is `backend`-only.\n\n### Anti-patterns\n\n- **`depends_on` without health checks** — the dependent service will\n  race its dependency\n- **Hardcoded secrets in `docker-compose.yml`** — use `env_file` with a\n  git-ignored local file\n- **`latest` tags for third-party images** — pin to a specific version\n  so builds are reproducible\n- **Bind-mounting `.` into the container in production** — bind mounts\n  are for development; production should use the built image\n- **Missing `restart:` policy** — default is `no`, which means a crashed\n  service stays down until you notice\n",{"name":5,"metadata":44,"description":50},{"processkit":45},{"id":46,"created":47,"version":48,"category":31,"apiVersion":49},"SKILL-container-orchestration",1775433600000,"1.1.0","processkit.projectious.work\u002Fv2","Docker Compose patterns for multi-service apps — health checks, networking, volumes, dependencies. Use when writing or editing docker-compose files, designing multi-service architectures, debugging container networking, or managing volumes and service dependencies.\n","main","7231f100e266e30d2c1699ecde5c00602471dc3c","src\u002Fcontext\u002Fskills\u002Fdevops\u002Fcontainer-orchestration","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit","https:\u002F\u002Fprojectious-work.github.io\u002Fprocesskit\u002F","https:\u002F\u002Fgithub.com\u002Fprojectious-work","2026-11-11 23:24:18",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add projectious-work\u002Fprocesskit --skill container-orchestration",{"tool":64,"command":65},"bunx","bunx skills add projectious-work\u002Fprocesskit --skill container-orchestration",{"tool":67,"command":68},"pnpm","pnpm dlx skills add projectious-work\u002Fprocesskit --skill container-orchestration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdevops\u002Fcontainer-orchestration\u002FSKILL.md",true,[72,78],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fcompose-patterns.md","REFERENCE","参考文档",4772,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdevops\u002Fcontainer-orchestration\u002Freferences\u002Fcompose-patterns.md",{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":14,"sourceHtmlUrl":82},"scripts\u002F.gitkeep","SCRIPT","脚本","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdevops\u002Fcontainer-orchestration\u002Fscripts\u002F.gitkeep",[84,91,98,104,131,151],{"skillNo":85,"name":86,"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":87,"categories":88,"keywords":89,"publishedAt":90},"01M7665G2ED3624R3X93304265","standard-ui-design","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-ui-design\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":90},"01M76651QTC6W0HJ4AFW2MMR3V","standard-agent-use","Company standard for working with AI agents. Use when deciding what to delegate to agents, capturing open work, keeping agent memory or knowledge notes, improving an agent workflow, or introducing agent work in a team or for a client.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-use\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"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":101,"categories":102,"keywords":103,"publishedAt":90},"01M76650NN4T8P241021NBR64S","standard-agent-building","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-building\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":115,"publishedAt":39},"01M6X5MTC89B4ZGXW3JVSQCPF8","skill-management","Manage Skill package manifests as v1 ontology entities.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-management\u002FSKILL.md",[110],{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[116,117,118,119,120,121,34,122,123,124,125,126,106,127,128,129,130],"management","skill management","ontology","v1","create","as","transition","get","manage","update","alpha","list","package","skill package","manifests",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":138,"publishedAt":39},"01M6X5MCV74NHW5MEDNHZRF2C8","schema-management","Manage generated processkit schema contracts through deterministic MCP rebuild and inspection workflows.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fschema-management\u002FSKILL.md",[137],{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},[139,140,116,141,142,143,144,145,146,147,148,149,34,123,124,126,150],"schema","schema management","contract","rebuild","contracts","workflows","wed","generated","MCP","validation","deterministic","mode",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":39},"01M6X5M5G6YJ96AMZGSCZJ1D13","proposition-management","Record claims, risks, beliefs, world facts, WSJF estimates, and assumptions through the Proposition interface.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fproposition-management\u002FSKILL.md",[],[158,116,159,160,120,161,162,163,34,123,164,165,125,166,126,167,168,169,170,171],"proposition management","proposition","interface","claims","record","world","creation","event","WSJF","index","updates","query","facts","log"]