🐫 CAMEL: The first and the best multi-agent framework. Finding the Scaling Law of Agents. https://www.camel-ai.org
Python agentai-societiesartificial-intelligencecommunicative-aicooperative-aideep-learninglarge-language-modelsmulti-agent-systemsnatural-language-processing
enhance: skill creator md (#3789)
Wendong-Fanf0524039ae28
diff --git a/.camel/skills/skill-creator/LICENSE.txt b/.camel/skills/skill-creator/LICENSE.txtdeleted file mode 100644index c46213dce..000000000--- a/.camel/skills/skill-creator/LICENSE.txt+++ /dev/null@@ -1,201 +0,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 2023 @ CAMEL-AI.org-- 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.diff --git a/.camel/skills/skill-creator/SKILL.md b/.camel/skills/skill-creator/SKILL.mdindex ad44c052f..bcef6b68c 100644--- a/.camel/skills/skill-creator/SKILL.md+++ b/.camel/skills/skill-creator/SKILL.md@@ -1,7 +1,6 @@---name: skill-creator-description: Guide for creating effective skills. Use when you need to create or update a skill that adds specialized knowledge, workflows, or tool integrations.-license: Complete terms in LICENSE.txt+description: Guide for creating effective skills. Use when creating a new skill or updating an existing skill that extends agent capabilities with specialized knowledge, workflows, or tool integrations.---# Skill Creator@@ -10,9 +9,10 @@ This skill provides guidance for creating effective skills.## About Skills-Skills are modular, self-contained packages that extend your capabilities by providing-specialized knowledge, workflows, and tools. Think of them as onboarding guides for specific-domains or tasks.+Skills are modular, self-contained packages that extend agent capabilities by providing+specialized knowledge, workflows, and tools. Think of them as "onboarding guides" for specific+domains or tasks—they transform a general-purpose agent into a specialized agent+equipped with procedural knowledge that no model can fully possess.### What Skills Provide@@ -25,19 +25,23 @@ domains or tasks.### Concise is Key-The context window is shared across system prompts, conversation history, and other skills.-Only add context that is truly needed. Challenge each piece of information:-"Is this needed to complete the task reliably?" Prefer concise examples over long prose.+The context window is a public good. Skills share the context window with everything else the agent needs: system prompt, conversation history, other Skills' metadata, and the actual user request.++**Default assumption: The agent is already very capable.** Only add context the agent doesn't already have. Challenge each piece of information: "Does the agent really need this explanation?" and "Does this paragraph justify its token cost?"++Prefer concise examples over verbose explanations.### Set Appropriate Degrees of FreedomMatch the level of specificity to the task's fragility and variability:-- High freedom (text-based instructions): Multiple approaches are valid.-- Medium freedom (pseudocode or scripts with parameters): A preferred pattern exists.-- Low freedom (specific scripts, few parameters): Consistency is critical.+**High freedom (text-based instructions)**: Use when multiple approaches are valid, decisions depend on context, or heuristics guide the approach.++**Medium freedom (pseudocode or scripts with parameters)**: Use when a preferred pattern exists, some variation is acceptable, or configuration affects behavior.-Think of exploration: a narrow bridge needs guardrails, an open field allows many routes.+**Low freedom (specific scripts, few parameters)**: Use when operations are fragile and error-prone, consistency is critical, or a specific sequence must be followed.++Think of the agent exploring a path: a narrow bridge with cliffs needs specific guardrails (low freedom), while an open field allows many routes (high freedom).### Anatomy of a Skill@@ -48,66 +52,79 @@ skill-name/├── SKILL.md (required)│ ├── YAML frontmatter metadata (required)│ │ ├── name: (required)-│ │ └── description: (required)+│ │ ├── description: (required)+│ │ └── compatibility: (optional, rarely needed)│ └── Markdown instructions (required)└── Bundled Resources (optional)├── scripts/ - Executable code (Python/Bash/etc.)- ├── references/ - Documentation intended to be loaded as needed- └── assets/ - Files used in output (templates, icons, fonts)+ ├── references/ - Documentation intended to be loaded into context as needed+ └── assets/ - Files used in output (templates, icons, fonts, etc.)```#### SKILL.md (required)Every SKILL.md consists of:-- Frontmatter (YAML): `name` and `description`. These are the only fields used to- determine when the skill should be used. Be explicit about triggers and contexts.-- Body (Markdown): Instructions and guidance for using the skill. Read only when needed.+- **Frontmatter** (YAML): Contains `name` and `description` fields (required), plus optional fields like `license`, `metadata`, and `compatibility`. Only `name` and `description` are read by the agent to determine when the skill triggers, so be clear and comprehensive about what the skill is and when it should be used. The `compatibility` field is for noting environment requirements (target product, system packages, etc.) but most skills don't need it.+- **Body** (Markdown): Instructions and guidance for using the skill. Only loaded AFTER the skill triggers (if at all).#### Bundled Resources (optional)##### Scripts (`scripts/`)-Executable code for tasks that require deterministic reliability or are repeatedly rewritten.+Executable code (Python/Bash/etc.) for tasks that require deterministic reliability or are repeatedly rewritten.-- When to include: Repeated code or fragile operations-- Example: `scripts/rotate_pdf.py` for PDF rotation tasks-- Benefits: Token efficient, deterministic, can be executed without reading into context-- Note: You may still need to read scripts for patching or environment-specific changes+- **When to include**: When the same code is being rewritten repeatedly or deterministic reliability is needed+- **Example**: `scripts/rotate_pdf.py` for PDF rotation tasks+- **Benefits**: Token efficient, deterministic, may be executed without loading into context+- **Note**: Scripts may still need to be read by the agent for patching or environment-specific adjustments##### References (`references/`)-Documentation intended to be loaded into context as needed.+Documentation and reference material intended to be loaded as needed into context to inform the agent's process and thinking.-- When to include: Detailed docs, schemas, policies, API specs-- Examples: `references/schema.md`, `references/policies.md`, `references/api.md`-- Best practice: Keep SKILL.md lean and point to references for details-- Avoid duplication: Details live in references, not in SKILL.md+- **When to include**: For documentation that the agent should reference while working+- **Examples**: `references/finance.md` for financial schemas, `references/mnda.md` for company NDA template, `references/policies.md` for company policies, `references/api_docs.md` for API specifications+- **Use cases**: Database schemas, API documentation, domain knowledge, company policies, detailed workflow guides+- **Benefits**: Keeps SKILL.md lean, loaded only when the agent determines it's needed+- **Best practice**: If files are large (>10k words), include grep search patterns in SKILL.md+- **Avoid duplication**: Information should live in either SKILL.md or references files, not both. Prefer references files for detailed information unless it's truly core to the skill—this keeps SKILL.md lean while making information discoverable without hogging the context window. Keep only essential procedural instructions and workflow guidance in SKILL.md; move detailed reference material, schemas, and examples to references files.##### Assets (`assets/`)-Files not intended for context, but used in outputs.+Files not intended to be loaded into context, but rather used within the output the agent produces.-- When to include: Templates, images, icons, boilerplate code, fonts-- Examples: `assets/logo.png`, `assets/slides.pptx`, `assets/frontend-template/`+- **When to include**: When the skill needs files that will be used in the final output+- **Examples**: `assets/logo.png` for brand assets, `assets/slides.pptx` for PowerPoint templates, `assets/frontend-template/` for HTML/React boilerplate, `assets/font.ttf` for typography+- **Use cases**: Templates, images, icons, boilerplate code, fonts, sample documents that get copied or modified+- **Benefits**: Separates output resources from documentation, enables the agent to use files without loading them into context#### What to Not Include in a Skill-Do not create extra docs like README.md, INSTALLATION_GUIDE.md, QUICK_REFERENCE.md,-CHANGELOG.md. Keep only files needed for the skill to do its job.+A skill should only contain essential files that directly support its functionality. Do NOT create extraneous documentation or auxiliary files, including:++- README.md+- INSTALLATION_GUIDE.md+- QUICK_REFERENCE.md+- CHANGELOG.md+- etc.++The skill should only contain the information needed for an AI agent to do the job at hand. It should not contain auxilary context about the process that went into creating it, setup and testing procedures, user-facing documentation, etc. Creating additional documentation files just adds clutter and confusion.### Progressive Disclosure Design PrincipleSkills use a three-level loading system to manage context efficiently:-1. Metadata (name + description) - Always in context-2. SKILL.md body - Read when the skill is relevant-3. Bundled resources - Read or run only as needed--Keep SKILL.md under ~500 lines. Split detailed or variant-specific content into references.+1. **Metadata (name + description)** - Always in context (~100 words)+2. **SKILL.md body** - When skill triggers (<5k words)+3. **Bundled resources** - As needed by the agent (Unlimited because scripts can be executed without reading into context window)#### Progressive Disclosure Patterns+Keep SKILL.md body to the essentials and under 500 lines to minimize context bloat. Split content into separate files when approaching this limit. When splitting out content into other files, it is very important to reference them from SKILL.md and describe clearly when to read them, to ensure the reader of the skill knows they exist and when to use them.++**Key principle:** When a skill supports multiple variations, frameworks, or options, keep only the core workflow and selection guidance in SKILL.md. Move variant-specific details (patterns, examples, configuration) into separate reference files.+**Pattern 1: High-level guide with references**```markdown@@ -120,71 +137,220 @@ Extract text with pdfplumber:## Advanced features-- Form filling: See references/FORM_FILLING.md-- API reference: See references/REFERENCE.md-- Examples: See references/EXAMPLES.md+- **Form filling**: See [FORMS.md](FORMS.md) for complete guide+- **API reference**: See [REFERENCE.md](REFERENCE.md) for all methods+- **Examples**: See [EXAMPLES.md](EXAMPLES.md) for common patterns```+The agent loads FORMS.md, REFERENCE.md, or EXAMPLES.md only when needed.+**Pattern 2: Domain-specific organization**+For Skills with multiple domains, organize content by domain to avoid loading irrelevant context:+```bigquery-skill/├── SKILL.md (overview and navigation)+└── reference/+ ├── finance.md (revenue, billing metrics)+ ├── sales.md (opportunities, pipeline)+ ├── product.md (API usage, features)+ └── marketing.md (campaigns, attribution)+```++When a user asks about sales metrics, the agent only reads sales.md.++Similarly, for skills supporting multiple frameworks or variants, organize by variant:++```+cloud-deploy/+├── SKILL.md (workflow + provider selection)└── references/- ├── finance.md- ├── sales.md- ├── product.md- └── marketing.md+ ├── aws.md (AWS deployment patterns)+ ├── gcp.md (GCP deployment patterns)+ └── azure.md (Azure deployment patterns)```+When the user chooses AWS, the agent only reads aws.md.+**Pattern 3: Conditional details**+Show basic content, link to advanced content:+```markdown# DOCX Processing## Creating documents-Use docx-js for new documents. See references/DOCX-JS.md.+Use docx-js for new documents. See [DOCX-JS.md](DOCX-JS.md).## Editing documentsFor simple edits, modify the XML directly.-For tracked changes: See references/REDLINING.md-For OOXML details: See references/OOXML.md+**For tracked changes**: See [REDLINING.md](REDLINING.md)+**For OOXML details**: See [OOXML.md](OOXML.md)```-**Guidelines:**+The agent reads REDLINING.md or OOXML.md only when the user needs those features.-- Avoid deeply nested references; keep references one level deep from SKILL.md.-- For reference files longer than 100 lines, add a table of contents.+**Important guidelines:**++- **Avoid deeply nested references** - Keep references one level deep from SKILL.md. All reference files should link directly from SKILL.md.+- **Structure longer reference files** - For files longer than 100 lines, include a table of contents at the top so the agent can see the full scope when previewing.## Skill Creation Process+Skill creation involves these steps:+1. Understand the skill with concrete examples2. Plan reusable skill contents (scripts, references, assets)-3. Initialize the skill (create folder + SKILL.md)+3. Initialize the skill (run init_skill.py)4. Edit the skill (implement resources and write SKILL.md)-5. Iterate based on real usage+5. Package the skill (run package_skill.py)+6. Iterate based on real usage++Follow these steps in order, skipping only if there is a clear reason why they are not applicable.### Step 1: Understanding the Skill with Concrete Examples-Ask for concrete examples and likely triggers. Start with a few questions and-follow up as needed.+Skip this step only when the skill's usage patterns are already clearly understood. It remains valuable even when working with an existing skill.++To create an effective skill, clearly understand concrete examples of how the skill will be used. This understanding can come from either direct user examples or generated examples that are validated with user feedback.++For example, when building an image-editor skill, relevant questions include:++- "What functionality should the image-editor skill support? Editing, rotating, anything else?"+- "Can you give some examples of how this skill would be used?"+- "I can imagine users asking for things like 'Remove the red-eye from this image' or 'Rotate this image'. Are there other ways you imagine this skill being used?"+- "What would a user say that should trigger this skill?"++To avoid overwhelming users, avoid asking too many questions in a single message. Start with the most important questions and follow up as needed for better effectiveness.++Conclude this step when there is a clear sense of the functionality the skill should support.### Step 2: Planning the Reusable Skill Contents-For each example, identify what should be captured in scripts, references, or assets.+To turn concrete examples into an effective skill, analyze each example by:++1. Considering how to execute on the example from scratch+2. Identifying what scripts, references, and assets would be helpful when executing these workflows repeatedly++Example: When building a `pdf-editor` skill to handle queries like "Help me rotate this PDF," the analysis shows:++1. Rotating a PDF requires re-writing the same code each time+2. A `scripts/rotate_pdf.py` script would be helpful to store in the skill++Example: When designing a `frontend-webapp-builder` skill for queries like "Build me a todo app" or "Build me a dashboard to track my steps," the analysis shows:++1. Writing a frontend webapp requires the same boilerplate HTML/React each time+2. An `assets/hello-world/` template containing the boilerplate HTML/React project files would be helpful to store in the skill++Example: When building a `big-query` skill to handle queries like "How many users have logged in today?" the analysis shows:++1. Querying BigQuery requires re-discovering the table schemas and relationships each time+2. A `references/schema.md` file documenting the table schemas would be helpful to store in the skill++To establish the skill's contents, analyze each concrete example to create a list of the reusable resources to include: scripts, references, and assets.### Step 3: Initializing the Skill-Create the skill folder with a SKILL.md template and only the resource folders you need.+At this point, it is time to actually create the skill.++Skip this step only if the skill being developed already exists, and iteration or packaging is needed. In this case, continue to the next step.++When creating a new skill from scratch, always run the `init_skill.py` script. The script conveniently generates a new template skill directory that automatically includes everything a skill requires, making the skill creation process much more efficient and reliable.++Usage:++```bash+scripts/init_skill.py <skill-name> --path <output-directory>+```++The script:++- Creates the skill directory at the specified path+- Generates a SKILL.md template with proper frontmatter and TODO placeholders+- Creates example resource directories: `scripts/`, `references/`, and `assets/`+- Adds example files in each directory that can be customized or deleted++After initialization, customize or remove the generated SKILL.md and example files as needed.### Step 4: Edit the Skill-Write in imperative form. Keep the body focused on workflows and decisions. Point to-references for detailed content.+When editing the (newly-generated or existing) skill, remember that the skill is being created for an agent to use. Include information that would be beneficial and non-obvious to the agent. Consider what procedural knowledge, domain-specific details, or reusable assets would help the agent execute these tasks more effectively.++#### Learn Proven Design Patterns++Consult these helpful guides based on your skill's needs:++- **Multi-step processes**: See references/workflows.md for sequential workflows and conditional logic+- **Specific output formats or quality standards**: See references/output-patterns.md for template and example patterns++These files contain established best practices for effective skill design.++#### Start with Reusable Skill Contents++To begin implementation, start with the reusable resources identified above: `scripts/`, `references/`, and `assets/` files. Note that this step may require user input. For example, when implementing a `brand-guidelines` skill, the user may need to provide brand assets or templates to store in `assets/`, or documentation to store in `references/`.++Added scripts must be tested by actually running them to ensure there are no bugs and that the output matches what is expected. If there are many similar scripts, only a representative sample needs to be tested to ensure confidence that they all work while balancing time to completion.++Any example files and directories not needed for the skill should be deleted. The initialization script creates example files in `scripts/`, `references/`, and `assets/` to demonstrate structure, but most skills won't need all of them.++#### Update SKILL.md++**Writing Guidelines:** Always use imperative/infinitive form.++##### Frontmatter++Write the YAML frontmatter with `name` and `description`:++- `name`: The skill name+- `description`: This is the primary triggering mechanism for your skill, and helps the agent understand when to use the skill.+ - Include both what the Skill does and specific triggers/contexts for when to use it.+ - Include all "when to use" information here - Not in the body. The body is only loaded after triggering, so "When to Use This Skill" sections in the body are not helpful to the agent.+ - Example description for a `docx` skill: "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. Use when the agent needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks"++Do not include any other fields in YAML frontmatter.++##### Body++Write instructions for using the skill and its bundled resources.++### Step 5: Packaging a Skill++Once development of the skill is complete, it must be packaged into a distributable .skill file that gets shared with the user. The packaging process automatically validates the skill first to ensure it meets all requirements:++```bash+scripts/package_skill.py <path/to/skill-folder>+```++Optional output directory specification:++```bash+scripts/package_skill.py <path/to/skill-folder> ./dist+```++The packaging script will:++1. **Validate** the skill automatically, checking:++ - YAML frontmatter format and required fields+ - Skill naming conventions and directory structure+ - Description completeness and quality+ - File organization and resource references++2. **Package** the skill if validation passes, creating a .skill file named after the skill (e.g., `my-skill.skill`) that includes all files and maintains the proper directory structure for distribution. The .skill file is a zip file with a .skill extension.++If validation fails, the script will report the errors and exit without creating a package. Fix any validation errors and run the packaging command again.++### Step 6: Iterate++After testing the skill, users may request improvements. Often this happens right after using the skill, with fresh context of how the skill performed.-### Step 5: Iterate+**Iteration workflow:**-After real usage, refine the skill based on observed failures or friction.+1. Use the skill on real tasks+2. Notice struggles or inefficiencies+3. Identify how SKILL.md or bundled resources should be updated+4. Implement changes and test again\ No newline at end of file