[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ACD8ASECG8VTQW879Z5057":3,"skill-same:01M7ACD8ASECG8VTQW879Z5057":142},{"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":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M7ACD8ASECG8VTQW879Z5057","serverlessrepo-application-deployer",null,"Provisions AWS Serverless Application Repository (SAR) applications with production defaults: SAM template (template.yaml) with Transform: AWS::Serverless-2016-10-31, README.md (required for publish), LICENSE (required for public), application packaging (zip upload or S3 bucket with code URI), semantic versioning (SemVer — required for every publish), application sharing model (private vs account-grant vs public), application policy (who can deploy cross-account), nested applications (AWS::Serverless:: Application), application parameters (cloudformation parameters surfaced at deploy time), deployment role (CAPABILITY_IAM \u002F CAPABILITY_NAMED_IAM \u002F CAPABILITY_AUTO_EXPAND), SAM transform during deploy (transform happens BEFORE CloudFormation sees the template), published author profile (author name, URL. Triggers: publish serverless application, sar publish, serverless application repository, sam package, sam deploy, sar application policy, cross-account sar deploy, nested sar application, semantic version sar.","jhkchan\u002Faws-agent-skills","jhkchan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1083902?v=4","01M7A2SVQYP9GQTPTDXP5JKYQ4","Jacky Chan","01M7A2SVS117YWCTZABB75HZR1",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fserverlessrepo-application-deployer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: serverlessrepo-application-deployer\ndescription: 'Provisions AWS Serverless Application Repository (SAR) applications with production defaults: SAM template (template.yaml) with Transform: AWS::Serverless-2016-10-31, README.md (required for publish), LICENSE (required for public), application packaging (zip upload or S3 bucket with code URI), semantic versioning (SemVer — required for every publish), application sharing model (private vs account-grant vs public), application policy (who can deploy cross-account), nested applications (AWS::Serverless:: Application), application parameters (cloudformation parameters surfaced at deploy time), deployment role (CAPABILITY_IAM \u002F CAPABILITY_NAMED_IAM \u002F CAPABILITY_AUTO_EXPAND), SAM transform during deploy (transform happens BEFORE CloudFormation sees the template), published author profile (author name, URL. Triggers: publish serverless application, sar publish, serverless application repository, sam package, sam deploy, sar application policy, cross-account sar deploy, nested sar application, semantic version sar.'\nlicense: Apache-2.0\ncompatibility: 'Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS SAM CLI (sam package, sam deploy) or AWS CLI v2 with serverlessrepo create-application \u002F put-application-policy \u002F create-cloud-formation-change-set. Requires an S3 bucket for artifact storage and IAM permissions for cloudformation:CreateChangeSet, serverlessrepo:CreateApplication, and the transforms the SAM template declares.'\nmetadata:\n  domain: aws-cloudops\n  complexity: high\n  requires_llm: 'true'\n  phase: '1'\n  supports_pipeline: 'true'\n  entry_point: 'false'\n  family: DevTools\n  task_type: deploy\n  skill_class: capability\n  lifecycle_status: active\n  verdict_shape: READY_TO_DEPLOY | PREREQUISITES_MISSING\n  version: 0.1.0\n  author: Jacky Chan — AWS Community Builder\n  tags: aws, serverless, sar, sam, cloudformation, cloudops, deploy, devtools, semantic-versioning, application-policy, nested-application, cross-account\n  dependencies: aws-orchestrator\n  keywords: aws, serverless application repository, sar, sam, sam template, sam deploy, sam package, cloudformation, semantic versioning, application policy, nested application, cross-account deploy, application sharing, public application, private application, appregistry, deployment role, lambda, cloudops, deploy, devtools\n  when_to_use: Invoke when the user wants to publish a serverless application to the Serverless Application Repository, share an application privately or publicly, deploy an application from SAR via CloudFormation, version an application update using semantic versioning, compose nested SAR applications, configure an application policy for cross-account deployment, or understand the SAM transform pipeline. Do NOT invoke for AWS Service Catalog product registration (different catalog), CDK app publishing (CDK has its own publishing path), or AppRegistry metadata grouping (AppRegistry is metadata-only, not a deploy surface).\n---\n\n# Serverless Application Repository Deployer\n\nAn AWS CloudOps agent skill that provisions AWS Serverless Application\nRepository (SAR) applications with correct defaults. The skill walks\nthe operator through the SAM template structure, packaging (zip upload\nor S3), semantic versioning, the application sharing model (private vs\naccount-grant vs public), the application policy that gates cross-\naccount deploy, the SAM transform pipeline (transform happens BEFORE\nCloudFormation), nested application composition, the deployment role\nand capabilities, and application deletion\u002Fcleanup. It captures the\napplication definition decisions, explains why each default matters,\nand emits a READY_TO_DEPLOY checklist with copy-pasteable verification\ncommands.\n\n## Activation keywords\n\npublish serverless application, sar publish, serverless application\nrepository, sam package, sam deploy, sar application policy, cross-\naccount sar deploy, nested sar application, semantic version sar.\n\n## STRICT output contract\n\nWhen this skill is invoked with a SAR-provisioning request (publish\nan application, share an application, deploy someone else's\napplication, version an update, compose nested applications, or a\npartial configuration), the agent MUST respond with the\nREADY_TO_DEPLOY checklist defined in the \"Output format\" section\nusing the literal all-caps labels `SAR_APPLICATION:`, `VERDICT:`,\n`CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do NOT preface the\nchecklist with prose, headings, or disclaimers — emit the block as\nthe first lines of the response. This contract is what assertion-\nbased evals and downstream provisioning pipelines rely on; deviating\nfrom the literal labels breaks automation silently.\n\nIf any prerequisite is missing, the verdict is `PREREQUISITES_MISSING`\nwith a specific gap citation in the checklist (marked `[✗]`), and\n`READY_TO_DEPLOY` MUST NOT also appear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before provisioning |\n| Step 1 — Application structure (template.yaml + README + LICENSE) | Core app anatomy |\n| Step 2 — SAM transform pipeline | Transform happens before CFN |\n| Step 3 — Packaging (zip upload or S3 code URI) | Artifact storage |\n| Step 4 — Semantic versioning | Every publish needs a version |\n| Step 5 — Application sharing (private vs public) | Visibility model |\n| Step 6 — Application policy (cross-account deploy) | Who can deploy |\n| Step 7 — Deployment via CloudFormation change set | Deploy mechanism |\n| Step 8 — Deployment role and capabilities | IAM surface |\n| Step 9 — Nested applications | Composition |\n| Step 10 — Application parameters | Surfaced at deploy time |\n| Step 11 — Author profile and labels | Published metadata |\n| Step 12 — Deletion and cleanup | Teardown |\n| Step 13 — SAR vs AppRegistry | Avoid confusion |\n| Step 14 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Fsam-transform-and-deploy.md | Transform + deploy detail |\n| references\u002Fsar-publishing-and-sharing.md | Publishing + sharing detail |\n\n## Mindset\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#mindset).\n> Three provisioning-time misconceptions: publish vs deploy, cross-account 403 without an application policy, mandatory immutable SemVer.\n\n## Configuration dependency graph (novel heuristic)\n\nSAR application configurations are NOT independent. The SAM template\nmust exist before packaging. Packaging must complete before publish.\nPublish must complete before sharing. The application policy must\nexist before cross-account deploy. Use this graph to sequence\nprovisioning.\n\n| Configuration | Hard dependencies (API error without) | Silent failure \u002F immutability | Enables downstream |\n|---|---|---|---|\n| SAM template (template.yaml) | Valid YAML; Transform declared; resources under 200 | Template with unresolved `CodeUri` uploads raw path, not code | the application definition |\n| README.md | Required at publish time (CreateApplication \u002F UpdateApplication) | Empty README is accepted but app cannot be shared publicly without content | public sharing eligibility |\n| LICENSE | Required for PUBLIC sharing only; private apps can omit | App without LICENSE cannot be made public (API rejects) | public sharing |\n| Packaging (sam package) | S3 bucket exists; IAM s3:PutObject | Forgetting to package → CodeUri points to local path → deploy fails | S3-backed code artifact |\n| Semantic version | Required at every publish; must be unique per application | Reusing a version → API rejects with ConflictException; no overwrite | update management |\n| Publish (create-application) | Template packaged; README present; version set | Publishing without an application policy → only the publisher account can deploy | catalog entry |\n| Application policy | Application published; consumer AWS account ID(s) known | Policy omitted → cross-account deploy fails with 403 | cross-account deployment |\n| Deployment (create-cloud-formation-change-set) | Application published; consumer has permission; capabilities match | Missing CAPABILITY_AUTO_EXPAND → nested application deploy fails | running stack |\n| Nested application | Parent template uses AWS::Serverless::Application; child app published and accessible | Child app not shared → parent deploy fails at expand time | composition |\n\n**The application-policy-gates-cross-account row is the one a\nbaseline model misses.** Publishing the app is necessary but NOT\nsufficient for cross-account use. The policy must explicitly grant\neach consumer account (for private) or be set to public (for public\napps). The SAM-transform-before-CFN row is the second commonly\nmisunderstood step.\n\n**Cross-dependency gotchas:**\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#configuration-dependency-graph--cross-dependency-gotchas).\n> Five gotchas: deploy-time transform, CAPABILITY_AUTO_EXPAND for nested apps, private sharing tiers, stack vs SAR deletion, version embedded in the ARN.\n\n## Expert heuristic: the SAM transform pipeline\n\nA baseline model says \"upload the template and deploy.\" The correct\nheuristic recognizes that SAR stores the RAW SAM template and the\ntransform happens at DEPLOY time on the CONSUMER side.\n\n```text\nPublisher flow:\n  1. Write template.yaml (Transform: AWS::Serverless-2016-10-31)\n  2. sam package → uploads code to S3, produces packaged.yaml\n  3. serverlessrepo create-application → stores SAM template + metadata\n  4. (optional) serverlessrepo put-application-policy → grants consumers\n\nConsumer flow:\n  1. serverlessrepo create-cloud-formation-change-set → SAR fetches template\n  2. SAM transform runs → AWS::Serverless::Function → AWS::Lambda::Function\n  3. CloudFormation receives the EXPANDED template\n  4. CloudFormation creates\u002Fupdates the stack with CAPABILITY_IAM\n```\n\n**Key implication:** the publisher's SAM template must be self-\ncontained and valid for transformation. Any intrinsic function refs\nmust resolve within the consumer's account at deploy time. The\npublisher cannot pre-transform — the transform is inherently a deploy-\ntime operation because it may generate account-specific resources\n(IAM roles, API Gateway stage names, etc.).\n\n## Expert heuristic: application policy gates cross-account deploy\n\nA baseline model publishes the app and assumes it is deployable\neverywhere. The correct heuristic recognizes three sharing tiers,\neach with a different deploy permission model.\n\n```text\nSharing tier decision:\n  ├── PRIVATE (default)\n  │     → Only the publisher account can deploy\n  │     → No application policy needed\n  │     → ARN: arn:aws:serverlessrepo:\u003Cregion>:\u003Cacct>:apps\u002F\u003Capp>\n  │\n  ├── PRIVATE + APPLICATION POLICY (account-grant)\n  │     → Publisher grants specific AWS account IDs\n  │     → put-application-policy with Principal: {AWS: [\"arn:...:\u003Cacct>\"]}\n  │     → Each granted account can deploy via create-cloud-formation-change-set\n  │     → Top-level deployment status: \"AWS::ServerlessRepo::Application\"\n  │\n  └── PUBLIC\n        → Anyone can discover and deploy (with capabilities)\n        → Requires LICENSE file in the application\n        → No application policy needed (public = open)\n        → Public apps appear in the SAR catalog search\n```\n\n**Key implication:** the application policy is the access control\nmechanism for PRIVATE cross-account sharing. For PUBLIC apps, the\npolicy is implicit (anyone). Missing the policy for a private cross-\naccount deploy is the #1 cause of \"403 Forbidden\" at deploy time.\n\n## Expert heuristic: semantic versioning for update management\n\nA baseline model treats versioning as a label. The correct heuristic\nrecognizes that SAR uses semantic versioning as an immutable,\nmonotonic identity for each published version.\n\n```text\nSemantic version rules (SAR enforces strict SemVer):\n  Format: MAJOR.MINOR.PATCH[-prerelease]\n    ├── MAJOR — breaking changes (new required parameters, removed resources)\n    ├── MINOR — backward-compatible features (new optional parameters, new resources)\n    ├── PATCH — backward-compatible fixes (bug fixes, template corrections)\n    └── -prerelease — alpha\u002Fbeta\u002Frc (e.g., 1.0.0-beta, 2.0.0-rc.1)\n\n  Immutability:\n    ├── Each version is published ONCE — cannot overwrite\n    ├── Re-publishing the same version → ConflictException\n    └── To update, publish a NEW version (e.g., 1.0.0 → 1.0.1)\n\n  Consumer update:\n    ├── Consumer pins: SemVerVersion: \"1.0.0\"\n    ├── To update: change to \"1.0.1\" and re-run create-cloud-formation-change-set\n    └── SAR keeps ALL versions — consumers can rollback by pinning older\n```\n\n**Key implication:** versioning is the ONLY update mechanism. There\nis no \"latest\" pointer — consumers must reference a specific version.\nPlan version increments as part of the release pipeline.\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting provisioning commands, verify these prerequisites. If\nany are missing, the verdict is **PREREQUISITES_MISSING**.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| SAM template (template.yaml) exists and is valid | The template defines the application resources | `sam validate --template template.yaml` |\n| Transform declared in template | Required for SAM resources to expand | Confirm `Transform: AWS::Serverless-2016-10-31` |\n| README.md exists | Required for publish (any visibility) | Check file exists and has content |\n| LICENSE exists (for public sharing) | Required for public apps; private can omit | Check file exists if sharing=public |\n| S3 bucket for packaging | sam package uploads code artifacts to S3 | `aws s3 ls s3:\u002F\u002F\u003Cbucket>` |\n| Semantic version defined | Every publish requires a unique version | Confirm version string follows SemVer |\n| AWS account ID (publisher) | The publishing account owns the application | `aws sts get-caller-identity` |\n| Consumer account IDs (for private sharing) | Application policy grants specific accounts | Confirm account IDs |\n| IAM: serverlessrepo:CreateApplication | Required to publish | Check policy includes serverlessrepo actions |\n| IAM: cloudformation:CreateChangeSet | Required to deploy | Check CloudFormation permissions |\n| Sharing decision (private vs public) | Determines policy requirements | Confirm visibility scope |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — Application structure (template.yaml + README + LICENSE)\n\nA SAR application consists of three required components (LICENSE is\nrequired only for public sharing):\n\n| Component | Required for | Purpose |\n|---|---|---|\n| template.yaml (SAM) | All publishes | Defines the serverless resources |\n| README.md | All publishes | Human-readable documentation; required by SAR API |\n| LICENSE | Public sharing only | Open-source license; private apps can omit |\n| (optional) metadata.yaml | Not required | Extra metadata; SAR API has dedicated fields |\n\n> Moved to [references\u002Fsam-transform-and-deploy.md](references\u002Fsam-transform-and-deploy.md#step-1--application-structure-minimal-templateyaml--readme).\n> Minimal template.yaml (Transform, Parameters, S3-event Lambda, Outputs) and required README.md content.\n\n## Step 2 — SAM transform pipeline\n\nThe SAM transform (AWS::Serverless-2016-10-31) is a macro that\nexpands `AWS::Serverless::*` resource types into CloudFormation-\nnative resources. This expansion happens at DEPLOY time (when the\nconsumer deploys the app), not at publish time.\n\n> Moved to [references\u002Fsam-transform-and-deploy.md](references\u002Fsam-transform-and-deploy.md#step-2--sam-transform-pipeline-expansion-table-and-dry-run).\n> SAM type expansion table, auto-generated IAM roles note, transform dry run via sam build\u002Fpackage.\n\n## Step 3 — Packaging (zip upload or S3 code URI)\n\nBefore publishing, the application's code must be packaged into an\nS3-backed artifact. The `sam package` command handles this.\n\n> Moved to [references\u002Fsam-transform-and-deploy.md](references\u002Fsam-transform-and-deploy.md#step-3--packaging-sam-package-and-s3-artifact-requirements).\n> sam package CLI, CodeUri rewrite to S3, published-template rule, S3 bucket requirements.\n\n## Step 4 — Semantic versioning\n\nEvery publish operation requires a semantic version. The version\nfollows SemVer format: `MAJOR.MINOR.PATCH[-prerelease]`.\n\n> Moved to [references\u002Fsar-publishing-and-sharing.md](references\u002Fsar-publishing-and-sharing.md#step-4--semantic-versioning-bump-table-and-publish-cli).\n> MAJOR\u002FMINOR\u002FPATCH\u002Fprerelease bump table, create-application publish and version-update CLI, unique-version rule.\n\n## Step 5 — Application sharing (private vs public)\n\nSAR applications have three sharing tiers:\n\n| Tier | Visibility | Deploy permission | LICENSE required |\n|---|---|---|---|\n| PRIVATE (default) | Only publisher account | Publisher only | No |\n| PRIVATE + policy | Discoverable by granted accounts | Granted accounts only | No |\n| PUBLIC | Everyone (catalog search) | Anyone with capabilities | YES |\n\n> Moved to [references\u002Fsar-publishing-and-sharing.md](references\u002Fsar-publishing-and-sharing.md#step-5--application-sharing-status-check-and-public-verification).\n> get-application sharing-status check and IsVerifiedAuthor public-app verification.\n\n## Step 6 — Application policy (cross-account deploy)\n\nFor PRIVATE cross-account sharing, the publisher must grant each\nconsumer account via an application policy.\n\n> Moved to [references\u002Fsar-publishing-and-sharing.md](references\u002Fsar-publishing-and-sharing.md#step-6--application-policy-cross-account-grant-cli).\n> put-application-policy \u002F get-application-policy CLI; CreateCloudFormationChangeSet action gates consumer deploy.\n\n## Step 7 — Deployment via CloudFormation change set\n\nConsumers deploy a SAR application by creating a CloudFormation change\nset from the application. This triggers the SAM transform and creates\nthe stack.\n\n> Moved to [references\u002Fsam-transform-and-deploy.md](references\u002Fsam-transform-and-deploy.md#step-7--deployment-via-cloudformation-change-set).\n> Consumer deploy CLI: create-cloud-formation-change-set, execute-change-set, sam deploy.\n\n## Step 8 — Deployment role and capabilities\n\nThe consumer's deployment role must have permissions for all resources\nthe SAM template creates. The capabilities declare what the stack is\nallowed to do.\n\n| Capability | When required |\n|---|---|\n| CAPABILITY_IAM | Template creates IAM roles\u002Fpolicies (SAM auto-generates these) |\n| CAPABILITY_NAMED_IAM | Template creates IAM resources with custom names |\n| CAPABILITY_AUTO_EXPAND | Template contains nested applications (AWS::Serverless::Application) |\n| CAPABILITY_RESOURCE_POLICY | Template modifies resource policies (e.g., S3 bucket policy) |\n\n**Critical:** most SAM templates need at least CAPABILITY_IAM because\nthe transform auto-generates IAM roles for functions with `Policies`.\nNested applications additionally require CAPABILITY_AUTO_EXPAND.\n\n## Step 9 — Nested applications\n\nA SAR application can include other SAR applications using the\n`AWS::Serverless::Application` resource type. This enables composition.\n\n> Moved to [references\u002Fsam-transform-and-deploy.md](references\u002Fsam-transform-and-deploy.md#step-9--nested-applications-parent-template).\n> Parent template with AWS::Serverless::Application (Location\u002FParameters\u002FNotificationARNs\u002FTimeoutInMinutes).\n\n**Requirements for nested applications:**\n- The nested app must be published and accessible (shared or public).\n- The consumer must have deploy permission for the nested app.\n- CAPABILITY_AUTO_EXPAND is REQUIRED at deploy time.\n- The nested app deploys as a nested CloudFormation stack.\n\n## Step 10 — Application parameters\n\nParameters defined in the SAM template are surfaced to the consumer\nat deploy time. The consumer provides values via `--parameter-overrides`.\n\n> Moved to [references\u002Fsam-transform-and-deploy.md](references\u002Fsam-transform-and-deploy.md#step-10--application-parameters-template-and-overrides).\n> Parameters YAML (BucketName, MemorySize, EnableXRay) and --parameter-overrides deploy example.\n\n## Step 11 — Author profile and labels\n\n> Moved to [references\u002Fsar-publishing-and-sharing.md](references\u002Fsar-publishing-and-sharing.md#step-11--author-profile-and-labels).\n> Author profile field table: author, home-page-url, source-code-url, labels (max 10), SpdxLicenseId, IsVerifiedAuthor.\n\n## Step 12 — Deletion and cleanup\n\nDeleting a SAR application is a two-step process: delete the deployed\nstack, then delete the application from the catalog.\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#step-12--deletion-and-cleanup).\n> Two-step teardown: delete-stack then delete-application; neither cascades to the other.\n\n## Step 13 — SAR vs AppRegistry\n\nSAR and AppRegistry serve different purposes:\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#step-13--sar-vs-appregistry).\n> SAR vs AppRegistry comparison: deploy surface vs metadata grouping, versioning, sharing.\n\n## Step 14 — Recent features\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#step-14--recent-features).\n> 2023-2026: sam build esbuild, public-app verification streamlining, nested version ranges, transform performance, cross-region deploy, CDK SAR construct.\n\n## NEVER do these things\n\n1. **NEVER publish a SAR application without a README.md.** The SAR\n   API requires README content at publish time. Without it, the\n   CreateApplication call fails.\n\n2. **NEVER publish as PUBLIC without a LICENSE file.** Public apps\n   require a license. The API rejects public publishes without one.\n   Private apps can omit the license.\n\n3. **NEVER reuse a semantic version.** Each publish must use a unique\n   version. Reusing a version results in a ConflictException. Plan\n   version increments as part of the release pipeline.\n\n4. **NEVER forget the SAM transform declaration.** The template must\n   include `Transform: AWS::Serverless-2016-10-31`. Without it,\n   `AWS::Serverless::*` types are not recognized and the deploy fails.\n\n5. **NEVER deploy a nested application without CAPABILITY_AUTO_EXPAND.**\n   Templates with `AWS::Serverless::Application` require this\n   capability. CloudFormation rejects the change set without it.\n\n6. **NEVER assume publishing makes an app deployable cross-account.**\n   For private apps, you MUST add an application policy granting each\n   consumer account. Without the policy, consumers get a 403.\n\n7. **NEVER forget that the SAM transform auto-generates IAM roles.**\n   Even if the template does not explicitly declare AWS::IAM::Role,\n   the transform creates roles for functions with `Policies`.\n   CAPABILITY_IAM is required.\n\n8. **NEVER confuse SAR with AppRegistry.** SAR deploys serverless\n   applications from SAM templates. AppRegistry groups existing\n   resources for metadata. They are different services.\n\n9. **NEVER assume deleting the CloudFormation stack deletes the SAR\n   app.** The stack and the SAR catalog entry are separate. Delete\n   both explicitly. Conversely, deleting the SAR app does not delete\n   already-deployed stacks.\n\n10. **NEVER upload the raw template.yaml (with local CodeUri) to SAR.**\n    Always run `sam package` first to replace local CodeUri with S3\n    URIs. Publishing the raw template means consumers cannot access\n    the code.\n\n## Output format\n\n```text\nSAR_APPLICATION: \u003Capplication-name> (\u003Csemantic-version>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] SAM template: \u003Ctemplate-file> (Transform: AWS::Serverless-2016-10-31)\n  [✓|✗] README.md: present | MISSING (required for publish)\n  [✓|✗] LICENSE: present | not required (private) | MISSING (required for public)\n  [✓|✗] Packaging: sam package → S3 artifact \u003Cs3-uri>\n  [✓|✗] Semantic version: \u003Cversion> (SemVer format)\n  [✓|✗] Sharing: Private | Private+Policy (\u003Caccount-ids>) | Public\n  [✓|✗] Application policy: granted (\u003Caccount-ids>) | not needed (private) | public (implicit)\n  [✓|✗] Capabilities: CAPABILITY_IAM [CAPABILITY_NAMED_IAM] [CAPABILITY_AUTO_EXPAND]\n  [✓|✗] Parameters: \u003Cparam-list> surfaced at deploy time\n  [✓|✗] Nested applications: none | \u003Cchild-app-ids>\n  [✓|✗] Author profile: \u003Cauthor>, labels: \u003Clabel-list>\n  [✓|✗] Application ARN: arn:aws:serverlessrepo:\u003Cregion>:\u003Cacct>:apps\u002F\u003Cname>\nVERIFICATION_COMMANDS:\n  aws serverlessrepo get-application --application-id \u003Carn> --region \u003Cregion>\n  aws cloudformation describe-stacks --stack-name \u003Cstack-name> --region \u003Cregion>\n```\n\n### Worked example — private app with SAM deploy and cross-account policy\n\n```text\nSAR_APPLICATION: s3-file-processor (1.0.0)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] SAM template: template.yaml (Transform: AWS::Serverless-2016-10-31)\n  [✓] README.md: present (S3 File Processor documentation)\n  [✓] LICENSE: present (Apache-2.0)\n  [✓] Packaging: sam package → s3:\u002F\u002Fmy-artifacts\u002Fs3-processor-1.0.0.zip\n  [✓] Semantic version: 1.0.0\n  [✓] Sharing: Private+Policy (granted to 999999999999)\n  [✓] Application policy: PutApplicationPolicy → Principal: 999999999999, Action: CreateCloudFormationChangeSet\n  [✓] Capabilities: CAPABILITY_IAM (transform auto-generates Lambda execution role)\n  [✓] Parameters: BucketName (String, required), MemorySize (Number, default 256)\n  [✓] Nested applications: none\n  [✓] Author profile: Jacky Chan, labels: s3, lambda, event-driven\n  [✓] Application ARN: arn:aws:serverlessrepo:us-east-1:123456789012:apps\u002Fs3-file-processor\nVERIFICATION_COMMANDS:\n  aws serverlessrepo get-application --application-id arn:aws:serverlessrepo:us-east-1:123456789012:apps\u002Fs3-file-processor --region us-east-1\n  aws serverlessrepo get-application-policy --application-id arn:aws:serverlessrepo:us-east-1:123456789012:apps\u002Fs3-file-processor --region us-east-1\n```\n\n## Error handling\n\n> Moved to [references\u002Ferror-handling.md](references\u002Ferror-handling.md#-createapplication-fails-with).\n> Six failure modes: README required, ConflictException, 403 policy gap, missing CAPABILITY_AUTO_EXPAND, transform failed, artifact upload.\n\n## References (load on demand)\n\n- [advanced-patterns](references\u002Fadvanced-patterns.md) — Mindset misconceptions, cross-dependency gotchas, deletion\u002Fcleanup, SAR vs AppRegistry, recent AWS features\n- [error-handling](references\u002Ferror-handling.md) — Six API failure modes: missing README, ConflictException, 403 policy gap, AUTO_EXPAND, transform failure, artifact upload\n- [sam-transform-and-deploy](references\u002Fsam-transform-and-deploy.md) — Transform\u002Fdeploy deep reference plus moved Step 1\u002F2\u002F3\u002F7\u002F9\u002F10 template, packaging, and deploy CLI\n- [sar-publishing-and-sharing](references\u002Fsar-publishing-and-sharing.md) — Publishing\u002Fsharing deep reference plus moved Step 4\u002F5\u002F6\u002F11 versioning, sharing, policy, and author-profile CLI\n\n## Domain\n\nAWS CloudOps \u002F AWS Serverless Application Repository Application\nPublishing & Deployment.\n\n## AWS documentation\n\n- **Serverless Application Repository** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fserverlessrepo\u002Flatest\u002Fdevguide\u002Fwhat-is-serverlessrepo.html\n- **Publishing applications** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fserverlessrepo\u002Flatest\u002Fdevguide\u002Fserverlessrepo-publishing-applications.html\n- **Sharing applications** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fserverlessrepo\u002Flatest\u002Fdevguide\u002Fserverlessrepo-sharing-applications.html\n- **Deploying applications** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fserverlessrepo\u002Flatest\u002Fdevguide\u002Fserverlessrepo-consuming-applications.html\n- **SAM transform** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fserverless-application-model\u002Flatest\u002Fdeveloperguide\u002Ftransform.html\n- **AWS::Serverless::Application** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fserverless-application-model\u002Flatest\u002Fdeveloperguide\u002Fsam-resource-application.html\n- **Application policies** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fserverlessrepo\u002Flatest\u002Fdevguide\u002Fserverlessrepo-how-to-use.html\n- **SAM CLI reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fserverless-application-model\u002Flatest\u002Fdeveloperguide\u002Fserverless-sam-reference.html\n- **Semantic versioning** — https:\u002F\u002Fsemver.org\u002F\n","# Serverless Application Repository Deployer\n\nAn AWS CloudOps agent skill that provisions AWS Serverless Application\nRepository (SAR) applications with correct defaults. The skill walks\nthe operator through the SAM template structure, packaging (zip upload\nor S3), semantic versioning, the application sharing model (private vs\naccount-grant vs public), the application policy that gates cross-\naccount deploy, the SAM transform pipeline (transform happens BEFORE\nCloudFormation), nested application composition, the deployment role\nand capabilities, and application deletion\u002Fcleanup. It captures the\napplication definition decisions, explains why each default matters,\nand emits a READY_TO_DEPLOY checklist with copy-pasteable verification\ncommands.\n\n## Activation keywords\n\npublish serverless application, sar publish, serverless application\nrepository, sam package, sam deploy, sar application policy, cross-\naccount sar deploy, nested sar application, semantic version sar.\n\n## STRICT output contract\n\nWhen this skill is invoked with a SAR-provisioning request (publish\nan application, share an application, deploy someone else's\napplication, version an update, compose nested applications, or a\npartial configuration), the agent MUST respond with the\nREADY_TO_DEPLOY checklist defined in the \"Output format\" section\nusing the literal all-caps labels `SAR_APPLICATION:`, `VERDICT:`,\n`CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do NOT preface the\nchecklist with prose, headings, or disclaimers — emit the block as\nthe first lines of the response. This contract is what assertion-\nbased evals and downstream provisioning pipelines rely on; deviating\nfrom the literal labels breaks automation silently.\n\nIf any prerequisite is missing, the verdict is `PREREQUISITES_MISSING`\nwith a specific gap citation in the checklist (marked `[✗]`), and\n`READY_TO_DEPLOY` MUST NOT also appear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before provisioning |\n| Step 1 — Application structure (template.yaml + README + LICENSE) | Core app anatomy |\n| Step 2 — SAM transform pipeline | Transform happens before CFN |\n| Step 3 — Packaging (zip upload or S3 code URI) | Artifact storage |\n| Step 4 — Semantic versioning | Every publish needs a version |\n| Step 5 — Application sharing (private vs public) | Visibility model |\n| Step 6 — Application policy (cross-account deploy) | Who can deploy |\n| Step 7 — Deployment via CloudFormation change set | Deploy mechanism |\n| Step 8 — Deployment role and capabilities | IAM surface |\n| Step 9 — Nested applications | Composition |\n| Step 10 — Application parameters | Surfaced at deploy time |\n| Step 11 — Author profile and labels | Published metadata |\n| Step 12 — Deletion and cleanup | Teardown |\n| Step 13 — SAR vs AppRegistry | Avoid confusion |\n| Step 14 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Fsam-transform-and-deploy.md | Transform + deploy detail |\n| references\u002Fsar-publishing-and-sharing.md | Publishing + sharing detail |\n\n## Mindset\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#mindset).\n> Three provisioning-time misconceptions: publish vs deploy, cross-account 403 without an application policy, mandatory immutable SemVer.\n\n## Configuration dependency graph (novel heuristic)\n\nSAR application configurations are NOT independent. The SAM template\nmust exist before packaging. Packaging must complete before publish.\nPublish must complete before sharing. The application policy must\nexist before cross-account deploy. Use this graph to sequence\nprovisioning.\n\n| Configuration | Hard dependencies (API error without) | Silent failure \u002F immutability | Enables downstream |\n|---|---|---|---|\n| SAM template (template.yaml) | Valid YAML; Transform declared; resources under 200 | Template with unresolved `CodeUri` uploads raw path, not code | the application definition |\n| README.md | Required at publish time (CreateApplication \u002F UpdateApplication) | Empty README is accepted but app cannot be shared publicly without content | public sharing eligibility |\n| LICENSE | Required for PUBLIC sharing only; private apps can omit | App without LICENSE cannot be made public (API rejects) | public sharing |\n| Packaging (sam package) | S3 bucket exists; IAM s3:PutObject | Forgetting to package → CodeUri points to local path → deploy fails | S3-backed code artifact |\n| Semantic version | Required at every publish; must be unique per application | Reusing a version → API rejects with ConflictException; no overwrite | update management |\n| Publish (create-application) | Template packaged; README present; version set | Publishing without an application policy → only the publisher account can deploy | catalog entry |\n| Application policy | Application published; consumer AWS account ID(s) known | Policy omitted → cross-account deploy fails with 403 | cross-account deployment |\n| Deployment (create-cloud-formation-change-set) | Application published; consumer has permission; capabilities match | Missing CAPABILITY_AUTO_EXPAND → nested application deploy fails | running stack |\n| Nested application | Parent template uses AWS::Serverless::Application; child app published and accessible | Child app not shared → parent deploy fails at expand time | composition |\n\n**The application-policy-gates-cross-account row is the one a\nbaseline model misses.** Publishing the app is necessary but NOT\nsufficient for cross-account use. The policy must explicitly grant\neach consumer account (for private) or be set to public (for public\napps). The SAM-transform-before-CFN row is the second commonly\nmisunderstood step.\n\n**Cross-dependency gotchas:**\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#configuration-dependency-graph--cross-dependency-gotchas).\n> Five gotchas: deploy-time transform, CAPABILITY_AUTO_EXPAND for nested apps, private sharing tiers, stack vs SAR deletion, version embedded in the ARN.\n\n## Expert heuristic: the SAM transform pipeline\n\nA baseline model says \"upload the template and deploy.\" The correct\nheuristic recognizes that SAR stores the RAW SAM template and the\ntransform happens at DEPLOY time on the CONSUMER side.\n\n```text\nPublisher flow:\n  1. Write template.yaml (Transform: AWS::Serverless-2016-10-31)\n  2. sam package → uploads code to S3, produces packaged.yaml\n  3. serverlessrepo create-application → stores SAM template + metadata\n  4. (optional) serverlessrepo put-application-policy → grants consumers\n\nConsumer flow:\n  1. serverlessrepo create-cloud-formation-change-set → SAR fetches template\n  2. SAM transform runs → AWS::Serverless::Function → AWS::Lambda::Function\n  3. CloudFormation receives the EXPANDED template\n  4. CloudFormation creates\u002Fupdates the stack with CAPABILITY_IAM\n```\n\n**Key implication:** the publisher's SAM template must be self-\ncontained and valid for transformation. Any intrinsic function refs\nmust resolve within the consumer's account at deploy time. The\npublisher cannot pre-transform — the transform is inherently a deploy-\ntime operation because it may generate account-specific resources\n(IAM roles, API Gateway stage names, etc.).\n\n## Expert heuristic: application policy gates cross-account deploy\n\nA baseline model publishes the app and assumes it is deployable\neverywhere. The correct heuristic recognizes three sharing tiers,\neach with a different deploy permission model.\n\n```text\nSharing tier decision:\n  ├── PRIVATE (default)\n  │     → Only the publisher account can deploy\n  │     → No application policy needed\n  │     → ARN: arn:aws:serverlessrepo:\u003Cregion>:\u003Cacct>:apps\u002F\u003Capp>\n  │\n  ├── PRIVATE + APPLICATION POLICY (account-grant)\n  │     → Publisher grants specific AWS account IDs\n  │     → put-application-policy with Principal: {AWS: [\"arn:...:\u003Cacct>\"]}\n  │     → Each granted account can deploy via create-cloud-formation-change-set\n  │     → Top-level deployment status: \"AWS::ServerlessRepo::Application\"\n  │\n  └── PUBLIC\n        → Anyone can discover and deploy (with capabilities)\n        → Requires LICENSE file in the application\n        → No application policy needed (public = open)\n        → Public apps appear in the SAR catalog search\n```\n\n**Key implication:** the application policy is the access control\nmechanism for PRIVATE cross-account sharing. For PUBLIC apps, the\npolicy is implicit (anyone). Missing the policy for a private cross-\naccount deploy is the #1 cause of \"403 Forbidden\" at deploy time.\n\n## Expert heuristic: semantic versioning for update management\n\nA baseline model treats versioning as a label. The correct heuristic\nrecognizes that SAR uses semantic versioning as an immutable,\nmonotonic identity for each published version.\n\n```text\nSemantic version rules (SAR enforces strict SemVer):\n  Format: MAJOR.MINOR.PATCH[-prerelease]\n    ├── MAJOR — breaking changes (new required parameters, removed resources)\n    ├── MINOR — backward-compatible features (new optional parameters, new resources)\n    ├── PATCH — backward-compatible fixes (bug fixes, template corrections)\n    └── -prerelease — alpha\u002Fbeta\u002Frc (e.g., 1.0.0-beta, 2.0.0-rc.1)\n\n  Immutability:\n    ├── Each version is published ONCE — cannot overwrite\n    ├── Re-publishing the same version → ConflictException\n    └── To update, publish a NEW version (e.g., 1.0.0 → 1.0.1)\n\n  Consumer update:\n    ├── Consumer pins: SemVerVersion: \"1.0.0\"\n    ├── To update: change to \"1.0.1\" and re-run create-cloud-formation-change-set\n    └── SAR keeps ALL versions — consumers can rollback by pinning older\n```\n\n**Key implication:** versioning is the ONLY update mechanism. There\nis no \"latest\" pointer — consumers must reference a specific version.\nPlan version increments as part of the release pipeline.\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting provisioning commands, verify these prerequisites. If\nany are missing, the verdict is **PREREQUISITES_MISSING**.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| SAM template (template.yaml) exists and is valid | The template defines the application resources | `sam validate --template template.yaml` |\n| Transform declared in template | Required for SAM resources to expand | Confirm `Transform: AWS::Serverless-2016-10-31` |\n| README.md exists | Required for publish (any visibility) | Check file exists and has content |\n| LICENSE exists (for public sharing) | Required for public apps; private can omit | Check file exists if sharing=public |\n| S3 bucket for packaging | sam package uploads code artifacts to S3 | `aws s3 ls s3:\u002F\u002F\u003Cbucket>` |\n| Semantic version defined | Every publish requires a unique version | Confirm version string follows SemVer |\n| AWS account ID (publisher) | The publishing account owns the application | `aws sts get-caller-identity` |\n| Consumer account IDs (for private sharing) | Application policy grants specific accounts | Confirm account IDs |\n| IAM: serverlessrepo:CreateApplication | Required to publish | Check policy includes serverlessrepo actions |\n| IAM: cloudformation:CreateChangeSet | Required to deploy | Check CloudFormation permissions |\n| Sharing decision (private vs public) | Determines policy requirements | Confirm visibility scope |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — Application structure (template.yaml + README + LICENSE)\n\nA SAR application consists of three required components (LICENSE is\nrequired only for public sharing):\n\n| Component | Required for | Purpose |\n|---|---|---|\n| template.yaml (SAM) | All publishes | Defines the serverless resources |\n| README.md | All publishes | Human-readable documentation; required by SAR API |\n| LICENSE | Public sharing only | Open-source license; private apps can omit |\n| (optional) metadata.yaml | Not required | Extra metadata; SAR API has dedicated fields |\n\n> Moved to [references\u002Fsam-transform-and-deploy.md](references\u002Fsam-transform-and-deploy.md#step-1--application-structure-minimal-templateyaml--readme).\n> Minimal template.yaml (Transform, Parameters, S3-event Lambda, Outputs) and required README.md content.\n\n## Step 2 — SAM transform pipeline\n\nThe SAM transform (AWS::Serverless-2016-10-31) is a macro that\nexpands `AWS::Serverless::*` resource types into CloudFormation-\nnative resources. This expansion happens at DEPLOY time (when the\nconsumer deploys the app), not at publish time.\n\n> Moved to [references\u002Fsam-transform-and-deploy.md](references\u002Fsam-transform-and-deploy.md#step-2--sam-transform-pipeline-expansion-table-and-dry-run).\n> SAM type expansion table, auto-generated IAM roles note, transform dry run via sam build\u002Fpackage.\n\n## Step 3 — Packaging (zip upload or S3 code URI)\n\nBefore publishing, the application's code must be packaged into an\nS3-backed artifact. The `sam package` command handles this.\n\n> Moved to [references\u002Fsam-transform-and-deploy.md](references\u002Fsam-transform-and-deploy.md#step-3--packaging-sam-package-and-s3-artifact-requirements).\n> sam package CLI, CodeUri rewrite to S3, published-template rule, S3 bucket requirements.\n\n## Step 4 — Semantic versioning\n\nEvery publish operation requires a semantic version. The version\nfollows SemVer format: `MAJOR.MINOR.PATCH[-prerelease]`.\n\n> Moved to [references\u002Fsar-publishing-and-sharing.md](references\u002Fsar-publishing-and-sharing.md#step-4--semantic-versioning-bump-table-and-publish-cli).\n> MAJOR\u002FMINOR\u002FPATCH\u002Fprerelease bump table, create-application publish and version-update CLI, unique-version rule.\n\n## Step 5 — Application sharing (private vs public)\n\nSAR applications have three sharing tiers:\n\n| Tier | Visibility | Deploy permission | LICENSE required |\n|---|---|---|---|\n| PRIVATE (default) | Only publisher account | Publisher only | No |\n| PRIVATE + policy | Discoverable by granted accounts | Granted accounts only | No |\n| PUBLIC | Everyone (catalog search) | Anyone with capabilities | YES |\n\n> Moved to [references\u002Fsar-publishing-and-sharing.md](references\u002Fsar-publishing-and-sharing.md#step-5--application-sharing-status-check-and-public-verification).\n> get-application sharing-status check and IsVerifiedAuthor public-app verification.\n\n## Step 6 — Application policy (cross-account deploy)\n\nFor PRIVATE cross-account sharing, the publisher must grant each\nconsumer account via an application policy.\n\n> Moved to [references\u002Fsar-publishing-and-sharing.md](references\u002Fsar-publishing-and-sharing.md#step-6--application-policy-cross-account-grant-cli).\n> put-application-policy \u002F get-application-policy CLI; CreateCloudFormationChangeSet action gates consumer deploy.\n\n## Step 7 — Deployment via CloudFormation change set\n\nConsumers deploy a SAR application by creating a CloudFormation change\nset from the application. This triggers the SAM transform and creates\nthe stack.\n\n> Moved to [references\u002Fsam-transform-and-deploy.md](references\u002Fsam-transform-and-deploy.md#step-7--deployment-via-cloudformation-change-set).\n> Consumer deploy CLI: create-cloud-formation-change-set, execute-change-set, sam deploy.\n\n## Step 8 — Deployment role and capabilities\n\nThe consumer's deployment role must have permissions for all resources\nthe SAM template creates. The capabilities declare what the stack is\nallowed to do.\n\n| Capability | When required |\n|---|---|\n| CAPABILITY_IAM | Template creates IAM roles\u002Fpolicies (SAM auto-generates these) |\n| CAPABILITY_NAMED_IAM | Template creates IAM resources with custom names |\n| CAPABILITY_AUTO_EXPAND | Template contains nested applications (AWS::Serverless::Application) |\n| CAPABILITY_RESOURCE_POLICY | Template modifies resource policies (e.g., S3 bucket policy) |\n\n**Critical:** most SAM templates need at least CAPABILITY_IAM because\nthe transform auto-generates IAM roles for functions with `Policies`.\nNested applications additionally require CAPABILITY_AUTO_EXPAND.\n\n## Step 9 — Nested applications\n\nA SAR application can include other SAR applications using the\n`AWS::Serverless::Application` resource type. This enables composition.\n\n> Moved to [references\u002Fsam-transform-and-deploy.md](references\u002Fsam-transform-and-deploy.md#step-9--nested-applications-parent-template).\n> Parent template with AWS::Serverless::Application (Location\u002FParameters\u002FNotificationARNs\u002FTimeoutInMinutes).\n\n**Requirements for nested applications:**\n- The nested app must be published and accessible (shared or public).\n- The consumer must have deploy permission for the nested app.\n- CAPABILITY_AUTO_EXPAND is REQUIRED at deploy time.\n- The nested app deploys as a nested CloudFormation stack.\n\n## Step 10 — Application parameters\n\nParameters defined in the SAM template are surfaced to the consumer\nat deploy time. The consumer provides values via `--parameter-overrides`.\n\n> Moved to [references\u002Fsam-transform-and-deploy.md](references\u002Fsam-transform-and-deploy.md#step-10--application-parameters-template-and-overrides).\n> Parameters YAML (BucketName, MemorySize, EnableXRay) and --parameter-overrides deploy example.\n\n## Step 11 — Author profile and labels\n\n> Moved to [references\u002Fsar-publishing-and-sharing.md](references\u002Fsar-publishing-and-sharing.md#step-11--author-profile-and-labels).\n> Author profile field table: author, home-page-url, source-code-url, labels (max 10), SpdxLicenseId, IsVerifiedAuthor.\n\n## Step 12 — Deletion and cleanup\n\nDeleting a SAR application is a two-step process: delete the deployed\nstack, then delete the application from the catalog.\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#step-12--deletion-and-cleanup).\n> Two-step teardown: delete-stack then delete-application; neither cascades to the other.\n\n## Step 13 — SAR vs AppRegistry\n\nSAR and AppRegistry serve different purposes:\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#step-13--sar-vs-appregistry).\n> SAR vs AppRegistry comparison: deploy surface vs metadata grouping, versioning, sharing.\n\n## Step 14 — Recent features\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#step-14--recent-features).\n> 2023-2026: sam build esbuild, public-app verification streamlining, nested version ranges, transform performance, cross-region deploy, CDK SAR construct.\n\n## NEVER do these things\n\n1. **NEVER publish a SAR application without a README.md.** The SAR\n   API requires README content at publish time. Without it, the\n   CreateApplication call fails.\n\n2. **NEVER publish as PUBLIC without a LICENSE file.** Public apps\n   require a license. The API rejects public publishes without one.\n   Private apps can omit the license.\n\n3. **NEVER reuse a semantic version.** Each publish must use a unique\n   version. Reusing a version results in a ConflictException. Plan\n   version increments as part of the release pipeline.\n\n4. **NEVER forget the SAM transform declaration.** The template must\n   include `Transform: AWS::Serverless-2016-10-31`. Without it,\n   `AWS::Serverless::*` types are not recognized and the deploy fails.\n\n5. **NEVER deploy a nested application without CAPABILITY_AUTO_EXPAND.**\n   Templates with `AWS::Serverless::Application` require this\n   capability. CloudFormation rejects the change set without it.\n\n6. **NEVER assume publishing makes an app deployable cross-account.**\n   For private apps, you MUST add an application policy granting each\n   consumer account. Without the policy, consumers get a 403.\n\n7. **NEVER forget that the SAM transform auto-generates IAM roles.**\n   Even if the template does not explicitly declare AWS::IAM::Role,\n   the transform creates roles for functions with `Policies`.\n   CAPABILITY_IAM is required.\n\n8. **NEVER confuse SAR with AppRegistry.** SAR deploys serverless\n   applications from SAM templates. AppRegistry groups existing\n   resources for metadata. They are different services.\n\n9. **NEVER assume deleting the CloudFormation stack deletes the SAR\n   app.** The stack and the SAR catalog entry are separate. Delete\n   both explicitly. Conversely, deleting the SAR app does not delete\n   already-deployed stacks.\n\n10. **NEVER upload the raw template.yaml (with local CodeUri) to SAR.**\n    Always run `sam package` first to replace local CodeUri with S3\n    URIs. Publishing the raw template means consumers cannot access\n    the code.\n\n## Output format\n\n```text\nSAR_APPLICATION: \u003Capplication-name> (\u003Csemantic-version>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] SAM template: \u003Ctemplate-file> (Transform: AWS::Serverless-2016-10-31)\n  [✓|✗] README.md: present | MISSING (required for publish)\n  [✓|✗] LICENSE: present | not required (private) | MISSING (required for public)\n  [✓|✗] Packaging: sam package → S3 artifact \u003Cs3-uri>\n  [✓|✗] Semantic version: \u003Cversion> (SemVer format)\n  [✓|✗] Sharing: Private | Private+Policy (\u003Caccount-ids>) | Public\n  [✓|✗] Application policy: granted (\u003Caccount-ids>) | not needed (private) | public (implicit)\n  [✓|✗] Capabilities: CAPABILITY_IAM [CAPABILITY_NAMED_IAM] [CAPABILITY_AUTO_EXPAND]\n  [✓|✗] Parameters: \u003Cparam-list> surfaced at deploy time\n  [✓|✗] Nested applications: none | \u003Cchild-app-ids>\n  [✓|✗] Author profile: \u003Cauthor>, labels: \u003Clabel-list>\n  [✓|✗] Application ARN: arn:aws:serverlessrepo:\u003Cregion>:\u003Cacct>:apps\u002F\u003Cname>\nVERIFICATION_COMMANDS:\n  aws serverlessrepo get-application --application-id \u003Carn> --region \u003Cregion>\n  aws cloudformation describe-stacks --stack-name \u003Cstack-name> --region \u003Cregion>\n```\n\n### Worked example — private app with SAM deploy and cross-account policy\n\n```text\nSAR_APPLICATION: s3-file-processor (1.0.0)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] SAM template: template.yaml (Transform: AWS::Serverless-2016-10-31)\n  [✓] README.md: present (S3 File Processor documentation)\n  [✓] LICENSE: present (Apache-2.0)\n  [✓] Packaging: sam package → s3:\u002F\u002Fmy-artifacts\u002Fs3-processor-1.0.0.zip\n  [✓] Semantic version: 1.0.0\n  [✓] Sharing: Private+Policy (granted to 999999999999)\n  [✓] Application policy: PutApplicationPolicy → Principal: 999999999999, Action: CreateCloudFormationChangeSet\n  [✓] Capabilities: CAPABILITY_IAM (transform auto-generates Lambda execution role)\n  [✓] Parameters: BucketName (String, required), MemorySize (Number, default 256)\n  [✓] Nested applications: none\n  [✓] Author profile: Jacky Chan, labels: s3, lambda, event-driven\n  [✓] Application ARN: arn:aws:serverlessrepo:us-east-1:123456789012:apps\u002Fs3-file-processor\nVERIFICATION_COMMANDS:\n  aws serverlessrepo get-application --application-id arn:aws:serverlessrepo:us-east-1:123456789012:apps\u002Fs3-file-processor --region us-east-1\n  aws serverlessrepo get-application-policy --application-id arn:aws:serverlessrepo:us-east-1:123456789012:apps\u002Fs3-file-processor --region us-east-1\n```\n\n## Error handling\n\n> Moved to [references\u002Ferror-handling.md](references\u002Ferror-handling.md#-createapplication-fails-with).\n> Six failure modes: README required, ConflictException, 403 policy gap, missing CAPABILITY_AUTO_EXPAND, transform failed, artifact upload.\n\n## References (load on demand)\n\n- [advanced-patterns](references\u002Fadvanced-patterns.md) — Mindset misconceptions, cross-dependency gotchas, deletion\u002Fcleanup, SAR vs AppRegistry, recent AWS features\n- [error-handling](references\u002Ferror-handling.md) — Six API failure modes: missing README, ConflictException, 403 policy gap, AUTO_EXPAND, transform failure, artifact upload\n- [sam-transform-and-deploy](references\u002Fsam-transform-and-deploy.md) — Transform\u002Fdeploy deep reference plus moved Step 1\u002F2\u002F3\u002F7\u002F9\u002F10 template, packaging, and deploy CLI\n- [sar-publishing-and-sharing](references\u002Fsar-publishing-and-sharing.md) — Publishing\u002Fsharing deep reference plus moved Step 4\u002F5\u002F6\u002F11 versioning, sharing, policy, and author-profile CLI\n\n## Domain\n\nAWS CloudOps \u002F AWS Serverless Application Repository Application\nPublishing & Deployment.\n\n## AWS documentation\n\n- **Serverless Application Repository** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fserverlessrepo\u002Flatest\u002Fdevguide\u002Fwhat-is-serverlessrepo.html\n- **Publishing applications** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fserverlessrepo\u002Flatest\u002Fdevguide\u002Fserverlessrepo-publishing-applications.html\n- **Sharing applications** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fserverlessrepo\u002Flatest\u002Fdevguide\u002Fserverlessrepo-sharing-applications.html\n- **Deploying applications** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fserverlessrepo\u002Flatest\u002Fdevguide\u002Fserverlessrepo-consuming-applications.html\n- **SAM transform** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fserverless-application-model\u002Flatest\u002Fdeveloperguide\u002Ftransform.html\n- **AWS::Serverless::Application** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fserverless-application-model\u002Flatest\u002Fdeveloperguide\u002Fsam-resource-application.html\n- **Application policies** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fserverlessrepo\u002Flatest\u002Fdevguide\u002Fserverlessrepo-how-to-use.html\n- **SAM CLI reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fserverless-application-model\u002Flatest\u002Fdeveloperguide\u002Fserverless-sam-reference.html\n- **Semantic versioning** — https:\u002F\u002Fsemver.org\u002F\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":41},{"tags":25,"phase":26,"author":27,"domain":28,"family":29,"version":30,"keywords":31,"task_type":32,"complexity":33,"entry_point":34,"skill_class":35,"when_to_use":36,"dependencies":37,"requires_llm":38,"verdict_shape":39,"lifecycle_status":40,"supports_pipeline":38},"aws, serverless, sar, sam, cloudformation, cloudops, deploy, devtools, semantic-versioning, application-policy, nested-application, cross-account","1","Jacky Chan — AWS Community Builder","aws-cloudops","DevTools","0.1.0","aws, serverless application repository, sar, sam, sam template, sam deploy, sam package, cloudformation, semantic versioning, application policy, nested application, cross-account deploy, application sharing, public application, private application, appregistry, deployment role, lambda, cloudops, deploy, devtools","deploy","high","false","capability","Invoke when the user wants to publish a serverless application to the Serverless Application Repository, share an application privately or publicly, deploy an application from SAR via CloudFormation, version an application update using semantic versioning, compose nested SAR applications, configure an application policy for cross-account deployment, or understand the SAM transform pipeline. Do NOT invoke for AWS Service Catalog product registration (different catalog), CDK app publishing (CDK has its own publishing path), or AppRegistry metadata grouping (AppRegistry is metadata-only, not a deploy surface).","aws-orchestrator","true","READY_TO_DEPLOY | PREREQUISITES_MISSING","active","Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS SAM CLI (sam package, sam deploy) or AWS CLI v2 with serverlessrepo create-application \u002F put-application-policy \u002F create-cloud-formation-change-set. Requires an S3 bucket for artifact storage and IAM permissions for cloudformation:CreateChangeSet, serverlessrepo:CreateApplication, and the transforms the SAM template declares.","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Fserverlessrepo-application-deployer",0,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills","https:\u002F\u002Fgithub.com\u002Fjhkchan","CTO & Co-Founder @Beever-AI  & @votee. CAISP. AWS Community Builder. Organizer@GDGCloudHK. MongoDB Champion. Technopreneur + Infornographer.","2026-09-24 08:54:10",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add jhkchan\u002Faws-agent-skills --skill serverlessrepo-application-deployer",{"tool":56,"command":57},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill serverlessrepo-application-deployer",{"tool":59,"command":60},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill serverlessrepo-application-deployer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fserverlessrepo-application-deployer\u002FSKILL.md",true,[64,70,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",6242,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fserverlessrepo-application-deployer\u002Feval\u002Ftest-cases.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fbaselines\u002Fmissing-readme-license.md",626,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fserverlessrepo-application-deployer\u002Fevals\u002Fbaselines\u002Fmissing-readme-license.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"evals\u002Fbaselines\u002Fnested-applications-composition.md",946,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fserverlessrepo-application-deployer\u002Fevals\u002Fbaselines\u002Fnested-applications-composition.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"evals\u002Fbaselines\u002Fprivate-app-sam-deploy.md",757,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fserverlessrepo-application-deployer\u002Fevals\u002Fbaselines\u002Fprivate-app-sam-deploy.md",{"path":83,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":84,"sourceHtmlUrl":85},"evals\u002Fbaselines\u002Fpublic-app-cross-account-policy.md",730,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fserverlessrepo-application-deployer\u002Fevals\u002Fbaselines\u002Fpublic-app-cross-account-policy.md",{"path":87,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":88,"sourceHtmlUrl":89},"evals\u002Fbaselines\u002Fsemantic-version-update.md",680,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fserverlessrepo-application-deployer\u002Fevals\u002Fbaselines\u002Fsemantic-version-update.md",{"path":91,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":92,"sourceHtmlUrl":93},"evals\u002Feval_config.yaml",1828,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fserverlessrepo-application-deployer\u002Fevals\u002Feval_config.yaml",{"path":95,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":96,"sourceHtmlUrl":97},"evals\u002Fevals.json",10757,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fserverlessrepo-application-deployer\u002Fevals\u002Fevals.json",{"path":99,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":100,"sourceHtmlUrl":101},"evals\u002Fprompts\u002Fmissing-readme-license.md",377,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fserverlessrepo-application-deployer\u002Fevals\u002Fprompts\u002Fmissing-readme-license.md",{"path":103,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":104,"sourceHtmlUrl":105},"evals\u002Fprompts\u002Fnested-applications-composition.md",647,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fserverlessrepo-application-deployer\u002Fevals\u002Fprompts\u002Fnested-applications-composition.md",{"path":107,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":108,"sourceHtmlUrl":109},"evals\u002Fprompts\u002Fprivate-app-sam-deploy.md",733,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fserverlessrepo-application-deployer\u002Fevals\u002Fprompts\u002Fprivate-app-sam-deploy.md",{"path":111,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":112,"sourceHtmlUrl":113},"evals\u002Fprompts\u002Fpublic-app-cross-account-policy.md",618,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fserverlessrepo-application-deployer\u002Fevals\u002Fprompts\u002Fpublic-app-cross-account-policy.md",{"path":115,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":116,"sourceHtmlUrl":117},"evals\u002Fprompts\u002Fsemantic-version-update.md",496,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fserverlessrepo-application-deployer\u002Fevals\u002Fprompts\u002Fsemantic-version-update.md",{"path":119,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":120,"sourceHtmlUrl":121},"examples\u002FREADME.md",6559,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fserverlessrepo-application-deployer\u002Fexamples\u002FREADME.md",{"path":123,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fadvanced-patterns.md",5805,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fserverlessrepo-application-deployer\u002Freferences\u002Fadvanced-patterns.md",{"path":127,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Ferror-handling.md",1501,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fserverlessrepo-application-deployer\u002Freferences\u002Ferror-handling.md",{"path":131,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Fsam-transform-and-deploy.md",14866,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fserverlessrepo-application-deployer\u002Freferences\u002Fsam-transform-and-deploy.md",{"path":135,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Fsar-publishing-and-sharing.md",13555,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fserverlessrepo-application-deployer\u002Freferences\u002Fsar-publishing-and-sharing.md",{"path":139,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":140,"sourceHtmlUrl":141},"skill.usf.yaml",4645,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fserverlessrepo-application-deployer\u002Fskill.usf.yaml",[143,150,157,164,171,178],{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":19},"01M7ADVD60X4PCAPKSE58P9NDC","xray-tracing-deployer","Deploys AWS X-Ray distributed tracing with production-grade configuration: X-Ray daemon deployment (EC2 systemd, ECS sidecar, EKS DaemonSet, Lambda built-in), SDK instrumentation (Java, Python, Node.js, Go, .NET) with annotations and metadata, sampling rules (default reservoir + rate vs custom rules with URL \u002F method \u002F service-name predicates), service map generation, trace query and retrieval, groups and insights, CloudWatch ServiceLens integration, IAM permissions (PutTraceSegments, GetSamplingRules), and latest features (Lambda Powertools tracing, OpenTelemetry \u002F ADOT Collector support, W3C trace context). Emits a READY_TO_DEPLOY checklist with every configuration item verified. Use when enabling X-Ray on a new application, adding tracing to ECS \u002F EKS \u002F Lambda, validating a sampling configuration, or generating daemon deployment CLI and IaC templates. Triggers: X-Ray, distributed tracing, X-Ray daemon, sampling rules, service map, X-Ray SDK, OpenTelemetry, ADOT, Lambda Powertools, CloudWatch ServiceLens.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002FSKILL.md",[],[],{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":19},"01M7ADTVJ7DCBM9CB1FY51GH7J","wellarchitected-workload-auditor","Audits AWS Well-Architected Tool workloads for review staleness, per-pillar high-risk issue counts, milestone tracking gaps, and remediation plan completeness. Emits a deterministic verdict (STALE_REVIEW | HIGH_RISK | CONFIG_GAP | OK) per workload with per-pillar risk breakdown, milestone trend analysis, and specific remediation. Use when reviewing Well-Architected workloads, checking WA review freshness, auditing high-risk issues per pillar, validating milestone coverage, or tracking remediation plans.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-workload-auditor\u002FSKILL.md",[],[],{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":19},"01M7ADT59G6FTTNZYHT2QRPNNP","wellarchitected-review-operator","Operates AWS Well-Architected Tool reviews end-to-end — creates workloads, runs pillar reviews (operational excellence, security, reliability, performance, cost optimization, sustainability, Prosperity), answers questions with risk-tier rationale, generates reports and improvement plans, creates milestones, and integrates with Trusted Advisor and Well-Architected Labs. Runs deterministic pre-checks (workload existence, lens availability, pillar coverage), emits the exact update-answer \u002F get-consolidated-report CLI behind a CONFIRM gate, and verifies risk-tier transitions. Emits READY | BLOCKED | COMPLETED. Use when creating a workload, answering pillar questions, generating an improvement plan, creating a milestone, or integrating with Trusted Advisor. Triggers: well-architected tool, well architected review, workload review, pillar, operational excellence, security, reliability, performance, cost optimization, sustainability, prosperity, improvement plan, milestone, trusted advisor.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-review-operator\u002FSKILL.md",[],[],{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":19},"01M7ADSH5JA9QHNPPHQCD7EVA7","wafv2-web-acl-deployer","Provisions AWS WAFv2 Web ACLs with correct production defaults: scope selection (CLOUDFRONT vs REGIONAL), managed rule groups (AWSManagedRulesCommonRuleSet, SQLiRuleSet, LinuxRuleSet, WindowsRuleSet, IPReputationList, BotControlRuleSet, AmazonIpReputationList, ATP), custom rules (byte match, IP set, regex pattern, geo match, size constraint, rate-based), rule priority ordering, logging destinations (Kinesis Firehose, CloudWatch Logs, S3), resource association (ALB, API Gateway, CloudFront), rate-based rules with aggregate keys (IP, forwarded IP), Challenge and CAPTCHA actions, and account takeover prevention. Emits a READY_TO_DEPLOY checklist. Use when creating a Web ACL, attaching managed rules, configuring rate limiting, enabling WAF logging, associating a Web ACL with an ALB\u002FAPI Gateway\u002FCloudFront, or configuring CAPTCHA\u002FChallenge actions. Triggers: create WAF Web ACL, WAFv2, managed rule groups, WAF rate limiting, WAF logging, WAF CAPTCHA, WAF Challenge action, bot control, ATP managed rules.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-deployer\u002FSKILL.md",[],[],{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":19},"01M7ADRYFAT8R73FBNCHRC573X","wafv2-web-acl-auditor","Audits AWS WAFv2 Web ACL configurations to determine whether the ACL provides effective protection: default-action posture (Allow vs Block), managed-rule-group coverage gaps, rule effectiveness (BLOCK vs COUNT, shadow\u002Fbypass rules, stale exclusions), rate-based rule correctness, logging and visibility configuration, and text-transformation bypass vectors. Emits a deterministic verdict per Web ACL. Use when reviewing a WAFv2 Web ACL for security posture, checking managed-rule coverage, validating rate-limit configuration, auditing WAF logging, or hardening a WAF before production deployment. Triggers: WAF, WAFv2, Web ACL, managed rule group, AWSManagedRules, rate-based rule, CAPTCHA, Challenge, OverrideAction, Count mode, forwarded IP, Bot Control, ATP, text transformation, WAF logging, WAF visibility, OWASP, SQLi, XSS, RFI.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-auditor\u002FSKILL.md",[],[],{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":19},"01M7ADR8W7G72JX4KFGN03QK8Q","waf-rule-deployer","Provisions AWS WAFv2 rule sets with production defaults: Web ACL creation (CloudFront scope in us-east-1 vs Regional scope), rule groups (managed vs custom) with capacity planning in WCU (Web ACL Capacity Units, 1500 default per ACL), managed rule groups (AWSManagedRulesCommonRuleSet, AWSManagedRulesSQLiRuleSet, AWSManagedRulesAmazonIpReputationList, AWSManagedRulesLinuxRuleSet, AWSManagedRulesWindowsRuleSet, AWSManagedRulesUnixRuleSet), custom rules (byte-match, regex pattern set, geo-match, rate-based), IP set and regex pattern set resources, rule priority ordering (lowest number evaluated first), action types (allow, block, count, CAPTCHA, Challenge), bot control managed rule group, account takeover. Triggers: create WAF rule, WAF managed rule group, WAF custom rule, WAF byte match, WAF geo match, WAF rate based rule, WAF IP set, WAF regex pattern set, WAF WCU budget, WAF CloudFront ACL, WAF logging Kinesis Firehose, WAF bot control, WAF ATP, WAF label matching, WAF Challenge action, WAF CAPTCHA.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwaf-rule-deployer\u002FSKILL.md",[],[]]