@ngxtm/devkit 3.14.0 → 3.16.0

package/skills/calendly-automation/SKILL.md

@@ -0,0 +1,216 @@
+---
+name: calendly-automation
+description: "Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio). Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+risk: unknown
+source: community
+---
+
+# Calendly Automation via Rube MCP
+
+Automate Calendly operations including event listing, invitee management, scheduling link creation, availability queries, and organization administration through Composio's Calendly toolkit.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Calendly connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `calendly`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+- Many operations require the user's Calendly URI, obtained via `CALENDLY_GET_CURRENT_USER`
+
+## 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 `calendly`
+3. If connection is not ACTIVE, follow the returned auth link to complete Calendly OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. List and View Scheduled Events
+
+**When to use**: User wants to see their upcoming, past, or filtered Calendly events
+
+**Tool sequence**:
+1. `CALENDLY_GET_CURRENT_USER` - Get authenticated user URI and organization URI [Prerequisite]
+2. `CALENDLY_LIST_EVENTS` - List events scoped by user, organization, or group [Required]
+3. `CALENDLY_GET_EVENT` - Get detailed info for a specific event by UUID [Optional]
+
+**Key parameters**:
+- `user`: Full Calendly API URI (e.g., `https://api.calendly.com/users/{uuid}`) - NOT `"me"`
+- `organization`: Full organization URI for org-scoped queries
+- `status`: `"active"` or `"canceled"`
+- `min_start_time` / `max_start_time`: UTC timestamps (e.g., `2024-01-01T00:00:00.000000Z`)
+- `invitee_email`: Filter events by invitee email (filter only, not a scope)
+- `sort`: `"start_time:asc"` or `"start_time:desc"`
+- `count`: Results per page (default 20)
+- `page_token`: Pagination token from previous response
+
+**Pitfalls**:
+- Exactly ONE of `user`, `organization`, or `group` must be provided - omitting or combining scopes fails
+- The `user` parameter requires the full API URI, not `"me"` - use `CALENDLY_GET_CURRENT_USER` first
+- `invitee_email` is a filter, not a scope; you still need one of user/organization/group
+- Pagination uses `count` + `page_token`; loop until `page_token` is absent for complete results
+- Admin rights may be needed for organization or group scope queries
+
+### 2. Manage Event Invitees
+
+**When to use**: User wants to see who is booked for events or get invitee details
+
+**Tool sequence**:
+1. `CALENDLY_LIST_EVENTS` - Find the target event(s) [Prerequisite]
+2. `CALENDLY_LIST_EVENT_INVITEES` - List all invitees for a specific event [Required]
+3. `CALENDLY_GET_EVENT_INVITEE` - Get detailed info for a single invitee [Optional]
+
+**Key parameters**:
+- `uuid`: Event UUID (for `LIST_EVENT_INVITEES`)
+- `event_uuid` + `invitee_uuid`: Both required for `GET_EVENT_INVITEE`
+- `email`: Filter invitees by email address
+- `status`: `"active"` or `"canceled"`
+- `sort`: `"created_at:asc"` or `"created_at:desc"`
+- `count`: Results per page (default 20)
+
+**Pitfalls**:
+- The `uuid` parameter for `CALENDLY_LIST_EVENT_INVITEES` is the event UUID, not the invitee UUID
+- Paginate using `page_token` until absent for complete invitee lists
+- Canceled invitees are excluded by default; use `status: "canceled"` to see them
+
+### 3. Create Scheduling Links and Check Availability
+
+**When to use**: User wants to generate a booking link or check available time slots
+
+**Tool sequence**:
+1. `CALENDLY_GET_CURRENT_USER` - Get user URI [Prerequisite]
+2. `CALENDLY_LIST_USER_S_EVENT_TYPES` - List available event types [Required]
+3. `CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES` - Check available slots for an event type [Optional]
+4. `CALENDLY_CREATE_SCHEDULING_LINK` - Generate a single-use scheduling link [Required]
+5. `CALENDLY_LIST_USER_AVAILABILITY_SCHEDULES` - View user's availability schedules [Optional]
+
+**Key parameters**:
+- `owner`: Event type URI (e.g., `https://api.calendly.com/event_types/{uuid}`)
+- `owner_type`: `"EventType"` (default)
+- `max_event_count`: Must be exactly `1` for single-use links
+- `start_time` / `end_time`: UTC timestamps for availability queries (max 7-day range)
+- `active`: Boolean to filter active/inactive event types
+- `user`: User URI for event type listing
+
+**Pitfalls**:
+- `CALENDLY_CREATE_SCHEDULING_LINK` can return 403 if token lacks rights or owner URI is invalid
+- `CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES` requires UTC timestamps and max 7-day range; split longer searches
+- Available times results are NOT paginated - all results returned in one response
+- Event type URIs must be full API URIs (e.g., `https://api.calendly.com/event_types/...`)
+
+### 4. Cancel Events
+
+**When to use**: User wants to cancel a scheduled Calendly event
+
+**Tool sequence**:
+1. `CALENDLY_LIST_EVENTS` - Find the event to cancel [Prerequisite]
+2. `CALENDLY_GET_EVENT` - Confirm event details before cancellation [Prerequisite]
+3. `CALENDLY_LIST_EVENT_INVITEES` - Check who will be affected [Optional]
+4. `CALENDLY_CANCEL_EVENT` - Cancel the event [Required]
+
+**Key parameters**:
+- `uuid`: Event UUID to cancel
+- `reason`: Optional cancellation reason (may be included in notification to invitees)
+
+**Pitfalls**:
+- Cancellation is IRREVERSIBLE - always confirm with the user before calling
+- Cancellation may trigger notifications to invitees
+- Only active events can be canceled; already-canceled events return errors
+- Get explicit user confirmation before executing `CALENDLY_CANCEL_EVENT`
+
+### 5. Manage Organization and Invitations
+
+**When to use**: User wants to invite members, manage organization, or handle org invitations
+
+**Tool sequence**:
+1. `CALENDLY_GET_CURRENT_USER` - Get user and organization context [Prerequisite]
+2. `CALENDLY_GET_ORGANIZATION` - Get organization details [Optional]
+3. `CALENDLY_LIST_ORGANIZATION_INVITATIONS` - Check existing invitations [Optional]
+4. `CALENDLY_CREATE_ORGANIZATION_INVITATION` - Send an org invitation [Required]
+5. `CALENDLY_REVOKE_USER_S_ORGANIZATION_INVITATION` - Revoke a pending invitation [Optional]
+6. `CALENDLY_REMOVE_USER_FROM_ORGANIZATION` - Remove a member [Optional]
+
+**Key parameters**:
+- `uuid`: Organization UUID
+- `email`: Email address of user to invite
+- `status`: Filter invitations by `"pending"`, `"accepted"`, or `"declined"`
+
+**Pitfalls**:
+- Only org owners/admins can manage invitations and removals; others get authorization errors
+- Duplicate active invitations for the same email are rejected - check existing invitations first
+- Organization owners cannot be removed via `CALENDLY_REMOVE_USER_FROM_ORGANIZATION`
+- Invitation statuses include pending, accepted, declined, and revoked - handle each appropriately
+
+## Common Patterns
+
+### ID Resolution
+Calendly uses full API URIs as identifiers, not simple IDs:
+- **Current user URI**: `CALENDLY_GET_CURRENT_USER` returns `resource.uri` (e.g., `https://api.calendly.com/users/{uuid}`)
+- **Organization URI**: Found in current user response at `resource.current_organization`
+- **Event UUID**: Extract from event URI or list responses
+- **Event type URI**: From `CALENDLY_LIST_USER_S_EVENT_TYPES` response
+
+Important: Never use `"me"` as a user parameter in list/filter endpoints. Always resolve to the full URI first.
+
+### Pagination
+Most Calendly list endpoints use token-based pagination:
+- Set `count` for page size (default 20)
+- Follow `page_token` from `pagination.next_page_token` until absent
+- Sort with `field:direction` format (e.g., `start_time:asc`, `created_at:desc`)
+
+### Time Handling
+- All timestamps must be in UTC format: `yyyy-MM-ddTHH:mm:ss.ffffffZ`
+- Use `min_start_time` / `max_start_time` for date range filtering on events
+- Available times queries have a maximum 7-day range; split longer searches into multiple calls
+
+## Known Pitfalls
+
+### URI Formats
+- All entity references use full Calendly API URIs (e.g., `https://api.calendly.com/users/{uuid}`)
+- Never pass bare UUIDs where URIs are expected, and never pass `"me"` to list endpoints
+- Extract UUIDs from URIs when tools expect UUID parameters (e.g., `CALENDLY_GET_EVENT`)
+
+### Scope Requirements
+- `CALENDLY_LIST_EVENTS` requires exactly one scope (user, organization, or group) - no more, no less
+- Organization/group scoped queries may require admin privileges
+- Token scope determines which operations are available; 403 errors indicate insufficient permissions
+
+### Data Relationships
+- Events have invitees (attendees who booked)
+- Event types define scheduling pages (duration, availability rules)
+- Organizations contain users and groups
+- Scheduling links are tied to event types, not directly to events
+
+### Rate Limits
+- Calendly API has rate limits; avoid tight loops over large datasets
+- Paginate responsibly and add delays for batch operations
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Get current user | `CALENDLY_GET_CURRENT_USER` | (none) |
+| Get user by UUID | `CALENDLY_GET_USER` | `uuid` |
+| List events | `CALENDLY_LIST_EVENTS` | `user`, `status`, `min_start_time` |
+| Get event details | `CALENDLY_GET_EVENT` | `uuid` |
+| Cancel event | `CALENDLY_CANCEL_EVENT` | `uuid`, `reason` |
+| List invitees | `CALENDLY_LIST_EVENT_INVITEES` | `uuid`, `status`, `email` |
+| Get invitee | `CALENDLY_GET_EVENT_INVITEE` | `event_uuid`, `invitee_uuid` |
+| List event types | `CALENDLY_LIST_USER_S_EVENT_TYPES` | `user`, `active` |
+| Get event type | `CALENDLY_GET_EVENT_TYPE` | `uuid` |
+| Check availability | `CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES` | event type URI, `start_time`, `end_time` |
+| Create scheduling link | `CALENDLY_CREATE_SCHEDULING_LINK` | `owner`, `max_event_count` |
+| List availability schedules | `CALENDLY_LIST_USER_AVAILABILITY_SCHEDULES` | user URI |
+| Get organization | `CALENDLY_GET_ORGANIZATION` | `uuid` |
+| Invite to org | `CALENDLY_CREATE_ORGANIZATION_INVITATION` | `uuid`, `email` |
+| List org invitations | `CALENDLY_LIST_ORGANIZATION_INVITATIONS` | `uuid`, `status` |
+| Revoke org invitation | `CALENDLY_REVOKE_USER_S_ORGANIZATION_INVITATION` | org UUID, invitation UUID |
+| Remove from org | `CALENDLY_REMOVE_USER_FROM_ORGANIZATION` | membership UUID |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/canva-automation/SKILL.md

@@ -0,0 +1,222 @@
+---
+name: canva-automation
+description: "Automate Canva tasks via Rube MCP (Composio): designs, exports, folders, brand templates, autofill. Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+risk: unknown
+source: community
+---
+
+# Canva Automation via Rube MCP
+
+Automate Canva design operations through Composio's Canva toolkit via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Canva connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `canva`
+- 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 `canva`
+3. If connection is not ACTIVE, follow the returned auth link to complete Canva OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. List and Browse Designs
+
+**When to use**: User wants to find existing designs or browse their Canva library
+
+**Tool sequence**:
+1. `CANVA_LIST_USER_DESIGNS` - List all designs with optional filters [Required]
+
+**Key parameters**:
+- `query`: Search term to filter designs by name
+- `continuation`: Pagination token from previous response
+- `ownership`: Filter by 'owned', 'shared', or 'any'
+- `sort_by`: Sort field (e.g., 'modified_at', 'title')
+
+**Pitfalls**:
+- Results are paginated; follow `continuation` token until absent
+- Deleted designs may still appear briefly; check design status
+- Search is substring-based, not fuzzy matching
+
+### 2. Create and Design
+
+**When to use**: User wants to create a new Canva design from scratch or from a template
+
+**Tool sequence**:
+1. `CANVA_ACCESS_USER_SPECIFIC_BRAND_TEMPLATES_LIST` - Browse available brand templates [Optional]
+2. `CANVA_CREATE_CANVA_DESIGN_WITH_OPTIONAL_ASSET` - Create a new design [Required]
+
+**Key parameters**:
+- `design_type`: Type of design (e.g., 'Presentation', 'Poster', 'SocialMedia')
+- `title`: Name for the new design
+- `asset_id`: Optional asset to include in the design
+- `width` / `height`: Custom dimensions in pixels
+
+**Pitfalls**:
+- Design type must match Canva's predefined types exactly
+- Custom dimensions have minimum and maximum limits
+- Asset must be uploaded first via CANVA_CREATE_ASSET_UPLOAD_JOB before referencing
+
+### 3. Upload Assets
+
+**When to use**: User wants to upload images or files to Canva for use in designs
+
+**Tool sequence**:
+1. `CANVA_CREATE_ASSET_UPLOAD_JOB` - Initiate the asset upload [Required]
+2. `CANVA_FETCH_ASSET_UPLOAD_JOB_STATUS` - Poll until upload completes [Required]
+
+**Key parameters**:
+- `name`: Display name for the asset
+- `url`: Public URL of the file to upload (for URL-based uploads)
+- `job_id`: Upload job ID returned from step 1 (for status polling)
+
+**Pitfalls**:
+- Upload is asynchronous; you MUST poll the job status until it completes
+- Supported formats include PNG, JPG, SVG, MP4, GIF
+- File size limits apply; large files may take longer to process
+- The `job_id` from CREATE returns the ID needed for status polling
+- Status values: 'in_progress', 'success', 'failed'
+
+### 4. Export Designs
+
+**When to use**: User wants to download or export a Canva design as PDF, PNG, or other format
+
+**Tool sequence**:
+1. `CANVA_LIST_USER_DESIGNS` - Find the design to export [Prerequisite]
+2. `CANVA_CREATE_CANVA_DESIGN_EXPORT_JOB` - Start the export process [Required]
+3. `CANVA_GET_DESIGN_EXPORT_JOB_RESULT` - Poll until export completes and get download URL [Required]
+
+**Key parameters**:
+- `design_id`: ID of the design to export
+- `format`: Export format ('pdf', 'png', 'jpg', 'svg', 'mp4', 'gif', 'pptx')
+- `pages`: Specific page numbers to export (array)
+- `quality`: Export quality ('regular', 'high')
+- `job_id`: Export job ID for polling status
+
+**Pitfalls**:
+- Export is asynchronous; you MUST poll the job result until it completes
+- Download URLs from completed exports expire after a limited time
+- Large designs with many pages take longer to export
+- Not all formats support all design types (e.g., MP4 only for animations)
+- Poll interval: wait 2-3 seconds between status checks
+
+### 5. Organize with Folders
+
+**When to use**: User wants to create folders or organize designs into folders
+
+**Tool sequence**:
+1. `CANVA_POST_FOLDERS` - Create a new folder [Required]
+2. `CANVA_MOVE_ITEM_TO_SPECIFIED_FOLDER` - Move designs into folders [Optional]
+
+**Key parameters**:
+- `name`: Folder name
+- `parent_folder_id`: Parent folder for nested organization
+- `item_id`: ID of the design or asset to move
+- `folder_id`: Target folder ID
+
+**Pitfalls**:
+- Folder names must be unique within the same parent folder
+- Moving items between folders updates their location immediately
+- Root-level folders have no parent_folder_id
+
+### 6. Autofill from Brand Templates
+
+**When to use**: User wants to generate designs by filling brand template placeholders with data
+
+**Tool sequence**:
+1. `CANVA_ACCESS_USER_SPECIFIC_BRAND_TEMPLATES_LIST` - List available brand templates [Required]
+2. `CANVA_INITIATE_CANVA_DESIGN_AUTOFILL_JOB` - Start autofill with data [Required]
+
+**Key parameters**:
+- `brand_template_id`: ID of the brand template to use
+- `title`: Title for the generated design
+- `data`: Key-value mapping of placeholder names to replacement values
+
+**Pitfalls**:
+- Template placeholders must match exactly (case-sensitive)
+- Autofill is asynchronous; poll for completion
+- Only brand templates support autofill, not regular designs
+- Data values must match the expected type for each placeholder (text, image URL)
+
+## Common Patterns
+
+### Async Job Pattern
+
+Many Canva operations are asynchronous:
+```
+1. Initiate job (upload, export, autofill) -> get job_id
+2. Poll status endpoint with job_id every 2-3 seconds
+3. Check for 'success' or 'failed' status
+4. On success, extract result (asset_id, download_url, design_id)
+```
+
+### ID Resolution
+
+**Design name -> Design ID**:
+```
+1. Call CANVA_LIST_USER_DESIGNS with query=design_name
+2. Find matching design in results
+3. Extract id field
+```
+
+**Brand template name -> Template ID**:
+```
+1. Call CANVA_ACCESS_USER_SPECIFIC_BRAND_TEMPLATES_LIST
+2. Find template by name
+3. Extract brand_template_id
+```
+
+### Pagination
+
+- Check response for `continuation` token
+- Pass token in next request's `continuation` parameter
+- Continue until `continuation` is absent or empty
+
+## Known Pitfalls
+
+**Async Operations**:
+- Uploads, exports, and autofills are all asynchronous
+- Always poll job status; do not assume immediate completion
+- Download URLs from exports expire; use them promptly
+
+**Asset Management**:
+- Assets must be uploaded before they can be used in designs
+- Upload job must reach 'success' status before the asset_id is valid
+- Supported formats vary; check Canva documentation for current limits
+
+**Rate Limits**:
+- Canva API has rate limits per endpoint
+- Implement exponential backoff for bulk operations
+- Batch operations where possible to reduce API calls
+
+**Response Parsing**:
+- Response data may be nested under `data` key
+- Job status responses include different fields based on completion state
+- Parse defensively with fallbacks for optional fields
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List designs | CANVA_LIST_USER_DESIGNS | query, continuation |
+| Create design | CANVA_CREATE_CANVA_DESIGN_WITH_OPTIONAL_ASSET | design_type, title |
+| Upload asset | CANVA_CREATE_ASSET_UPLOAD_JOB | name, url |
+| Check upload | CANVA_FETCH_ASSET_UPLOAD_JOB_STATUS | job_id |
+| Export design | CANVA_CREATE_CANVA_DESIGN_EXPORT_JOB | design_id, format |
+| Get export | CANVA_GET_DESIGN_EXPORT_JOB_RESULT | job_id |
+| Create folder | CANVA_POST_FOLDERS | name, parent_folder_id |
+| Move to folder | CANVA_MOVE_ITEM_TO_SPECIFIED_FOLDER | item_id, folder_id |
+| List templates | CANVA_ACCESS_USER_SPECIFIC_BRAND_TEMPLATES_LIST | (none) |
+| Autofill template | CANVA_INITIATE_CANVA_DESIGN_AUTOFILL_JOB | brand_template_id, data |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/canvas-design/SKILL.md

@@ -1,7 +1,9 @@
 ---
 name: canvas-design
-description: Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
+description: "Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create ..."
 license: Complete terms in LICENSE.txt
+risk: unknown
+source: community
 ---
 
 These are instructions for creating design philosophies - aesthetic movements that are then EXPRESSED VISUALLY. Output only .md files, .pdf files, and .png files.
@@ -127,4 +129,7 @@ Take a second pass. Go back to the code and refine/polish further to make this a
 
 ## MULTI-PAGE OPTION
 
-To create additional pages when requested, create more creative pages along the same lines as the design philosophy but distinctly different as well. Bundle those pages in the same .pdf or many .pngs. Treat the first page as just a single page in a whole coffee table book waiting to be filled. Make the next pages unique twists and memories of the original. Have them almost tell a story in a very tasteful way. Exercise full creative freedom.
+To create additional pages when requested, create more creative pages along the same lines as the design philosophy but distinctly different as well. Bundle those pages in the same .pdf or many .pngs. Treat the first page as just a single page in a whole coffee table book waiting to be filled. Make the next pages unique twists and memories of the original. Have them almost tell a story in a very tasteful way. Exercise full creative freedom.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/cc-skill-backend-patterns/SKILL.md

@@ -1,8 +1,10 @@
 ---
-name: backend-patterns
-description: Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
+name: cc-skill-backend-patterns
+description: "Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes."
 author: affaan-m
 version: "1.0"
+risk: unknown
+source: community
 ---
 
 # Backend Development Patterns
@@ -581,4 +583,7 @@ export async function GET(request: Request) {
 }
 ```
 
-**Remember**: Backend patterns enable scalable, maintainable server-side applications. Choose patterns that fit your complexity level.
+**Remember**: Backend patterns enable scalable, maintainable server-side applications. Choose patterns that fit your complexity level.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/cc-skill-clickhouse-io/SKILL.md

@@ -1,8 +1,10 @@
 ---
-name: clickhouse-io
-description: ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.
+name: cc-skill-clickhouse-io
+description: "ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads."
 author: affaan-m
 version: "1.0"
+risk: unknown
+source: community
 ---
 
 # ClickHouse Analytics Patterns
@@ -428,4 +430,7 @@ pgClient.on('notification', async (msg) => {
 - Check merge operations
 - Review slow query log
 
-**Remember**: ClickHouse excels at analytical workloads. Design tables for your query patterns, batch inserts, and leverage materialized views for real-time aggregations.
+**Remember**: ClickHouse excels at analytical workloads. Design tables for your query patterns, batch inserts, and leverage materialized views for real-time aggregations.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/cc-skill-coding-standards/SKILL.md

@@ -1,8 +1,10 @@
 ---
-name: coding-standards
-description: Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
+name: cc-skill-coding-standards
+description: "Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development."
 author: affaan-m
 version: "1.0"
+risk: unknown
+source: community
 ---
 
 # Coding Standards & Best Practices
@@ -519,4 +521,7 @@ if (retryCount > MAX_RETRIES) { }
 setTimeout(callback, DEBOUNCE_DELAY_MS)
 ```
 
-**Remember**: Code quality is not negotiable. Clear, maintainable code enables rapid development and confident refactoring.
+**Remember**: Code quality is not negotiable. Clear, maintainable code enables rapid development and confident refactoring.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/cc-skill-continuous-learning/SKILL.md

@@ -1,10 +1,15 @@
 ---
 name: cc-skill-continuous-learning
-description: Development skill from everything-claude-code
+description: "Development skill from everything-claude-code"
 author: affaan-m
 version: "1.0"
+risk: unknown
+source: community
 ---
 
 # cc-skill-continuous-learning
 
 Development skill skill.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/cc-skill-frontend-patterns/SKILL.md

@@ -1,8 +1,10 @@
 ---
-name: frontend-patterns
-description: Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.
+name: cc-skill-frontend-patterns
+description: "Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices."
 author: affaan-m
 version: "1.0"
+risk: unknown
+source: community
 ---
 
 # Frontend Development Patterns
@@ -630,4 +632,7 @@ export function Modal({ isOpen, onClose, children }: ModalProps) {
 }
 ```
 
-**Remember**: Modern frontend patterns enable maintainable, performant user interfaces. Choose patterns that fit your project complexity.
+**Remember**: Modern frontend patterns enable maintainable, performant user interfaces. Choose patterns that fit your project complexity.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/cc-skill-project-guidelines-example/SKILL.md

@@ -1,8 +1,10 @@
 ---
 name: cc-skill-project-guidelines-example
-description: Project Guidelines Skill (Example)
+description: "Project Guidelines Skill (Example)"
 author: affaan-m
 version: "1.0"
+risk: unknown
+source: community
 ---
 
 # Project Guidelines Skill (Example)

package/skills/cc-skill-security-review/SKILL.md

@@ -1,8 +1,10 @@
 ---
-name: security-review
-description: Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
+name: cc-skill-security-review
+description: "Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist a..."
 author: affaan-m
 version: "1.0"
+risk: unknown
+source: community
 ---
 
 # Security Review Skill
@@ -493,4 +495,7 @@ Before ANY production deployment:
 
 ---
 
-**Remember**: Security is not optional. One vulnerability can compromise the entire platform. When in doubt, err on the side of caution.
+**Remember**: Security is not optional. One vulnerability can compromise the entire platform. When in doubt, err on the side of caution.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/cc-skill-strategic-compact/SKILL.md

@@ -1,10 +1,15 @@
 ---
 name: cc-skill-strategic-compact
-description: Development skill from everything-claude-code
+description: "Development skill from everything-claude-code"
 author: affaan-m
 version: "1.0"
+risk: unknown
+source: community
 ---
 
 # cc-skill-strategic-compact
 
 Development skill skill.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/changelog-automation/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: changelog-automation
-description: Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
+description: "Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions."
+risk: unknown
+source: community
 ---
 
 # Changelog Automation

package/skills/cicd-automation-workflow-automate/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: cicd-automation-workflow-automate
-description: "You are a workflow automation expert specializing in creating efficient CI/CD pipelines, GitHub Actions workflows, and automated development processes. Design automation that reduces manual work, improves consistency, and accelerates delivery while maintaining quality and security."
+description: "You are a workflow automation expert specializing in creating efficient CI/CD pipelines, GitHub Actions workflows, and automated development processes. Design automation that reduces manual work, i..."
+risk: unknown
+source: community
 ---
 
 # Workflow Automation