@botlearn/doc-gen 0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 BotLearn
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,35 @@
+# @botlearn/doc-gen
+
+> Automated documentation generation for APIs, READMEs, changelogs, and code-level docs — raising doc completeness from 30% to 90% for OpenClaw Agent
+
+## Installation
+
+```bash
+# via npm
+npm install @botlearn/doc-gen
+
+# via clawhub
+clawhub install @botlearn/doc-gen
+```
+
+## Category
+
+programming-assistance
+
+## Dependencies
+
+`@botlearn/code-gen`
+
+## Files
+
+| File | Description |
+|------|-------------|
+| `manifest.json` | Skill metadata and configuration |
+| `skill.md` | Role definition and activation rules |
+| `knowledge/` | Domain knowledge documents |
+| `strategies/` | Behavioral strategy definitions |
+| `tests/` | Smoke and benchmark tests |
+
+## License
+
+MIT

package/knowledge/anti-patterns.md

@@ -0,0 +1,70 @@
+---
+domain: doc-gen
+topic: anti-patterns
+priority: medium
+ttl: 30d
+---
+
+# Documentation Generation — Anti-Patterns
+
+## Content Anti-Patterns
+
+### 1. Auto-Generated Gibberish
+- **Problem**: Generating documentation that simply restates the function name in sentence form — `getUser` becomes "Gets the user" with no additional context about parameters, return values, edge cases, or usage
+- **Fix**: Every doc entry must add information beyond what the signature already tells the reader. Describe *behavior*, *constraints*, *side effects*, and *failure modes*. If `getUser(id)` hits a database, state that. If it caches, state the TTL. If it throws on invalid IDs, document the error
+
+### 2. Missing Examples
+- **Problem**: API documentation that describes what a function does but provides no example of how to call it or what output to expect. Users must read source code to understand usage patterns
+- **Fix**: Include at least one runnable example per public function. Show input, invocation, and expected output. For complex APIs, provide a basic example and an advanced example
+
+### 3. Stale Documentation
+- **Problem**: Documentation that describes behavior from a previous version of the code. Parameters that no longer exist, return types that have changed, or features that have been removed are still documented
+- **Fix**: Compare documentation against the current code before finalizing. Check that every documented parameter exists in the function signature. Verify return types match. Flag any documentation that references removed or renamed identifiers
+
+### 4. Copy-Paste Descriptions
+- **Problem**: Using identical descriptions across similar functions without adapting to the specific behavior of each — e.g., `createUser`, `updateUser`, `deleteUser` all described as "Manages user data"
+- **Fix**: Each function must have a description unique to its behavior. `createUser` inserts a new record, `updateUser` modifies an existing record (partial or full), `deleteUser` removes a record (soft or hard delete). State the specific action and its implications
+
+### 5. Undocumented Error Cases
+- **Problem**: Documentation only covers the happy path. Users discover thrown exceptions, rejection reasons, or error codes by encountering them at runtime
+- **Fix**: Document every error/exception the function can throw or return. Include the condition that triggers each error and the error type/code. For async functions, document both rejection reasons and possible error response shapes
+
+## Structural Anti-Patterns
+
+### 6. Wall of Text README
+- **Problem**: A README that is one continuous block of prose without headings, code blocks, or visual hierarchy. Users cannot scan for the information they need
+- **Fix**: Use the standard README structure with clear sections: Title, Install, Quick Start, API, Configuration, Contributing, License. Use headers, code blocks, tables, and bullet lists to create scannable content
+
+### 7. Missing Installation Instructions
+- **Problem**: Documentation assumes the reader already knows how to install and configure the project. No package manager commands, no peer dependencies listed, no environment requirements stated
+- **Fix**: Include explicit install commands for npm/yarn/pnpm. List all peer dependencies. State the minimum Node.js/Python/runtime version. Provide a verification step
+
+### 8. Orphaned API References
+- **Problem**: API documentation that exists in isolation without context — a list of functions with no guidance on which to use first, how they relate, or what workflow they support
+- **Fix**: Start API documentation with an overview section that explains the main use cases and which functions to call. Group related functions. Provide a "Getting Started" flow that walks through the primary workflow
+
+### 9. Inconsistent Formatting
+- **Problem**: Documentation mixes different styles: some functions use JSDoc, others use plain comments; some parameters are in tables, others in bullet lists; some examples use TypeScript, others plain JavaScript
+- **Fix**: Establish and follow a single documentation style guide. All functions use the same tag format. All parameters use the same presentation (table or list). All examples use the same language and style. Run a linter if available
+
+### 10. Changelog as Commit Log
+- **Problem**: The changelog is a raw dump of git commit messages — cryptic, inconsistent, and full of noise like "fix typo", "wip", "merge branch"
+- **Fix**: Curate changelog entries to describe user-facing changes only. Group by category (Added, Changed, Fixed, etc.). Write entries in imperative mood. Exclude internal refactors, typo fixes, and CI changes unless they affect users. Reference issue numbers
+
+## Quality Anti-Patterns
+
+### 11. Type Information Without Context
+- **Problem**: Documenting that a parameter is `string` without explaining what string values are valid — e.g., "id: string" tells the reader nothing about format (UUID? slug? numeric string?), length constraints, or validation rules
+- **Fix**: Always include semantic context with types: "id: string — A UUID v4 identifying the user (e.g., `550e8400-e29b-41d4-a716-446655440000`)" or "status: string — One of `active`, `suspended`, `deleted`"
+
+### 12. Documenting Private Internals as Public API
+- **Problem**: Documentation includes internal helper functions, private methods, or implementation details that users should not depend on, creating an implied contract on unstable APIs
+- **Fix**: Clearly separate public and internal documentation. Mark private/internal functions with `@internal` or `@private`. Exclude them from generated API docs by default. If internal details are documented for contributors, place them in a separate section or file (e.g., `ARCHITECTURE.md`)
+
+### 13. No Deprecation Migration Path
+- **Problem**: Marking a function as deprecated without explaining what to use instead or how to migrate existing code
+- **Fix**: Every deprecation notice must include: (1) what to use instead, (2) a code example showing the migration from old to new, (3) the version when the deprecated API will be removed. Example: `@deprecated Since v2.0. Use fetchUser() instead. Will be removed in v3.0.`
+
+### 14. Version-Blind Documentation
+- **Problem**: Documentation does not indicate which version of the software it applies to. Users on older versions follow instructions that fail, or miss features available in their version
+- **Fix**: Use `@since` tags to mark when APIs were introduced. Include version badges on READMEs. In changelogs, ensure version numbers and dates are accurate. For multi-version projects, provide version-specific documentation or clearly mark version requirements

package/knowledge/best-practices.md

@@ -0,0 +1,154 @@
+---
+domain: doc-gen
+topic: documentation-quality-and-coverage
+priority: high
+ttl: 30d
+---
+
+# Documentation Generation — Best Practices
+
+## API Documentation Coverage
+
+### 1. Completeness Checklist
+Every public API entry point must have:
+- **Summary** — One-sentence description of what the function/method does
+- **Description** — Detailed explanation of behavior, including edge cases
+- **Parameters** — Every parameter with name, type, default value, constraints, and description
+- **Return value** — Type and description of what is returned, including null/undefined cases
+- **Errors/Exceptions** — All throwable errors with conditions that trigger them
+- **Examples** — At least one usage example with realistic input and expected output
+- **Since/Version** — When the API was introduced or last changed
+
+### 2. Coverage Metrics
+Target documentation coverage levels:
+
+| Level | Coverage | Description |
+|-------|----------|-------------|
+| Minimal | 30% | Only function names and parameter names |
+| Basic | 50% | Summaries + parameter types |
+| Good | 70% | Full descriptions + return values + errors |
+| Excellent | 85% | All of above + examples + cross-references |
+| Complete | 90%+ | Full coverage including edge cases, deprecation notices, and migration guides |
+
+### 3. Measuring Coverage
+- Count **public exports** (functions, classes, types, constants) as the denominator
+- Count **fully documented** exports (meeting "Good" level) as the numerator
+- Report per-module coverage alongside aggregate project coverage
+
+## Example Quality Standards
+
+### Write Examples That Teach
+- Start with the **simplest possible usage** — demonstrate the happy path first
+- Follow with **common variations** — optional parameters, configuration options
+- End with **edge cases** — error handling, boundary conditions
+- Use **realistic data** — avoid `foo`, `bar`, `test123`; use domain-appropriate values
+
+### Example Structure Template
+```javascript
+// 1. Basic usage — what most users need
+const client = new ApiClient({ baseUrl: 'https://api.example.com' });
+const user = await client.getUser('usr_abc123');
+// => { id: 'usr_abc123', name: 'Alice', email: 'alice@example.com' }
+
+// 2. With options — common customization
+const users = await client.listUsers({ limit: 10, role: 'admin' });
+// => [{ id: 'usr_abc123', ... }, ...]
+
+// 3. Error handling — what can go wrong
+try {
+  await client.getUser('nonexistent');
+} catch (error) {
+  if (error instanceof NotFoundError) {
+    console.log(error.message); // => "User not found: nonexistent"
+  }
+}
+```
+
+### Example Anti-Patterns to Avoid
+- Trivial examples that don't demonstrate real value: `add(1, 2) // => 3`
+- Examples that depend on external state without setup context
+- Examples with fictional imports or unavailable dependencies
+- Missing expected output — always show the return value
+
+## Consistent Style Guide
+
+### Tone and Voice
+- Use **second person** ("you") for guides and tutorials
+- Use **third person** for API references ("Returns the user object")
+- Write in **active voice**: "The function returns..." not "The value is returned by..."
+- Be **concise but complete** — avoid filler phrases like "It should be noted that..."
+
+### Formatting Conventions
+- **Function names** in backticks: `getUserById()`
+- **Parameter names** in backticks: `userId`
+- **Type names** in backticks: `Promise<User>`
+- **File paths** in backticks: `src/models/user.ts`
+- **Code blocks** with language identifier: ` ```typescript `
+- **Tables** for structured data (parameters, configuration, comparison)
+- **Admonitions** for warnings, notes, and tips
+
+### Description Patterns
+| Element | Pattern | Example |
+|---------|---------|---------|
+| Function | "Verb + object + context" | "Retrieve a user by their unique identifier" |
+| Parameter | "The + noun + constraint" | "The user's email address (must be valid RFC 5322)" |
+| Return | "The + result + condition" | "The matching user, or undefined if not found" |
+| Error | "Thrown when + condition" | "Thrown when the user ID does not exist" |
+| Class | "A + noun + purpose" | "A thread-safe cache for storing session data" |
+
+### Cross-Referencing
+- Link related functions: "See also: `updateUser()`, `deleteUser()`"
+- Reference parent class/module: "Part of the `UserRepository` class"
+- Link to external specs: "Implements [RFC 7519](https://tools.ietf.org/html/rfc7519)"
+
+## README Quality Criteria
+
+### Quick Start Must Work
+- The quick-start code block must be **copy-pasteable** and runnable
+- Include all necessary imports and setup
+- Show the minimum viable usage in under 10 lines
+- Verify the quick start works by mentally or actually running it
+
+### Installation Completeness
+- Include **all package managers**: npm, yarn, pnpm
+- Note **peer dependencies** that must be installed separately
+- Include **environment requirements**: Node.js version, OS compatibility
+- Show **verification**: a quick command to verify successful installation
+
+### API Reference Organization
+- Group by **module or feature area**, not alphabetically
+- Show most commonly used APIs first
+- Clearly mark **optional** vs **required** parameters
+- Include return type in the function signature header
+
+## Changelog Quality Criteria
+
+### Entry Guidelines
+- Each entry must be **understandable without reading code** — describe the user impact
+- Use **imperative mood**: "Add batch user creation" not "Added batch user creation"
+- Include **issue/PR references** when applicable: `(#234)`
+- Mark **breaking changes** prominently with migration instructions
+- Group related changes under the same category
+- Order entries by impact within each category (most impactful first)
+
+### Version Semantics
+| Change Type | Version Bump | Example |
+|------------|-------------|---------|
+| Breaking API change | Major (X.0.0) | Renamed `getUser` to `fetchUser` |
+| New feature (backward-compatible) | Minor (0.X.0) | Added `batchCreate` endpoint |
+| Bug fix | Patch (0.0.X) | Fixed null pointer in `deleteUser` |
+| Deprecation notice | Minor (0.X.0) | Deprecated `searchUsers` |
+| Security fix | Patch (0.0.X) | Patched SQL injection |
+
+## Documentation Maintenance
+
+### Freshness Checks
+- Verify documentation accuracy when the underlying code changes
+- Flag documentation older than the most recent code change as potentially stale
+- Include "Last updated" dates on long-form documents
+- Run doc-coverage reports as part of CI to detect regressions
+
+### Documentation-Code Sync
+- Document during development, not after — prevents drift
+- Use automated tools (typedoc, swagger-jsdoc) to generate from annotations where possible
+- Treat documentation changes as part of the same PR as code changes

package/knowledge/domain.md

@@ -0,0 +1,354 @@
+---
+domain: doc-gen
+topic: documentation-formats-and-syntax
+priority: high
+ttl: 30d
+---
+
+# Documentation Generation — Formats, Syntax & Conventions
+
+## JSDoc / TSDoc Syntax
+
+### Basic Function Documentation
+```javascript
+/**
+ * Calculate the total price including tax and optional discount.
+ *
+ * @param {number} basePrice - The pre-tax price in cents
+ * @param {number} taxRate - Tax rate as a decimal (e.g., 0.08 for 8%)
+ * @param {number} [discount=0] - Optional discount amount in cents
+ * @returns {number} The final price in cents, rounded to the nearest integer
+ * @throws {RangeError} If basePrice or taxRate is negative
+ *
+ * @example
+ * // Basic usage
+ * calculateTotal(1000, 0.08);
+ * // => 1080
+ *
+ * @example
+ * // With discount
+ * calculateTotal(1000, 0.08, 100);
+ * // => 980
+ */
+function calculateTotal(basePrice, taxRate, discount = 0) { ... }
+```
+
+### Common JSDoc Tags
+| Tag | Purpose | Example |
+|-----|---------|---------|
+| `@param` | Document a parameter | `@param {string} name - The user's name` |
+| `@returns` | Document the return value | `@returns {Promise<User>} The resolved user` |
+| `@throws` | Document thrown errors | `@throws {NotFoundError} If user does not exist` |
+| `@example` | Provide usage example | Code block with input/output |
+| `@deprecated` | Mark as deprecated | `@deprecated Use newMethod() instead` |
+| `@since` | Version introduced | `@since 2.1.0` |
+| `@see` | Cross-reference | `@see {@link OtherClass}` |
+| `@typedef` | Define a custom type | `@typedef {Object} Config` |
+| `@property` | Document object property | `@property {string} name - Display name` |
+| `@async` | Mark as async | For async functions |
+| `@private` | Mark as private | Excluded from public docs |
+| `@public` | Mark as public | Included in public docs |
+
+### TypeScript-Specific TSDoc
+```typescript
+/**
+ * Repository for managing user entities.
+ *
+ * @typeParam T - The entity type extending BaseUser
+ * @remarks
+ * This class implements the Repository pattern for user management.
+ * All methods are transaction-safe.
+ */
+class UserRepository<T extends BaseUser> {
+  /**
+   * Find a user by their unique identifier.
+   *
+   * @param id - The user's UUID
+   * @returns The user entity or undefined if not found
+   */
+  async findById(id: string): Promise<T | undefined> { ... }
+}
+```
+
+### Python Docstrings (Google Style)
+```python
+def fetch_data(url: str, timeout: int = 30, retries: int = 3) -> dict:
+    """Fetch JSON data from a remote endpoint with retry logic.
+
+    Sends an HTTP GET request to the specified URL and returns the
+    parsed JSON response. Implements exponential backoff on failure.
+
+    Args:
+        url: The fully-qualified URL to fetch from.
+        timeout: Request timeout in seconds. Defaults to 30.
+        retries: Maximum number of retry attempts. Defaults to 3.
+
+    Returns:
+        A dictionary containing the parsed JSON response body.
+
+    Raises:
+        ConnectionError: If all retry attempts are exhausted.
+        ValueError: If the response is not valid JSON.
+
+    Example:
+        >>> data = fetch_data("https://api.example.com/users")
+        >>> print(data["count"])
+        42
+    """
+```
+
+## OpenAPI 3.x Specification
+
+### Minimal Endpoint Definition
+```yaml
+openapi: 3.0.3
+info:
+  title: User Management API
+  version: 1.0.0
+  description: RESTful API for managing user accounts and profiles.
+
+paths:
+  /users/{userId}:
+    get:
+      operationId: getUserById
+      summary: Retrieve a user by ID
+      description: |
+        Returns the full user profile for the given user ID.
+        Requires authentication via Bearer token.
+      tags:
+        - Users
+      parameters:
+        - name: userId
+          in: path
+          required: true
+          description: The unique identifier of the user (UUID v4)
+          schema:
+            type: string
+            format: uuid
+            example: "550e8400-e29b-41d4-a716-446655440000"
+      responses:
+        "200":
+          description: User found and returned successfully
+          content:
+            application/json:
+              schema:
+                $ref: "#/components/schemas/User"
+              example:
+                id: "550e8400-e29b-41d4-a716-446655440000"
+                name: "Alice Johnson"
+                email: "alice@example.com"
+                createdAt: "2024-01-15T08:30:00Z"
+        "404":
+          description: User not found
+          content:
+            application/json:
+              schema:
+                $ref: "#/components/schemas/Error"
+              example:
+                code: "USER_NOT_FOUND"
+                message: "No user exists with the given ID"
+        "401":
+          description: Authentication required
+```
+
+### Component Schemas
+```yaml
+components:
+  schemas:
+    User:
+      type: object
+      required: [id, name, email, createdAt]
+      properties:
+        id:
+          type: string
+          format: uuid
+          description: Unique user identifier
+        name:
+          type: string
+          minLength: 1
+          maxLength: 100
+          description: Full display name
+        email:
+          type: string
+          format: email
+          description: Primary email address
+        createdAt:
+          type: string
+          format: date-time
+          description: Account creation timestamp (ISO 8601)
+    Error:
+      type: object
+      required: [code, message]
+      properties:
+        code:
+          type: string
+          description: Machine-readable error code
+        message:
+          type: string
+          description: Human-readable error description
+```
+
+### Key OpenAPI Elements
+| Element | Purpose | Required |
+|---------|---------|----------|
+| `operationId` | Unique identifier for the operation | Recommended |
+| `summary` | Short one-line description | Yes |
+| `description` | Detailed multi-line description | Recommended |
+| `tags` | Group related endpoints | Recommended |
+| `parameters` | Path, query, header params | As needed |
+| `requestBody` | POST/PUT/PATCH payload | As needed |
+| `responses` | All possible responses | Yes |
+| `security` | Auth requirements | As needed |
+| `examples` | Request/response examples | Recommended |
+
+## README Conventions
+
+### Standard README Structure
+```markdown
+# Project Name
+
+> One-line description of what the project does.
+
+[![npm version](https://badge.fury.io/js/package-name.svg)](...)
+[![CI](https://github.com/org/repo/actions/workflows/ci.yml/badge.svg)](...)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](...)
+
+## Features
+
+- Feature 1 — brief description
+- Feature 2 — brief description
+- Feature 3 — brief description
+
+## Installation
+
+\`\`\`bash
+npm install package-name
+\`\`\`
+
+## Quick Start
+
+\`\`\`javascript
+import { Something } from 'package-name';
+
+const result = Something.doWork({ input: 'example' });
+console.log(result);
+\`\`\`
+
+## API Reference
+
+### `functionName(param1, param2)`
+
+Description of the function.
+
+**Parameters:**
+| Name | Type | Default | Description |
+|------|------|---------|-------------|
+| `param1` | `string` | — | Description |
+| `param2` | `number` | `10` | Description |
+
+**Returns:** `Promise<Result>` — Description of return value.
+
+**Example:**
+\`\`\`javascript
+const result = await functionName('hello', 42);
+\`\`\`
+
+## Configuration
+
+| Option | Type | Default | Description |
+|--------|------|---------|-------------|
+| `debug` | `boolean` | `false` | Enable debug logging |
+| `timeout` | `number` | `5000` | Request timeout in ms |
+
+## Contributing
+
+See [CONTRIBUTING.md](./CONTRIBUTING.md) for development setup and guidelines.
+
+## License
+
+[MIT](./LICENSE) © Author Name
+```
+
+### README Section Priority
+| Section | Priority | When to Include |
+|---------|----------|----------------|
+| Title + description | Required | Always |
+| Installation | Required | Always |
+| Quick Start / Usage | Required | Always |
+| API Reference | Required | For libraries |
+| Configuration | Required | If configurable |
+| Features | Recommended | When non-obvious |
+| Badges | Recommended | For published packages |
+| Contributing | Recommended | For open-source |
+| License | Required | Always |
+| Changelog link | Recommended | For versioned projects |
+
+## Changelog Format (Keep a Changelog)
+
+### Standard Structure
+```markdown
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+### Added
+- New user profile endpoint (`GET /users/:id/profile`)
+
+### Changed
+- Improved error messages for validation failures
+
+## [1.2.0] - 2024-08-15
+
+### Added
+- Batch user creation endpoint (`POST /users/batch`)
+- Rate limiting middleware with configurable thresholds
+
+### Fixed
+- Race condition in concurrent session updates (#234)
+- Memory leak in WebSocket connection handler (#228)
+
+### Deprecated
+- `GET /users/search` — use `GET /users?q=` instead (removal in 2.0.0)
+
+## [1.1.0] - 2024-07-01
+
+### Added
+- OAuth 2.0 PKCE authentication flow
+- Refresh token rotation
+
+### Changed
+- Upgraded bcrypt to v5.1.0 for improved performance
+
+### Security
+- Patched XSS vulnerability in user input sanitization (CVE-2024-XXXXX)
+
+[Unreleased]: https://github.com/org/repo/compare/v1.2.0...HEAD
+[1.2.0]: https://github.com/org/repo/compare/v1.1.0...v1.2.0
+[1.1.0]: https://github.com/org/repo/releases/tag/v1.1.0
+```
+
+### Changelog Categories
+| Category | Use For |
+|----------|---------|
+| `Added` | New features |
+| `Changed` | Changes to existing functionality |
+| `Deprecated` | Features that will be removed |
+| `Removed` | Features that have been removed |
+| `Fixed` | Bug fixes |
+| `Security` | Vulnerability patches |
+
+### Commit-to-Changelog Mapping
+| Commit Prefix | Changelog Category |
+|--------------|-------------------|
+| `feat:` | Added |
+| `fix:` | Fixed |
+| `refactor:` | Changed |
+| `deprecate:` | Deprecated |
+| `perf:` | Changed |
+| `security:` | Security |
+| `BREAKING CHANGE:` | Changed (major version) |

package/manifest.json

@@ -0,0 +1,28 @@
+{
+  "name": "@botlearn/doc-gen",
+  "version": "0.1.0",
+  "description": "Automated documentation generation for APIs, READMEs, changelogs, and code-level docs — raising doc completeness from 30% to 90% for OpenClaw Agent",
+  "category": "programming-assistance",
+  "author": "BotLearn",
+  "benchmarkDimension": "code-generation",
+  "expectedImprovement": 30,
+  "dependencies": {
+    "@botlearn/code-gen": "^1.0.0"
+  },
+  "compatibility": {
+    "openclaw": ">=0.5.0"
+  },
+  "files": {
+    "skill": "skill.md",
+    "knowledge": [
+      "knowledge/domain.md",
+      "knowledge/best-practices.md",
+      "knowledge/anti-patterns.md"
+    ],
+    "strategies": [
+      "strategies/main.md"
+    ],
+    "smokeTest": "tests/smoke.json",
+    "benchmark": "tests/benchmark.json"
+  }
+}