[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76X4S85S0J97RPCGKF4B664":3,"skill-same:01M76X4S85S0J97RPCGKF4B664":73},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M76X4S85S0J97RPCGKF4B664","render-blueprints",null,"Authors and validates render.yaml Blueprints for Render infrastructure. Use when the user needs to write or edit a render.yaml, wire services together with fromDatabase\u002FfromService\u002FfromGroup, set up projects and environments for multi-service apps, configure preview environments, validate against the schema, or fix immutable field errors. Trigger terms: render.yaml, Blueprint, IaC, fromDatabase, fromService, envVarGroups, previews, projects, environments.","stanfish06\u002Fskillquarium","stanfish06","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F93099613?v=4","01M75F1CK4ZW109ZK3T26VN52F","Zhiyuan","01M75F1CM53VH6F79DZ8GXKKES",12,"MIT","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Frender-blueprints\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: render-blueprints\ndescription: >-\n  Authors and validates render.yaml Blueprints for Render infrastructure. Use\n  when the user needs to write or edit a render.yaml, wire services together\n  with fromDatabase\u002FfromService\u002FfromGroup, set up projects and environments\n  for multi-service apps, configure preview environments, validate against\n  the schema, or fix immutable field errors. Trigger terms: render.yaml,\n  Blueprint, IaC, fromDatabase, fromService, envVarGroups, previews, projects,\n  environments.\nlicense: MIT\ncompatibility: >-\n  Git repository on GitHub, GitLab, or Bitbucket for Blueprint sync. Render CLI\n  v2.7.0+ recommended for `render blueprints validate`. IDEs can validate\n  against the public JSON Schema URL below.\nmetadata:\n  author: Render\n  version: \"1.0.0\"\n  category: configuration\n---\n\n# Render Blueprints (render.yaml)\n\nBlueprints define Render infrastructure as YAML (commonly `render.yaml` at the repo root). This skill focuses on **authoring**, **wiring**, **projects\u002Fenvironments**, **previews**, **validation**, and **immutable fields**. Heavy detail lives under `references\u002F`.\n\n## When to Use\n\nApply this skill when the user:\n\n- Creates or edits a `render.yaml` \u002F Blueprint\n- Wires databases, private services, or Key Value into app env vars\n- Groups services with **projects** and **environments**\n- Configures **preview environments** for pull requests\n- Validates YAML against Render’s schema or CLI\n- Asks what can or cannot change after a resource is created\n\nFor end-to-end deploy flows and MCP\u002FCLI operations, see **render-deploy**. For env var strategy outside Blueprint syntax, see **render-env-vars**. For Docker-specific Blueprint fields, see **render-docker**.\n\n## Blueprint Structure\n\n### Top-level keys\n\n| Key | Purpose |\n|-----|---------|\n| `services` | Web, worker, cron, private service, Key Value, static (via `web` + `runtime: static`) |\n| `databases` | Managed PostgreSQL instances |\n| `envVarGroups` | Reusable env var sets attached to services |\n| `projects` | Optional grouping; contains `environments` and service lists |\n| `previews` | Defaults for PR preview environments |\n\nA Blueprint may also use patterns like **ungrouped** resources vs **environment-scoped** lists, depending on whether you adopt the projects model. Avoid duplicating the same logical resource in multiple places (see `references\u002Fcommon-mistakes.md`).\n\n### Schema and IDE validation\n\n- **JSON Schema URL:** `https:\u002F\u002Frender.com\u002Fschema\u002Frender.yaml.json`\n- Configure your editor to associate `render.yaml` with that schema for completions and diagnostics.\n\n### Minimal example: web + PostgreSQL\n\n```yaml\ndatabases:\n  - name: mydb\n    plan: basic-256mb\n    region: oregon\n\nservices:\n  - type: web\n    name: api\n    runtime: node\n    region: oregon\n    plan: starter\n    buildCommand: npm ci && npm run build\n    startCommand: npm start\n    envVars:\n      - key: DATABASE_URL\n        fromDatabase:\n          name: mydb\n          property: connectionString\n```\n\n## Service Types\n\n| `type` | Role |\n|--------|------|\n| `web` | Public HTTP service (use `runtime: static` for static sites) |\n| `pserv` | Private service (internal HTTP\u002FTCP; not public) |\n| `worker` | Long-running background process |\n| `cron` | Scheduled job (`schedule` required) |\n| `keyvalue` | Managed Key Value (Redis-compatible); alias **`redis`** accepted in Blueprints |\n\n## Runtimes\n\nCommon `runtime` values: **`node`**, **`python`**, **`go`**, **`ruby`**, **`rust`**, **`elixir`**, **`docker`**, **`image`**, **`static`**.\n\n- **`docker`**: Build from `Dockerfile` (see `dockerfilePath`, `dockerContext`, `dockerCommand`).\n- **`image`**: Run a prebuilt container image (registry + optional `registryCredential`).\n- **`static`**: Static site; requires `staticPublishPath` and build output paths (see references).\n\n## Cross-Service Wiring\n\nEnv vars under `envVars` (and analogous patterns in groups) can pull values from other resources instead of hardcoding secrets.\n\n### `fromDatabase`\n\nReference a database in `databases:` by `name`. Properties include:\n\n- `connectionString`, `host`, `port`, `user`, `password`, `database`\n\n### `fromService`\n\nReference a service by `name`. Typical properties:\n\n- `host`, `port`, `hostport`, `connectionString`, `envVarKey`\n\nWhich properties are valid depends on target service type (e.g. Key Value vs `pserv`). See `references\u002Fwiring-patterns.md`.\n\n### `fromGroup`\n\nAttach shared vars from `envVarGroups` (by group `name`).\n\n### Other env var keys\n\n- **`value`**: Literal string.\n- **`generateValue`**: Let Render generate a random secret (password\u002FAPI key).\n- **`sync`**: Set `sync: false` for secrets that should not sync from repo on every update (see edge cases in wiring reference).\n\nFull patterns and combinations: `references\u002Fwiring-patterns.md`.\n\n## Projects and Environments\n\nFor multi-service apps, use the **`projects`\u002F`environments`** pattern instead of flat top-level `services`\u002F`databases`. This groups all related resources into a single Render project, supports multiple environments (production, staging), and enables environment-scoped configuration.\n\n```yaml\nprojects:\n  - name: my-app\n    environments:\n      - name: production\n        services:\n          - type: web\n            name: api\n            runtime: node\n            plan: standard\n            buildCommand: npm ci && npm run build\n            startCommand: npm start\n            envVars:\n              - key: DATABASE_URL\n                fromDatabase:\n                  name: db\n                  property: connectionString\n              - key: REDIS_URL\n                fromService:\n                  type: keyvalue\n                  name: cache\n                  property: connectionString\n              - key: API_SECRET\n                sync: false\n\n          - type: worker\n            name: jobs\n            runtime: node\n            plan: starter\n            buildCommand: npm ci\n            startCommand: node worker.js\n            envVars:\n              - key: DATABASE_URL\n                fromDatabase:\n                  name: db\n                  property: connectionString\n              - key: REDIS_URL\n                fromService:\n                  type: keyvalue\n                  name: cache\n                  property: connectionString\n\n          - type: keyvalue\n            name: cache\n            plan: starter\n            maxmemoryPolicy: noeviction\n            ipAllowList:\n              - source: 0.0.0.0\u002F0\n                description: everywhere\n\n        databases:\n          - name: db\n            plan: starter\n```\n\nKey rules:\n\n- Each environment owns its `services` and `databases` lists.\n- Do not define the same resource at both the root level and inside an environment.\n- `envVarGroups` can be scoped to a project environment or shared across the workspace.\n- Environment isolation (Professional+) can block cross-environment private network traffic.\n\nFor single-service apps, flat top-level `services`\u002F`databases` is fine. Reach for the projects pattern when you have multiple services, need staging\u002Fproduction separation, or want environment-scoped env groups.\n\n## Preview Environments\n\nTop-level `previews` controls PR previews:\n\n- **`previews.generation`**: `off` (default), `manual`, or `automatic`\n- **`previews.expireAfterDays`**: Auto-delete preview stacks after N days\n\nServices can override preview behavior (e.g. service-level `previews.generation`). Limitations: autoscaling behavior, `sync: false` vars, `previewPlan` \u002F flexible instance constraints—see `references\u002Fpreview-environments.md`.\n\n## Validation\n\n```bash\nrender blueprints validate\n```\n\nRequires **Render CLI v2.7.0+**. Run from the repo root (or pass the appropriate path options your CLI version supports). Fix schema and semantic errors before merging Blueprint changes.\n\nOfficial schema: `https:\u002F\u002Frender.com\u002Fschema\u002Frender.yaml.json`\n\n## Immutable Fields\n\n**CRITICAL:** Some fields cannot change after the resource is created. Edits may be rejected or require replacement resources.\n\n### Services\n\n- **`type`**: Cannot change (e.g. web → worker).\n- **`runtime`**: Cannot change (e.g. node → docker).\n\n### Databases\n\nCannot change after creation:\n\n- `name` (logical Blueprint\u002Fdatabase identifier in this context)\n- `databaseName`\n- `user`\n- `region`\n- `postgresMajorVersion`\n\nPlan other fields (disk, HA, replicas) carefully up front; consult Render docs for fields that can scale vs require recreation.\n\n## Key Fields (Quick Map)\n\n| Area | Fields |\n|------|--------|\n| Plans | `plan`, `previewPlan` (previews), database `plan` |\n| Build\u002Frun | `buildCommand`, `startCommand`, `preDeployCommand`, `rootDir` |\n| Deploy | `autoDeployTrigger`: `commit`, `checksPass`, or `off` |\n| Lifecycle | `maxShutdownDelaySeconds`: 1–300, default **30** |\n| HTTP | `healthCheckPath`, `domains` |\n| Storage | `disk` (`name`, `mountPath`, `sizeGB`) |\n| Scale | `scaling` \u002F `numInstances` (see references) |\n| Monorepo | `buildFilter` (`paths`, `ignoredPaths`) |\n| Docker | `dockerfilePath`, `dockerContext`, `dockerCommand`, `registryCredential` |\n\nDeprecated names to avoid: `env` (use `runtime`), `redis` (use `keyvalue`), `autoDeploy` (use `autoDeployTrigger`), `pullRequestPreviewsEnabled` (use `previews.generation`). Details: `references\u002Fcommon-mistakes.md`.\n\n## References\n\n| Document | Contents |\n|----------|----------|\n| `references\u002Ffield-reference.md` | YAML fields by service type, database, groups, projects, previews, scaling, disk, static, Key Value |\n| `references\u002Fwiring-patterns.md` | `fromDatabase` \u002F `fromService` \u002F `fromGroup` examples, `sync: false`, `generateValue`, combinations |\n| `references\u002Fcommon-mistakes.md` | Branch + previews, `buildFilter`, replicas, duplicates, preview plans, wiring mistakes |\n| `references\u002Fpreview-environments.md` | `previews.generation`, expiry, overrides, `previewPlan`, disks, PR workflow |\n\n## Related Skills\n\n- **render-deploy** — Deploy flows, Blueprint vs direct create, MCP\u002Fdeeplinks\n- **render-env-vars** — Env var strategy, secrets, Dashboard vs Blueprint\n- **render-docker** — Dockerfile-backed services and image runtime nuances\n","# Render Blueprints (render.yaml)\n\nBlueprints define Render infrastructure as YAML (commonly `render.yaml` at the repo root). This skill focuses on **authoring**, **wiring**, **projects\u002Fenvironments**, **previews**, **validation**, and **immutable fields**. Heavy detail lives under `references\u002F`.\n\n## When to Use\n\nApply this skill when the user:\n\n- Creates or edits a `render.yaml` \u002F Blueprint\n- Wires databases, private services, or Key Value into app env vars\n- Groups services with **projects** and **environments**\n- Configures **preview environments** for pull requests\n- Validates YAML against Render’s schema or CLI\n- Asks what can or cannot change after a resource is created\n\nFor end-to-end deploy flows and MCP\u002FCLI operations, see **render-deploy**. For env var strategy outside Blueprint syntax, see **render-env-vars**. For Docker-specific Blueprint fields, see **render-docker**.\n\n## Blueprint Structure\n\n### Top-level keys\n\n| Key | Purpose |\n|-----|---------|\n| `services` | Web, worker, cron, private service, Key Value, static (via `web` + `runtime: static`) |\n| `databases` | Managed PostgreSQL instances |\n| `envVarGroups` | Reusable env var sets attached to services |\n| `projects` | Optional grouping; contains `environments` and service lists |\n| `previews` | Defaults for PR preview environments |\n\nA Blueprint may also use patterns like **ungrouped** resources vs **environment-scoped** lists, depending on whether you adopt the projects model. Avoid duplicating the same logical resource in multiple places (see `references\u002Fcommon-mistakes.md`).\n\n### Schema and IDE validation\n\n- **JSON Schema URL:** `https:\u002F\u002Frender.com\u002Fschema\u002Frender.yaml.json`\n- Configure your editor to associate `render.yaml` with that schema for completions and diagnostics.\n\n### Minimal example: web + PostgreSQL\n\n```yaml\ndatabases:\n  - name: mydb\n    plan: basic-256mb\n    region: oregon\n\nservices:\n  - type: web\n    name: api\n    runtime: node\n    region: oregon\n    plan: starter\n    buildCommand: npm ci && npm run build\n    startCommand: npm start\n    envVars:\n      - key: DATABASE_URL\n        fromDatabase:\n          name: mydb\n          property: connectionString\n```\n\n## Service Types\n\n| `type` | Role |\n|--------|------|\n| `web` | Public HTTP service (use `runtime: static` for static sites) |\n| `pserv` | Private service (internal HTTP\u002FTCP; not public) |\n| `worker` | Long-running background process |\n| `cron` | Scheduled job (`schedule` required) |\n| `keyvalue` | Managed Key Value (Redis-compatible); alias **`redis`** accepted in Blueprints |\n\n## Runtimes\n\nCommon `runtime` values: **`node`**, **`python`**, **`go`**, **`ruby`**, **`rust`**, **`elixir`**, **`docker`**, **`image`**, **`static`**.\n\n- **`docker`**: Build from `Dockerfile` (see `dockerfilePath`, `dockerContext`, `dockerCommand`).\n- **`image`**: Run a prebuilt container image (registry + optional `registryCredential`).\n- **`static`**: Static site; requires `staticPublishPath` and build output paths (see references).\n\n## Cross-Service Wiring\n\nEnv vars under `envVars` (and analogous patterns in groups) can pull values from other resources instead of hardcoding secrets.\n\n### `fromDatabase`\n\nReference a database in `databases:` by `name`. Properties include:\n\n- `connectionString`, `host`, `port`, `user`, `password`, `database`\n\n### `fromService`\n\nReference a service by `name`. Typical properties:\n\n- `host`, `port`, `hostport`, `connectionString`, `envVarKey`\n\nWhich properties are valid depends on target service type (e.g. Key Value vs `pserv`). See `references\u002Fwiring-patterns.md`.\n\n### `fromGroup`\n\nAttach shared vars from `envVarGroups` (by group `name`).\n\n### Other env var keys\n\n- **`value`**: Literal string.\n- **`generateValue`**: Let Render generate a random secret (password\u002FAPI key).\n- **`sync`**: Set `sync: false` for secrets that should not sync from repo on every update (see edge cases in wiring reference).\n\nFull patterns and combinations: `references\u002Fwiring-patterns.md`.\n\n## Projects and Environments\n\nFor multi-service apps, use the **`projects`\u002F`environments`** pattern instead of flat top-level `services`\u002F`databases`. This groups all related resources into a single Render project, supports multiple environments (production, staging), and enables environment-scoped configuration.\n\n```yaml\nprojects:\n  - name: my-app\n    environments:\n      - name: production\n        services:\n          - type: web\n            name: api\n            runtime: node\n            plan: standard\n            buildCommand: npm ci && npm run build\n            startCommand: npm start\n            envVars:\n              - key: DATABASE_URL\n                fromDatabase:\n                  name: db\n                  property: connectionString\n              - key: REDIS_URL\n                fromService:\n                  type: keyvalue\n                  name: cache\n                  property: connectionString\n              - key: API_SECRET\n                sync: false\n\n          - type: worker\n            name: jobs\n            runtime: node\n            plan: starter\n            buildCommand: npm ci\n            startCommand: node worker.js\n            envVars:\n              - key: DATABASE_URL\n                fromDatabase:\n                  name: db\n                  property: connectionString\n              - key: REDIS_URL\n                fromService:\n                  type: keyvalue\n                  name: cache\n                  property: connectionString\n\n          - type: keyvalue\n            name: cache\n            plan: starter\n            maxmemoryPolicy: noeviction\n            ipAllowList:\n              - source: 0.0.0.0\u002F0\n                description: everywhere\n\n        databases:\n          - name: db\n            plan: starter\n```\n\nKey rules:\n\n- Each environment owns its `services` and `databases` lists.\n- Do not define the same resource at both the root level and inside an environment.\n- `envVarGroups` can be scoped to a project environment or shared across the workspace.\n- Environment isolation (Professional+) can block cross-environment private network traffic.\n\nFor single-service apps, flat top-level `services`\u002F`databases` is fine. Reach for the projects pattern when you have multiple services, need staging\u002Fproduction separation, or want environment-scoped env groups.\n\n## Preview Environments\n\nTop-level `previews` controls PR previews:\n\n- **`previews.generation`**: `off` (default), `manual`, or `automatic`\n- **`previews.expireAfterDays`**: Auto-delete preview stacks after N days\n\nServices can override preview behavior (e.g. service-level `previews.generation`). Limitations: autoscaling behavior, `sync: false` vars, `previewPlan` \u002F flexible instance constraints—see `references\u002Fpreview-environments.md`.\n\n## Validation\n\n```bash\nrender blueprints validate\n```\n\nRequires **Render CLI v2.7.0+**. Run from the repo root (or pass the appropriate path options your CLI version supports). Fix schema and semantic errors before merging Blueprint changes.\n\nOfficial schema: `https:\u002F\u002Frender.com\u002Fschema\u002Frender.yaml.json`\n\n## Immutable Fields\n\n**CRITICAL:** Some fields cannot change after the resource is created. Edits may be rejected or require replacement resources.\n\n### Services\n\n- **`type`**: Cannot change (e.g. web → worker).\n- **`runtime`**: Cannot change (e.g. node → docker).\n\n### Databases\n\nCannot change after creation:\n\n- `name` (logical Blueprint\u002Fdatabase identifier in this context)\n- `databaseName`\n- `user`\n- `region`\n- `postgresMajorVersion`\n\nPlan other fields (disk, HA, replicas) carefully up front; consult Render docs for fields that can scale vs require recreation.\n\n## Key Fields (Quick Map)\n\n| Area | Fields |\n|------|--------|\n| Plans | `plan`, `previewPlan` (previews), database `plan` |\n| Build\u002Frun | `buildCommand`, `startCommand`, `preDeployCommand`, `rootDir` |\n| Deploy | `autoDeployTrigger`: `commit`, `checksPass`, or `off` |\n| Lifecycle | `maxShutdownDelaySeconds`: 1–300, default **30** |\n| HTTP | `healthCheckPath`, `domains` |\n| Storage | `disk` (`name`, `mountPath`, `sizeGB`) |\n| Scale | `scaling` \u002F `numInstances` (see references) |\n| Monorepo | `buildFilter` (`paths`, `ignoredPaths`) |\n| Docker | `dockerfilePath`, `dockerContext`, `dockerCommand`, `registryCredential` |\n\nDeprecated names to avoid: `env` (use `runtime`), `redis` (use `keyvalue`), `autoDeploy` (use `autoDeployTrigger`), `pullRequestPreviewsEnabled` (use `previews.generation`). Details: `references\u002Fcommon-mistakes.md`.\n\n## References\n\n| Document | Contents |\n|----------|----------|\n| `references\u002Ffield-reference.md` | YAML fields by service type, database, groups, projects, previews, scaling, disk, static, Key Value |\n| `references\u002Fwiring-patterns.md` | `fromDatabase` \u002F `fromService` \u002F `fromGroup` examples, `sync: false`, `generateValue`, combinations |\n| `references\u002Fcommon-mistakes.md` | Branch + previews, `buildFilter`, replicas, duplicates, preview plans, wiring mistakes |\n| `references\u002Fpreview-environments.md` | `previews.generation`, expiry, overrides, `previewPlan`, disks, PR workflow |\n\n## Related Skills\n\n- **render-deploy** — Deploy flows, Blueprint vs direct create, MCP\u002Fdeeplinks\n- **render-env-vars** — Env var strategy, secrets, Dashboard vs Blueprint\n- **render-docker** — Dockerfile-backed services and image runtime nuances\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":28},{"author":25,"version":26,"category":27},"Render","1.0.0","configuration","Git repository on GitHub, GitLab, or Bitbucket for Blueprint sync. Render CLI v2.7.0+ recommended for `render blueprints validate`. IDEs can validate against the public JSON Schema URL below.","master","49e49abf2f670d429e0b7e2c0349739c3fdd5cbe","skills\u002Frender-blueprints",5,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium","https:\u002F\u002Fgithub.com\u002Fstanfish06","https:\u002F\u002Fwww.stanfish.dev\u002F","2026-11-14 21:31:37",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add stanfish06\u002Fskillquarium --skill render-blueprints",{"tool":43,"command":44},"bunx","bunx skills add stanfish06\u002Fskillquarium --skill render-blueprints",{"tool":46,"command":47},"pnpm","pnpm dlx skills add stanfish06\u002Fskillquarium --skill render-blueprints","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Frender-blueprints\u002FSKILL.md",true,[51,57,61,65,69],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"agents\u002Fopenai.yaml","REFERENCE","参考文档",216,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Frender-blueprints\u002Fagents\u002Fopenai.yaml",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fcommon-mistakes.md",4396,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Frender-blueprints\u002Freferences\u002Fcommon-mistakes.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Ffield-reference.md",8470,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Frender-blueprints\u002Freferences\u002Ffield-reference.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fpreview-environments.md",3837,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Frender-blueprints\u002Freferences\u002Fpreview-environments.md",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fwiring-patterns.md",4436,"https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Frender-blueprints\u002Freferences\u002Fwiring-patterns.md",[74,81,90,97,104,111],{"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},"01M76ZJTRVA456GD7K8Y3EP82H","zarr-python","Stores and queries chunked N-D scientific arrays with Zarr-Python 3, including codecs, sharding, S3\u002FGCS storage, and NumPy\u002FDask\u002FXarray integration. Use for array layout, bounded I\u002FO, format migration, or scientific metadata preservation.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fzarr-python\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":85,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M76ZJQZ15Q1HKC5V85NHE325","yeet","Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M76ZJ8ASZ4QYQ70Y6SBA4Z4S","xarray","N-dimensional labeled arrays and datasets in Python. Built on top of NumPy and Dask. It introduces labels in the form of dimensions, coordinates, and attributes on top of raw NumPy-like arrays, making data analysis in physical sciences more intuitive and less error-prone. Use for working with multi-dimensional scientific data, NetCDF\u002FGRIB\u002FZarr files, climate\u002Fweather\u002Foceanographic datasets, remote sensing, geospatial imaging, large out-of-memory datasets with Dask, and labeled array operations.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fxarray\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"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":19},"01M76ZHFBXD6VXPQ02VCEG202B","writing-mstest-tests","Use when asked to fix, rewrite, update, improve, modernize, show corrected code for, or explain existing MSTest tests or MSTest-specific configuration. Use for \"review\" when corrected code or edits are wanted, even for one pasted assertion or passing tests with bad failure output. Covers expected\u002Factual labels; generic Boolean, collection, string, numeric, null, identity, exception, hard-cast, and object[] checks; TestContext\u002Flifecycle; timeout\u002Fcancellation; OS\u002FCI conditions, retry, cleanup, parallelization, MSTest.Sdk project setup, and MSTESTxxxx. Honor the installed MSTest version. DO NOT USE to design new test cases (code-testing), perform report-only audits, create project files rather than explain MSTest setup, run tests, migrate frameworks, or handle non-MSTest\u002Fnon-.NET code.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwriting-mstest-tests\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":110,"publishedAt":19},"01M76ZDFDF4N88RH6HSYGS7GP2","wgs-prs","End-to-end WGS to polygenic risk score pipeline. Takes paired-end FASTQ files (or a pre-existing VCF) through nf-core\u002Fsarek for variant calling, applies VCF QC (normalisation, hard filtering, Ti\u002FTv and Het\u002FHom checks), then computes polygenic risk scores via the PGS Catalog. Fills the FASTQ to VCF gap upstream of the gwas-prs skill.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwgs-prs\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M76ZCC1SC68J42QK4MDC8RCG","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.","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fstanfish06\u002Fskillquarium\u002Fblob\u002Fmaster\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[]]