@ngxtm/devkit 3.14.0 → 3.16.0

package/merged-commands/canva-automation.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/merged-commands/canvas-design.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/merged-commands/cc-skill-backend-patterns.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/merged-commands/cc-skill-clickhouse-io.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/merged-commands/cc-skill-coding-standards.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/merged-commands/cc-skill-continuous-learning.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/merged-commands/cc-skill-frontend-patterns.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/merged-commands/cc-skill-project-guidelines-example.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/merged-commands/cc-skill-security-review.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/merged-commands/cc-skill-strategic-compact.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/merged-commands/changelog-automation.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/merged-commands/cicd-automation-workflow-automate.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

package/merged-commands/circleci-automation.md

@@ -0,0 +1,182 @@
+---
+name: circleci-automation
+description: "Automate CircleCI tasks via Rube MCP (Composio): trigger pipelines, monitor workflows/jobs, retrieve artifacts and test metadata. Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+risk: unknown
+source: community
+---
+
+# CircleCI Automation via Rube MCP
+
+Automate CircleCI CI/CD operations through Composio's CircleCI toolkit via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active CircleCI connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `circleci`
+- 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 `circleci`
+3. If connection is not ACTIVE, follow the returned auth link to complete CircleCI authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Trigger a Pipeline
+
+**When to use**: User wants to start a new CI/CD pipeline run
+
+**Tool sequence**:
+1. `CIRCLECI_TRIGGER_PIPELINE` - Trigger a new pipeline on a project [Required]
+2. `CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID` - Monitor resulting workflows [Optional]
+
+**Key parameters**:
+- `project_slug`: Project identifier in format `gh/org/repo` or `bb/org/repo`
+- `branch`: Git branch to run the pipeline on
+- `tag`: Git tag to run the pipeline on (mutually exclusive with branch)
+- `parameters`: Pipeline parameter key-value pairs
+
+**Pitfalls**:
+- `project_slug` format is `{vcs}/{org}/{repo}` (e.g., `gh/myorg/myrepo`)
+- `branch` and `tag` are mutually exclusive; providing both causes an error
+- Pipeline parameters must match those defined in `.circleci/config.yml`
+- Triggering returns a pipeline ID; workflows start asynchronously
+
+### 2. Monitor Pipelines and Workflows
+
+**When to use**: User wants to check the status of pipelines or workflows
+
+**Tool sequence**:
+1. `CIRCLECI_LIST_PIPELINES_FOR_PROJECT` - List recent pipelines for a project [Required]
+2. `CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID` - List workflows within a pipeline [Required]
+3. `CIRCLECI_GET_PIPELINE_CONFIG` - View the pipeline configuration used [Optional]
+
+**Key parameters**:
+- `project_slug`: Project identifier in `{vcs}/{org}/{repo}` format
+- `pipeline_id`: UUID of a specific pipeline
+- `branch`: Filter pipelines by branch name
+- `page_token`: Pagination cursor for next page of results
+
+**Pitfalls**:
+- Pipeline IDs are UUIDs, not numeric IDs
+- Workflows inherit the pipeline ID; a single pipeline can have multiple workflows
+- Workflow states include: success, running, not_run, failed, error, failing, on_hold, canceled, unauthorized
+- `page_token` is returned in responses for pagination; continue until absent
+
+### 3. Inspect Job Details
+
+**When to use**: User wants to drill into a specific job's execution details
+
+**Tool sequence**:
+1. `CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID` - Find workflow containing the job [Prerequisite]
+2. `CIRCLECI_GET_JOB_DETAILS` - Get detailed job information [Required]
+
+**Key parameters**:
+- `project_slug`: Project identifier
+- `job_number`: Numeric job number (not UUID)
+
+**Pitfalls**:
+- Job numbers are integers, not UUIDs (unlike pipeline and workflow IDs)
+- Job details include executor type, parallelism, start/stop times, and status
+- Job statuses: success, running, not_run, failed, retried, timedout, infrastructure_fail, canceled
+
+### 4. Retrieve Build Artifacts
+
+**When to use**: User wants to download or list artifacts produced by a job
+
+**Tool sequence**:
+1. `CIRCLECI_GET_JOB_DETAILS` - Confirm job completed successfully [Prerequisite]
+2. `CIRCLECI_GET_JOB_ARTIFACTS` - List all artifacts from the job [Required]
+
+**Key parameters**:
+- `project_slug`: Project identifier
+- `job_number`: Numeric job number
+
+**Pitfalls**:
+- Artifacts are only available after job completion
+- Each artifact has a `path` and `url` for download
+- Artifact URLs may require authentication headers to download
+- Large artifacts may have download size limits
+
+### 5. Review Test Results
+
+**When to use**: User wants to check test outcomes for a specific job
+
+**Tool sequence**:
+1. `CIRCLECI_GET_JOB_DETAILS` - Verify job ran tests [Prerequisite]
+2. `CIRCLECI_GET_TEST_METADATA` - Retrieve test results and metadata [Required]
+
+**Key parameters**:
+- `project_slug`: Project identifier
+- `job_number`: Numeric job number
+
+**Pitfalls**:
+- Test metadata requires the job to have uploaded test results (JUnit XML format)
+- If no test results were uploaded, the response will be empty
+- Test metadata includes classname, name, result, message, and run_time fields
+- Failed tests include failure messages in the `message` field
+
+## Common Patterns
+
+### Project Slug Format
+
+```
+Format: {vcs_type}/{org_name}/{repo_name}
+- GitHub:    gh/myorg/myrepo
+- Bitbucket: bb/myorg/myrepo
+```
+
+### Pipeline -> Workflow -> Job Hierarchy
+
+```
+1. Call CIRCLECI_LIST_PIPELINES_FOR_PROJECT to get pipeline IDs
+2. Call CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID with pipeline_id
+3. Extract job numbers from workflow details
+4. Call CIRCLECI_GET_JOB_DETAILS with job_number
+```
+
+### Pagination
+
+- Check response for `next_page_token` field
+- Pass token as `page_token` in next request
+- Continue until `next_page_token` is absent or null
+
+## Known Pitfalls
+
+**ID Formats**:
+- Pipeline IDs: UUIDs (e.g., `5034460f-c7c4-4c43-9457-de07e2029e7b`)
+- Workflow IDs: UUIDs
+- Job numbers: Integers (e.g., `123`)
+- Do NOT mix up UUIDs and integers between different endpoints
+
+**Project Slugs**:
+- Must include VCS prefix: `gh/` for GitHub, `bb/` for Bitbucket
+- Organization and repo names are case-sensitive
+- Incorrect slug format causes 404 errors
+
+**Rate Limits**:
+- CircleCI API has per-endpoint rate limits
+- Implement exponential backoff on 429 responses
+- Avoid rapid polling; use reasonable intervals (5-10 seconds)
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Trigger pipeline | CIRCLECI_TRIGGER_PIPELINE | project_slug, branch, parameters |
+| List pipelines | CIRCLECI_LIST_PIPELINES_FOR_PROJECT | project_slug, branch |
+| List workflows | CIRCLECI_LIST_WORKFLOWS_BY_PIPELINE_ID | pipeline_id |
+| Get pipeline config | CIRCLECI_GET_PIPELINE_CONFIG | pipeline_id |
+| Get job details | CIRCLECI_GET_JOB_DETAILS | project_slug, job_number |
+| Get job artifacts | CIRCLECI_GET_JOB_ARTIFACTS | project_slug, job_number |
+| Get test metadata | CIRCLECI_GET_TEST_METADATA | project_slug, job_number |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/claude-code-guide.md

@@ -1,6 +1,8 @@
 ---
-name: Claude Code Guide
-description: Master guide for using Claude Code effectively. Includes configuration templates, prompting strategies "Thinking" keywords, debugging techniques, and best practices for interacting with the agent.
+name: claude-code-guide
+description: "Master guide for using Claude Code effectively. Includes configuration templates, prompting strategies \\\"Thinking\\\" keywords, debugging techniques, and best practices for interacting wit..."
+risk: unknown
+source: community
 ---
 
 # Claude Code Guide
@@ -66,3 +68,6 @@ If the agent is stuck or behaving unexpectedly:
 ## Reference
 
 Based on [Claude Code Guide by zebbern](https://github.com/zebbern/claude-code-guide).
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/claude-d3js-skill.md

@@ -1,6 +1,8 @@
 ---
-name: d3-viz
-description: Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisations, or any complex SVG-based data visualisation that requires fine-grained control over visual elements, transitions, or interactions. Use this for bespoke visualisations beyond standard charting libraries, whether in React, Vue, Svelte, vanilla JavaScript, or any other environment.
+name: claude-d3js-skill
+description: "Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisations, or any complex SVG-based data visua..."
+risk: unknown
+source: community
 ---
 
 # D3.js Visualisation