[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ACE0SXGX0R8MN76XYM99FP":3,"skill-same:01M7ACE0SXGX0R8MN76XYM99FP":148},{"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":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M7ACE0SXGX0R8MN76XYM99FP","service-catalog-portfolio-deployer",null,"Provisions AWS Service Catalog portfolios and products with production-safe defaults: portfolio creation (DisplayName, ProviderName, description), product creation from CloudFormation templates (CLOUDFORMATION_TEMPLATE, semantic versions, provisioning artifacts), constraints (LAUNCH stack\u002Ftemplate-based roles, STACK_UPDATE, TAG_UPDATE, NOTIFICATION), launch paths (local + shared via Organizations), portfolio sharing (org, account, OU), TagOptions (key-value pairs applied to launched products), and latest primitives (Terraform Open Source, Service App Registry, Terraform Cloud). Emits READY_TO_DEPLOY \u002F PREREQUISITES_MISSING with verified portfolios, products, constraints, and copy-pasteable servicecatalog + iam + sns commands. Use when provisioning Service Catalog for self-service launchpad, governance-gated distribution, or cross-account template distribution. Triggers: Service Catalog, portfolio, product, launch constraint, TagOptions, organizational sharing, self-service launchpad.","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\u002Fservice-catalog-portfolio-deployer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: service-catalog-portfolio-deployer\ndescription: 'Provisions AWS Service Catalog portfolios and products with production-safe defaults: portfolio creation (DisplayName, ProviderName, description), product creation from CloudFormation templates (CLOUDFORMATION_TEMPLATE, semantic versions, provisioning artifacts), constraints (LAUNCH stack\u002Ftemplate-based roles, STACK_UPDATE, TAG_UPDATE, NOTIFICATION), launch paths (local + shared via Organizations), portfolio sharing (org, account, OU), TagOptions (key-value pairs applied to launched products), and latest primitives (Terraform Open Source, Service App Registry, Terraform Cloud). Emits READY_TO_DEPLOY \u002F PREREQUISITES_MISSING with verified portfolios, products, constraints, and copy-pasteable servicecatalog + iam + sns commands. Use when provisioning Service Catalog for self-service launchpad, governance-gated distribution, or cross-account template distribution. Triggers: Service Catalog, portfolio, product, launch constraint, TagOptions, organizational sharing, self-service launchpad.'\nlicense: Apache-2.0\ncompatibility: Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). Live provisioning uses AWS CLI v2 with servicecatalog (create-portfolio, create-product, create-constraint, associate-product-with-portfolio, create-portfolio-share, create-tag-option, associate-tag-option-with-resource), cloudformation (validate-template), iam (create-role, pass-role), sns (create-topic), and organizations (enable-aws-service-access, list-delegated-administrators). Works with Terraform...\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: Governance\n  task_type: deploy\n  skill_class: capability\n  lifecycle_status: active\n  verdict_shape: READY_TO_DEPLOY | PREREQUISITES_MISSING\n  when_to_use: Provisioning a Service Catalog portfolio for self-service product distribution; creating a product from a CloudFormation template; applying constraints (launch role, tag update, stack update, notification); configuring launch paths for a local account or sharing a portfolio via AWS Organizations; setting up TagOptions for governed tag application; integrating Service Catalog with Service App Registry for application inventory tagging; or provisioning Service Catalog with Terraform Open Source. Do NOT invoke for launching a product instance (use the appropriate operate skill), for AWS Marketplace integration (separate workflow), or for non-Service-Catalog CloudFormation deployment.\n  activation_triggers: Service Catalog portfolio, Service Catalog product, launch constraint, stack-based constraint, template-based constraint, tag-update constraint, notification constraint, launch path, portfolio share, organizational sharing, TagOptions, self-service launchpad, CloudFormation product, product versioning, Service App Registry, Service Catalog Terraform\n  invocation_schema: 'Input: either (a) a portfolio spec including DisplayName, ProviderName, products (name + CloudFormation URL + version), constraints, launch paths, TagOptions, and sharing target; or (b) a partial spec for interactive refinement (e.g., \"Service Catalog portfolio with a curated S3-bucket product and a launch role\"). Output: a deterministic PORTFOLIO \u002F VERDICT \u002F CHECKLIST \u002F VERIFICATION_COMMANDS block per the STRICT output contract, where VERDICT is READY_TO_DEPLOY or PREREQUISITES_MISSING.'\n  version: 0.1.0\n  author: Jacky Chan — AWS Community Builder\n  keywords: aws, service catalog, portfolio, product, provisioning artifact, launch constraint, stack-based constraint, template-based constraint, tag-update constraint, notification constraint, launch path, portfolio share, organizational sharing, tagoptions, self-service launchpad, cloudformation product, product versioning, service app registry, cloudops, deploy\n  tags: aws, service-catalog, portfolio, product, launch-constraint, tagoptions, governance, deploy\n  dependencies: aws-orchestrator\n---\n\n# Service Catalog Portfolio Deployer\n\n## What this skill does\n\nProvisions AWS Service Catalog portfolios and products with correct\nproduction-safe defaults: a least-privilege launch role passed via the\nLAUNCH constraint, scoped launch paths, portfolio sharing (account-\nlevel or organization-level), TagOptions for governed tag application,\nand versioned provisioning artifacts. The skill walks an 8-step\nprocedure, surfaces the silent-failure modes unique to Service Catalog\n(most dangerous: a product launched without a LAUNCH constraint\ndeploys as the end-user's permissions — a privilege-escalation path\nthat produces production resources owned by individual operators), and\nemits a READY_TO_DEPLOY checklist verifying every portfolio, product,\nconstraint, and share against the IAM and Organizations state. The\nsingle most common incident this skill prevents: an administrator\npublishes a powerful product (e.g., VPC creator) to a portfolio shared\nwith the whole organization, with no LAUNCH constraint, and any user\nwith launch permissions deploys a full VPC in any account using their\nown broad role — runaway cost and compliance drift with no central\ngovernance.\n\n## Quick navigation\n\n| Section | What it covers | When to read it |\n|---|---|---|\n| **Quick reference** | Provisioning summary (8 steps), verdict thresholds, constraint matrix | Before any operation |\n| **Activation keywords** | Phrases that route to this skill | Disambiguating routing |\n| **Invocation contract** | Required literal labels in the response | Formatting the response |\n| **Reasoning framework** | Why the 8-step order matters; launch-permission model | Understanding the deploy model |\n| **Dependency graph** | Which configs silently no-op without their prerequisite | Debugging \"product not visible \u002F can't launch\" |\n| **Expert heuristic** | Launch-constraint myth; share-region quirk; TagOptions inheritance | Pre-empt production incidents |\n| **Prerequisites** | What to verify before emitting any command | Avoid PREREQUISITES_MISSING rework |\n| **8-step procedure** | The actual provisioning with copy-pasteable CLI | Executing the deploy |\n| **NEVER (top 5)** | Hard rules that prevent privilege escalation \u002F governance gaps | Review before deploy |\n| **STRICT output contract** | Required PORTFOLIO \u002F VERDICT \u002F CHECKLIST \u002F VERIFICATION_COMMANDS block | Formatting the response |\n| **Recent AWS features** | Terraform Open Source, App Registry, CloudFormation StackSets | Stay current |\n\n## Quick reference — provisioning summary (8 steps)\n\n| Step | Action | Reversible? | Key risk if skipped |\n|---|---|---|---|\n| 1 | Confirm portfolio intent + consumer scope | — | wrong scope = wrong visibility |\n| 2 | Create portfolio (DisplayName, ProviderName, description) | Yes | missing description = unsearchable |\n| 3 | Create products + provisioning artifacts (versions) | Yes | wrong template URL = launch failure |\n| 4 | Associate products with the portfolio | Yes | unassociated product = invisible |\n| 5 | Configure constraints (LAUNCH, TAG_UPDATE, STACK_UPDATE, NOTIFICATION) | Yes | no LAUNCH = end-user deploys as themselves |\n| 6 | Configure TagOptions + bind to portfolio\u002Fproducts | Yes | no TagOptions = ungoverned tagging |\n| 7 | Configure launch paths + portfolio shares (account, OU, org) | Yes | wrong share target = governance gap |\n| 8 | Verify via `search-products` + `describe-portfolio` + emit checklist | — | silent no-ops |\n\n**Critical ordering constraints:** portfolio exists before products\n(products need a parent association); products created with their\ninitial provisioning artifact before constraints (constraints\nreference product IDs); launch role created before the LAUNCH\nconstraint (the constraint references `RoleArn`); TagOptions bound\nbefore sharing (so consumers inherit tag policy on launch); shares\nconfigured last (sharing an unconstrained portfolio exposes the\ngovernance gap immediately). Rationale and the silent-failure table\nare below.\n\n## Activation keywords\n\nService Catalog portfolio, Service Catalog product, provisioning\nartifact, product version, launch constraint, stack-based constraint,\ntemplate-based constraint, tag-update constraint, notification\nconstraint, launch path, portfolio share, organizational sharing,\nTagOptions, self-service launchpad, CloudFormation product, Service\nApp Registry, Service Catalog Terraform, delegated administrator.\n\n## Invocation contract (hard requirement)\n\nWhen this skill is invoked with a Service Catalog portfolio\nprovisioning request, the agent MUST respond with the checklist\ndefined in §\"STRICT output contract\" using the literal all-caps labels\n`PORTFOLIO:`, `VERDICT:`, `CHECKLIST:`, and `VERIFICATION_COMMANDS:`.\nDo NOT preface with prose, headings, or disclaimers — emit the block\nas the 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\n## Reasoning framework (why the provisioning order matters)\n\nService Catalog looks like \"publish a portfolio of templates\" but the\nunderlying model has four traps:\n\n1. **The LAUNCH constraint determines the role that provisions the\n   product — not the launching user's role.** Without a LAUNCH\n   constraint, CloudFormation deploys using the launching user's\n   permissions. That means an operator with broad IAM can launch a\n   VPC, an IAM role, a Lambda — anything their role allows — and the\n   resource belongs to them, not the central governance team. The\n   LAUNCH constraint pins the provisioning to a specific role\n   (typically a role with only the product's required permissions),\n   regardless of who launches it. This is the central governance\n   primitive of Service Catalog.\n\n2. **Two constraint scoping models exist: STACK-based and TEMPLATE-\n   based.** A STACK-based launch constraint passes the same role for\n   every launch of the product. A TEMPLATE-based launch constraint\n   applies a rules engine to choose the role per-launch (e.g., based\n   on the launching user's team). Template-based constraints are\n   powerful but rarely used; the canonical pattern is STACK-based with\n   one role per product family. Mixing them silently degrades to\n   STACK-based when the template engine produces no match.\n\n3. **Portfolio shares are region-scoped.** Sharing a portfolio with an\n   Organization account does NOT make the portfolio visible in other\n   regions. A share in us-east-1 is invisible to a user in eu-west-1\n   unless they switch regions in the console. For multi-region\n   deployments, replicate the portfolio per region or document the\n   region expectation explicitly.\n\n4. **TagOptions are NOT Service Control Policies.** TagOptions are a\n   \"suggested tags\" mechanism: when a user launches a product\n   associated with a TagOption, the tag is pre-populated in the launch\n   wizard. The user can change the value or remove the tag entirely\n   (unless TAG_UPDATE constraint is set to `NOT_ALLOWED`). TagOptions\n   do not enforce tagging; they suggest it. Enforce tagging via SCP\n   on the organization or via a CloudFormation-backed tag policy.\n\nThe procedure below sequences the steps to surface these traps.\n\n## Dependency graph (silent-failure table)\n\n| Configuration | Hard dependencies (API error without) | Silent failure mode (returns 200, does nothing useful) | Enables downstream |\n|---|---|---|---|\n| Portfolio | unique DisplayName | **portfolio with same DisplayName in different accounts creates duplicate invisible inventories** | container for products |\n| Product (CLOUDFORMATION_TEMPLATE) | valid CloudFormation URL | **product with broken template URL launches OK, fails at stack create with no alarm** | launchable item |\n| Provisioning artifact (version) | semantic version string | **two artifacts with same version silently overwrites \"active\" flag; old version invisible** | versioned launches |\n| Product-portfolio association | product ID + portfolio ID | **unassociated product silently invisible to portfolio users** | product visibility |\n| LAUNCH constraint (STACK-based) | valid RoleArn (PassRole) | **no LAUNCH constraint = CloudFormation deploys as the end-user's role = privilege escalation risk** | governance |\n| LAUNCH constraint (TEMPLATE-based) | template rules engine | **template rule that matches no role silently degrades to no constraint = end-user role** | conditional governance |\n| TAG_UPDATE constraint | product ID | **default allows tag changes post-launch — TagOptions suggested at launch can be removed** | tag immutability |\n| NOTIFICATION constraint | SNS ARN | **SNS topic with no subscribers = notifications silently lost** | launch tracking |\n| TagOption | unique key+value | **TagOption not associated with portfolio = never applied at launch** | governed tagging |\n| Launch path | local account by default | **no launch path in shared account = portfolio visible but unlaunchable** | cross-account launching |\n| Portfolio share (account-level) | account ID | **share to wrong account ID = silent invisible; no error, no usage** | cross-account visibility |\n| Portfolio share (org-level) | Organizations `servicecatalog:enable` | **share without delegated admin = recipients see portfolio but cannot manage** | centralized catalog |\n| Portfolio share (OU-level) | OU ID | **share to OU root vs. OU child silently changes recipient set** | scoped distribution |\n| App Registry association | application exists | **application deleted after association = association silently inert** | application inventory |\n\n**The four most dangerous silent-failure rows** are no-LAUNCH-\nconstraint, TEMPLATE-based-no-match-degradation, region-scoped-share-\nvisibility, and TagOptions-not-associated. All return success on the\nAPI call; the failure surfaces only when a product is launched\nwithout governance or a user cannot find the portfolio. Step 5\n(LAUNCH constraint), Step 7 (sharing with region\u002Fdelegated-admin\nverification), and Step 8 (`search-products` + `describe-portfolio`\nas the recipient account) are non-negotiable for any production-\nadjacent portfolio.\n\n## Expert heuristic: the no-LAUNCH-constraint myth\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#expert-heuristic-the-no-launch-constraint-myth).\n> Operator-expectation vs actual-behavior comparison and the one-launch-role-per-product-family remedy.\n\n## Expert heuristic: portfolio share region quirk\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#expert-heuristic-portfolio-share-region-quirk).\n> Region-scoped shares: create-portfolio-share has no region parameter; three multi-region remedies (StackSets replication, documented region expectation, custom launcher).\n\n## Expert heuristic: TagOptions vs. SCPs vs. TAG_UPDATE constraint\n\nThree independent mechanisms govern tags on Service Catalog-launched\nproducts. Operators frequently conflate them.\n\n- **TagOptions** (suggested): when a user launches a product\n  associated with a TagOption, the tag is pre-populated in the launch\n  wizard. The user can change the value or remove the tag.\n- **TAG_UPDATE constraint (`NOT_ALLOWED`)**: prevents the user from\n  modifying the tags on the launched product's CloudFormation stack\n  after launch. It does NOT prevent modification at launch time —\n  only post-launch.\n- **SCP \u002F tag policy on the organization**: enforces tag compliance\n  across the entire account, including Service Catalog launches. This\n  is the only one of the three that can enforce a tag value at launch\n  time.\n\nFor true tag governance, use all three: TagOptions to suggest, TAG_\nUPDATE constraint to lock post-launch, and SCP to enforce at the\ncontrol-plane layer.\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting any provisioning command, verify these prerequisites.\nIf any are missing, the verdict is **PREREQUISITES_MISSING** with a\nspecific gap citation.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| Caller IAM | `servicecatalog:CreatePortfolio`, `iam:CreateRole`, `iam:PassRole` required | `aws sts get-caller-identity` + IAM policy check |\n| CloudFormation template URL resolvable | Broken URL = launch failure at consumer time | `aws cloudformation validate-template --template-url \u003CURL>` |\n| Launch role exists (for LAUNCH constraint) | Constraint references RoleArn | `aws iam get-role --role-name \u003Cname>` |\n| Organizations enabled (for org\u002FOU shares) | Org-level share requires Organizations | `aws organizations describe-organization` |\n| Service Catalog delegated admin (for cross-account) | Recipients can view but not manage without it | `aws organizations list-delegated-administrators --service-principal servicecatalog.amazonaws.com` |\n| SNS topic exists (for NOTIFICATION constraint) | Constraint references SNS ARN | `aws sns get-topic-attributes --topic-arn \u003Carn>` |\n| Tag keys (for TagOptions) | TagOption key must exist before associating | `aws servicecatalog list-tag-options` |\n| Region of share matches consumer region | Shares are region-scoped | Caller region matches target user's region |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## 8-step provisioning procedure\n\n### Step 1 — Confirm portfolio intent + consumer scope\n\nBefore any resource lookup, name the intent in one sentence:\n\"distribute a curated S3-bucket product to all organization accounts\nfor analytics workloads,\" or \"self-service launchpad for the\nplatform team in this account only.\" The intent drives the share\ntarget, the launch role scope, and the constraint set.\n\n### Step 2 — Create portfolio\n\n```bash\naws servicecatalog create-portfolio \\\n  --display-name \"Curated S3 Products\" \\\n  --provider-name \"Platform Governance\" \\\n  --description \"S3-bucket products for analytics workloads. Launch role scoped to s3:* only. Region: us-east-1.\" \\\n  --tags Key=Owner,Value=platform-governance\n```\n\nThe `description` field is searchable in the consumer console —\ninclude the region, the launch-role summary, and the intended consumer\nscope. Missing description = consumers cannot find the portfolio.\n\n### Step 3 — Create products + provisioning artifacts\n\n> Moved to [references\u002Fprovisioning-cli-commands.md](references\u002Fprovisioning-cli-commands.md#step-3--create-products--provisioning-artifacts-cli).\n> create-product with provisioning-artifact-parameters and create-provisioning-artifact for new versions.\n\nA provisioning artifact is a version. Multiple versions can coexist;\nconsumers pick one at launch. The \"active\" version is the default;\nolder versions remain launchable for rollback.\n\n**Common mistake:** using `LoadTemplateFromURL` with a private S3\nURL. The URL must be accessible to Service Catalog (presigned or\npublic-read). A private URL launches OK but fails at stack-create\ntime with no alarm.\n\n### Step 4 — Associate products with the portfolio\n\n```bash\naws servicecatalog associate-product-with-portfolio \\\n  --product-id $PRODUCT_ID \\\n  --portfolio-id $PORTFOLIO_ID\n```\n\nA product not associated with any portfolio is silently invisible to\nall consumers — even the administrator. Association is what makes the\nproduct available inside the portfolio.\n\n**Common mistake:** creating the product but forgetting the\nassociation. The product appears in `search-products-as-admin` but\nnot in `search-products` (the consumer-facing API).\n\n### Step 5 — Configure constraints (LAUNCH, TAG_UPDATE, NOTIFICATION)\n\n> Moved to [references\u002Fconstraint-and-launch-role-templates.md](references\u002Fconstraint-and-launch-role-templates.md#step-5--configure-constraints-creation-cli).\n> Launch-role creation (iam create-role \u002F put-role-policy) and LAUNCH create-constraint CLI.\n\nConstraint types:\n\n| Type | Effect | Required? |\n|---|---|---|\n| `LAUNCH` | CloudFormation assumes the specified role at launch (not the user's role) | YES — without this, end-user permissions apply |\n| `TAG_UPDATE` | `NOT_ALLOWED` blocks tag changes to the launched stack post-launch | Recommended |\n| `STACK_UPDATE` | `NOT_ALLOWED` blocks updates to the launched stack post-launch (immutable launches) | Optional |\n| `NOTIFICATION` | Sends SNS notifications for launch\u002Fupdate\u002Fterminate events | Recommended for audits |\n| `LAUNCH_PERMISSION` | Limits who can launch the product (via principal ARNs) | Optional |\n\n**Common mistake:** using a `TEMPLATE`-type launch constraint without\ntesting the rules engine. A template rule that matches no role\nsilently degrades to no constraint — the end-user's role is used.\n\n### Step 6 — Configure TagOptions + bind to portfolio\u002Fproducts\n\n> Moved to [references\u002Fsharing-and-tagoptions-procedures.md](references\u002Fsharing-and-tagoptions-procedures.md#step-6--configure-tagoptions-cli).\n> create-tag-option and associate-tag-option-with-resource CLI.\n\nBind TagOptions at the portfolio level (inherited by all products in\nthe portfolio) or at the product level (product-specific). Portfolio-\nlevel TagOptions propagate to every product on launch.\n\n### Step 7 — Configure launch paths + portfolio shares\n\n**Local account launch path** is implicit — no configuration needed.\nThe portfolio is launchable by users in the source account (subject\nto IAM).\n\n> Moved to [references\u002Fsharing-and-tagoptions-procedures.md](references\u002Fsharing-and-tagoptions-procedures.md#step-7--launch-paths--portfolio-shares-cli).\n> Account-, organization-, and OU-level create-portfolio-share CLI plus Organizations enable-aws-service-access.\n\n**Common mistake:** sharing to the organization root vs. the\norganization ID. `Type=ORGANIZATION` shares to every account in the\norg; `Type=ORGANIZATIONAL_UNIT` with the OU root ID shares to a\nsubset. Confirm the recipient set explicitly.\n\n### Step 8 — Verify via `search-products` + `describe-portfolio`\n\n> Moved to [references\u002Fsharing-and-tagoptions-procedures.md](references\u002Fsharing-and-tagoptions-procedures.md#step-8--verification-cli).\n> Verification CLI: describe-portfolio, search-products-as-admin, describe-constraint, consumer search-products.\n\nCross-account verification is critical: a share that looks successful\nfrom the source account may be invisible in the consumer account due\nto region mismatch, missing delegated admin, or IAM scoping.\n\n## NEVER do these things\n\nThese anti-patterns cause privilege escalation, governance gaps, or\nsilent no-ops. Each is observed in real production incidents.\n\n1. **NEVER publish a product without a LAUNCH constraint.** Why it's\n   wrong: without a LAUNCH constraint, CloudFormation assumes the\n   launching user's role. An operator with PowerUserAccess launches a\n   powerful product and deploys resources owned by their individual\n   role. Central governance has no visibility until audit time. Always\n   configure a STACK-based LAUNCH constraint with a least-privilege\n   role scoped to the product's required permissions.\n\n2. **NEVER use a TEMPLATE-based LAUNCH constraint without testing the\n   rules engine against every consumer path.** Why it's wrong: a\n   template rule that matches no role silently degrades to no\n   constraint. The end-user's role is used. The remediation is to\n   fall back to STACK-based constraints with a default role, and to\n   unit-test template rules with every consumer persona before\n   deployment.\n\n3. **NEVER share a portfolio at the organization root when you mean\n   an OU subset.** Why it's wrong: `Type=ORGANIZATION` shares to every\n   account in the org, including Sandbox, Security, and Audit\n   accounts. Use `Type=ORGANIZATIONAL_UNIT` with a specific OU ID,\n   and document the recipient set in the portfolio description.\n\n4. **NEVER assume a portfolio share is multi-region.** Why it's\n   wrong: shares are region-scoped to the caller's region. A share\n   from us-east-1 is invisible in eu-west-1. For multi-region\n   deployments, replicate the portfolio via CloudFormation StackSets\n   or document the region expectation explicitly.\n\n5. **NEVER use TagOptions as the only tag-governance mechanism.** Why\n   it's wrong: TagOptions are suggestions, not enforcement. A user\n   can remove a suggested tag at launch or post-launch (unless TAG_\n   UPDATE constraint is set). For true tag governance, combine\n   TagOptions, TAG_UPDATE constraint, and an SCP\u002Ftag policy at the\n   organization level.\n\n## Output format\n\n```\nPORTFOLIO: \u003Cdisplay-name> (products: \u003Ccount>, shares: \u003Crecipient-summary>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Intent + consumer scope: \u003Cone-sentence intent>, scope \u003Clocal|account|OU|org>\n  [✓|✗] Portfolio created: \u003Cdisplay-name> by \u003CProviderName> (\u003Cregion>)\n  [✓|✗] Product(s): \u003Ccount> products, \u003Ccount> provisioning artifacts (versions)\n  [✓|✗] Product-portfolio association: \u003Ccount> associations\n  [✓|✗] Constraint(s): LAUNCH \u003Crole-name> (STACK-based), TAG_UPDATE \u003Cvalue>, NOTIFICATION \u003Csns-name>\n  [✓|✗] TagOptions: \u003Ccount> key-value pairs bound at portfolio level\n  [✓|✗] Share(s): \u003Crecipient-summary> (region: \u003Ccaller-region>, delegated admin: \u003Ctrue|false>)\nVERIFICATION_COMMANDS:\n  \u003Ccopy-pasteable verification commands>\n```\n\n## STRICT output contract\n\nThe rules below are hard constraints. Violating any one produces a\nchecklist that looks complete but contains a silent misconfiguration.\nSelf-check EVERY emitted block against these rules before returning.\n\n### Required output structure\n\nEvery response MUST be a single block using these literal labels, in\nthis order. Do NOT preface with prose, headings, or disclaimers.\n\n```text\nPORTFOLIO: \u003Cdisplay-name> (products: \u003Ccount>, shares: \u003Crecipient-summary>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Intent + consumer scope: \u003Cone-sentence intent>, scope \u003Clocal|account|OU|org>\n  [✓|✗] Portfolio created: \u003Cdisplay-name> by \u003CProviderName> (\u003Cregion>)\n  [✓|✗] Product(s): \u003Ccount> products, \u003Ccount> provisioning artifacts (versions)\n  [✓|✗] Product-portfolio association: \u003Ccount> associations\n  [✓|✗] Constraint(s): LAUNCH \u003Crole-name> (STACK-based), TAG_UPDATE \u003Cvalue>, NOTIFICATION \u003Csns-name>\n  [✓|✗] TagOptions: \u003Ccount> key-value pairs bound at portfolio level\n  [✓|✗] Share(s): \u003Crecipient-summary> (region: \u003Ccaller-region>, delegated admin: \u003Ctrue|false>)\nVERIFICATION_COMMANDS:\n  \u003Ccopy-pasteable verification commands — one per [✓] item>\n```\n\n### FORBIDDEN output patterns\n\n1. **NEVER emit `VERDICT: READY_TO_DEPLOY` without showing ALL 7\n   checklist items.** Every item MUST appear with a status marker:\n   `[✓]`, `[✗]`, or `[OPTIONAL]`. Omitting a row implies it was not\n   evaluated.\n\n2. **NEVER mark Constraint(s) `[✓] LAUNCH` without citing the role\n   name AND confirming it is STACK-based (or TEMPLATE-based with a\n   tested default fallback).** A LAUNCH constraint with no role ARN\n   silently falls back to the end-user's role — privilege escalation.\n   The checklist MUST cite the role name and the constraint scoping\n   model.\n\n3. **NEVER mark Share(s) `[✓]` without citing the recipient scope\n   (ORGANIZATION, ORGANIZATIONAL_UNIT, ACCOUNT) AND the caller\n   region.** Region mismatch is the leading cause of \"portfolio\n   invisible in consumer account\" tickets. The checklist MUST cite\n   both.\n\n4. **NEVER mark TagOptions `[✓]` without citing the binding level\n   (portfolio vs. product).** Portfolio-level TagOptions propagate to\n   every product; product-level TagOptions are scoped. Mixing them\n   silently produces inconsistent tagging.\n\n5. **NEVER mark Product(s) `[✓]` without citing the provisioning\n   artifact count AND the active version.** A product with one\n   provisioning artifact has no rollback; a product with multiple\n   untagged artifacts is ambiguous at launch.\n\n6. **NEVER emit `VERDICT: PREREQUISITES_MISSING` without citing the\n   specific gap.** Each `[✗]` item MUST have a one-line reason:\n   `[✗] Share(s): Organizations not enabled — enable\n   enable-aws-service-access for servicecatalog.amazonaws.com before\n   sharing`. A bare `[✗]` is non-compliant.\n\n7. **NEVER include `TEMPLATE`-type LAUNCH constraint in the checklist\n   without a `[WARN]` note.** Template-based constraints silently\n   degrade to no constraint when no rule matches. The checklist MUST\n   cite the fallback role or mark the item `[✗]`.\n\n### Perfect example output — READY_TO_DEPLOY\n\n```text\nPORTFOLIO: Curated S3 Products (products: 1, shares: ou-abc1-abcdef in us-east-1)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Intent + consumer scope: Distribute a curated S3-bucket product to platform-team OU for analytics workloads, scope OU\n  [✓] Portfolio created: Curated S3 Products by Platform Governance (us-east-1)\n  [✓] Product(s): 1 product (Curated S3 Bucket), 2 provisioning artifacts (v1.0.0 active, v1.1.0)\n  [✓] Product-portfolio association: 1 association (Curated S3 Bucket -> Curated S3 Products)\n  [✓] Constraint(s): LAUNCH sc-launch-s3-role (STACK-based, scoped to s3:* + iam:PassRole with tag condition), TAG_UPDATE NOT_ALLOWED, NOTIFICATION sc-launch-events SNS topic\n  [✓] TagOptions: 2 key-value pairs bound at portfolio level (CostCenter=platform-1234, Owner=platform-governance)\n  [✓] Share(s): ORGANIZATIONAL_UNIT ou-abc1-abcdef (region: us-east-1, delegated admin: enabled)\nVERIFICATION_COMMANDS:\n  aws servicecatalog describe-portfolio --id port-aaaa1111\n  aws servicecatalog search-products-as-admin --portfolio-id port-aaaa1111\n  aws servicecatalog describe-constraint --id cons-bbbb2222\n  aws servicecatalog list-tag-options\n  aws servicecatalog list-portfolio-access --portfolio-id port-aaaa1111\n  aws organizations list-delegated-administrators --service-principal servicecatalog.amazonaws.com\n```\n\n### Perfect example output — PREREQUISITES_MISSING\n\n> Moved to [references\u002Fworked-examples.md](references\u002Fworked-examples.md#perfect-example-output--prerequisites_missing).\n> PREREQUISITES_MISSING block: org-level share without Organizations enabled and no launch role, gaps cited.\n\n**Self-check before emit:**\n- [ ] All 7 checklist rows present (no omitted items)?\n- [ ] Every `[✓]` has a matching verification command?\n- [ ] LAUNCH constraint cites role name + scoping model?\n- [ ] Share(s) cite recipient scope AND caller region?\n- [ ] TagOptions cite binding level (portfolio vs. product)?\n- [ ] Product(s) cite provisioning artifact count + active version?\n- [ ] Every `[✗]` cites the specific gap?\n- [ ] TEMPLATE-type LAUNCH constraint (if present) carries a `[WARN]`?\n\n## Recent AWS features\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#recent-aws-features).\n> Terraform Open Source\u002FCloud products, App Registry association, StackSets products, TagOption inheritance, delegated admin, SourceProduct copy.\n\n## References (load on demand)\n\n- [advanced-patterns](references\u002Fadvanced-patterns.md) — No-LAUNCH-constraint myth deep dive, recent AWS features (Terraform, App Registry, StackSets, delegated admin)\n- [worked-examples](references\u002Fworked-examples.md) — Perfect PREREQUISITES_MISSING example output\n- [provisioning-cli-commands](references\u002Fprovisioning-cli-commands.md) — Product and provisioning-artifact creation CLI (Step 3)\n- [constraint-and-launch-role-templates](references\u002Fconstraint-and-launch-role-templates.md) — Constraint JSON, launch-role policies, constraint creation commands (incl. Step 5 CLI)\n- [sharing-and-tagoptions-procedures](references\u002Fsharing-and-tagoptions-procedures.md) — Sharing, TagOptions, App Registry, verification procedures (incl. Steps 6-8 CLI)\n\n## AWS documentation\n\n- **AWS Service Catalog Administrator Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fservicecatalog\u002Flatest\u002Fadminguide\u002Fintroduction.html\n- **Service Catalog Portfolios** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fservicecatalog\u002Flatest\u002Fadminguide\u002Fcatalogs_portfolios.html\n- **Service Catalog Products** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fservicecatalog\u002Flatest\u002Fadminguide\u002Fcatalogs_products.html\n- **Service Catalog Constraints** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fservicecatalog\u002Flatest\u002Fadminguide\u002Fconstraints.html\n- **Service Catalog Launch Constraints** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fservicecatalog\u002Flatest\u002Fadminguide\u002Fconstraints-launch.html\n- **Service Catalog TagOptions** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fservicecatalog\u002Flatest\u002Fadminguide\u002Ftagoptions.html\n- **Service Catalog Portfolio Sharing** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fservicecatalog\u002Flatest\u002Fadminguide\u002Fcatalogs_portfolios_sharing.html\n- **Service Catalog API Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fservicecatalog\u002Flatest\u002Fdg\u002Fwelcome.html\n- **Service Catalog CLI Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Fservicecatalog\u002F\n- **Blog: Service Catalog + Terraform Open Source** — https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fmt\u002Fannouncing-aws-service-catalog-support-for-terraform-open-source\u002F\n- **Workshop: Service Catalog** — https:\u002F\u002Fcatalog.workshops.aws\u002Fservicecatalog\n","# Service Catalog Portfolio Deployer\n\n## What this skill does\n\nProvisions AWS Service Catalog portfolios and products with correct\nproduction-safe defaults: a least-privilege launch role passed via the\nLAUNCH constraint, scoped launch paths, portfolio sharing (account-\nlevel or organization-level), TagOptions for governed tag application,\nand versioned provisioning artifacts. The skill walks an 8-step\nprocedure, surfaces the silent-failure modes unique to Service Catalog\n(most dangerous: a product launched without a LAUNCH constraint\ndeploys as the end-user's permissions — a privilege-escalation path\nthat produces production resources owned by individual operators), and\nemits a READY_TO_DEPLOY checklist verifying every portfolio, product,\nconstraint, and share against the IAM and Organizations state. The\nsingle most common incident this skill prevents: an administrator\npublishes a powerful product (e.g., VPC creator) to a portfolio shared\nwith the whole organization, with no LAUNCH constraint, and any user\nwith launch permissions deploys a full VPC in any account using their\nown broad role — runaway cost and compliance drift with no central\ngovernance.\n\n## Quick navigation\n\n| Section | What it covers | When to read it |\n|---|---|---|\n| **Quick reference** | Provisioning summary (8 steps), verdict thresholds, constraint matrix | Before any operation |\n| **Activation keywords** | Phrases that route to this skill | Disambiguating routing |\n| **Invocation contract** | Required literal labels in the response | Formatting the response |\n| **Reasoning framework** | Why the 8-step order matters; launch-permission model | Understanding the deploy model |\n| **Dependency graph** | Which configs silently no-op without their prerequisite | Debugging \"product not visible \u002F can't launch\" |\n| **Expert heuristic** | Launch-constraint myth; share-region quirk; TagOptions inheritance | Pre-empt production incidents |\n| **Prerequisites** | What to verify before emitting any command | Avoid PREREQUISITES_MISSING rework |\n| **8-step procedure** | The actual provisioning with copy-pasteable CLI | Executing the deploy |\n| **NEVER (top 5)** | Hard rules that prevent privilege escalation \u002F governance gaps | Review before deploy |\n| **STRICT output contract** | Required PORTFOLIO \u002F VERDICT \u002F CHECKLIST \u002F VERIFICATION_COMMANDS block | Formatting the response |\n| **Recent AWS features** | Terraform Open Source, App Registry, CloudFormation StackSets | Stay current |\n\n## Quick reference — provisioning summary (8 steps)\n\n| Step | Action | Reversible? | Key risk if skipped |\n|---|---|---|---|\n| 1 | Confirm portfolio intent + consumer scope | — | wrong scope = wrong visibility |\n| 2 | Create portfolio (DisplayName, ProviderName, description) | Yes | missing description = unsearchable |\n| 3 | Create products + provisioning artifacts (versions) | Yes | wrong template URL = launch failure |\n| 4 | Associate products with the portfolio | Yes | unassociated product = invisible |\n| 5 | Configure constraints (LAUNCH, TAG_UPDATE, STACK_UPDATE, NOTIFICATION) | Yes | no LAUNCH = end-user deploys as themselves |\n| 6 | Configure TagOptions + bind to portfolio\u002Fproducts | Yes | no TagOptions = ungoverned tagging |\n| 7 | Configure launch paths + portfolio shares (account, OU, org) | Yes | wrong share target = governance gap |\n| 8 | Verify via `search-products` + `describe-portfolio` + emit checklist | — | silent no-ops |\n\n**Critical ordering constraints:** portfolio exists before products\n(products need a parent association); products created with their\ninitial provisioning artifact before constraints (constraints\nreference product IDs); launch role created before the LAUNCH\nconstraint (the constraint references `RoleArn`); TagOptions bound\nbefore sharing (so consumers inherit tag policy on launch); shares\nconfigured last (sharing an unconstrained portfolio exposes the\ngovernance gap immediately). Rationale and the silent-failure table\nare below.\n\n## Activation keywords\n\nService Catalog portfolio, Service Catalog product, provisioning\nartifact, product version, launch constraint, stack-based constraint,\ntemplate-based constraint, tag-update constraint, notification\nconstraint, launch path, portfolio share, organizational sharing,\nTagOptions, self-service launchpad, CloudFormation product, Service\nApp Registry, Service Catalog Terraform, delegated administrator.\n\n## Invocation contract (hard requirement)\n\nWhen this skill is invoked with a Service Catalog portfolio\nprovisioning request, the agent MUST respond with the checklist\ndefined in §\"STRICT output contract\" using the literal all-caps labels\n`PORTFOLIO:`, `VERDICT:`, `CHECKLIST:`, and `VERIFICATION_COMMANDS:`.\nDo NOT preface with prose, headings, or disclaimers — emit the block\nas the 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\n## Reasoning framework (why the provisioning order matters)\n\nService Catalog looks like \"publish a portfolio of templates\" but the\nunderlying model has four traps:\n\n1. **The LAUNCH constraint determines the role that provisions the\n   product — not the launching user's role.** Without a LAUNCH\n   constraint, CloudFormation deploys using the launching user's\n   permissions. That means an operator with broad IAM can launch a\n   VPC, an IAM role, a Lambda — anything their role allows — and the\n   resource belongs to them, not the central governance team. The\n   LAUNCH constraint pins the provisioning to a specific role\n   (typically a role with only the product's required permissions),\n   regardless of who launches it. This is the central governance\n   primitive of Service Catalog.\n\n2. **Two constraint scoping models exist: STACK-based and TEMPLATE-\n   based.** A STACK-based launch constraint passes the same role for\n   every launch of the product. A TEMPLATE-based launch constraint\n   applies a rules engine to choose the role per-launch (e.g., based\n   on the launching user's team). Template-based constraints are\n   powerful but rarely used; the canonical pattern is STACK-based with\n   one role per product family. Mixing them silently degrades to\n   STACK-based when the template engine produces no match.\n\n3. **Portfolio shares are region-scoped.** Sharing a portfolio with an\n   Organization account does NOT make the portfolio visible in other\n   regions. A share in us-east-1 is invisible to a user in eu-west-1\n   unless they switch regions in the console. For multi-region\n   deployments, replicate the portfolio per region or document the\n   region expectation explicitly.\n\n4. **TagOptions are NOT Service Control Policies.** TagOptions are a\n   \"suggested tags\" mechanism: when a user launches a product\n   associated with a TagOption, the tag is pre-populated in the launch\n   wizard. The user can change the value or remove the tag entirely\n   (unless TAG_UPDATE constraint is set to `NOT_ALLOWED`). TagOptions\n   do not enforce tagging; they suggest it. Enforce tagging via SCP\n   on the organization or via a CloudFormation-backed tag policy.\n\nThe procedure below sequences the steps to surface these traps.\n\n## Dependency graph (silent-failure table)\n\n| Configuration | Hard dependencies (API error without) | Silent failure mode (returns 200, does nothing useful) | Enables downstream |\n|---|---|---|---|\n| Portfolio | unique DisplayName | **portfolio with same DisplayName in different accounts creates duplicate invisible inventories** | container for products |\n| Product (CLOUDFORMATION_TEMPLATE) | valid CloudFormation URL | **product with broken template URL launches OK, fails at stack create with no alarm** | launchable item |\n| Provisioning artifact (version) | semantic version string | **two artifacts with same version silently overwrites \"active\" flag; old version invisible** | versioned launches |\n| Product-portfolio association | product ID + portfolio ID | **unassociated product silently invisible to portfolio users** | product visibility |\n| LAUNCH constraint (STACK-based) | valid RoleArn (PassRole) | **no LAUNCH constraint = CloudFormation deploys as the end-user's role = privilege escalation risk** | governance |\n| LAUNCH constraint (TEMPLATE-based) | template rules engine | **template rule that matches no role silently degrades to no constraint = end-user role** | conditional governance |\n| TAG_UPDATE constraint | product ID | **default allows tag changes post-launch — TagOptions suggested at launch can be removed** | tag immutability |\n| NOTIFICATION constraint | SNS ARN | **SNS topic with no subscribers = notifications silently lost** | launch tracking |\n| TagOption | unique key+value | **TagOption not associated with portfolio = never applied at launch** | governed tagging |\n| Launch path | local account by default | **no launch path in shared account = portfolio visible but unlaunchable** | cross-account launching |\n| Portfolio share (account-level) | account ID | **share to wrong account ID = silent invisible; no error, no usage** | cross-account visibility |\n| Portfolio share (org-level) | Organizations `servicecatalog:enable` | **share without delegated admin = recipients see portfolio but cannot manage** | centralized catalog |\n| Portfolio share (OU-level) | OU ID | **share to OU root vs. OU child silently changes recipient set** | scoped distribution |\n| App Registry association | application exists | **application deleted after association = association silently inert** | application inventory |\n\n**The four most dangerous silent-failure rows** are no-LAUNCH-\nconstraint, TEMPLATE-based-no-match-degradation, region-scoped-share-\nvisibility, and TagOptions-not-associated. All return success on the\nAPI call; the failure surfaces only when a product is launched\nwithout governance or a user cannot find the portfolio. Step 5\n(LAUNCH constraint), Step 7 (sharing with region\u002Fdelegated-admin\nverification), and Step 8 (`search-products` + `describe-portfolio`\nas the recipient account) are non-negotiable for any production-\nadjacent portfolio.\n\n## Expert heuristic: the no-LAUNCH-constraint myth\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#expert-heuristic-the-no-launch-constraint-myth).\n> Operator-expectation vs actual-behavior comparison and the one-launch-role-per-product-family remedy.\n\n## Expert heuristic: portfolio share region quirk\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#expert-heuristic-portfolio-share-region-quirk).\n> Region-scoped shares: create-portfolio-share has no region parameter; three multi-region remedies (StackSets replication, documented region expectation, custom launcher).\n\n## Expert heuristic: TagOptions vs. SCPs vs. TAG_UPDATE constraint\n\nThree independent mechanisms govern tags on Service Catalog-launched\nproducts. Operators frequently conflate them.\n\n- **TagOptions** (suggested): when a user launches a product\n  associated with a TagOption, the tag is pre-populated in the launch\n  wizard. The user can change the value or remove the tag.\n- **TAG_UPDATE constraint (`NOT_ALLOWED`)**: prevents the user from\n  modifying the tags on the launched product's CloudFormation stack\n  after launch. It does NOT prevent modification at launch time —\n  only post-launch.\n- **SCP \u002F tag policy on the organization**: enforces tag compliance\n  across the entire account, including Service Catalog launches. This\n  is the only one of the three that can enforce a tag value at launch\n  time.\n\nFor true tag governance, use all three: TagOptions to suggest, TAG_\nUPDATE constraint to lock post-launch, and SCP to enforce at the\ncontrol-plane layer.\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting any provisioning command, verify these prerequisites.\nIf any are missing, the verdict is **PREREQUISITES_MISSING** with a\nspecific gap citation.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| Caller IAM | `servicecatalog:CreatePortfolio`, `iam:CreateRole`, `iam:PassRole` required | `aws sts get-caller-identity` + IAM policy check |\n| CloudFormation template URL resolvable | Broken URL = launch failure at consumer time | `aws cloudformation validate-template --template-url \u003CURL>` |\n| Launch role exists (for LAUNCH constraint) | Constraint references RoleArn | `aws iam get-role --role-name \u003Cname>` |\n| Organizations enabled (for org\u002FOU shares) | Org-level share requires Organizations | `aws organizations describe-organization` |\n| Service Catalog delegated admin (for cross-account) | Recipients can view but not manage without it | `aws organizations list-delegated-administrators --service-principal servicecatalog.amazonaws.com` |\n| SNS topic exists (for NOTIFICATION constraint) | Constraint references SNS ARN | `aws sns get-topic-attributes --topic-arn \u003Carn>` |\n| Tag keys (for TagOptions) | TagOption key must exist before associating | `aws servicecatalog list-tag-options` |\n| Region of share matches consumer region | Shares are region-scoped | Caller region matches target user's region |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## 8-step provisioning procedure\n\n### Step 1 — Confirm portfolio intent + consumer scope\n\nBefore any resource lookup, name the intent in one sentence:\n\"distribute a curated S3-bucket product to all organization accounts\nfor analytics workloads,\" or \"self-service launchpad for the\nplatform team in this account only.\" The intent drives the share\ntarget, the launch role scope, and the constraint set.\n\n### Step 2 — Create portfolio\n\n```bash\naws servicecatalog create-portfolio \\\n  --display-name \"Curated S3 Products\" \\\n  --provider-name \"Platform Governance\" \\\n  --description \"S3-bucket products for analytics workloads. Launch role scoped to s3:* only. Region: us-east-1.\" \\\n  --tags Key=Owner,Value=platform-governance\n```\n\nThe `description` field is searchable in the consumer console —\ninclude the region, the launch-role summary, and the intended consumer\nscope. Missing description = consumers cannot find the portfolio.\n\n### Step 3 — Create products + provisioning artifacts\n\n> Moved to [references\u002Fprovisioning-cli-commands.md](references\u002Fprovisioning-cli-commands.md#step-3--create-products--provisioning-artifacts-cli).\n> create-product with provisioning-artifact-parameters and create-provisioning-artifact for new versions.\n\nA provisioning artifact is a version. Multiple versions can coexist;\nconsumers pick one at launch. The \"active\" version is the default;\nolder versions remain launchable for rollback.\n\n**Common mistake:** using `LoadTemplateFromURL` with a private S3\nURL. The URL must be accessible to Service Catalog (presigned or\npublic-read). A private URL launches OK but fails at stack-create\ntime with no alarm.\n\n### Step 4 — Associate products with the portfolio\n\n```bash\naws servicecatalog associate-product-with-portfolio \\\n  --product-id $PRODUCT_ID \\\n  --portfolio-id $PORTFOLIO_ID\n```\n\nA product not associated with any portfolio is silently invisible to\nall consumers — even the administrator. Association is what makes the\nproduct available inside the portfolio.\n\n**Common mistake:** creating the product but forgetting the\nassociation. The product appears in `search-products-as-admin` but\nnot in `search-products` (the consumer-facing API).\n\n### Step 5 — Configure constraints (LAUNCH, TAG_UPDATE, NOTIFICATION)\n\n> Moved to [references\u002Fconstraint-and-launch-role-templates.md](references\u002Fconstraint-and-launch-role-templates.md#step-5--configure-constraints-creation-cli).\n> Launch-role creation (iam create-role \u002F put-role-policy) and LAUNCH create-constraint CLI.\n\nConstraint types:\n\n| Type | Effect | Required? |\n|---|---|---|\n| `LAUNCH` | CloudFormation assumes the specified role at launch (not the user's role) | YES — without this, end-user permissions apply |\n| `TAG_UPDATE` | `NOT_ALLOWED` blocks tag changes to the launched stack post-launch | Recommended |\n| `STACK_UPDATE` | `NOT_ALLOWED` blocks updates to the launched stack post-launch (immutable launches) | Optional |\n| `NOTIFICATION` | Sends SNS notifications for launch\u002Fupdate\u002Fterminate events | Recommended for audits |\n| `LAUNCH_PERMISSION` | Limits who can launch the product (via principal ARNs) | Optional |\n\n**Common mistake:** using a `TEMPLATE`-type launch constraint without\ntesting the rules engine. A template rule that matches no role\nsilently degrades to no constraint — the end-user's role is used.\n\n### Step 6 — Configure TagOptions + bind to portfolio\u002Fproducts\n\n> Moved to [references\u002Fsharing-and-tagoptions-procedures.md](references\u002Fsharing-and-tagoptions-procedures.md#step-6--configure-tagoptions-cli).\n> create-tag-option and associate-tag-option-with-resource CLI.\n\nBind TagOptions at the portfolio level (inherited by all products in\nthe portfolio) or at the product level (product-specific). Portfolio-\nlevel TagOptions propagate to every product on launch.\n\n### Step 7 — Configure launch paths + portfolio shares\n\n**Local account launch path** is implicit — no configuration needed.\nThe portfolio is launchable by users in the source account (subject\nto IAM).\n\n> Moved to [references\u002Fsharing-and-tagoptions-procedures.md](references\u002Fsharing-and-tagoptions-procedures.md#step-7--launch-paths--portfolio-shares-cli).\n> Account-, organization-, and OU-level create-portfolio-share CLI plus Organizations enable-aws-service-access.\n\n**Common mistake:** sharing to the organization root vs. the\norganization ID. `Type=ORGANIZATION` shares to every account in the\norg; `Type=ORGANIZATIONAL_UNIT` with the OU root ID shares to a\nsubset. Confirm the recipient set explicitly.\n\n### Step 8 — Verify via `search-products` + `describe-portfolio`\n\n> Moved to [references\u002Fsharing-and-tagoptions-procedures.md](references\u002Fsharing-and-tagoptions-procedures.md#step-8--verification-cli).\n> Verification CLI: describe-portfolio, search-products-as-admin, describe-constraint, consumer search-products.\n\nCross-account verification is critical: a share that looks successful\nfrom the source account may be invisible in the consumer account due\nto region mismatch, missing delegated admin, or IAM scoping.\n\n## NEVER do these things\n\nThese anti-patterns cause privilege escalation, governance gaps, or\nsilent no-ops. Each is observed in real production incidents.\n\n1. **NEVER publish a product without a LAUNCH constraint.** Why it's\n   wrong: without a LAUNCH constraint, CloudFormation assumes the\n   launching user's role. An operator with PowerUserAccess launches a\n   powerful product and deploys resources owned by their individual\n   role. Central governance has no visibility until audit time. Always\n   configure a STACK-based LAUNCH constraint with a least-privilege\n   role scoped to the product's required permissions.\n\n2. **NEVER use a TEMPLATE-based LAUNCH constraint without testing the\n   rules engine against every consumer path.** Why it's wrong: a\n   template rule that matches no role silently degrades to no\n   constraint. The end-user's role is used. The remediation is to\n   fall back to STACK-based constraints with a default role, and to\n   unit-test template rules with every consumer persona before\n   deployment.\n\n3. **NEVER share a portfolio at the organization root when you mean\n   an OU subset.** Why it's wrong: `Type=ORGANIZATION` shares to every\n   account in the org, including Sandbox, Security, and Audit\n   accounts. Use `Type=ORGANIZATIONAL_UNIT` with a specific OU ID,\n   and document the recipient set in the portfolio description.\n\n4. **NEVER assume a portfolio share is multi-region.** Why it's\n   wrong: shares are region-scoped to the caller's region. A share\n   from us-east-1 is invisible in eu-west-1. For multi-region\n   deployments, replicate the portfolio via CloudFormation StackSets\n   or document the region expectation explicitly.\n\n5. **NEVER use TagOptions as the only tag-governance mechanism.** Why\n   it's wrong: TagOptions are suggestions, not enforcement. A user\n   can remove a suggested tag at launch or post-launch (unless TAG_\n   UPDATE constraint is set). For true tag governance, combine\n   TagOptions, TAG_UPDATE constraint, and an SCP\u002Ftag policy at the\n   organization level.\n\n## Output format\n\n```\nPORTFOLIO: \u003Cdisplay-name> (products: \u003Ccount>, shares: \u003Crecipient-summary>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Intent + consumer scope: \u003Cone-sentence intent>, scope \u003Clocal|account|OU|org>\n  [✓|✗] Portfolio created: \u003Cdisplay-name> by \u003CProviderName> (\u003Cregion>)\n  [✓|✗] Product(s): \u003Ccount> products, \u003Ccount> provisioning artifacts (versions)\n  [✓|✗] Product-portfolio association: \u003Ccount> associations\n  [✓|✗] Constraint(s): LAUNCH \u003Crole-name> (STACK-based), TAG_UPDATE \u003Cvalue>, NOTIFICATION \u003Csns-name>\n  [✓|✗] TagOptions: \u003Ccount> key-value pairs bound at portfolio level\n  [✓|✗] Share(s): \u003Crecipient-summary> (region: \u003Ccaller-region>, delegated admin: \u003Ctrue|false>)\nVERIFICATION_COMMANDS:\n  \u003Ccopy-pasteable verification commands>\n```\n\n## STRICT output contract\n\nThe rules below are hard constraints. Violating any one produces a\nchecklist that looks complete but contains a silent misconfiguration.\nSelf-check EVERY emitted block against these rules before returning.\n\n### Required output structure\n\nEvery response MUST be a single block using these literal labels, in\nthis order. Do NOT preface with prose, headings, or disclaimers.\n\n```text\nPORTFOLIO: \u003Cdisplay-name> (products: \u003Ccount>, shares: \u003Crecipient-summary>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Intent + consumer scope: \u003Cone-sentence intent>, scope \u003Clocal|account|OU|org>\n  [✓|✗] Portfolio created: \u003Cdisplay-name> by \u003CProviderName> (\u003Cregion>)\n  [✓|✗] Product(s): \u003Ccount> products, \u003Ccount> provisioning artifacts (versions)\n  [✓|✗] Product-portfolio association: \u003Ccount> associations\n  [✓|✗] Constraint(s): LAUNCH \u003Crole-name> (STACK-based), TAG_UPDATE \u003Cvalue>, NOTIFICATION \u003Csns-name>\n  [✓|✗] TagOptions: \u003Ccount> key-value pairs bound at portfolio level\n  [✓|✗] Share(s): \u003Crecipient-summary> (region: \u003Ccaller-region>, delegated admin: \u003Ctrue|false>)\nVERIFICATION_COMMANDS:\n  \u003Ccopy-pasteable verification commands — one per [✓] item>\n```\n\n### FORBIDDEN output patterns\n\n1. **NEVER emit `VERDICT: READY_TO_DEPLOY` without showing ALL 7\n   checklist items.** Every item MUST appear with a status marker:\n   `[✓]`, `[✗]`, or `[OPTIONAL]`. Omitting a row implies it was not\n   evaluated.\n\n2. **NEVER mark Constraint(s) `[✓] LAUNCH` without citing the role\n   name AND confirming it is STACK-based (or TEMPLATE-based with a\n   tested default fallback).** A LAUNCH constraint with no role ARN\n   silently falls back to the end-user's role — privilege escalation.\n   The checklist MUST cite the role name and the constraint scoping\n   model.\n\n3. **NEVER mark Share(s) `[✓]` without citing the recipient scope\n   (ORGANIZATION, ORGANIZATIONAL_UNIT, ACCOUNT) AND the caller\n   region.** Region mismatch is the leading cause of \"portfolio\n   invisible in consumer account\" tickets. The checklist MUST cite\n   both.\n\n4. **NEVER mark TagOptions `[✓]` without citing the binding level\n   (portfolio vs. product).** Portfolio-level TagOptions propagate to\n   every product; product-level TagOptions are scoped. Mixing them\n   silently produces inconsistent tagging.\n\n5. **NEVER mark Product(s) `[✓]` without citing the provisioning\n   artifact count AND the active version.** A product with one\n   provisioning artifact has no rollback; a product with multiple\n   untagged artifacts is ambiguous at launch.\n\n6. **NEVER emit `VERDICT: PREREQUISITES_MISSING` without citing the\n   specific gap.** Each `[✗]` item MUST have a one-line reason:\n   `[✗] Share(s): Organizations not enabled — enable\n   enable-aws-service-access for servicecatalog.amazonaws.com before\n   sharing`. A bare `[✗]` is non-compliant.\n\n7. **NEVER include `TEMPLATE`-type LAUNCH constraint in the checklist\n   without a `[WARN]` note.** Template-based constraints silently\n   degrade to no constraint when no rule matches. The checklist MUST\n   cite the fallback role or mark the item `[✗]`.\n\n### Perfect example output — READY_TO_DEPLOY\n\n```text\nPORTFOLIO: Curated S3 Products (products: 1, shares: ou-abc1-abcdef in us-east-1)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Intent + consumer scope: Distribute a curated S3-bucket product to platform-team OU for analytics workloads, scope OU\n  [✓] Portfolio created: Curated S3 Products by Platform Governance (us-east-1)\n  [✓] Product(s): 1 product (Curated S3 Bucket), 2 provisioning artifacts (v1.0.0 active, v1.1.0)\n  [✓] Product-portfolio association: 1 association (Curated S3 Bucket -> Curated S3 Products)\n  [✓] Constraint(s): LAUNCH sc-launch-s3-role (STACK-based, scoped to s3:* + iam:PassRole with tag condition), TAG_UPDATE NOT_ALLOWED, NOTIFICATION sc-launch-events SNS topic\n  [✓] TagOptions: 2 key-value pairs bound at portfolio level (CostCenter=platform-1234, Owner=platform-governance)\n  [✓] Share(s): ORGANIZATIONAL_UNIT ou-abc1-abcdef (region: us-east-1, delegated admin: enabled)\nVERIFICATION_COMMANDS:\n  aws servicecatalog describe-portfolio --id port-aaaa1111\n  aws servicecatalog search-products-as-admin --portfolio-id port-aaaa1111\n  aws servicecatalog describe-constraint --id cons-bbbb2222\n  aws servicecatalog list-tag-options\n  aws servicecatalog list-portfolio-access --portfolio-id port-aaaa1111\n  aws organizations list-delegated-administrators --service-principal servicecatalog.amazonaws.com\n```\n\n### Perfect example output — PREREQUISITES_MISSING\n\n> Moved to [references\u002Fworked-examples.md](references\u002Fworked-examples.md#perfect-example-output--prerequisites_missing).\n> PREREQUISITES_MISSING block: org-level share without Organizations enabled and no launch role, gaps cited.\n\n**Self-check before emit:**\n- [ ] All 7 checklist rows present (no omitted items)?\n- [ ] Every `[✓]` has a matching verification command?\n- [ ] LAUNCH constraint cites role name + scoping model?\n- [ ] Share(s) cite recipient scope AND caller region?\n- [ ] TagOptions cite binding level (portfolio vs. product)?\n- [ ] Product(s) cite provisioning artifact count + active version?\n- [ ] Every `[✗]` cites the specific gap?\n- [ ] TEMPLATE-type LAUNCH constraint (if present) carries a `[WARN]`?\n\n## Recent AWS features\n\n> Moved to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md#recent-aws-features).\n> Terraform Open Source\u002FCloud products, App Registry association, StackSets products, TagOption inheritance, delegated admin, SourceProduct copy.\n\n## References (load on demand)\n\n- [advanced-patterns](references\u002Fadvanced-patterns.md) — No-LAUNCH-constraint myth deep dive, recent AWS features (Terraform, App Registry, StackSets, delegated admin)\n- [worked-examples](references\u002Fworked-examples.md) — Perfect PREREQUISITES_MISSING example output\n- [provisioning-cli-commands](references\u002Fprovisioning-cli-commands.md) — Product and provisioning-artifact creation CLI (Step 3)\n- [constraint-and-launch-role-templates](references\u002Fconstraint-and-launch-role-templates.md) — Constraint JSON, launch-role policies, constraint creation commands (incl. Step 5 CLI)\n- [sharing-and-tagoptions-procedures](references\u002Fsharing-and-tagoptions-procedures.md) — Sharing, TagOptions, App Registry, verification procedures (incl. Steps 6-8 CLI)\n\n## AWS documentation\n\n- **AWS Service Catalog Administrator Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fservicecatalog\u002Flatest\u002Fadminguide\u002Fintroduction.html\n- **Service Catalog Portfolios** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fservicecatalog\u002Flatest\u002Fadminguide\u002Fcatalogs_portfolios.html\n- **Service Catalog Products** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fservicecatalog\u002Flatest\u002Fadminguide\u002Fcatalogs_products.html\n- **Service Catalog Constraints** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fservicecatalog\u002Flatest\u002Fadminguide\u002Fconstraints.html\n- **Service Catalog Launch Constraints** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fservicecatalog\u002Flatest\u002Fadminguide\u002Fconstraints-launch.html\n- **Service Catalog TagOptions** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fservicecatalog\u002Flatest\u002Fadminguide\u002Ftagoptions.html\n- **Service Catalog Portfolio Sharing** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fservicecatalog\u002Flatest\u002Fadminguide\u002Fcatalogs_portfolios_sharing.html\n- **Service Catalog API Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fservicecatalog\u002Flatest\u002Fdg\u002Fwelcome.html\n- **Service Catalog CLI Reference** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fcli\u002Flatest\u002Freference\u002Fservicecatalog\u002F\n- **Blog: Service Catalog + Terraform Open Source** — https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fmt\u002Fannouncing-aws-service-catalog-support-for-terraform-open-source\u002F\n- **Workshop: Service Catalog** — https:\u002F\u002Fcatalog.workshops.aws\u002Fservicecatalog\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":43},{"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,"invocation_schema":41,"supports_pipeline":38,"activation_triggers":42},"aws, service-catalog, portfolio, product, launch-constraint, tagoptions, governance, deploy","1","Jacky Chan — AWS Community Builder","aws-cloudops","Governance","0.1.0","aws, service catalog, portfolio, product, provisioning artifact, launch constraint, stack-based constraint, template-based constraint, tag-update constraint, notification constraint, launch path, portfolio share, organizational sharing, tagoptions, self-service launchpad, cloudformation product, product versioning, service app registry, cloudops, deploy","deploy","high","false","capability","Provisioning a Service Catalog portfolio for self-service product distribution; creating a product from a CloudFormation template; applying constraints (launch role, tag update, stack update, notification); configuring launch paths for a local account or sharing a portfolio via AWS Organizations; setting up TagOptions for governed tag application; integrating Service Catalog with Service App Registry for application inventory tagging; or provisioning Service Catalog with Terraform Open Source. Do NOT invoke for launching a product instance (use the appropriate operate skill), for AWS Marketplace integration (separate workflow), or for non-Service-Catalog CloudFormation deployment.","aws-orchestrator","true","READY_TO_DEPLOY | PREREQUISITES_MISSING","active","Input: either (a) a portfolio spec including DisplayName, ProviderName, products (name + CloudFormation URL + version), constraints, launch paths, TagOptions, and sharing target; or (b) a partial spec for interactive refinement (e.g., \"Service Catalog portfolio with a curated S3-bucket product and a launch role\"). Output: a deterministic PORTFOLIO \u002F VERDICT \u002F CHECKLIST \u002F VERIFICATION_COMMANDS block per the STRICT output contract, where VERDICT is READY_TO_DEPLOY or PREREQUISITES_MISSING.","Service Catalog portfolio, Service Catalog product, launch constraint, stack-based constraint, template-based constraint, tag-update constraint, notification constraint, launch path, portfolio share, organizational sharing, TagOptions, self-service launchpad, CloudFormation product, product versioning, Service App Registry, Service Catalog Terraform","Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). Live provisioning uses AWS CLI v2 with servicecatalog (create-portfolio, create-product, create-constraint, associate-product-with-portfolio, create-portfolio-share, create-tag-option, associate-tag-option-with-resource), cloudformation (validate-template), iam (create-role, pass-role), sns (create-topic), and organizations (enable-aws-service-access, list-delegated-administrators). Works with Terraform...","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Fservice-catalog-portfolio-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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add jhkchan\u002Faws-agent-skills --skill service-catalog-portfolio-deployer",{"tool":58,"command":59},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill service-catalog-portfolio-deployer",{"tool":61,"command":62},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill service-catalog-portfolio-deployer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fservice-catalog-portfolio-deployer\u002FSKILL.md",true,[66,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136,140,144],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",6266,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fservice-catalog-portfolio-deployer\u002Feval\u002Ftest-cases.yaml",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"evals\u002Fbaselines\u002Fcross-region-share-visibility-check.md",1412,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fservice-catalog-portfolio-deployer\u002Fevals\u002Fbaselines\u002Fcross-region-share-visibility-check.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"evals\u002Fbaselines\u002Fmissing-launch-role-rejected.md",1250,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fservice-catalog-portfolio-deployer\u002Fevals\u002Fbaselines\u002Fmissing-launch-role-rejected.md",{"path":81,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":82,"sourceHtmlUrl":83},"evals\u002Fbaselines\u002Fou-share-with-delegated-admin.md",1380,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fservice-catalog-portfolio-deployer\u002Fevals\u002Fbaselines\u002Fou-share-with-delegated-admin.md",{"path":85,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":86,"sourceHtmlUrl":87},"evals\u002Fbaselines\u002Fs3-product-local-account-with-constraints.md",1170,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fservice-catalog-portfolio-deployer\u002Fevals\u002Fbaselines\u002Fs3-product-local-account-with-constraints.md",{"path":89,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":90,"sourceHtmlUrl":91},"evals\u002Fbaselines\u002Fterraform-open-source-product.md",1217,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fservice-catalog-portfolio-deployer\u002Fevals\u002Fbaselines\u002Fterraform-open-source-product.md",{"path":93,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":94,"sourceHtmlUrl":95},"evals\u002Feval_config.yaml",1923,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fservice-catalog-portfolio-deployer\u002Fevals\u002Feval_config.yaml",{"path":97,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":98,"sourceHtmlUrl":99},"evals\u002Fevals.json",13432,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fservice-catalog-portfolio-deployer\u002Fevals\u002Fevals.json",{"path":101,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":102,"sourceHtmlUrl":103},"evals\u002Fprompts\u002Fcross-region-share-visibility-check.md",546,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fservice-catalog-portfolio-deployer\u002Fevals\u002Fprompts\u002Fcross-region-share-visibility-check.md",{"path":105,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":106,"sourceHtmlUrl":107},"evals\u002Fprompts\u002Fmissing-launch-role-rejected.md",446,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fservice-catalog-portfolio-deployer\u002Fevals\u002Fprompts\u002Fmissing-launch-role-rejected.md",{"path":109,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":110,"sourceHtmlUrl":111},"evals\u002Fprompts\u002Fou-share-with-delegated-admin.md",699,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fservice-catalog-portfolio-deployer\u002Fevals\u002Fprompts\u002Fou-share-with-delegated-admin.md",{"path":113,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":114,"sourceHtmlUrl":115},"evals\u002Fprompts\u002Fs3-product-local-account-with-constraints.md",893,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fservice-catalog-portfolio-deployer\u002Fevals\u002Fprompts\u002Fs3-product-local-account-with-constraints.md",{"path":117,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":118,"sourceHtmlUrl":119},"evals\u002Fprompts\u002Fterraform-open-source-product.md",558,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fservice-catalog-portfolio-deployer\u002Fevals\u002Fprompts\u002Fterraform-open-source-product.md",{"path":121,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":122,"sourceHtmlUrl":123},"example\u002FREADME.md",8927,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fservice-catalog-portfolio-deployer\u002Fexample\u002FREADME.md",{"path":125,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":126,"sourceHtmlUrl":127},"references\u002Fadvanced-patterns.md",4693,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fservice-catalog-portfolio-deployer\u002Freferences\u002Fadvanced-patterns.md",{"path":129,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":130,"sourceHtmlUrl":131},"references\u002Fconstraint-and-launch-role-templates.md",7522,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fservice-catalog-portfolio-deployer\u002Freferences\u002Fconstraint-and-launch-role-templates.md",{"path":133,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":134,"sourceHtmlUrl":135},"references\u002Fprovisioning-cli-commands.md",889,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fservice-catalog-portfolio-deployer\u002Freferences\u002Fprovisioning-cli-commands.md",{"path":137,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":138,"sourceHtmlUrl":139},"references\u002Fsharing-and-tagoptions-procedures.md",9179,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fservice-catalog-portfolio-deployer\u002Freferences\u002Fsharing-and-tagoptions-procedures.md",{"path":141,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":142,"sourceHtmlUrl":143},"references\u002Fworked-examples.md",1527,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fservice-catalog-portfolio-deployer\u002Freferences\u002Fworked-examples.md",{"path":145,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":146,"sourceHtmlUrl":147},"skill.usf.yaml",4644,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fservice-catalog-portfolio-deployer\u002Fskill.usf.yaml",[149,156,163,170,177,184],{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"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":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"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":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"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":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"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":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"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":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":190,"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",[],[]]