[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NW8RGTKFWS98RP7WDX6877":3,"skill-same:01M6NW8RGTKFWS98RP7WDX6877":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":30,"commitSha":47,"skillDirectory":48,"forksCount":13,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6NW8RGTKFWS98RP7WDX6877","aws-sst-development",null,"SST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework.","duc-duy-1612\u002FOnline-Delivery-Systems-Web","duc-duy-1612","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192231384?v=4","01M6NSDKQQDKVTHZ8DZMZ1VYY6","01M6NSDKW8DDVTQHBT1HBDDJPT",0,"MIT","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Faws-sst-development\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"development","aws sst development","aws","sst","for","github","tree","pulumi","with","resources","critical","as","main","community","expert","iac","plugins","https","license","code","2026-11-10 10:12:30",false,"---\nname: aws-sst-development\ndescription: \"SST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework.\"\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fzxkane\u002Faws-skills\u002Ftree\u002Fmain\u002Fplugins\u002Faws-iac\u002Fskills\u002Faws-sst-development\nsource_repo: zxkane\u002Faws-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fzxkane\u002Faws-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# SST v4 for AWS\n## When to Use\n\nUse this skill when you need sST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework. Use when writing or editing sst.config.ts, building infra\u002F modules (sst.aws.Function\u002FBucket\u002FDynamo\u002FCron\u002FService\u002FRouter, sst.Secret, sst.Linkable, raw aws.* Pulumi resources), wiring resource links,...\n\n\nSST v4 (the \"Ion\" engine) is a Pulumi-backed IaC framework: you describe AWS\nresources in TypeScript and SST\u002FPulumi reconciles them into your account. It\ngives you high-level `sst.aws.*` components (Function, Bucket, Dynamo, Cron,\nService, …) that expand into many underlying resources, plus an escape hatch to\n*any* raw Pulumi `aws.*` resource for the long tail. This skill encodes a\nproduction-proven way to author, link, test, deploy, and troubleshoot SST\nstacks on AWS — distilled from real multi-stack projects that have paid for\neach lesson with a prod incident.\n\n**SST and Pulumi are third-party — verify current syntax with Context7**\n(`resolve-library-id` → `query-docs` for `sst` or `pulumi-aws`) when you're\nunsure about a component's options. Verify AWS-side facts (service limits,\nmodel IDs, IAM action names, region availability) with the AWS docs MCP, never\nfrom memory. The patterns here are the *how*; the docs are the *what*.\n\n## When you're invoked\n\nFigure out which mode you're in and jump to the right reference:\n\n| Situation | Go to |\n|-----------|-------|\n| New project, or adding a resource\u002Fmodule to an existing SST app | **Author** → `references\u002Fauthoring.md` |\n| Wiring one module's output into another (links, SSM, IAM scope) | **Author** → `references\u002Fauthoring.md` § Sharing |\n| Writing tests for infra so changes don't silently break | **Test** → `references\u002Ftesting.md` |\n| Running a deploy, or a deploy just failed | **Deploy\u002FOperate** → `references\u002Fdeploy-and-troubleshoot.md` |\n| Migrating a resource between Pulumi types, renaming a physical name | **Deploy\u002FOperate** → `references\u002Fdeploy-and-troubleshoot.md` § Migrations |\n\nAlways read the relevant reference before editing — they carry the *why* behind\neach rule, which matters more than the rule itself.\n\n## Orientation: read the repo before you touch it\n\nSST projects are conventional but not identical. Before editing, build a quick\nmap so your change matches the house style instead of fighting it:\n\n1. **`sst.config.ts`** — the app name, `home`, providers\u002Fregion, `defaultTags`,\n   any global `$transform` (Node runtime pin, bundle fixups), and the order in\n   which `run()` imports `infra\u002F` modules. The import order *is* the dependency\n   order; respect it.\n2. **`infra\u002F`** — one file per domain (storage, functions, api, observability…).\n   This is where resources are declared. Check for an `infra\u002FCLAUDE.md` — these\n   projects keep IaC-specific rules there, and it's the single most valuable\n   file to read first.\n3. **`infra\u002Ftests\u002F`** — source-level Vitest assertions that pin resource\n   invariants. If they exist, your change must keep them green and probably\n   needs a new assertion.\n4. **`package.json` \u002F `.nvmrc`** — package manager (npm vs pnpm), Node version,\n   and the `sst`\u002F`pulumi` versions actually installed.\n\nRun `npx sst version` to confirm you're on v4\u002FIon (the `$config` + `.sst\u002Fplatform\u002F`\nsignature). v2\u002Fv3 (\"SST Classic\", CDK-based) is a different framework — these\npatterns don't apply there.\n\n## The conventions, and which are universal vs tunable\n\nThe projects this skill is built from share a deliberate house style. Some of it\nis **universal** (true for any SST v4 + AWS project — apply it everywhere); some\nis **project-specific** (a sensible default these projects chose — adopt it for\nconsistency, but recognize a project may differ).\n\n**Universal — these principles hold for any SST v4 + AWS project:**\n\n- **Control the Node runtime deliberately, in one place.** Don't leave it to\n  whatever the installed SST happens to default to. The idiom is a single global\n  `$transform(sst.aws.Function, (args) => { args.runtime ??= \"nodejs24.x\" })` in\n  `run()` — `??=` is correct here (the transform runs before the component\n  applies its own default, so it fills in only when the user didn't set one).\n  Recent SST already defaults to a current Node runtime, so check the installed\n  default first (Context7); the transform is then version-independence insurance\n  so a future SST downgrade can't silently move your fleet. See\n  `references\u002Fauthoring.md`.\n- **Never interpolate a Pulumi `Output\u003CT>` into a plain JS template literal.**\n  Use `$interpolate` (or `pulumi.interpolate`). A bare top-level\n  `` `${bucket.arn}\u002F*` `` stringifies the `Output` to a `[Output\u003CT>]` placeholder\n  and produces a broken ARN that only fails at deploy time (it type-checks and\n  `sst dev` runs fine). The fix is `$interpolate`​`` `${bucket.arn}\u002F*` ``. This\n  has caused prod deploy outages. See `references\u002Fauthoring.md` § Outputs.\n- **Migrating a resource between Pulumi *types* should default to two PRs** —\n  Pulumi creates-before-destroys, so for a uniqueness-constrained AWS name\n  (bucket, IAM role, gateway) the old resource still owns it and the create\n  fails with `ConflictException`. Two sequential deploys (teardown, then\n  recreate) is the conservative default; `aliases:` \u002F `pulumi import` \u002F state\n  surgery can bridge identity in some cases but only with a reviewed plan. See\n  `references\u002Fdeploy-and-troubleshoot.md` § Migrations.\n- **Prefer typed `sst.aws.*` \u002F `aws.*` resources over the\n  `aws.cloudcontrol.Resource` escape hatch.** CloudControl outputs are\n  stringly-typed and `oneOf` fields don't patch cleanly. Use it only when no\n  typed resource exists yet, and migrate off it when one ships.\n\n**Project-specific defaults — adopt for consistency, but confirm per repo:**\n\n- **Region `ap-northeast-1`**, `home: \"aws\"`, and `defaultTags` carrying\n  `Project` \u002F `Stage` \u002F `ManagedBy: \"sst\"`.\n- **Stage-gated lifecycle**: `removal: stage === \"prod\" ? \"retain\" : \"remove\"`\n  and `protect: stage === \"prod\"` so prod resources survive a stack tear-down\n  and non-prod previews clean up.\n- **SSM Parameter Store as the out-of-graph contract** under a\n  `\u002F{app}\u002F{stage}\u002F{domain}\u002F...` prefix — for consumers that aren't in the\n  Pulumi graph (CI scripts, sibling apps, operators). For *same-app* Lambdas,\n  prefer SST `link:` (it wires a real dependency edge and grants IAM); don't\n  route same-app sharing through SSM. See `references\u002Fauthoring.md` § Sharing.\n- **Lazy `await import(\".\u002Finfra\u002F\u003Cmodule>\")` inside `run()`** so `sst dev`\n  hot-reload stays light. (For testing, a module export still runs its top-level\n  `new sst.aws.*` unless it's wrapped in a factory function — see\n  `references\u002Ftesting.md` for how to test infra.)\n- **Source-level Vitest tests** on every infra module — a lightweight,\n  house-style regression net asserting on the *source text* (resource names,\n  index shapes, IAM scopes). It's a deliberate choice, not an SST limit: Pulumi\n  *does* support runtime mocks (`@pulumi\u002Fpulumi\u002Fruntime`) for behavioral graph\n  tests when a module has real logic. Source assertions don't replace a\n  preview-deploy + smoke test. See `references\u002Ftesting.md`.\n- **An observability gate**: every new Lambda\u002Fqueue\u002Fschedule gets an alarm and\n  structured logging before merge. Whether you enforce this depends on the\n  project, but it's cheap insurance. See `references\u002Fdeploy-and-troubleshoot.md`\n  § Observability.\n\nWhen you introduce a convention, say which bucket it's in (\"this is universal\"\nvs \"matching this repo's house style\") so the user can override the\nproject-specific ones deliberately.\n\n## Working rhythm\n\n1. **Orient** (above) — map config, modules, tests, tooling.\n2. **Verify syntax** with Context7 \u002F AWS docs MCP if anything is non-obvious.\n   Don't guess at a component's option name.\n3. **Author** the resource\u002Fmodule following `references\u002Fauthoring.md`. Match the\n   surrounding file's commenting density and naming — these projects comment the\n   *why* heavily, and a terse one-liner in a heavily-annotated file reads as a\n   regression.\n4. **Test** — add or update source-level assertions (`references\u002Ftesting.md`) and\n   run `npx vitest` (or the repo's `test` script). Run `npx sst diff` and\u002For\n   `tsc --noEmit` to catch type and plan errors before deploying.\n5. **Deploy\u002Foperate** per `references\u002Fdeploy-and-troubleshoot.md`. Confirm the\n   target account with `aws sts get-caller-identity` before any `sst deploy`.\n6. **Clean up** any exported state files — they contain account IDs and ARNs and\n   must not linger in `\u002Ftmp` or chat history.\n\n## What good looks like\n\n- The change is the smallest diff that satisfies the requirement, in the right\n  `infra\u002F` module, wired into `run()` in dependency order.\n- Every Lambda gets the right runtime via the global transform (you didn't\n  hand-set `runtime` unless intentionally diverging — e.g. a Python function).\n- Cross-resource references use `link:` (in-graph) and\u002For `$interpolate`-scoped\n  IAM; outputs other tools consume are published to SSM under the stage prefix.\n- New infra has a matching source-level test, and the existing suite stays green.\n- You confirmed AWS-side facts via the docs MCP and SST\u002FPulumi syntax via\n  Context7 rather than relying on recall.\n- Anything irreversible (deploy, `sst remove`, a resource-type migration) was\n  flagged to the user with the account it targets, and migrations were planned\n  as two PRs, not one.\n\n## Example\n\n**User request:**\n\n> Use @aws-sst-development for this task: SST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# SST v4 for AWS\n## When to Use\n\nUse this skill when you need sST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework. Use when writing or editing sst.config.ts, building infra\u002F modules (sst.aws.Function\u002FBucket\u002FDynamo\u002FCron\u002FService\u002FRouter, sst.Secret, sst.Linkable, raw aws.* Pulumi resources), wiring resource links,...\n\n\nSST v4 (the \"Ion\" engine) is a Pulumi-backed IaC framework: you describe AWS\nresources in TypeScript and SST\u002FPulumi reconciles them into your account. It\ngives you high-level `sst.aws.*` components (Function, Bucket, Dynamo, Cron,\nService, …) that expand into many underlying resources, plus an escape hatch to\n*any* raw Pulumi `aws.*` resource for the long tail. This skill encodes a\nproduction-proven way to author, link, test, deploy, and troubleshoot SST\nstacks on AWS — distilled from real multi-stack projects that have paid for\neach lesson with a prod incident.\n\n**SST and Pulumi are third-party — verify current syntax with Context7**\n(`resolve-library-id` → `query-docs` for `sst` or `pulumi-aws`) when you're\nunsure about a component's options. Verify AWS-side facts (service limits,\nmodel IDs, IAM action names, region availability) with the AWS docs MCP, never\nfrom memory. The patterns here are the *how*; the docs are the *what*.\n\n## When you're invoked\n\nFigure out which mode you're in and jump to the right reference:\n\n| Situation | Go to |\n|-----------|-------|\n| New project, or adding a resource\u002Fmodule to an existing SST app | **Author** → `references\u002Fauthoring.md` |\n| Wiring one module's output into another (links, SSM, IAM scope) | **Author** → `references\u002Fauthoring.md` § Sharing |\n| Writing tests for infra so changes don't silently break | **Test** → `references\u002Ftesting.md` |\n| Running a deploy, or a deploy just failed | **Deploy\u002FOperate** → `references\u002Fdeploy-and-troubleshoot.md` |\n| Migrating a resource between Pulumi types, renaming a physical name | **Deploy\u002FOperate** → `references\u002Fdeploy-and-troubleshoot.md` § Migrations |\n\nAlways read the relevant reference before editing — they carry the *why* behind\neach rule, which matters more than the rule itself.\n\n## Orientation: read the repo before you touch it\n\nSST projects are conventional but not identical. Before editing, build a quick\nmap so your change matches the house style instead of fighting it:\n\n1. **`sst.config.ts`** — the app name, `home`, providers\u002Fregion, `defaultTags`,\n   any global `$transform` (Node runtime pin, bundle fixups), and the order in\n   which `run()` imports `infra\u002F` modules. The import order *is* the dependency\n   order; respect it.\n2. **`infra\u002F`** — one file per domain (storage, functions, api, observability…).\n   This is where resources are declared. Check for an `infra\u002FCLAUDE.md` — these\n   projects keep IaC-specific rules there, and it's the single most valuable\n   file to read first.\n3. **`infra\u002Ftests\u002F`** — source-level Vitest assertions that pin resource\n   invariants. If they exist, your change must keep them green and probably\n   needs a new assertion.\n4. **`package.json` \u002F `.nvmrc`** — package manager (npm vs pnpm), Node version,\n   and the `sst`\u002F`pulumi` versions actually installed.\n\nRun `npx sst version` to confirm you're on v4\u002FIon (the `$config` + `.sst\u002Fplatform\u002F`\nsignature). v2\u002Fv3 (\"SST Classic\", CDK-based) is a different framework — these\npatterns don't apply there.\n\n## The conventions, and which are universal vs tunable\n\nThe projects this skill is built from share a deliberate house style. Some of it\nis **universal** (true for any SST v4 + AWS project — apply it everywhere); some\nis **project-specific** (a sensible default these projects chose — adopt it for\nconsistency, but recognize a project may differ).\n\n**Universal — these principles hold for any SST v4 + AWS project:**\n\n- **Control the Node runtime deliberately, in one place.** Don't leave it to\n  whatever the installed SST happens to default to. The idiom is a single global\n  `$transform(sst.aws.Function, (args) => { args.runtime ??= \"nodejs24.x\" })` in\n  `run()` — `??=` is correct here (the transform runs before the component\n  applies its own default, so it fills in only when the user didn't set one).\n  Recent SST already defaults to a current Node runtime, so check the installed\n  default first (Context7); the transform is then version-independence insurance\n  so a future SST downgrade can't silently move your fleet. See\n  `references\u002Fauthoring.md`.\n- **Never interpolate a Pulumi `Output\u003CT>` into a plain JS template literal.**\n  Use `$interpolate` (or `pulumi.interpolate`). A bare top-level\n  `` `${bucket.arn}\u002F*` `` stringifies the `Output` to a `[Output\u003CT>]` placeholder\n  and produces a broken ARN that only fails at deploy time (it type-checks and\n  `sst dev` runs fine). The fix is `$interpolate`​`` `${bucket.arn}\u002F*` ``. This\n  has caused prod deploy outages. See `references\u002Fauthoring.md` § Outputs.\n- **Migrating a resource between Pulumi *types* should default to two PRs** —\n  Pulumi creates-before-destroys, so for a uniqueness-constrained AWS name\n  (bucket, IAM role, gateway) the old resource still owns it and the create\n  fails with `ConflictException`. Two sequential deploys (teardown, then\n  recreate) is the conservative default; `aliases:` \u002F `pulumi import` \u002F state\n  surgery can bridge identity in some cases but only with a reviewed plan. See\n  `references\u002Fdeploy-and-troubleshoot.md` § Migrations.\n- **Prefer typed `sst.aws.*` \u002F `aws.*` resources over the\n  `aws.cloudcontrol.Resource` escape hatch.** CloudControl outputs are\n  stringly-typed and `oneOf` fields don't patch cleanly. Use it only when no\n  typed resource exists yet, and migrate off it when one ships.\n\n**Project-specific defaults — adopt for consistency, but confirm per repo:**\n\n- **Region `ap-northeast-1`**, `home: \"aws\"`, and `defaultTags` carrying\n  `Project` \u002F `Stage` \u002F `ManagedBy: \"sst\"`.\n- **Stage-gated lifecycle**: `removal: stage === \"prod\" ? \"retain\" : \"remove\"`\n  and `protect: stage === \"prod\"` so prod resources survive a stack tear-down\n  and non-prod previews clean up.\n- **SSM Parameter Store as the out-of-graph contract** under a\n  `\u002F{app}\u002F{stage}\u002F{domain}\u002F...` prefix — for consumers that aren't in the\n  Pulumi graph (CI scripts, sibling apps, operators). For *same-app* Lambdas,\n  prefer SST `link:` (it wires a real dependency edge and grants IAM); don't\n  route same-app sharing through SSM. See `references\u002Fauthoring.md` § Sharing.\n- **Lazy `await import(\".\u002Finfra\u002F\u003Cmodule>\")` inside `run()`** so `sst dev`\n  hot-reload stays light. (For testing, a module export still runs its top-level\n  `new sst.aws.*` unless it's wrapped in a factory function — see\n  `references\u002Ftesting.md` for how to test infra.)\n- **Source-level Vitest tests** on every infra module — a lightweight,\n  house-style regression net asserting on the *source text* (resource names,\n  index shapes, IAM scopes). It's a deliberate choice, not an SST limit: Pulumi\n  *does* support runtime mocks (`@pulumi\u002Fpulumi\u002Fruntime`) for behavioral graph\n  tests when a module has real logic. Source assertions don't replace a\n  preview-deploy + smoke test. See `references\u002Ftesting.md`.\n- **An observability gate**: every new Lambda\u002Fqueue\u002Fschedule gets an alarm and\n  structured logging before merge. Whether you enforce this depends on the\n  project, but it's cheap insurance. See `references\u002Fdeploy-and-troubleshoot.md`\n  § Observability.\n\nWhen you introduce a convention, say which bucket it's in (\"this is universal\"\nvs \"matching this repo's house style\") so the user can override the\nproject-specific ones deliberately.\n\n## Working rhythm\n\n1. **Orient** (above) — map config, modules, tests, tooling.\n2. **Verify syntax** with Context7 \u002F AWS docs MCP if anything is non-obvious.\n   Don't guess at a component's option name.\n3. **Author** the resource\u002Fmodule following `references\u002Fauthoring.md`. Match the\n   surrounding file's commenting density and naming — these projects comment the\n   *why* heavily, and a terse one-liner in a heavily-annotated file reads as a\n   regression.\n4. **Test** — add or update source-level assertions (`references\u002Ftesting.md`) and\n   run `npx vitest` (or the repo's `test` script). Run `npx sst diff` and\u002For\n   `tsc --noEmit` to catch type and plan errors before deploying.\n5. **Deploy\u002Foperate** per `references\u002Fdeploy-and-troubleshoot.md`. Confirm the\n   target account with `aws sts get-caller-identity` before any `sst deploy`.\n6. **Clean up** any exported state files — they contain account IDs and ARNs and\n   must not linger in `\u002Ftmp` or chat history.\n\n## What good looks like\n\n- The change is the smallest diff that satisfies the requirement, in the right\n  `infra\u002F` module, wired into `run()` in dependency order.\n- Every Lambda gets the right runtime via the global transform (you didn't\n  hand-set `runtime` unless intentionally diverging — e.g. a Python function).\n- Cross-resource references use `link:` (in-graph) and\u002For `$interpolate`-scoped\n  IAM; outputs other tools consume are published to SSM under the stage prefix.\n- New infra has a matching source-level test, and the existing suite stays green.\n- You confirmed AWS-side facts via the docs MCP and SST\u002FPulumi syntax via\n  Context7 rather than relying on recall.\n- Anything irreversible (deploy, `sst remove`, a resource-type migration) was\n  flagged to the user with the account it targets, and migrations were planned\n  as two PRs, not one.\n\n## Example\n\n**User request:**\n\n> Use @aws-sst-development for this task: SST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":28,"source":43,"license":14,"date_added":44,"description":7,"source_repo":45,"source_type":31,"license_source":46},"https:\u002F\u002Fgithub.com\u002Fzxkane\u002Faws-skills\u002Ftree\u002Fmain\u002Fplugins\u002Faws-iac\u002Fskills\u002Faws-sst-development",1782864000000,"zxkane\u002Faws-skills","https:\u002F\u002Fgithub.com\u002Fzxkane\u002Faws-skills\u002Fblob\u002Fmain\u002FLICENSE","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Faws-sst-development","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612","2026-10-25 23:50:58",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill aws-sst-development",{"tool":58,"command":59},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill aws-sst-development",{"tool":61,"command":62},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill aws-sst-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Faws-sst-development\u002FSKILL.md",true,[],[67,95,119,141,169,192],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":78,"publishedAt":38},"01M6Q0FA5FZ410Z33Z3TFQ4DBA","zero-trust","Implement zero-trust network architecture. Configure identity-based access, micro-segmentation, and continuous verification. Use when implementing modern security architectures.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzero-trust\u002FSKILL.md",[73],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[79,80,81,82,83,84,69,85,86,87,88,89,31,30,90,28,91,92,93,94],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","configure","only","active","scope","scripts","relevant","implementing",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":38},"01M6Q0F1YZJW3KX5FBKEVZ8CV4","zcode-delegate","Delegate coding tasks to the Z.AI ZCode CLI only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzcode-delegate\u002FSKILL.md",[],[102,103,104,105,106,107,108,109,110,111,112,113,114,89,115,31,116,117,28,118],"delegate","zcode","zcode delegate","review","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":38},"01M6Q0ETK41VGNMYEXW0T00AJN","youtube-transcript","Fetch YouTube transcripts through DeepAPI or local fallback tooling and save clean text output.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript\u002FSKILL.md",[],[126,127,128,129,23,130,131,36,35,132,133,134,135,31,30,136,137,138,139,140],"transcript","youtube transcript","youtube","safe","codex","research","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":158,"publishedAt":38},"01M6Q0EPPH2PVMDW40017F8WX0","youtube-transcript-skills","Fetch YouTube video transcripts, search videos\u002Fchannels, browse channels, and extract playlists via the getyoutubetranscript.com API - free tier, no card required.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript-skills\u002FSKILL.md",[147,150,153],{"categoryNo":148,"categoryName":149,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":151,"categoryName":152,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":154,"categoryName":155,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[126,127,128,159,129,160,23,130,36,161,162,163,164,133,165,31,30,166,167,168],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":179,"publishedAt":38},"01M6Q0EAB96PX83W5PTE8A0R8D","youtube-notetaker","Turn YouTube talks into local study notes with slides, transcripts, editable annotations, and a markdown-backed viewer.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-notetaker\u002FSKILL.md",[175,178],{"categoryNo":176,"categoryName":177,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":151,"categoryName":152,"taxonomyType":76,"taxonomyTypeDesc":77},[128,180,181,106,129,182,183,184,37,36,163,185,186,187,188,30,189,136,190,191],"youtube notetaker","notetaker","workflow","official","notes","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":199,"publishedAt":38},"01M6Q0E55F0GW5MX48V8HXS8B5","youtube-full","Fetch YouTube transcripts, search videos, browse channels, and extract playlists via TranscriptAPI — no yt-dlp, no Google API key, works from any cloud server.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-full\u002FSKILL.md",[198],{"categoryNo":148,"categoryName":149,"taxonomyType":76,"taxonomyTypeDesc":77},[200,128,201,202,129,160,161,203,204,162,163,164,133,205,165,31,30,166,206,139],"youtube full","full","google","server","dlp","credits","automatic"]