metame-cli 1.5.11 → 1.5.12

package/skills/skill-creator/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 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 [yyyy] [name of copyright owner]
+
+   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.

package/skills/skill-creator/README.md

@@ -0,0 +1,72 @@
+# MetaMe Skill Creator
+
+A complete skill lifecycle management system for [Claude Code](https://claude.ai/code) — create, iterate, evolve, and package skills that extend Claude's capabilities.
+
+## What It Does
+
+| Capability | Description |
+|---|---|
+| **Create** | Scaffold new skills with `init_skill.py`, write `SKILL.md`, bundle scripts/references/assets |
+| **Iterate** | Structured workflow for improving skills after real usage |
+| **Evolve** | Auto-captures session experience (bugs, preferences, workarounds) and stitches it into SKILL.md |
+| **Package** | Produces portable `.skill` files for distribution |
+
+## Install
+
+Install via [skill-manager](https://github.com/anthropics/claude-code) or manually:
+
+```bash
+# Manual install
+cp -r skill-creator ~/.claude/skills/
+
+# One-time setup: enables auto-evolution after every session
+python3 ~/.claude/skills/skill-creator/scripts/setup.py
+```
+
+That's it. Skills now evolve automatically.
+
+## Auto-Evolution
+
+After each Claude Code session, a Stop hook:
+1. Detects which skills were active
+2. Extracts failures and patterns from the transcript
+3. If `ANTHROPIC_API_KEY` is set → Haiku analyzes and generates structured insights
+4. Persists experience into `evolution.json` + stitches it into `SKILL.md`
+
+Experience survives skill upgrades — it lives in a dedicated `## User-Learned Best Practices` section that persists through updates.
+
+**No `ANTHROPIC_API_KEY`?** Hook runs in rule-based mode, capturing raw tool failures. Full Haiku analysis activates automatically once the key is available.
+
+## Manual Triggers
+
+```bash
+# Evolve a skill from session experience
+/evolve
+
+# Or say: "进化技能", "记录这个经验", "skill evolution"
+```
+
+## Scripts
+
+```
+scripts/
+├── init_skill.py          # Scaffold new skill directory
+├── package_skill.py       # Validate + pack to .skill file
+├── quick_validate.py      # Validate without packaging
+├── merge_evolution.py     # Merge experience into evolution.json
+├── smart_stitch.py        # Write evolution.json → SKILL.md section
+├── align_all.py           # Re-stitch all skills after batch update
+├── auto_evolve_hook.js    # Stop hook (configured by setup.py)
+└── setup.py               # One-time hook installer
+```
+
+## References
+
+- `references/creation-guide.md` — Full 7-step skill creation workflow
+- `references/evolution-guide.md` — Evolution workflow and data format
+- `references/workflows.md` — Sequential/conditional workflow design patterns
+- `references/output-patterns.md` — Output quality and template patterns
+
+## License
+
+See `LICENSE.txt`

package/skills/skill-creator/SKILL.md

@@ -0,0 +1,96 @@
+---
+name: skill-creator
+description: Create, iterate, evolve, and package skills that extend Claude's capabilities. Use when: (1) Creating a new skill from scratch, (2) Updating or improving an existing skill's instructions or bundled resources, (3) Evolving a skill based on session experience (bugs, preferences, workarounds) — triggers: "进化技能", "更新 skill", "/evolve", "记录这个经验", "skill evolution", (4) Packaging a skill for distribution to other Claude Code (Codex) users. Do NOT trigger for general programming tasks unrelated to skill authoring.
+license: Complete terms in LICENSE.txt
+---
+
+# Skill Studio
+
+## Auto-Evolve Setup (run once, idempotent)
+
+Before starting any task, run setup. The script auto-detects your platform:
+
+```bash
+# Claude Code
+python3 "$(find ~/.claude/skills -path '*/skill-creator/scripts/setup.py' 2>/dev/null | head -1)"
+
+# OpenAI Codex CLI
+python3 "$(find ~/.codex/skills -path '*/skill-creator/scripts/setup.py' 2>/dev/null | head -1)"
+```
+
+Safe to run every time — exits immediately if already installed.
+
+**CC**: adds a Stop hook to `~/.claude/settings.json` — skills evolve automatically at session end with full transcript analysis (Haiku if `ANTHROPIC_API_KEY` is set, rule-based otherwise).
+
+**Codex**: adds a `notify` entry to `~/.codex/config.toml` — fires per turn but Codex passes no transcript data, so signals are recorded for manual `/evolve` review. Full auto-analysis not available on Codex.
+
+---
+
+Three paths — pick based on your goal:
+
+**🆕 Creating a new skill** → read `references/creation-guide.md`
+
+**🔄 Evolving an existing skill** (session experience, bugs, preferences) → read `references/evolution-guide.md`
+
+**🎨 Designing workflows or output patterns** → read `references/workflows.md` and/or `references/output-patterns.md`
+
+---
+
+## Core Principles
+
+**Context window is a public good.** Default assumption: Claude is smart. Only include what Claude doesn't already have. Challenge every paragraph: "Does this justify its token cost?"
+
+**Progressive disclosure** — three loading levels:
+1. Frontmatter `description` (~100 words) — always in context, determines triggering
+2. SKILL.md body (<500 lines) — loaded when skill triggers
+3. `references/` and `scripts/` — loaded only when Claude decides they're needed
+
+**Degrees of freedom** — match specificity to fragility:
+- High freedom (text instructions): multiple valid approaches
+- Medium freedom (pseudocode/parameterized scripts): preferred pattern with variation
+- Low freedom (specific scripts): fragile operations needing exact sequence
+
+---
+
+## Anatomy of a Skill
+
+```
+skill-name/
+├── SKILL.md                  ← required: frontmatter + body
+├── scripts/                  ← executable code (deterministic, reusable)
+├── references/               ← docs loaded into context as needed
+└── assets/                   ← files used in output (not loaded into context)
+```
+
+**Frontmatter required fields:** `name`, `description` (+ `needs_browser: true` if Playwright MCP needed)
+
+**What NOT to include:** README.md, CHANGELOG.md, INSTALLATION_GUIDE.md, or any auxiliary docs.
+
+---
+
+## Scripts Reference
+
+| Script | Purpose | Usage |
+|---|---|---|
+| `init_skill.py` | Scaffold new skill | `python scripts/init_skill.py <name> --path <dir>` |
+| `package_skill.py` | Validate + pack to `.skill` file | `python scripts/package_skill.py <skill-dir> [output-dir]` |
+| `quick_validate.py` | Validate without packaging | `python scripts/quick_validate.py <skill-dir>` |
+| `merge_evolution.py` | Persist session experience to evolution.json | `python scripts/merge_evolution.py <skill-dir> '<json>'` |
+| `smart_stitch.py` | Write evolution.json → SKILL.md section | `python scripts/smart_stitch.py <skill-dir>` |
+| `align_all.py` | Re-stitch all skills after batch update | `python scripts/align_all.py <skills-root-dir>` |
+| `auto_evolve_hook.js` | Stop hook — auto-runs after each CC session | configured by `setup.py` |
+| `setup.py` | Install Stop hook into `~/.claude/settings.json` | `python3 scripts/setup.py` |
+
+**For Codex/CC users:** `.skill` files are portable zip archives. Host on GitHub → discoverable via `skill-scout`. No hardcoded path assumptions — all scripts accept explicit paths.
+
+
+<!-- METAME-EVOLUTION:START -->
+
+## User-Learned Best Practices & Constraints
+
+> **Auto-Generated Section**: Maintained by skill-evolution-manager. Do not edit manually.
+
+### User Preferences
+- Add template for semantic trigger hooks to prevent accidental skill invocation (Signal 23), and enforce pointer-style one-line descriptions instead of full skill content reads to reduce TOKEN bloat. User emphasizes elegance and conciseness across all skill configurations (Signals 25, 63).
+
+<!-- METAME-EVOLUTION:END -->

package/skills/skill-creator/evolution.json

@@ -0,0 +1,6 @@
+{
+  "last_updated": "2026-03-16T12:51:35.102Z",
+  "preferences": [
+    "Add template for semantic trigger hooks to prevent accidental skill invocation (Signal 23), and enforce pointer-style one-line descriptions instead of full skill content reads to reduce TOKEN bloat. User emphasizes elegance and conciseness across all skill configurations (Signals 25, 63)."
+  ]
+}

package/skills/skill-creator/references/creation-guide.md

@@ -0,0 +1,116 @@
+# Skill Creation Guide
+
+## Step 1: Understand the Skill with Concrete Examples
+
+Skip only when usage patterns are already clearly understood.
+
+To create an effective skill, understand concrete examples of how it will be used. Ask:
+- "What functionality should this skill support?"
+- "Can you give examples of how this skill would be used?"
+- "What would a user say to trigger this skill?"
+
+Avoid asking too many questions at once. Conclude when the functionality scope is clear.
+
+## Step 2: Plan Reusable Skill Contents
+
+Analyze each example:
+1. How to execute it from scratch
+2. What scripts, references, and assets would help when repeating it
+
+| Example task | What to bundle |
+|---|---|
+| "Rotate this PDF" | `scripts/rotate_pdf.py` |
+| "Build me a todo app" | `assets/hello-world/` boilerplate |
+| "How many users logged in today?" | `references/schema.md` |
+
+## Step 3: Initialize the Skill
+
+For new skills, always run `init_skill.py`:
+
+```bash
+python scripts/init_skill.py <skill-name> --path <output-directory>
+```
+
+Creates: skill directory, SKILL.md template, example `scripts/`, `references/`, `assets/`.
+
+Skip if iterating on an existing skill.
+
+## Step 4: Edit the Skill
+
+You are writing for another Claude instance. Include non-obvious procedural knowledge.
+
+### Frontmatter
+
+Required fields only:
+- `name`: skill name
+- `description`: primary trigger mechanism — include what the skill does AND when to use it. Put ALL "when to use" info here (body is only loaded after triggering). Set `needs_browser: true` if Playwright MCP is required.
+
+Do not add other frontmatter fields.
+
+### Body
+
+- Use imperative/infinitive form
+- Keep under 500 lines — split larger content into references files
+- Only include info Claude doesn't already have
+- Move detailed reference material to `references/` files, link from SKILL.md
+- See `workflows.md` for sequential/conditional workflow patterns
+- See `output-patterns.md` for template and example patterns
+
+### Resource Guidelines
+
+**scripts/** — when the same code is rewritten repeatedly or deterministic reliability is needed. Always test scripts by running them.
+
+**references/** — documentation to load as needed. For files >10k words, include grep patterns in SKILL.md. Keep SKILL.md lean; detail lives here.
+
+**assets/** — files used in output (templates, images, fonts, boilerplate). Not loaded into context.
+
+**Do NOT include:** README.md, INSTALLATION_GUIDE.md, CHANGELOG.md, or any auxiliary docs.
+
+## Step 5: Package the Skill
+
+```bash
+python scripts/package_skill.py <path/to/skill-folder>
+# Optional: specify output dir
+python scripts/package_skill.py <path/to/skill-folder> ./dist
+```
+
+Validates then creates a `.skill` file (zip with .skill extension). Fix any validation errors before packaging.
+
+**For Codex/CC users distributing skills:**
+- Package produces a `.skill` file ready for `skill-manager` install
+- Host on GitHub for others to discover via `skill-scout`
+- The `.skill` format is portable — no path assumptions about `~/.claude/skills/`
+
+## Step 6: Iterate
+
+After real usage, notice struggles and inefficiencies, then update SKILL.md or bundled resources.
+
+## Step 7: Evaluate & Optimize (Advanced)
+
+### Skill Evals
+
+Define test cases in SKILL.md to verify skill effectiveness:
+
+```markdown
+## Evals
+
+| Input | Expected behavior | Success criteria |
+|---|---|---|
+| "Rotate this PDF" | calls rotate_pdf.py | file output succeeds |
+| "Extract page 3 text" | calls extract_text.py | returns text content |
+```
+
+Re-validate after each modification.
+
+### A/B Testing
+
+Run two skill versions in parallel. Compare: output quality, token cost, trigger accuracy. Use before/after major changes (rewriting description, restructuring workflow). Keep the better version.
+
+### Trigger Optimization
+
+Analyze the `description` field for:
+- **False triggers**: unrelated tasks triggering this skill
+- **Missed triggers**: related tasks not triggering
+- **Ambiguity**: unstable triggering due to vague description
+
+Fix by adding concrete trigger examples to description. Explicitly exclude easily-confused scenarios with "Do NOT trigger when...".

package/skills/skill-creator/references/evolution-guide.md

@@ -0,0 +1,74 @@
+# Skill Evolution Guide
+
+Evolution captures runtime experience (bugs, preferences, workarounds) and stitches it persistently into a skill's SKILL.md — surviving future skill upgrades.
+
+## When to Evolve
+
+Trigger: user says `/evolve`, "复盘一下", "记录这个经验", "把这个偏好保存到 Skill", or expresses friction during a skill session.
+
+## Workflow
+
+### 1. Review & Extract
+
+Scan the conversation for:
+- Things the user was unhappy with (errors, wrong style, bad params)
+- Things that worked well (effective prompts, useful patterns)
+- Environment-specific quirks (OS differences, path issues)
+
+Identify which skill needs evolving.
+
+Build a JSON structure in memory:
+
+```json
+{
+  "preferences": ["user prefers silent download by default"],
+  "fixes": ["on Windows, ffmpeg path needs backslash escaping"],
+  "custom_prompts": "always print estimated time before starting"
+}
+```
+
+Fields:
+- `preferences` — user workflow preferences (list, deduplicated)
+- `fixes` — known bugs, workarounds, env-specific patches (list, deduplicated)
+- `custom_prompts` — persistent instruction injection (string, overwrites previous)
+
+### 2. Persist to evolution.json
+
+```bash
+python scripts/merge_evolution.py <skill_dir> '<json_string>'
+```
+
+Merges new data into `<skill_dir>/evolution.json` with deduplication on list fields.
+
+### 3. Stitch into SKILL.md
+
+```bash
+python scripts/smart_stitch.py <skill_dir>
+```
+
+Writes or updates a `## User-Learned Best Practices & Constraints` section at the end of SKILL.md. This section survives skill upgrades because it's in a dedicated marked block.
+
+### 4. Post-Upgrade Realignment
+
+After `skill-manager` updates a skill (which replaces SKILL.md), re-stitch all stored experience:
+
+```bash
+python scripts/align_all.py <skills_root_dir>
+```
+
+Traverses all skill folders, re-applies any existing `evolution.json` to the updated SKILL.md. Run this after any batch skill update.
+
+**For Codex/CC users:** `<skills_root_dir>` defaults to `~/.claude/skills/` but can be any path — pass the actual location of your skills directory.
+
+## Important Rules
+
+- **Never directly edit** the `## User-Learned Best Practices & Constraints` section in SKILL.md — it will be overwritten by `smart_stitch.py`. All changes must go through `evolution.json`.
+- If a conversation touches multiple skills, run the full workflow for each skill separately.
+- The `evolution.json` file is the source of truth; SKILL.md section is derived from it.
+
+## Multi-Skill Session
+
+When one session uses several skills, after the session:
+1. List all skills used
+2. For each skill, extract relevant experience
+3. Run `merge_evolution.py` + `smart_stitch.py` per skill

package/skills/skill-creator/references/output-patterns.md

@@ -0,0 +1,82 @@
+# Output Patterns
+
+Use these patterns when skills need to produce consistent, high-quality output.
+
+## Template Pattern
+
+Provide templates for output format. Match the level of strictness to your needs.
+
+**For strict requirements (like API responses or data formats):**
+
+```markdown
+## Report structure
+
+ALWAYS use this exact template structure:
+
+# [Analysis Title]
+
+## Executive summary
+[One-paragraph overview of key findings]
+
+## Key findings
+- Finding 1 with supporting data
+- Finding 2 with supporting data
+- Finding 3 with supporting data
+
+## Recommendations
+1. Specific actionable recommendation
+2. Specific actionable recommendation
+```
+
+**For flexible guidance (when adaptation is useful):**
+
+```markdown
+## Report structure
+
+Here is a sensible default format, but use your best judgment:
+
+# [Analysis Title]
+
+## Executive summary
+[Overview]
+
+## Key findings
+[Adapt sections based on what you discover]
+
+## Recommendations
+[Tailor to the specific context]
+
+Adjust sections as needed for the specific analysis type.
+```
+
+## Examples Pattern
+
+For skills where output quality depends on seeing examples, provide input/output pairs:
+
+```markdown
+## Commit message format
+
+Generate commit messages following these examples:
+
+**Example 1:**
+Input: Added user authentication with JWT tokens
+Output:
+```
+feat(auth): implement JWT-based authentication
+
+Add login endpoint and token validation middleware
+```
+
+**Example 2:**
+Input: Fixed bug where dates displayed incorrectly in reports
+Output:
+```
+fix(reports): correct date formatting in timezone conversion
+
+Use UTC timestamps consistently across report generation
+```
+
+Follow this style: type(scope): brief description, then detailed explanation.
+```
+
+Examples help Claude understand the desired style and level of detail more clearly than descriptions alone.

package/skills/skill-creator/references/workflows.md

@@ -0,0 +1,28 @@
+# Workflow Patterns
+
+## Sequential Workflows
+
+For complex tasks, break operations into clear, sequential steps. It is often helpful to give Claude an overview of the process towards the beginning of SKILL.md:
+
+```markdown
+Filling a PDF form involves these steps:
+
+1. Analyze the form (run analyze_form.py)
+2. Create field mapping (edit fields.json)
+3. Validate mapping (run validate_fields.py)
+4. Fill the form (run fill_form.py)
+5. Verify output (run verify_output.py)
+```
+
+## Conditional Workflows
+
+For tasks with branching logic, guide Claude through decision points:
+
+```markdown
+1. Determine the modification type:
+   **Creating new content?** → Follow "Creation workflow" below
+   **Editing existing content?** → Follow "Editing workflow" below
+
+2. Creation workflow: [steps]
+3. Editing workflow: [steps]
+```