@zenobius/opencode-skillful 1.0.0 → 1.1.0-next.3

package/README.md

@@ -2,7 +2,7 @@
 
 An interpretation of the [Anthropic Agent Skills Specification](https://github.com/anthropics/skills) for OpenCode, providing lazy-loaded skill discovery and injection.
 
-Differenator is : 
+Differentiators include:
 
 - Conversationally the agent uses `skill_find words, words words` to discover skills
 - The agent uses `skill_use fully_resolved_skill_name` and,
@@ -68,20 +68,19 @@ skill_find "testing -performance"
 
 ## Features
 
-- :mag: Discover SKILL.md files from multiple locations
-- :zap: Lazy loading - skills only inject when explicitly requested
-- :file_folder: Path prefix matching for organized skill browsing
-- :abc: Natural query syntax with negation and quoted phrases
-- :label: Skill ranking by relevance (name matches weighted higher)
-- :recycle: Silent message insertion (noReply pattern)
+- Discover SKILL.md files from multiple locations
+- Lazy loading - skills only inject when explicitly requested
+- Path prefix matching for organized skill browsing
+- Natural query syntax with negation and quoted phrases
+- Skill ranking by relevance (name matches weighted higher)
+- Silent message insertion (noReply pattern)
 
 ## Skill Discovery Paths
 
 Skills are discovered from these locations (in priority order, last wins on duplicates):
 
-1. `~/.opencode/skills/` - User global skills (lowest priority)
-2. `~/.config/opencode/skills/` - Standard XDG config location
-3. `.opencode/skills/` - Project-local skills (highest priority)
+1. `~/.config/opencode/skills/` - Standard XDG config location or (`%APPDATA%/.opencode/skills` for windows users)
+2. `.opencode/skills/` - Project-local skills (highest priority)
 
 ## Usage in OpenCode
 
@@ -89,69 +88,598 @@ Skills are discovered from these locations (in priority order, last wins on dupl
 
 ```
 # List all available skills
-skill_find
-  query="*"
+skill_find query="*"
 
 # Search by keyword
-skill_find
-  query="git commit"
-
-# Path prefix matching
-skill_find
-  query="experts/data-ai"
+skill_find query="git commit"
 
 # Exclude terms
-skill_find
-  query="testing -performance"
+skill_find query="testing -performance"
 ```
 
 ### Loading Skills
 
+Skills must be loaded by their fully-qualified identifier (generated from the directory path).
+
+The skill identifier is created by converting the directory path to a slug: directory separators and hyphens become underscores.
+
+```
+skills/
+  experts/
+    ai/
+      agentic-engineer/        # Identifier: experts_ai_agentic_engineer
+  superpowers/
+    writing/
+      code-review/             # Identifier: superpowers_writing_code_review
+```
+
+When loading skills, use the full identifier:
+
 ```
-# Load a single skill
-skill_use
-  skill_names=["writing-git-commits"]
+# Load a skill by its identifier
+skill_use skill_names=["experts_ai_agentic_engineer"]
 
 # Load multiple skills
-skill_use
-  skill_names=["writing-git-commits", "code-review"]
+skill_use skill_names=["experts_ai_agentic_engineer", "superpowers_writing_code_review"]
 ```
 
 ### Reading Skill Resources
 
 ```
-# Read a resource file from a skill's directory
-skill_resource
-  skill_name="brand-guidelines"
-  relative_path="templates/logo-usage.md"
+
+# Read a reference document
+
+skill_resource skill_name="writing-git-commits" relative_path="references/style-guide.md"
+
+# Read a template
+
+skill_resource skill_name="brand-guidelines" relative_path="assets/logo-usage.html"
+
+```
+
+Normally you won't need to use `skill_resource` directly, since the llm will do it for you.
+
+When skill_use is called, it will be wrapped with instructions to the llm on
+how to load references, assets, and scripts from the skill.
+
+But when writing your skills, there's nothing stopping you from using `skill_resource` to be explicit.
+
+(Just be aware that exotic file types might need special tooling to handle them properly.)
+
+### Executing Skill Scripts
+
+```
+
+# Execute a script without arguments
+
+skill_exec skill_name="build-utils" relative_path="scripts/generate-changelog.sh"
+
+# Execute a script with arguments
+
+skill_exec skill_name="code-generator" relative_path="scripts/gen.py" args=["--format", "json", "--output", "schema.json"]
+
 ```
 
 ## Plugin Tools
 
-### `skill_find`
+The plugin provides four core tools implemented in `src/tools/`:
+
+### `skill_find` (SkillFinder.ts)
+
+Search for skills using natural query syntax with intelligent ranking by relevance.
 
-Search for skills using natural query syntax.
+**Parameters:**
 
 - `query`: Search string supporting:
   - `*` or empty: List all skills
-  - Path prefixes: `experts`, `superpowers/writing`
-  - Keywords: `git commit`
-  - Negation: `-term`
-  - Quoted phrases: `"exact match"`
+  - Path prefixes: `experts`, `superpowers/writing` (prefix matching)
+  - Keywords: `git commit` (multiple terms use AND logic)
+  - Negation: `-term` (exclude results)
+  - Quoted phrases: `"exact match"` (phrase matching)
+
+**Returns:**
+
+- List of matching skills with:
+  - `skill_name`: Skill identifier (e.g., `experts_writing_git_commits`)
+  - `skill_shortname`: Directory name of the skill (e.g., `writing-git-commits`)
+  - `description`: Human-readable description
+- If config.debug is enabled:
+  - Debug information: discovered count, parsed results, rejections, duplicates, errors
+
+**Example Response:**
+
+```xml
+<SkillSearchResults query="git commit">
+  <Skills>
+    <Skill skill_name="experts_writing_git_commits" skill_shortname="writing-git-commits">
+      Guidelines for writing effective git commit messages
+    </Skill>
+  </Skills>
+  <Summary>
+    <Total>42</Total>
+    <Matches>1</Matches>
+    <Feedback>Found 1 skill matching your query</Feedback>
+  </Summary>
+</SkillSearchResults>
+```
+
+### `skill_use` (SkillUser.ts)
+
+Load one or more skills into the chat context with full resource metadata.
+
+**Parameters:**
+
+- `skill_names`: Array of skill identifiers to load (e.g., `experts_ai_agentic_engineer`)
+
+**Features:**
+
+- Injects skill metadata and content including:
+  - Skill name and description
+  - Resource inventory:
+    - `references`: Documentation and reference files
+    - `assets`: Binary files, templates, images
+    - `scripts`: Executable scripts with paths and MIME types
+  - Full skill content formatted as Markdown for easy reading
+  - Base directory context for relative path resolution
+
+**Behavior:** Silently injects skills as user messages (persists in conversation history)
+
+**Example Response:**
 
-### `skill_use`
+```json
+{ "loaded": ["experts/writing-git-commits"], "notFound": [] }
+```
+
+### `skill_resource` (SkillResourceReader.ts)
 
-Load one or more skills into the chat context.
+Read a specific resource file from a skill's directory and inject silently into the chat.
 
-- `skill_names`: Array of skill names to load (by toolName or short name)
+**When to Use:**
 
-### `skill_resource`
+- Load specific reference documents or templates from a skill
+- Access supporting files without loading the entire skill
+- Retrieve examples, guides, or configuration templates
+- Most commonly used after loading a skill with `skill_use` to access its resources
 
-Read a resource file from a skill's directory.
+**Parameters:**
 
-- `skill_name`: The skill containing the resource
+- `skill_name`: The skill containing the resource (by toolName/FQDN or short name)
 - `relative_path`: Path to the resource relative to the skill directory
 
+**Returns:**
+
+- MIME type of the resource
+- Success confirmation with skill name, resource path, and type
+
+**Behavior:**
+
+- Silently injects resource content without triggering AI response (noReply pattern)
+- Resolves relative paths within skill directory (e.g., `references/guide.md`, `assets/template.html`, `scripts/setup.sh`)
+- Supports any text or binary file type
+
+**Example Response:**
+
+```
+Load Skill Resource
+
+  skill: experts/writing-git-commits
+  resource: templates/commit-template.md
+  type: text/markdown
+```
+
+### `skill_exec` (SkillScriptExec.ts)
+
+Execute scripts from skill resources with optional arguments.
+
+**Parameters:**
+
+- `skill_name`: The skill containing the script (by toolName/FQDN or short name)
+- `relative_path`: Path to the script file relative to the skill directory
+- `args`: Optional array of string arguments to pass to the script
+
+**Returns:**
+
+- Exit code of the script execution
+- Standard output (stdout)
+- Standard error (stderr)
+- Formatted text representation
+
+**Behavior:**
+
+- Locates and executes scripts within skill directories
+- Passes arguments to the script
+- Silently injects execution results
+- Includes proper error handling and reporting
+
+**Example Response:**
+
+```
+Executed script from skill "build-utils": scripts/generate-changelog.sh
+
+Exit Code: 0
+STDOUT: Changelog generated successfully
+STDERR: (none)
+```
+
+## Error Handling
+
+### skill_find Errors
+
+When a search query doesn't match any skills, the response includes feedback:
+
+```xml
+<SkillSearchResults query="nonexistent">
+  <Skills></Skills>
+  <Summary>
+    <Total>42</Total>
+    <Matches>0</Matches>
+    <Feedback>No skills found matching your query</Feedback>
+  </Summary>
+</SkillSearchResults>
+```
+
+### skill_use Errors
+
+When loading skills, if a skill name is not found, it's returned in the `notFound` array:
+
+```json
+{ "loaded": ["writing-git-commits"], "notFound": ["nonexistent-skill"] }
+```
+
+The loaded skills are still injected into the conversation, allowing you to use available skills even if some are not found.
+
+### skill_resource Errors
+
+Resource loading failures occur when:
+
+- The skill doesn't exist
+- The resource path doesn't exist within the skill
+- The file cannot be read due to permissions
+
+The tool returns an error message indicating which skill or resource path was problematic.
+
+### skill_exec Errors
+
+Script execution includes exit codes and error output:
+
+```
+Executed script from skill "build-utils": scripts/generate-changelog.sh
+
+Exit Code: 1
+STDOUT: (partial output)
+STDERR: Permission denied: scripts/generate-changelog.sh
+```
+
+Non-zero exit codes indicate script failures. Always check STDERR and the exit code when troubleshooting.
+
+## Configuration
+
+The plugin reads configuration from the OpenCode config file (`~/.config/opencode/config.json`):
+
+```json
+{
+  "plugins": ["@zenobius/opencode-skillful"],
+  "skillful": {
+    "debug": false,
+    "basePaths": ["~/.config/opencode/skills", ".opencode/skills"]
+  }
+}
+```
+
+### Configuration Options
+
+- **debug** (boolean, default: `false`): Enable debug output showing skill discovery stats
+  - When enabled, `skill_find` includes discovered, parsed, rejected, and duplicate counts
+  - Useful for diagnosing skill loading issues
+- **basePaths** (array, default: standard locations): Custom skill search directories
+  - Paths are searched in order; later paths override earlier ones for duplicate skill names
+  - Use project-local `.opencode/skills/` for project-specific skills
+
+## Architecture
+
+### System Design Overview
+
+The plugin uses a **layered, modular architecture** with clear separation of concerns and two-phase initialization.
+
+#### Design Principles
+
+- **Async Coordination**: ReadyStateMachine ensures tools don't execute before registry initialization completes
+- **Security-First Resource Access**: All resources are pre-indexed at parse time; no path traversal possible
+- **Factory Pattern**: Centralized API creation for easy testing and configuration management
+- **Lazy Loading**: Skills only injected when explicitly requested, minimal memory overhead
+
+### System Layers
+
+```
+┌──────────────────────────────────────────────────────┐
+│ Plugin Entry Point (index.ts)                        │
+│ - Defines 3 core tools: skill_find, skill_use,      │
+│   skill_resource                                     │
+│ - Initializes API factory and config                │
+│ - Manages message injection (XML serialization)      │
+└──────────────────────────────────────────────────────┘
+                          ↓
+┌──────────────────────────────────────────────────────┐
+│ API Factory Layer (api.ts, config.ts)                │
+│ - createApi(): initializes logger, registry, tools   │
+│ - getPluginConfig(): resolves base paths with proper │
+│   precedence (project-local overrides global)        │
+└──────────────────────────────────────────────────────┘
+                          ↓
+┌──────────────────────────────────────────────────────┐
+│ Services Layer (src/services/)                       │
+│ - SkillRegistry: discovery, parsing, resource       │
+│   mapping with ReadyStateMachine coordination        │
+│ - SkillSearcher: query parsing + intelligent ranking│
+│ - SkillResourceResolver: safe path-based retrieval   │
+│ - SkillFs (via lib): filesystem abstraction (mockable)
+└──────────────────────────────────────────────────────┘
+                          ↓
+┌──────────────────────────────────────────────────────┐
+│ Core Libraries (src/lib/)                            │
+│ - ReadyStateMachine: async initialization sequencing │
+│ - SkillFs: abstract filesystem operations            │
+│ - Identifiers: path ↔ tool name conversions          │
+│ - OpenCodeChat: message injection abstraction        │
+│ - xml.ts: JSON → XML serialization                   │
+└──────────────────────────────────────────────────────┘
+```
+
+### Initialization Flow (Why This Matters)
+
+The plugin uses a **two-phase initialization pattern** to coordinate async discovery with tool execution:
+
+```
+PHASE 1: SYNCHRONOUS CREATION
+├─ Plugin loads configuration
+├─ createApi() called:
+│  ├─ Creates logger
+│  ├─ Creates SkillRegistry (factory, NOT initialized yet)
+│  └─ Returns registry + tool creators
+└─ index.ts registers tools immediately
+
+PHASE 2: ASYNCHRONOUS DISCOVERY (Background)
+├─ registry.initialise() called
+│  ├─ Sets ready state to "loading"
+│  ├─ Scans all base paths for SKILL.md files
+│  ├─ Parses each file (YAML frontmatter + resources)
+│  ├─ Pre-indexes all resources (scripts/assets/references)
+│  └─ Sets ready state to "ready"
+│
+└─ WHY PRE-INDEXING: Prevents path traversal attacks.
+   Tools can only retrieve pre-registered resources,
+   never arbitrary filesystem paths.
+
+PHASE 3: TOOL EXECUTION (User Requested)
+├─ User calls: skill_find("git commits")
+├─ Tool executes:
+│  ├─ await registry.controller.ready.whenReady()
+│  │  (blocks until Phase 2 completes)
+│  ├─ Search registry
+│  └─ Return results
+└─ WHY THIS PATTERN: Multiple tools can call whenReady()
+   at different times without race conditions.
+   Simple Promise would resolve once; this allows
+   concurrent waiters.
+```
+
+### Data Flow Diagram: skill_find Query
+
+```
+┌─────────────────────────────────────────┐
+│ User Query: skill_find("git commit")    │
+└────────────┬────────────────────────────┘
+             ↓
+┌─────────────────────────────────────────┐
+│ SkillFinder Tool (tools/SkillFinder.ts) │
+│ - Validates query string                │
+│ - Awaits: controller.ready.whenReady()  │
+└────────────┬────────────────────────────┘
+             ↓ (continues when registry ready)
+┌─────────────────────────────────────────┐
+│ SkillSearcher.search()                  │
+│ - Parse query via search-string library │
+│   ("git commit" → include: [git,commit])│
+│ - Filter ALL include terms must match   │
+│   (name, description, or toolName)      │
+│ - Exclude results matching exclude      │
+│   terms                                 │
+│ - Rank results:                         │
+│   * nameMatches × 3 (strong signal)     │
+│   * descMatches × 1 (weak signal)       │
+│   * exact match bonus +10                │
+└────────────┬────────────────────────────┘
+             ↓
+┌─────────────────────────────────────────┐
+│ Results with Feedback                   │
+│ - Matched skills array                  │
+│ - Sorted by relevance score             │
+│ - User-friendly feedback message        │
+│   "Searching for: **git commit** |      │
+│    Found 3 matches"                     │
+└────────────┬────────────────────────────┘
+             ↓
+┌─────────────────────────────────────────┐
+│ Format & Return (index.ts)              │
+│ - Convert to XML via jsonToXml()        │
+│ - Inject into message context           │
+│ - Return to user                        │
+└─────────────────────────────────────────┘
+```
+
+### Data Flow Diagram: skill_use Loading
+
+```
+┌──────────────────────────────────┐
+│ User: skill_use("git-commits")   │
+└────────────┬─────────────────────┘
+             ↓
+┌──────────────────────────────────┐
+│ SkillUser Tool (tools/SkillUser) │
+│ - Await ready state              │
+│ - Validate skill names           │
+└────────────┬─────────────────────┘
+             ↓
+┌──────────────────────────────────┐
+│ Registry.controller.get(key)     │
+│ - Look up skill in Map           │
+│ - Return Skill object with:      │
+│   * Name, description            │
+│   * Content (markdown)           │
+│   * Resource maps (indexed)      │
+└────────────┬─────────────────────┘
+             ↓
+┌──────────────────────────────────┐
+│ Format Skill for Injection       │
+│ - Skill metadata                 │
+│ - Resource inventory (with MIME) │
+│ - Full content as markdown       │
+│ - Base directory context         │
+└────────────┬─────────────────────┘
+             ↓
+┌──────────────────────────────────┐
+│ Silent Injection Pattern         │
+│ - Inject as user message         │
+│ - Persists in conversation       │
+│ - Returns success summary        │
+│   { loaded: [...], notFound: []}│
+└──────────────────────────────────┘
+```
+
+### Data Flow Diagram: skill_resource Access
+
+```
+┌──────────────────────────────────────────────┐
+│ User: skill_resource("git-commits",         │
+│                     "scripts/commit.sh")     │
+└──────────────┬───────────────────────────────┘
+               ↓
+┌──────────────────────────────────────────────┐
+│ SkillResourceReader Tool                     │
+│ (tools/SkillResourceReader.ts)               │
+│ - Validate skill_name                       │
+│ - Parse path: "scripts/commit.sh"            │
+│   ├─ type = "scripts"                        │
+│   └─ relative_path = "commit.sh"             │
+│ - Assert type is valid (scripts|assets|refs)│
+└──────────────┬───────────────────────────────┘
+               ↓
+┌──────────────────────────────────────────────┐
+│ SkillResourceResolver                       │
+│ - Fetch skill object from registry           │
+│ - Look up in skill.scripts Map               │
+│   (pre-indexed at parse time)                │
+│ - Retrieve: { absolutePath, mimeType }      │
+│                                              │
+│ ★ SECURITY: Only pre-indexed paths exist    │
+│   No way to request ../../../etc/passwd      │
+└──────────────┬───────────────────────────────┘
+               ↓
+┌──────────────────────────────────────────────┐
+│ File I/O (SkillFs abstraction)               │
+│ - Read file content from absolutePath        │
+│ - Detect MIME type (e.g., text/plain)       │
+└──────────────┬───────────────────────────────┘
+               ↓
+┌──────────────────────────────────────────────┐
+│ Return Injection Object                      │
+│ {                                            │
+│   skill_name,                                │
+│   resource_path,                             │
+│   resource_mimetype,                         │
+│   content                                    │
+│ }                                            │
+└──────────────┬───────────────────────────────┘
+               ↓
+┌──────────────────────────────────────────────┐
+│ Silent Injection                             │
+│ - Inject content into message                │
+│ - User sees resource inline                  │
+└──────────────────────────────────────────────┘
+```
+
+### Key Design Decisions and Their Rationale
+
+| Decision                     | Why                                                | Impact                                                       |
+| ---------------------------- | -------------------------------------------------- | ------------------------------------------------------------ |
+| **ReadyStateMachine**        | Ensures tools don't race with async registry setup | Tools are guaranteed registry is ready before execution      |
+| **Pre-indexed Resources**    | Prevents path traversal attacks                    | Security: only pre-registered paths retrievable              |
+| **Factory Pattern (api.ts)** | Centralizes initialization                         | Easy to test, swap implementations, mock components          |
+| **Removed SkillProvider**    | Eliminated unnecessary abstraction                 | Simpler code, direct registry access, easier debugging       |
+| **XML Serialization**        | Human-readable message injection                   | Results display nicely formatted in chat context             |
+| **Two-phase Init**           | Async discovery doesn't block tool registration    | Tools available immediately, discovery happens in background |
+
+### Services Layer Breakdown
+
+#### SkillRegistry (`src/services/SkillRegistry.ts`)
+
+- **Role**: Central skill catalog and discovery engine
+- **Responsibilities**:
+  1. Scan multiple base paths for SKILL.md files (recursive)
+  2. Parse each file's YAML frontmatter (validates schema)
+  3. Index all resources (scripts/assets/references) for safe retrieval
+  4. Register skills in controller.skills Map by toolName
+  5. Coordinate initialization via ReadyStateMachine
+- **Key Methods**:
+  - `initialise()`: Async discovery and parsing pipeline
+  - `register()`: Parse and store skill files
+  - `parseSkill()`: Extract metadata and resource paths
+- **Error Handling**: Malformed skills logged but don't halt discovery
+
+#### SkillSearcher (`src/services/SkillSearcher.ts`)
+
+- **Role**: Natural language query interpretation and ranking
+- **Responsibilities**:
+  1. Parse queries using search-string library (Gmail syntax)
+  2. Filter: ALL include terms must match (AND logic)
+  3. Exclude: Remove results matching exclude terms
+  4. Rank by relevance (name matches 3×, description 1×, exact +10)
+  5. Generate user-friendly feedback
+- **Scoring Formula**: `(nameMatches × 3) + (descMatches × 1) + exactBonus`
+- **Edge Cases**: Empty queries or "\*" list all skills
+
+### Tools Layer Overview
+
+#### SkillFinder (`src/tools/SkillFinder.ts`)
+
+- Wraps SkillSearcher with ready-state synchronization
+- Transforms results to SkillFinder schema
+- Returns matched skills + summary metadata
+
+#### SkillUser (`src/tools/SkillUser.ts`)
+
+- Loads skills into chat context
+- Injects as user message (persists in conversation)
+- Returns { loaded: [...], notFound: [...] }
+
+#### SkillResourceReader (`src/tools/SkillResourceReader.ts`)
+
+- Safe resource path parsing and validation
+- Pre-indexed path lookup (prevents traversal)
+- Returns injection object with MIME type and content
+
+### Configuration and Path Resolution
+
+```
+Configuration Priority (Last Wins):
+1. Global: ~/.opencode/skills/ (lowest)
+2. Project: ./.opencode/skills/ (highest)
+
+Why This Order:
+- Users install global skills once
+- Projects override with local versions
+- Same skill name in both → project version wins
+```
+
+## Contributing
+
+Contributions are welcome! When adding features, follow these principles:
+
+- **Explain the WHY, not the WHAT**: Code comments should document design decisions, not mechanics
+- **Keep modules focused**: Each file has one primary responsibility
+- **Test async behavior**: Ready state coordination is critical
+- **Document algorithms**: Ranking, parsing, and search logic should have detailed comments
+
 ## Creating Skills
 
 Skills follow the [Anthropic Agent Skills Specification](https://github.com/anthropics/skills). Each skill is a directory containing a `SKILL.md` file:
@@ -164,18 +692,28 @@ skills/
       template.md
 ```
 
+### Skill Structure
+
+```
+my-skill/
+  SKILL.md                 # Required: Skill metadata and instructions
+  references/              # Optional: Documentation and guides
+    guide.md
+    examples.md
+  assets/                  # Optional: Binary files and templates
+    template.html
+    logo.png
+  scripts/                 # Optional: Executable scripts
+    setup.sh
+    generate.py
+```
+
 ### SKILL.md Format
 
 ```yaml
 ---
 name: my-skill
 description: A brief description of what this skill does (min 20 chars)
-license: MIT
-allowed-tools:
-  - bash
-  - read
-metadata:
-  author: Your Name
 ---
 # My Skill
 
@@ -185,9 +723,28 @@ Instructions for the AI agent when this skill is loaded...
 **Requirements:**
 
 - `name` must match the directory name (lowercase, alphanumeric, hyphens only)
-- `description` must be at least 20 characters
+- `description` must be at least 20 characters and should be concise (under 500 characters recommended)
+  - Focus on when to use the skill, not what it does
+  - Include specific triggering conditions and symptoms
+  - Use third person for system prompt injection
+  - Example: "Use when designing REST APIs to establish consistent patterns and improve developer experience"
 - Directory name and frontmatter `name` must match exactly
 
+### Resource Types
+
+Skill resources are automatically discovered and categorized:
+
+- **References** (`references/` directory): Documentation, guides, and reference materials
+  - Typically Markdown, plaintext, or HTML files
+  - Accessed via `skill_resource` for reading documentation
+- **Assets** (`assets/` directory): Templates, images, and binary files
+  - Can include HTML templates, images, configuration files
+  - Useful for providing templates and examples to the AI
+- **Scripts** (`scripts/` directory): Executable scripts that perform actions
+  - Shell scripts (.sh), Python scripts (.py), or other executables
+  - Executed via `skill_exec` with optional arguments
+  - Useful for automation, code generation, or complex operations
+
 ## Considerations
 
 - Skills are discovered at plugin initialization (requires restart to reload)