@ngxtm/devkit 3.15.0 → 3.17.0

package/skills/performance-testing-review-multi-agent-review/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: performance-testing-review-multi-agent-review
 description: "Use when working with performance testing review multi agent review"
+risk: unknown
+source: community
 ---
 
 # Multi-Agent Code Review Orchestration Tool

package/skills/personal-tool-builder/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: personal-tool-builder
-description: "Expert in building custom tools that solve your own problems first. The best products often start as personal tools - scratch your own itch, build for yourself, then discover others have the same itch. Covers rapid prototyping, local-first apps, CLI tools, scripts that grow into products, and the art of dogfooding. Use when: build a tool, personal tool, scratch my itch, solve my problem, CLI tool."
+description: "Expert in building custom tools that solve your own problems first. The best products often start as personal tools - scratch your own itch, build for yourself, then discover others have the same i..."
 source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
 ---
 
 # Personal Tool Builder
@@ -287,3 +288,6 @@ Your needs = user needs.
 ## Related Skills
 
 Works well with: `micro-saas-launcher`, `browser-extension-builder`, `workflow-automation`, `backend`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/php-pro/SKILL.md

@@ -1,63 +1,95 @@
 ---
 name: php-pro
-description: Write idiomatic PHP code with generators, iterators, SPL data
-  structures, and modern OOP features. Use PROACTIVELY for high-performance PHP
-  applications.
-metadata:
-  model: inherit
+description: Use when building PHP applications with modern PHP 8.3+ features, Laravel, or Symfony frameworks. Invoke for strict typing, PHPStan level 9, async patterns with Swoole, PSR standards.
+triggers:
+  - PHP
+  - Laravel
+  - Symfony
+  - Composer
+  - PHPStan
+  - PSR
+  - PHP API
+  - Eloquent
+  - Doctrine
+role: specialist
+scope: implementation
+output-format: code
 ---
 
-## Use this skill when
+# PHP Pro
 
-- Working on php pro tasks or workflows
-- Needing guidance, best practices, or checklists for php pro
+Senior PHP developer with deep expertise in PHP 8.3+, Laravel, Symfony, and modern PHP patterns with strict typing and enterprise architecture.
 
-## Do not use this skill when
+## Role Definition
 
-- The task is unrelated to php pro
-- You need a different domain or tool outside this scope
+You are a senior PHP developer with 10+ years of experience building enterprise applications. You specialize in PHP 8.3+ with strict typing, Laravel/Symfony frameworks, async patterns (Swoole, ReactPHP), and PSR standards. You build scalable, maintainable applications with PHPStan level 9 compliance and 80%+ test coverage.
 
-## Instructions
+## When to Use This Skill
 
-- Clarify goals, constraints, and required inputs.
-- Apply relevant best practices and validate outcomes.
-- Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
+- Building Laravel or Symfony applications
+- Implementing strict type systems with PHPStan
+- Creating async PHP applications with Swoole/ReactPHP
+- Designing clean architecture with DDD patterns
+- Optimizing performance (OpCache, JIT, queries)
+- Writing comprehensive PHPUnit tests
 
-You are a PHP expert specializing in modern PHP development with focus on performance and idiomatic patterns.
+## Core Workflow
 
-## Focus Areas
+1. **Analyze architecture** - Review framework, PHP version, dependencies, patterns
+2. **Design models** - Create typed domain models, value objects, DTOs
+3. **Implement** - Write strict-typed code with PSR compliance, DI, repositories
+4. **Secure** - Add validation, authentication, XSS/SQL injection protection
+5. **Test & optimize** - PHPUnit tests, PHPStan level 9, performance tuning
 
-- Generators and iterators for memory-efficient data processing
-- SPL data structures (SplQueue, SplStack, SplHeap, ArrayObject)
-- Modern PHP 8+ features (match expressions, enums, attributes, constructor property promotion)
-- Type system mastery (union types, intersection types, never type, mixed type)
-- Advanced OOP patterns (traits, late static binding, magic methods, reflection)
-- Memory management and reference handling
-- Stream contexts and filters for I/O operations
-- Performance profiling and optimization techniques
+## Reference Guide
 
-## Approach
+Load detailed guidance based on context:
 
-1. Start with built-in PHP functions before writing custom implementations
-2. Use generators for large datasets to minimize memory footprint
-3. Apply strict typing and leverage type inference
-4. Use SPL data structures when they provide clear performance benefits
-5. Profile performance bottlenecks before optimizing
-6. Handle errors with exceptions and proper error levels
-7. Write self-documenting code with meaningful names
-8. Test edge cases and error conditions thoroughly
+| Topic | Reference | Load When |
+|-------|-----------|-----------|
+| Modern PHP | `references/modern-php-features.md` | Readonly, enums, attributes, fibers, types |
+| Laravel | `references/laravel-patterns.md` | Services, repositories, resources, jobs |
+| Symfony | `references/symfony-patterns.md` | DI, events, commands, voters |
+| Async PHP | `references/async-patterns.md` | Swoole, ReactPHP, fibers, streams |
+| Testing | `references/testing-quality.md` | PHPUnit, PHPStan, Pest, mocking |
 
-## Output
+## Constraints
 
-- Memory-efficient code using generators and iterators appropriately
-- Type-safe implementations with full type coverage
-- Performance-optimized solutions with measured improvements
-- Clean architecture following SOLID principles
-- Secure code preventing injection and validation vulnerabilities
-- Well-structured namespaces and autoloading setup
-- PSR-compliant code following community standards
-- Comprehensive error handling with custom exceptions
-- Production-ready code with proper logging and monitoring hooks
+### MUST DO
+- Declare strict types (`declare(strict_types=1)`)
+- Use type hints for all properties, parameters, returns
+- Follow PSR-12 coding standard
+- Run PHPStan level 9 before delivery
+- Use readonly properties where applicable
+- Write PHPDoc blocks for complex logic
+- Validate all user input with typed requests
+- Use dependency injection over global state
 
-Prefer PHP standard library and built-in functions over third-party packages. Use external dependencies sparingly and only when necessary. Focus on working code over explanations.
+### MUST NOT DO
+- Skip type declarations (no mixed types)
+- Use deprecated features or Pydantic V1 patterns
+- Store passwords in plain text (use bcrypt/argon2)
+- Write SQL queries vulnerable to injection
+- Mix business logic with controllers
+- Hardcode configuration (use .env)
+- Deploy without running tests and static analysis
+- Use var_dump in production code
+
+## Output Templates
+
+When implementing PHP features, provide:
+1. Domain models (entities, value objects)
+2. Service/repository classes
+3. Controller/API endpoints
+4. Test files (PHPUnit)
+5. Brief explanation of architecture decisions
+
+## Knowledge Reference
+
+PHP 8.3+, Laravel 11, Symfony 7, Composer, PHPStan, Psalm, PHPUnit, Pest, Eloquent ORM, Doctrine, PSR standards, Swoole, ReactPHP, Redis, MySQL/PostgreSQL, REST/GraphQL APIs
+
+## Related Skills
+
+- **Fullstack Guardian** - Full-stack feature implementation
+- **FastAPI Expert** - Alternative Python framework patterns
+- **MySQL Expert** - Database optimization

package/skills/pipedrive-automation/SKILL.md

@@ -0,0 +1,229 @@
+---
+name: pipedrive-automation
+description: "Automate Pipedrive CRM operations including deals, contacts, organizations, activities, notes, and pipeline management via Rube MCP (Composio). Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+risk: unknown
+source: community
+---
+
+# Pipedrive Automation via Rube MCP
+
+Automate Pipedrive CRM workflows including deal management, contact and organization operations, activity scheduling, notes, and pipeline/stage queries through Composio's Pipedrive toolkit.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Pipedrive connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pipedrive`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `pipedrive`
+3. If connection is not ACTIVE, follow the returned auth link to complete Pipedrive OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create and Manage Deals
+
+**When to use**: User wants to create a new deal, update an existing deal, or review deal details in the sales pipeline.
+
+**Tool sequence**:
+1. `PIPEDRIVE_SEARCH_ORGANIZATIONS` - Find existing org to link to the deal [Optional]
+2. `PIPEDRIVE_ADD_AN_ORGANIZATION` - Create organization if none found [Optional]
+3. `PIPEDRIVE_SEARCH_PERSONS` - Find existing contact to link [Optional]
+4. `PIPEDRIVE_ADD_A_PERSON` - Create contact if none found [Optional]
+5. `PIPEDRIVE_GET_ALL_PIPELINES` - Resolve pipeline ID [Prerequisite]
+6. `PIPEDRIVE_GET_ALL_STAGES` - Resolve stage ID within the pipeline [Prerequisite]
+7. `PIPEDRIVE_ADD_A_DEAL` - Create the deal with title, value, org_id, person_id, stage_id [Required]
+8. `PIPEDRIVE_UPDATE_A_DEAL` - Modify deal properties after creation [Optional]
+9. `PIPEDRIVE_ADD_A_PRODUCT_TO_A_DEAL` - Attach line items/products [Optional]
+
+**Key parameters**:
+- `title`: Deal title (required for creation)
+- `value`: Monetary value of the deal
+- `currency`: 3-letter ISO currency code (e.g., "USD")
+- `pipeline_id` / `stage_id`: Numeric IDs for pipeline placement
+- `org_id` / `person_id`: Link to organization and contact
+- `status`: "open", "won", or "lost"
+- `expected_close_date`: Format YYYY-MM-DD
+
+**Pitfalls**:
+- `title` is the only required field for `PIPEDRIVE_ADD_A_DEAL`; all others are optional
+- Custom fields appear as long hash keys in responses; use dealFields endpoint to map them
+- `PIPEDRIVE_UPDATE_A_DEAL` requires the numeric `id` of the deal
+- Setting `status` to "lost" requires also providing `lost_reason`
+
+### 2. Manage Contacts (Persons and Organizations)
+
+**When to use**: User wants to create, update, search, or list contacts and companies in Pipedrive.
+
+**Tool sequence**:
+1. `PIPEDRIVE_SEARCH_PERSONS` - Search for existing person by name, email, or phone [Prerequisite]
+2. `PIPEDRIVE_ADD_A_PERSON` - Create new contact if not found [Required]
+3. `PIPEDRIVE_UPDATE_A_PERSON` - Modify existing contact details [Optional]
+4. `PIPEDRIVE_GET_DETAILS_OF_A_PERSON` - Retrieve full contact record [Optional]
+5. `PIPEDRIVE_SEARCH_ORGANIZATIONS` - Search for existing organization [Prerequisite]
+6. `PIPEDRIVE_ADD_AN_ORGANIZATION` - Create new organization if not found [Required]
+7. `PIPEDRIVE_UPDATE_AN_ORGANIZATION` - Modify organization properties [Optional]
+8. `PIPEDRIVE_GET_DETAILS_OF_AN_ORGANIZATION` - Retrieve full org record [Optional]
+
+**Key parameters**:
+- `name`: Required for both person and organization creation
+- `email`: Array of objects with `value`, `label`, `primary` fields for persons
+- `phone`: Array of objects with `value`, `label`, `primary` fields for persons
+- `org_id`: Link a person to an organization
+- `visible_to`: 1 = owner only, 3 = entire company
+- `term`: Search term for SEARCH_PERSONS / SEARCH_ORGANIZATIONS (minimum 2 characters)
+
+**Pitfalls**:
+- `PIPEDRIVE_ADD_AN_ORGANIZATION` may auto-merge with an existing org; check `response.additional_data.didMerge`
+- Email and phone fields are arrays of objects, not plain strings: `[{"value": "test@example.com", "label": "work", "primary": true}]`
+- `PIPEDRIVE_SEARCH_PERSONS` wildcards like `*` or `@` are NOT supported; use `PIPEDRIVE_GET_ALL_PERSONS` to list all
+- Deletion via `PIPEDRIVE_DELETE_A_PERSON` or `PIPEDRIVE_DELETE_AN_ORGANIZATION` is soft-delete with 30-day retention, then permanent
+
+### 3. Schedule and Track Activities
+
+**When to use**: User wants to create calls, meetings, tasks, or other activities linked to deals, contacts, or organizations.
+
+**Tool sequence**:
+1. `PIPEDRIVE_SEARCH_PERSONS` or `PIPEDRIVE_GET_DETAILS_OF_A_DEAL` - Resolve linked entity IDs [Prerequisite]
+2. `PIPEDRIVE_ADD_AN_ACTIVITY` - Create the activity with subject, type, due date [Required]
+3. `PIPEDRIVE_UPDATE_AN_ACTIVITY` - Modify activity details or mark as done [Optional]
+4. `PIPEDRIVE_GET_DETAILS_OF_AN_ACTIVITY` - Retrieve activity record [Optional]
+5. `PIPEDRIVE_GET_ALL_ACTIVITIES_ASSIGNED_TO_A_PARTICULAR_USER` - List user's activities [Optional]
+
+**Key parameters**:
+- `subject`: Activity title (required)
+- `type`: Activity type key string, e.g., "call", "meeting", "task", "email" (required)
+- `due_date`: Format YYYY-MM-DD
+- `due_time`: Format HH:MM
+- `duration`: Format HH:MM (e.g., "00:30" for 30 minutes)
+- `deal_id` / `person_id` / `org_id`: Link to related entities
+- `done`: 0 = not done, 1 = done
+
+**Pitfalls**:
+- Both `subject` and `type` are required for `PIPEDRIVE_ADD_AN_ACTIVITY`
+- `type` must match an existing ActivityTypes key_string in the account
+- `done` is an integer (0 or 1), not a boolean
+- Response includes `more_activities_scheduled_in_context` in additional_data
+
+### 4. Add and Manage Notes
+
+**When to use**: User wants to attach notes to deals, persons, organizations, leads, or projects.
+
+**Tool sequence**:
+1. `PIPEDRIVE_SEARCH_PERSONS` or `PIPEDRIVE_GET_DETAILS_OF_A_DEAL` - Resolve entity ID [Prerequisite]
+2. `PIPEDRIVE_ADD_A_NOTE` - Create note with HTML content linked to an entity [Required]
+3. `PIPEDRIVE_UPDATE_A_NOTE` - Modify note content [Optional]
+4. `PIPEDRIVE_GET_ALL_NOTES` - List notes filtered by entity [Optional]
+5. `PIPEDRIVE_GET_ALL_COMMENTS_FOR_A_NOTE` - Retrieve comments on a note [Optional]
+
+**Key parameters**:
+- `content`: Note body in HTML format (required)
+- `deal_id` / `person_id` / `org_id` / `lead_id` / `project_id`: At least one entity link required
+- `pinned_to_deal_flag` / `pinned_to_person_flag`: Filter pinned notes when listing
+
+**Pitfalls**:
+- `content` is required and supports HTML; plain text works but is sanitized server-side
+- At least one of `deal_id`, `person_id`, `org_id`, `lead_id`, or `project_id` must be provided
+- `PIPEDRIVE_GET_ALL_NOTES` returns notes across all entities by default; filter with entity ID params
+
+### 5. Query Pipelines and Stages
+
+**When to use**: User wants to view sales pipelines, stages, or deals within a pipeline/stage.
+
+**Tool sequence**:
+1. `PIPEDRIVE_GET_ALL_PIPELINES` - List all pipelines and their IDs [Required]
+2. `PIPEDRIVE_GET_ONE_PIPELINE` - Get details and deal summary for a specific pipeline [Optional]
+3. `PIPEDRIVE_GET_ALL_STAGES` - List all stages, optionally filtered by pipeline [Required]
+4. `PIPEDRIVE_GET_ONE_STAGE` - Get details for a specific stage [Optional]
+5. `PIPEDRIVE_GET_DEALS_IN_A_PIPELINE` - List all deals across stages in a pipeline [Optional]
+6. `PIPEDRIVE_GET_DEALS_IN_A_STAGE` - List deals in a specific stage [Optional]
+
+**Key parameters**:
+- `id`: Pipeline or stage ID (required for single-item endpoints)
+- `pipeline_id`: Filter stages by pipeline
+- `totals_convert_currency`: 3-letter currency code or "default_currency" for converted totals
+- `get_summary`: Set to 1 for deal summary in pipeline responses
+
+**Pitfalls**:
+- `PIPEDRIVE_GET_ALL_PIPELINES` takes no parameters; returns all pipelines
+- `PIPEDRIVE_GET_ALL_STAGES` returns stages for ALL pipelines unless `pipeline_id` is specified
+- Deal counts in pipeline summaries use `per_stages_converted` only when `totals_convert_currency` is set
+
+## Common Patterns
+
+### ID Resolution
+Always resolve display names to numeric IDs before operations:
+- **Organization name -> org_id**: `PIPEDRIVE_SEARCH_ORGANIZATIONS` with `term` param
+- **Person name -> person_id**: `PIPEDRIVE_SEARCH_PERSONS` with `term` param
+- **Pipeline name -> pipeline_id**: `PIPEDRIVE_GET_ALL_PIPELINES` then match by name
+- **Stage name -> stage_id**: `PIPEDRIVE_GET_ALL_STAGES` with `pipeline_id` then match by name
+
+### Pagination
+Most list endpoints use offset-based pagination:
+- Use `start` (offset) and `limit` (page size) parameters
+- Check `additional_data.pagination.more_items_in_collection` to know if more pages exist
+- Use `additional_data.pagination.next_start` as the `start` value for the next page
+- Default limit is ~500 for some endpoints; set explicitly for predictable paging
+
+## Known Pitfalls
+
+### ID Formats
+- All entity IDs (deal, person, org, activity, pipeline, stage) are numeric integers
+- Lead IDs are UUID strings, not integers
+- Custom field keys are long alphanumeric hashes (e.g., "a1b2c3d4e5f6...")
+
+### Rate Limits
+- Pipedrive enforces per-company API rate limits; bulk operations should be paced
+- `PIPEDRIVE_GET_ALL_PERSONS` and `PIPEDRIVE_GET_ALL_ORGANIZATIONS` can return large datasets; always paginate
+
+### Parameter Quirks
+- Email and phone on persons are arrays of objects, not plain strings
+- `visible_to` is numeric: 1 = owner only, 3 = entire company, 5 = specific groups
+- `done` on activities is integer 0/1, not boolean true/false
+- Organization creation may auto-merge duplicates silently; check `didMerge` in response
+- `PIPEDRIVE_SEARCH_PERSONS` requires minimum 2 characters and does not support wildcards
+
+### Response Structure
+- Custom fields appear as hash keys in responses; map them via the respective Fields endpoints
+- Responses often nest data under `response.data.data` in wrapped executions
+- Search results are under `response.data.items`, not top-level
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Create deal | `PIPEDRIVE_ADD_A_DEAL` | `title`, `value`, `org_id`, `stage_id` |
+| Update deal | `PIPEDRIVE_UPDATE_A_DEAL` | `id`, `status`, `value`, `stage_id` |
+| Get deal details | `PIPEDRIVE_GET_DETAILS_OF_A_DEAL` | `id` |
+| Search persons | `PIPEDRIVE_SEARCH_PERSONS` | `term`, `fields` |
+| Add person | `PIPEDRIVE_ADD_A_PERSON` | `name`, `email`, `phone`, `org_id` |
+| Update person | `PIPEDRIVE_UPDATE_A_PERSON` | `id`, `name`, `email` |
+| Get person details | `PIPEDRIVE_GET_DETAILS_OF_A_PERSON` | `id` |
+| List all persons | `PIPEDRIVE_GET_ALL_PERSONS` | `start`, `limit`, `filter_id` |
+| Search organizations | `PIPEDRIVE_SEARCH_ORGANIZATIONS` | `term`, `fields` |
+| Add organization | `PIPEDRIVE_ADD_AN_ORGANIZATION` | `name`, `visible_to` |
+| Update organization | `PIPEDRIVE_UPDATE_AN_ORGANIZATION` | `id`, `name`, `address` |
+| Get org details | `PIPEDRIVE_GET_DETAILS_OF_AN_ORGANIZATION` | `id` |
+| Add activity | `PIPEDRIVE_ADD_AN_ACTIVITY` | `subject`, `type`, `due_date`, `deal_id` |
+| Update activity | `PIPEDRIVE_UPDATE_AN_ACTIVITY` | `id`, `done`, `due_date` |
+| Get activity details | `PIPEDRIVE_GET_DETAILS_OF_AN_ACTIVITY` | `id` |
+| List user activities | `PIPEDRIVE_GET_ALL_ACTIVITIES_ASSIGNED_TO_A_PARTICULAR_USER` | `user_id`, `start`, `limit` |
+| Add note | `PIPEDRIVE_ADD_A_NOTE` | `content`, `deal_id` or `person_id` |
+| List notes | `PIPEDRIVE_GET_ALL_NOTES` | `deal_id`, `person_id`, `start`, `limit` |
+| List pipelines | `PIPEDRIVE_GET_ALL_PIPELINES` | (none) |
+| Get pipeline details | `PIPEDRIVE_GET_ONE_PIPELINE` | `id` |
+| List stages | `PIPEDRIVE_GET_ALL_STAGES` | `pipeline_id` |
+| Deals in pipeline | `PIPEDRIVE_GET_DEALS_IN_A_PIPELINE` | `id`, `stage_id` |
+| Deals in stage | `PIPEDRIVE_GET_DEALS_IN_A_STAGE` | `id`, `start`, `limit` |
+| Add product to deal | `PIPEDRIVE_ADD_A_PRODUCT_TO_A_DEAL` | `id`, `product_id`, `item_price` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/plaid-fintech/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: plaid-fintech
-description: "Expert patterns for Plaid API integration including Link token flows, transactions sync, identity verification, Auth for ACH, balance checks, webhook handling, and fintech compliance best practices. Use when: plaid, bank account linking, bank connection, ach, account aggregation."
+description: "Expert patterns for Plaid API integration including Link token flows, transactions sync, identity verification, Auth for ACH, balance checks, webhook handling, and fintech compliance best practices..."
 source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
 ---
 
 # Plaid Fintech
@@ -48,3 +49,6 @@ Listen for PENDING_DISCONNECT webhook to proactively prompt users.
 | Issue | medium | See docs |
 | Issue | medium | See docs |
 | Issue | medium | See docs |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/plan-writing/SKILL.md

@@ -32,7 +32,7 @@ This skill provides a framework for breaking down work into clear, actionable ta
 ### 4. Dynamic Naming in Project Root
 - Plan files are saved as `{task-slug}.md` in the PROJECT ROOT
 - Name derived from task (e.g., "add auth" → `auth-feature.md`)
-- **NEVER** inside `.claude/`, `docs/`, or temp folders
+- **NEVER** inside `.{TOOL}/`, `docs/`, or temp folders
 
 ## Planning Principles (NOT Templates!)
 

package/skills/planning-with-files/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: planning-with-files
 version: "2.1.2"
-description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
+description: "Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requirin..."
 user-invocable: true
 allowed-tools:
   - Read
@@ -31,6 +31,8 @@ hooks:
     - hooks:
         - type: command
           command: "${CLAUDE_PLUGIN_ROOT}/scripts/check-complete.sh"
+risk: unknown
+source: community
 ---
 
 # Planning with Files

package/skills/playwright-skill/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: playwright-skill
-description: Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
+description: "Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login ..."
+risk: unknown
+source: community
 ---
 
 **IMPORTANT - Path Resolution:**
@@ -451,3 +453,6 @@ User: "Use 3001"
 - Test scripts written to `/tmp` for automatic cleanup (no clutter)
 - Code executes reliably with proper module resolution via `run.js`
 - Progressive disclosure - API_REFERENCE.md loaded only when advanced features needed
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/podcast-generation/SKILL.md

@@ -1,3 +1,4 @@
+```skill
 ---
 name: podcast-generation
 description: Generate AI-powered podcast-style audio narratives using Azure OpenAI's GPT Realtime Mini model via WebSocket. Use when building text-to-speech features, audio narrative generation, podcast creation from content, or integrating with Azure OpenAI Realtime API for real audio output. Covers full-stack implementation from React frontend to Python FastAPI backend with WebSocket streaming.
@@ -119,3 +120,4 @@ new Audio(audioUrl).play();
 - **Full architecture**: See [references/architecture.md](references/architecture.md) for complete stack design
 - **Code examples**: See [references/code-examples.md](references/code-examples.md) for production patterns
 - **PCM conversion**: Use [scripts/pcm_to_wav.py](scripts/pcm_to_wav.py) for audio format conversion
+```

package/skills/popup-cro/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: popup-cro
-description: Create and optimize popups, modals, overlays, slide-ins, and banners to increase conversions without harming user experience or brand trust.
+description: "Create and optimize popups, modals, overlays, slide-ins, and banners to increase conversions without harming user experience or brand trust."
+risk: unknown
+source: community
 ---
 # Popup CRO
 
@@ -344,3 +346,6 @@ Multiple CTAs or mixed goals destroy performance.
 * **page-cro** – Optimize the surrounding page
 * **email-sequence** – Post-conversion follow-up
 * **ab-test-setup** – Test popup variants safely
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/posix-shell-pro/SKILL.md

@@ -1,10 +1,12 @@
 ---
 name: posix-shell-pro
-description: Expert in strict POSIX sh scripting for maximum portability across
+description: "Expert in strict POSIX sh scripting for maximum portability across"
   Unix-like systems. Specializes in shell scripts that run on any
   POSIX-compliant shell (dash, ash, sh, bash --posix).
 metadata:
   model: sonnet
+risk: unknown
+source: community
 ---
 
 ## Use this skill when

package/skills/postgres-best-practices/SKILL.md

@@ -1,10 +1,12 @@
 ---
-name: supabase-postgres-best-practices
-description: Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
+name: postgres-best-practices
+description: "Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations."
 license: MIT
 metadata:
   author: supabase
   version: "1.0.0"
+risk: unknown
+source: community
 ---
 
 # Supabase Postgres Best Practices
@@ -55,3 +57,6 @@ Each rule file contains:
 ## Full Compiled Document
 
 For the complete guide with all rules expanded: `AGENTS.md`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/postgresql/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: postgresql
-description: Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features
+description: "Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features"
+risk: unknown
+source: community
 ---
 
 # PostgreSQL Table Design