@slycode/slycode 0.1.19 → 0.2.0

package/dist/store/skills/reference-fetch/SKILL.md

@@ -1,206 +0,0 @@
----
-name: reference-fetch
-version: 1.1.1
-updated: 2026-02-22
-allowed-tools: mcp__context7__resolve-library-id, mcp__context7__get-library-docs, mcp__firecrawl__firecrawl_scrape, mcp__firecrawl__firecrawl_search, Read, Write, Glob, Bash(date:*), Bash(powershell:*), Bash(Get-ChildItem:*), Bash(Get-Item:*), Bash(Get-Date:*), find
-argument-hint: "[topic/url] [optional output filename] [--firecrawl|--context7]"
-description: "Fetch reference documentation using Context7 (structured) or Firecrawl (web scraping)"
----
-
-# Reference Documentation Fetcher
-
-## Summary
-Fetch reference documentation from multiple sources and create/update summary MD files in the Documentation/Reference folder. Uses **Context7** for structured library documentation (preferred) with **Firecrawl** as fallback for web scraping. Checks for existing documents and only updates if older than 24 hours.
-
-## Source Selection Logic
-
-```
-Input: topic/URL [--firecrawl|--context7]
-    │
-    ├─► --firecrawl flag? ─────────────► Force Firecrawl
-    │
-    ├─► --context7 flag? ──────────────► Force Context7 only (no fallback)
-    │
-    ├─► Is it a URL? ──────────────────► Firecrawl (direct scrape)
-    │
-    └─► Is it a topic/library name?
-            │
-            └─► Try Context7 first
-                    │
-                    ├─► Sufficient result? ──► Use Context7
-                    │
-                    └─► Insufficient? ────────► Fallback to Firecrawl
-```
-
-### When to Use Each Source
-
-| Source | Best For | Limitations |
-|--------|----------|-------------|
-| **Context7** | Popular libraries, frameworks, SDKs (React, FastAPI, boto3, etc.) | Only known libraries, no arbitrary URLs |
-| **Firecrawl** | Direct URLs, blogs, niche tools, general topics | Raw scraping, messier output |
-
-## Variable Declarations
-
-### Input Variables
-- **Search Topic/URL**: `$1` - The topic to search for or direct URL to fetch
-- **Output Filename**: `$2` (optional) - Custom filename for the output (defaults to sanitized topic name)
-- **Source Flag**: `--firecrawl` or `--context7` (optional) - Force a specific source
-
-### Working Variables
-- **Target Directory**: `documentation/reference/`
-- **Existing File Path**: Discovered via glob pattern matching
-- **File Age**: Calculated from file modification time
-- **24 Hour Threshold**: 86400 seconds
-- **Selected Source**: Context7 or Firecrawl
-- **Fetch Results**: Content retrieved from selected source
-
-### Output Variables
-- **Summary File**: Markdown file in documentation/reference/ folder
-- **Creation Status**: New file created or existing file updated
-- **Content Statistics**: Word count, sections created, source used
-
-## Setup Tasks
-
-### 1. Parse Arguments
-- Extract topic/URL from arguments
-- Check for `--firecrawl` or `--context7` flags
-- Strip flags from topic before processing
-
-### 2. Check for Existing Documentation
-- Use Glob tool to search for existing files matching the topic pattern
-- If files found, check their modification time using Read tool
-- Compare with current time to determine if older than 24 hours
-
-### 3. Handle Existing Files
-If existing file is older than 24 hours:
-- Display file information and age
-- ASK FOR PERMISSION before deletion (not auto-allowed)
-- Only proceed with user confirmation
-
-### 4. Prepare Output Path
-- Sanitize topic name for filename if $2 not provided
-- Ensure documentation/reference/ directory exists
-- Determine final output path
-
-## Workflow
-
-### Phase 1: Discovery
-1. **Parse Input**
-   - Detect if input is URL (starts with http) or topic
-   - Check for source override flags
-   - Report: "Input: [topic/url], Source override: [none/firecrawl/context7]"
-
-2. **Check Existing Files**
-   - Look for existing reference documentation on the topic
-   - Calculate file age if found
-   - Report findings to user
-
-3. **User Confirmation**
-   - If file exists and is >24 hours old:
-     - Ask: "Found existing file [name] from [date]. Update it?"
-   - If file exists and is <24 hours old:
-     - Inform: "Recent file exists (created [time] ago). Skipping update."
-
-### Phase 2: Source Selection & Fetching
-
-#### If `--firecrawl` flag or input is URL:
-- Skip Context7, go directly to Firecrawl
-- Report: "Using Firecrawl (forced/URL detected)"
-
-#### If `--context7` flag:
-- Use Context7 only, no fallback
-- Report: "Using Context7 only (forced)"
-
-#### Default (topic without flags):
-1. **Try Context7 First**
-   - Report: "Trying Context7 for structured documentation..."
-   - Use `mcp__context7__resolve-library-id` to find library
-   - Use `mcp__context7__get-library-docs` to fetch docs
-
-2. **Evaluate Result Sufficiency**
-   A Context7 result is **insufficient** if ANY of:
-   - No content returned / library not found
-   - Content is under ~500 words AND has no code examples
-   - Content appears to be an error message
-
-3. **Fallback to Firecrawl if Insufficient**
-   - Report: "Context7 result insufficient, falling back to Firecrawl..."
-   - Use `mcp__firecrawl__firecrawl_search` to find sources
-   - Scrape top results
-
-#### Firecrawl Operations
-- For URLs: Use `mcp__firecrawl__firecrawl_scrape`
-- For topics: Use `mcp__firecrawl__firecrawl_search` with scraping
-- Fetch comprehensive content with markdown format
-
-### Phase 3: Content Processing
-1. **Organize Information**
-   - Structure content with clear sections
-   - Add metadata (fetch date, source used)
-   - Create table of contents
-   - Ensure information density
-
-2. **Format Document**
-   - Add header with title and last updated date
-   - Include source attribution (Context7 or Firecrawl + URLs)
-   - Organize by logical sections
-   - Add summary at the top
-
-### Phase 4: File Creation
-1. **Write Documentation File**
-   - Save to documentation/reference/ folder
-   - Use descriptive filename
-   - Include generation metadata
-
-2. **Validation**
-   - Verify file was created successfully
-   - Check file size and content
-   - Confirm markdown formatting
-
-## Reporting Format
-
-### Success Report
-```
-✅ Reference Documentation Created/Updated
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-📄 File: documentation/reference/[filename].md
-🔍 Source: [Context7|Firecrawl] [fallback note if applicable]
-📊 Size: [X] KB, [Y] sections
-⏰ Generated: [timestamp]
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Summary:
-- [Key point 1]
-- [Key point 2]
-- [Key point 3]
-
-Use '/reference-fetch [topic]' to fetch other documentation
-Use '--firecrawl' or '--context7' to force a specific source
-```
-
-### Skipped Report (Recent File Exists)
-```
-ℹ️ Recent Documentation Exists
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-📄 File: documentation/reference/[filename].md
-⏰ Created: [X] hours ago
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-File is less than 24 hours old. Skipping update.
-To force update, delete the existing file first.
-```
-
-### Fallback Report
-```
-⚠️ Context7 Insufficient, Using Firecrawl
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Reason: [Library not found | Content too sparse | No code examples]
-Falling back to web search...
-```
-
-### Error Handling
-- Context7 not available: Automatically use Firecrawl
-- Network errors: Retry with fallback sources
-- No results found: Suggest alternative search terms
-- Permission denied: Explain why deletion wasn't allowed
-- Invalid URL: Provide format guidance

package/dist/store/skills/skill-creator/LICENSE.txt

@@ -1,202 +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 [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/dist/store/skills/skill-creator/SKILL.md

@@ -1,246 +0,0 @@
----
-name: skill-creator
-version: 1.0.1
-updated: 2026-02-22
-description: Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
----
-
-# Skill Creator
-
-This skill provides guidance for creating effective skills.
-
-## About Skills
-
-Skills are modular, self-contained packages that extend Claude's capabilities by providing
-specialized knowledge, workflows, and tools. Think of them as "onboarding guides" for specific
-domains or tasks—they transform Claude from a general-purpose agent into a specialized agent
-equipped with procedural knowledge that no model can fully possess.
-
-### What Skills Provide
-
-1. Specialized workflows - Multi-step procedures for specific domains
-2. Tool integrations - Instructions for working with specific file formats or APIs
-3. Domain expertise - Company-specific knowledge, schemas, business logic
-4. Bundled resources - Scripts, references, and assets for complex and repetitive tasks
-
-### Anatomy of a Skill
-
-Every skill consists of a required SKILL.md file and optional bundled resources:
-
-```
-skill-name/
-├── SKILL.md (required)
-│   ├── YAML frontmatter metadata (required)
-│   │   ├── name: (required)
-│   │   └── description: (required)
-│   └── Markdown instructions (required)
-└── Bundled Resources (optional)
-    ├── scripts/          - Executable code (Python/Bash/etc.)
-    ├── references/       - Documentation intended to be loaded into context as needed
-    └── assets/           - Files used in output (templates, icons, fonts, etc.)
-```
-
-#### SKILL.md (required)
-
-**Metadata Quality:** The `name` and `description` in YAML frontmatter determine when Claude will use the skill. Be specific about what the skill does and when to use it. Use the third-person (e.g. "This skill should be used when..." instead of "Use this skill when...").
-
-#### Bundled Resources (optional)
-
-##### Scripts (`scripts/`)
-
-Executable code (Python/Bash/etc.) for tasks that require deterministic reliability or are repeatedly rewritten.
-
-- **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 Claude for patching or environment-specific adjustments
-
-##### References (`references/`)
-
-Documentation and reference material intended to be loaded as needed into context to inform Claude's process and thinking.
-
-- **When to include**: For documentation that Claude 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 Claude 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 to be loaded into context, but rather used within the output Claude produces.
-
-- **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 Claude to use files without loading them into context
-
-### Progressive Disclosure Design Principle
-
-Skills use a three-level loading system to manage context efficiently:
-
-1. **Metadata (name + description)** - Always in context (~100 words)
-2. **SKILL.md body** - When skill triggers (<5k words)
-3. **Bundled resources** - As needed by Claude (Unlimited*)
-
-*Unlimited because scripts can be executed without reading into context window.
-
-## Skill Creation Process
-
-To create a skill, follow the "Skill Creation Process" in order, skipping steps only if there is a clear reason why they are not applicable.
-
-### Step 1: Understanding the Skill with Concrete Examples
-
-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
-
-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.
-
-**Evaluate self-maintenance need**: If the skill involves any of these, suggest self-maintaining capabilities (see "Self-Maintaining Skills" section):
-- Evolving reference material that may drift from reality (codebase context, documentation)
-- Heuristics or triggers that may need tuning based on experience
-- Accumulated learnings or notes over time
-
-### Step 3: Initializing the Skill
-
-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
-
-When editing the (newly-generated or existing) skill, remember that the skill is being created for another instance of Claude to use. Focus on including information that would be beneficial and non-obvious to Claude. Consider what procedural knowledge, domain-specific details, or reusable assets would help another Claude instance execute these tasks more effectively.
-
-#### 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/`.
-
-Also, delete any example files and directories not needed for the skill. 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 Style:** Write the entire skill using **imperative/infinitive form** (verb-first instructions), not second person. Use objective, instructional language (e.g., "To accomplish X, do Y" rather than "You should do X" or "If you need to do X"). This maintains consistency and clarity for AI consumption.
-
-To complete SKILL.md, answer the following questions:
-
-1. What is the purpose of the skill, in a few sentences?
-2. When should the skill be used?
-3. In practice, how should Claude use the skill? All reusable skill contents developed above should be referenced so that Claude knows how to use them.
-
-### Step 5: Validating a Skill
-
-Once the skill is ready, validate it to ensure it meets structural requirements:
-
-```bash
-scripts/quick_validate.py <path/to/skill-folder>
-```
-
-The validator checks:
-- YAML frontmatter format and required fields
-- Skill naming conventions and directory structure
-- Description completeness and quality
-- File organization and resource references
-
-Skills are created as folders directly in `.claude/skills/` - no zip packaging required for project-local skills. The `package_skill.py` script exists for distribution scenarios but is optional.
-
-### 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.
-
-**Iteration workflow:**
-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
-
-## Self-Maintaining Skills
-
-Some skills benefit from self-improvement capabilities - the ability to evaluate their own performance and suggest updates when challenged.
-
-### When to Include Self-Maintenance
-
-Consider self-maintenance for skills that:
-- Manage evolving reference material (codebase context, documentation)
-- Have heuristics that may need tuning based on experience
-- Accumulate learnings over time
-
-### Self-Maintenance Pattern
-
-When a user challenges what the skill did ("you should have known this", "why didn't you do X"):
-
-1. **Evaluate the action**: What did the skill do or fail to do?
-2. **Identify root cause**: Why? Bad heuristic, missing information, stale reference, wrong trigger?
-3. **Propose improvement**: Suggest a specific change to address the gap
-4. **Await approval**: Only update skill files (SKILL.md, doctrine, core references) with explicit user consent
-5. **Document the change**: If approved, make the update and briefly note what changed
-
-### Permission Boundaries
-
-Define which files the skill can update autonomously vs. which require approval:
-
-| Update Type | Permission |
-|-------------|------------|
-| Reference content (area details, examples) | Can update in stride |
-| Index/metadata (dates, triggers) | Can update in stride |
-| Core skill logic (SKILL.md) | Requires approval |
-| Operational doctrine | Requires approval |
-
-### Avoiding Bloat
-
-Self-improvement notes and learnings should be:
-- Concise: short phrase tweaks, not paragraphs
-- Prunable: old/obsolete notes get removed
-- Bounded: set limits on accumulated learnings (e.g., max 10 notes per area)
-
-When suggesting changes, prefer minimal edits that address the specific issue over broad restructuring.