adobe-create-mockups · OpenAI · Codex
로고나 스케치를 티셔츠·머그컵 같은 제품 장면에 시각화합니다.
로고가 파일 안에서만 보일 때 실제 제품에 적용한 모습을 상상하기 어렵습니다. 이 스킬은 티셔츠나 머그컵 같은 장면에 디자인을 넣어 목업으로 확인하는 작업에 사용합니다.
로고와 제품 종류, 원하는 장면을 전달해보세요. 배치와 크기를 비교할 수 있는 시각물을 받아 제작 방향을 정하거나 소개 자료에 활용할 수 있습니다.
“이 로고를 흰 머그컵에 적용한 목업을 만들어줘. 정면과 약간 돌린 모습을 비교해 로고 크기를 정하고 싶어.”
받을 수 있는 결과제품 목업 이미지
Codex와 해당 플러그인이 필요합니다. 연결형 스킬은 대상 앱 계정과 접근 권한을 준비하세요. 포함 플러그인: adobe. Adobe 로그인과 일부 생성 기능의 크레딧 조건을 확인하세요.
앱 연결·MCP·보조 파일이 포함된 플러그인이에요. 아래 SKILL.md는 동작을 읽어보는 용도로도 사용할 수 있지만, 파일 하나로 앱 연결이 설치되지는 않아요.
Codex의 Plugins에서 adobe에 해당하는 플러그인을 찾아 설치하세요. 제공되는 연결 앱과 권한을 설정한 뒤 새 세션에서 adobe-create-mockups 작업을 요청하세요. 목록에 없다면 제작자 저장소의 plugins/adobe/ 구성과 설치 안내를 확인하세요. 연결된 서비스의 요금은 해당 서비스 정책을 따릅니다.
“adobe-create-mockups 스킬을 사용해줘. 입력 자료: 로고·제품 종류·참고 장면”처럼 요청하세요. 위의 예시를 내 자료에 맞게 바꿔도 좋아요.
예상 결과는 ‘제품 목업 이미지’입니다. 필요한 내용이 포함됐는지 확인하세요. 입력 자료의 사실·숫자와 결과를 대조하고, 부족한 부분을 이어서 요청하세요.
제작자 원본 2026-10-04 확인 · 설치 안내 2026-10-04 확인 · 실제 설치·실행 미검증
모델 사용 요금과 연결 앱 요금은 이용 중인 서비스의 정책을 따릅니다.
설치 안내 출처--- name: adobe-create-mockups description: > Use when a user wants to see their logo, design, or sketch on a product or scene mockup — mugs, t-shirts, business cards, hats, phone screens, posters, billboards, or similar. Triggers on "create mockups", "show my logo on products", or any logo upload with a request to visualize it on items. Access: 🔐 Signed-In required | Gen AI: ✅ Adobe Firefly via `image_generate` used for design creation, sketch polishing, and mockup scene generation allowed-tools: adobe_mandatory_init asset_share_link boards_add_items_to_board boards_create_new_board image_generate license: Apache-2.0 metadata: version: 0.1.0 visibility: public surface: [codex] --- # Create Mockups Takes a logo sketch, clean logo image, or broader design asset and produces a suite of product mockups styled to a desired brand vibe. The design is always passed to `image_generate` as a reference image — never described in text as a substitute. Uses progressive checkpoints to validate scene direction before committing to the full set. --- ## Tool Reference | Step | Tool | Notes | |------|------|-------| | 0 | `adobe_mandatory_init` | File-handling and routing rules; call first | | 1 - 5 | `image_generate` | Generate designs from scratch, polish sketches into clean logos with `referenceImage`, and generate mockup scenes with the design as `referenceImage`. See **`image_generate` Call Rules** below. |--- name: adobe-create-mockups description: > Use when a user wants to see their logo, design, or sketch on a product or scene mockup — mugs, t-shirts, business cards, hats, phone screens, posters, billboards, or similar. Triggers on "create mockups", "show my logo on products", or any logo upload with a request to visualize it on items. Access: 🔐 Signed-In required | Gen AI: ✅ Adobe Firefly via `image_generate` used for design creation, sketch polishing, and mockup scene generation allowed-tools: adobe_mandatory_init asset_share_link boards_add_items_to_board boards_create_new_board image_generate license: Apache-2.0 metadata: version: 0.1.0 visibility: public surface: [codex] --- # Create Mockups Takes a logo sketch, clean logo image, or broader design asset and produces a suite of product mockups styled to a desired brand vibe. The design is always passed to `image_generate` as a reference image — never described in text as a substitute. Uses progressive checkpoints to validate scene direction before committing to the full set. --- ## Tool Reference | Step | Tool | Notes | |------|------|-------| | 0 | `adobe_mandatory_init` | File-handling and routing rules; call first | | 1 - 5 | `image_generate` | Generate designs from scratch, polish sketches into clean logos with `referenceImage`, and generate mockup scenes with the design as `referenceImage`. See **`image_generate` Call Rules** below. | | 7 | `boards_create_new_board` | create a Firefly Board and return its `boardId` | | 7 | `boards_add_items_to_board` | add final mockup images to the Firefly Board | | 7 | `asset_share_link` | convert the returned Firefly Board `boardId` into a shareable Firefly Board URL | ### `image_generate` Call Rules - Pass all generation settings inside `options`. - Use `options.referenceImage: "<designAssetUrl>"` whenever generating from an uploaded or previously generated design. - Do not combine `referenceImage` with `aspectRatio` or `size`; express the intended composition in the prompt instead. - Use `outputFileType: "png"` unless the user explicitly requests JPEG. --- ## High-Level Pipeline 1. **Get the design** — If no design was provided, ask to upload or create one from scratch 2. **Brand profile** — Infer brand direction from the design and only ask for missing output choices 3. **Review design** *(sketches and unclear designs only)* — Ask whether to use as-is or polish first; skip for clean digital assets 4. **Pilot mockup** — Generate one mockup to validate scene direction → **get approval before continuing** 5. **Generate remaining mockups** — Complete the full set (max 5 per turn) 6. **Deliver** — Display all mockups inline with iteration options 7. **Firefly Board** — Create a Firefly Board, add the final mockup images, and return the shareable board link --- ## Workflow ### Step 0: Initialize Adobe Tools Call `adobe_mandatory_init` first. This returns file handling rules and tool routing guidance required for the rest of the workflow. ```json { "skill_name": "adobe-create-mockups", "skill_version": "0.1.0" } ``` --- ### Step 1: Get the Design If the user already provided a design asset in their message, skip this step and proceed to Step 2. If no design was provided: ``` ask_user_question({ questions: [{ question: "Do you already have a logo or design, or would you like to create one?", header: "Design", multiSelect: false, options: [ { label: "Upload my design", description: "I have a logo or design ready to use" }, { label: "Create a design", description: "Help me design something from scratch" } ] }] }) ``` - **Upload my design** → User uploads their design. Proceed to Step 2. - **Create a design** → Ask what they're envisioning (brand name, style, colors, any inspiration). Generate using `image_generate`, show the result, and iterate until they're happy. Use the approved generation URL as `designAssetUrl`. Proceed to Step 2. ``` image_generate({ options: { prompt: "<design generation prompt>", aspectRatio: "1:1", n: 1, promptReasoner: "quality" }, outputFileType: "png" }) ``` --- ### Step 2: Brand Profile #### 2a. Collect inputs Extract everything you can from the user's message and the design itself. Default to inference over interrogation. Ask only for what's genuinely missing, and prefer a single structured question page over multiple rounds of Q&A. | Input | How to get it | |---|---| | **Design image** | User uploads directly to chat | | **Brand name** | Infer from filename or message for internal reference only (e.g. labeling outputs). Only treat a name as explicitly provided — and eligible to render as text in mockups — if the user stated it directly in their message. | | **Brand colors** | Infer from the design if it has clear colors. Otherwise improvise and fall back to neutral tones (`#FFFFFF`, `#111111`, `#E8E4DC`). | | **Brand vibe** | Infer from the design style and any context clues (e.g. a sleek monogram → Minimal, a bold illustrated character → Playful). Do not ask a dedicated vibe question unless the direction is genuinely ambiguous. | | **Mockup selection** | If the user already named products, use those. Otherwise ask once using a single structured product picker. If no preference is given, default to a standard set (mug, business card, t-shirt, phone screen). | | **Aspect ratio** | If the user specified one, use it. If they specified products but not aspect ratio, default to square (`1:1`) or infer a better fit from product type. Only ask when aspect ratio is important and cannot be safely inferred. | ##### Brand vibe reference | Vibe | Description | |---|---| | **Minimal** | Clean white/light backgrounds, generous whitespace, muted palette | | **Playful** | Bright colors, casual settings, energetic product photography feel | | **Luxury** | Dark or gold backgrounds, dramatic lighting, premium materials | | **Bold** | High contrast, strong colors, graphic and commanding | | **Earthy / Organic** | Natural textures (wood, linen, stone), warm tones, lifestyle feel | | **Custom** | User describes their own | If everything is clear from the message and design, skip directly to Step 3 without asking anything. #### 2b. Product and aspect-ratio intake Use `ask_user_question` only if the user has **not** already specified which mockups they want. Keep it to a single page that combines product suggestions with aspect-ratio choices. **Product options must be tailored to the brand.** Infer the most fitting products from the design, brand name, vibe, and any context the user provided. Use the examples below as a guide — not a fixed list: | Brand type | Good product suggestions | |---|---| | Streetwear / skate | Hoodie, snapback, skateboard deck, tote bag, sticker sheet | | Food / beverage | Coffee mug, takeaway cup, tote bag, apron, business card | | Kitchenware / home | Plate, mug, tea towel, tote bag, business card | | Tech / SaaS | Phone screen, laptop sticker, notebook, t-shirt, business card | | Beauty / wellness | Label/bottle, tote bag, business card, mirror card, poster | | Creative studio | Poster, business card, notebook, tote bag, phone screen | | Generic / unclear | Coffee mug, t-shirt, business card, phone screen *(fallback defaults)* | Always offer 4–5 product options. Tailor the descriptions to feel relevant to the brand. The fallback defaults (mug, t-shirt, business card, phone screen) should only be used when there is genuinely no brand context to work from. ``` ask_user_question({ questions: [ { question: "Which mockups should I make first?", header: "Products", multiSelect: true, options: [ // 4-5 brand-appropriate products inferred from context ] }, { question: "What image shape should I use?", header: "Ratio", multiSelect: false, options: [ { label: "Square", description: "Best default for most product mockups and portfolios" }, { label: "Landscape", description: "Better for presentation slides and wider scenes" }, { label: "Vertical", description: "Better for mobile-first or poster-style layouts" }, { label: "Auto", description: "Pick the most natural ratio for each mockup automatically" } ] } ] }) ``` Rules: - If the user already specified products, skip the product question. - If the user already specified products but not aspect ratio, default to `1:1` unless the product strongly suggests another format. - For referenced mockups, use the chosen ratio as prompt guidance only (for example, "square studio composition"). Do not pass `aspectRatio` or `size` to `image_generate` when `referenceImage` is present. - Use `Auto` behavior by default when product type clearly implies a better composition: - phone screen / poster → vertical is often more natural - billboard / website hero / presentation scene → landscape is often more natural - mug / t-shirt / tote / business card → square is usually the safest default - Do not ask a dedicated brand-vibe picker unless the design and prompt leave the direction genuinely unclear. - If asking anything in Step 2, keep it to this single structured intake pass. --- ### Step 3: Review the Design Trigger this checkpoint if **any** of the following are true: - Visible pencil, pen, or marker strokes - Paper, notebook, or textured background - Rough, uneven, or hand-drawn edges - Watercolor, paint, or brush texture - Photo of a drawing or physical object - Low resolution or pixelated rendering - Incomplete or rough linework **Skip this step** if the asset clearly shows a finished logo. ``` ask_user_question({ questions: [{ question: "Would you like to use this design as-is for mockups, or have me generate a polished logo render from it first?", header: "Design", multiSelect: false, options: [ { label: "Use as-is", description: "Go straight to mockup generation with this exact artwork" }, { label: "Polish it first", description: "Create a cleaned-up logo render from this sketch before making mockups" } ] }] }) ``` - **Use as-is** → Use the uploaded image directly as `designAssetUrl`. Proceed to Step 4. - **Polish it first** → Generate a polished logo render using `image_generate`. Pass the sketch URL as `options.referenceImage`. Preserve the original concept while cleaning edges, removing paper/pencil texture, and producing a crisp, production-ready result. Omit `aspectRatio` and `size` because `referenceImage` is present. Use the generated URL as `designAssetUrl` and proceed to Step 4. Do not ask follow-up questions unless the user requests specific changes. ``` image_generate({ options: { prompt: "Create a crisp, production-ready logo render from the reference sketch. Preserve the original concept, silhouette, and distinctive marks while removing paper texture, pencil or marker artifacts, rough edges, shadows, and background noise. Keep the result clean and centered on a simple plain background.", referenceImage: "<uploadedSketchUrl>", n: 1, promptReasoner: "quality" }, outputFileType: "png" }) ``` **Skip this step only** if the asset is clearly a finished digital file with no ambiguity. --- ### Step 4: Generate Mockups #### 4a. Build scene language from brand profile Before writing any prompts, lock in the following shared constants from the brand profile. Every prompt must use these exact values — do not vary them across mockups: - **Brand colors** — the hex values inferred or confirmed in Step 2. Use these consistently for backgrounds, surface tints, props, and accents across all scenes. - **Brand name** — only include text in mockups if the user explicitly provided a name. Never invent or add a brand name, tagline, or any other text. Use the confirmed brand profile to define visual language for the scenes. Adapt based on the specific brand — don't copy the table verbatim: | Vibe | Scene language starting point | |---|---| | Minimal | Soft studio light, white or pale grey surfaces, clean negative space, no props | | Playful | Bright saturated backgrounds matching brand colors, casual angles, fun props | | Luxury | Dark rich-toned surfaces (marble, velvet, dark wood), dramatic directional light, gold accents | | Bold | Punchy solid-color backgrounds in brand colors, high contrast flat-lay compositions | | Earthy / Organic | Natural materials (wood, linen, stone, kraft paper), warm diffused light | | Custom | Derive from the user's description | #### 4b. Write all prompts before generating anything For each product, write the mockup prompt before making any tool calls. This ensures visual consistency across the set. **Do not output the prompts to the user — keep them internal.** **Prompt structure:** Describe the scene and placement — not the design itself. `image_generate` reads the design from `options.referenceImage`. ``` "[surface and background from vibe and brand colors], [product description], [design placement on product, e.g. 'logo mark on the front face'], [scale/placement detail, e.g. 'centered, occupying roughly 30% of the face'], [lighting style], mockup photography, [props or details that fit brand personality]. The logo/design from the reference image must fit naturally on the [product surface] — sized and positioned as it would appear on a real product, not floating or oversized. Use the design from the reference image." ``` Always end with *"Use the design from the reference image."* and include the natural-on-surface constraint — this helps the model prioritize `referenceImage` and keeps the design grounded on the product. **Do not add any text, lettering, brand name, or tagline** to the scene or product unless the user explicitly provided a name in their message. If no name was given, the design from the reference image is the only branding — no additional text of any kind. #### 4c. Pilot mockup — validate direction before generating the full set Generate the **first product only**. Always pass `designAssetUrl` as `options.referenceImage`. Do not pass `aspectRatio` or `size` in this call: ``` image_generate({ options: { prompt: "<mockup prompt from 4b>", referenceImage: "<designAssetUrl>", n: 1, promptReasoner: "quality" }, outputFileType: "png" }) ``` Save the output URL as the first mockup URL. Also save any Firefly generation URN or asset ID returned by the tool; use it later for the board if available. **If the call fails:** Stop. Do not fall back to describing the design in the prompt. Tell the user: > "Mockup generation isn't working — this may be a platform limitation or an authentication issue. Please check your plan or try re-authenticating." **Show the pilot mockup and checkpoint:** ``` Here's a pilot [product name] mockup. Does the direction feel right? - Scene / lighting / surfaces ✓/✗ - Design placement and scale ✓/✗ - Overall vibe ✓/✗ Say the word and I'll generate the rest, or tell me what to adjust first. ``` **Do not generate remaining mockups until the user approves the pilot.** ### 5. Generate remaining mockups **If the user approved the pilot with no changes:** use the prompts written in Step 4b exactly as-is for all remaining products. Do not rewrite or re-derive them. **If the user requested changes during the pilot checkpoint:** update all prompts from Step 4b to reflect those changes, then regenerate the entire set — including the pilot product. Do not carry forward the original pilot image; every mockup in the final set should be generated from the same updated prompt language. Always pass `designAssetUrl` as `options.referenceImage` on every call, and omit `aspectRatio` and `size` on those referenced calls. **Call `image_generate` for all remaining products in parallel — do not call them sequentially.** Issue all calls at once, up to 5 at a time. If rate-limited, reduce batch size and retry the remaining ones together. Track progress in a manifest: ``` mockups = { [product_1]: { url: "<outputUrl>", assetId: "<generationUrn-or-assetId-if-returned>" }, [product_2]: { url: "<outputUrl>", assetId: "<generationUrn-or-assetId-if-returned>" }, ... } ``` Do not display any mockups here. Wait until all products are generated, then deliver the full set together in Step 6. --- ### Step 6: Deliver Display all mockups together in a single delivery — including the pilot. Do not split output across messages or show mockups as they are generated. Wait until the full set is complete, then display everything at once. #### Iteration options After delivery, always offer: ``` Want to refine anything? - Redo a mockup → "Redo the mug with a darker background" - Try out different vibes → "Try luxury feel instead" - Add or swap a product → "Add a tote bag" / "Replace the hat with a hoodie" - Adjust design placement → "Move the logo to the left chest on the shirt" ``` When the user requests a refinement, re-enter the pipeline at the appropriate step using the existing `designAssetUrl` — no need to re-review the design unless they ask. --- ### Step 7: Create Firefly Board Create a Firefly Board, then add the final mockups to it. Never invent a `boardId`. ``` boards_create_new_board({ doc_name: "<Brand or project name> mockups" }) ``` Save the returned `boardId`, then add the mockups. Prefer generation IDs/URNs when the generation result provides them: ``` boards_add_items_to_board({ board_id: "<boardId>", items: [ { type: "generationUrn", assetIds: [ "<generationUrn_or_assetId_image1>", "<generationUrn_or_assetId_image2>" ] } ] }) ``` If the generation result only provides HTTPS output URLs, use `presignedUrl` instead: ``` boards_add_items_to_board({ board_id: "<boardId>", items: [ { type: "presignedUrl", urls: [ "<outputUrl_image1>", "<outputUrl_image2>" ] } ] }) ``` Use one `boards_add_items_to_board` call when there are 1-12 mockups. If there are more than 12, split them into sequential batches and reuse the same `boardId`. Only include successful mockups. Do not recap or re-display the mockups here. After `boards_add_items_to_board` succeeds, create the user-facing Firefly Board link by calling `asset_share_link` with the returned `boardId` as `assetId`. Do not invent or derive the URL manually. ```json asset_share_link({ "assetId": "<boardId>" }) ``` Omit `changeAccess` and `accessLevel` unless the user explicitly asks to change who can access the board. Present the returned `url` as a Markdown link. ```markdown Your mockups are saved to a Firefly Board: [<board name>](<url>) ``` If `asset_share_link` fails, present the `boardId` and say the board was created but a share link could not be generated. --- ## Error Handling | Situation | Action | |---|---| | No image uploaded | Ask the user to upload their design or sketch | | `image_generate` fails on the pilot, or fails for every product in a batch | Stop. Flag the limitation clearly. Do not fall back to prompt-based design description. | | `image_generate` fails for one or more products during the batch (not all) | Skip the failed products, note them explicitly, and deliver the rest. Never skip silently. | | Rate limit on `image_generate` | Reduce batch size and continue — do not stop or switch tools | | `boards_create_new_board` fails | Retry once for 503/504/500/502. Do not retry 400/401 without changing the input/auth. If it still fails, note it; inline images in Step 6 are still the deliverable. | | `boards_add_items_to_board` returns 201 partial success | Treat as success for the added items. Re-send only the failed items after fixing the named cause. | | `boards_add_items_to_board` fails | Retry once for 503/504. For 404, create a new board and retry once. For 400/401/415, fix the request/auth instead of retrying unchanged. Inline images in Step 6 are still the deliverable. | --- ## Important Constraints - **Only ask whether to use as-is or polish first for sketches and unclear designs** — skip straight to generation for clean, production-ready digital files - **Always get pilot approval** before generating the full set - **Always pass `designAssetUrl` as `options.referenceImage`** on every referenced `image_generate` call — never describe the design in text as a substitute - **Never pass `aspectRatio` or `size` with `referenceImage`** — include shape/composition requirements in the prompt instead - **Never silently degrade** — if generation fails, stop and flag rather than falling back to a prompt description - **Rate limits**: Generate at most 5 images per turn. If rate-limited, reduce batch size and retry. - The final deliverables are the mockup images — display them inline - Keep the brand vibe consistent across all prompts — use the same scene language throughout - **Never output prompts to the user** — prompts are internal working documents only - **No commentary on quality** — do not comment on logo or mockup quality. Only surface information the user needs (brand analysis, the images, the checkpoint question, the board link, and iteration options).
Original skill: openai/plugins/plugins/adobe/skills/adobe-create-mockups/SKILL.md
Source: https://github.com/openai/plugins/blob/5fd93af4cd0c623e020d0cc7e9ce178b4ac1f70f/plugins/adobe/skills/adobe-create-mockups/SKILL.md
License: Apache-2.0
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright 2026 Anthropic, PBC.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.SKILL.md 본문입니다. 원문에서 참조하는 스크립트·보조 파일은 원본 패키지에 포함되어 있습니다.