@ngxtm/devkit 3.15.0 → 3.17.0

package/merged-commands/brainstorming.md

@@ -1,230 +1,54 @@
 ---
 name: brainstorming
-description: >
-  Use this skill before any creative or constructive work
-  (features, components, architecture, behavior changes, or functionality).
-  This skill transforms vague ideas into validated designs through
-  disciplined, incremental reasoning and collaboration.
+description: "You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation."
 ---
 
 # Brainstorming Ideas Into Designs
 
-## Purpose
+## Overview
 
-Turn raw ideas into **clear, validated designs and specifications**
-through structured dialogue **before any implementation begins**.
+Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
 
-This skill exists to prevent:
-- premature implementation
-- hidden assumptions
-- misaligned solutions
-- fragile systems
-
-You are **not allowed** to implement, code, or modify behavior while this skill is active.
-
----
-
-## Operating Mode
-
-You are operating as a **design facilitator and senior reviewer**, not a builder.
-
-- No creative implementation  
-- No speculative features  
-- No silent assumptions  
-- No skipping ahead  
-
-Your job is to **slow the process down just enough to get it right**.
-
----
+Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.
 
 ## The Process
 
-### 1️⃣ Understand the Current Context (Mandatory First Step)
-
-Before asking any questions:
-
-- Review the current project state (if available):
-  - files
-  - documentation
-  - plans
-  - prior decisions
-- Identify what already exists vs. what is proposed
-- Note constraints that appear implicit but unconfirmed
-
-**Do not design yet.**
-
----
-
-### 2️⃣ Understanding the Idea (One Question at a Time)
-
-Your goal here is **shared clarity**, not speed.
-
-**Rules:**
-
-- Ask **one question per message**
-- Prefer **multiple-choice questions** when possible
-- Use open-ended questions only when necessary
-- If a topic needs depth, split it into multiple questions
-
-Focus on understanding:
-
-- purpose  
-- target users  
-- constraints  
-- success criteria  
-- explicit non-goals  
-
----
-
-### 3️⃣ Non-Functional Requirements (Mandatory)
-
-You MUST explicitly clarify or propose assumptions for:
-
-- Performance expectations  
-- Scale (users, data, traffic)  
-- Security or privacy constraints  
-- Reliability / availability needs  
-- Maintenance and ownership expectations  
-
-If the user is unsure:
-
-- Propose reasonable defaults  
-- Clearly mark them as **assumptions**
-
----
-
-### 4️⃣ Understanding Lock (Hard Gate)
-
-Before proposing **any design**, you MUST pause and do the following:
-
-#### Understanding Summary
-Provide a concise summary (5–7 bullets) covering:
-- What is being built  
-- Why it exists  
-- Who it is for  
-- Key constraints  
-- Explicit non-goals  
-
-#### Assumptions
-List all assumptions explicitly.
-
-#### Open Questions
-List unresolved questions, if any.
-
-Then ask:
-
-> “Does this accurately reflect your intent?  
-> Please confirm or correct anything before we move to design.”
-
-**Do NOT proceed until explicit confirmation is given.**
-
----
-
-### 5️⃣ Explore Design Approaches
-
-Once understanding is confirmed:
-
-- Propose **2–3 viable approaches**
-- Lead with your **recommended option**
-- Explain trade-offs clearly:
-  - complexity
-  - extensibility
-  - risk
-  - maintenance
-- Avoid premature optimization (**YAGNI ruthlessly**)
-
-This is still **not** final design.
-
----
-
-### 6️⃣ Present the Design (Incrementally)
-
-When presenting the design:
-
-- Break it into sections of **200–300 words max**
-- After each section, ask:
-
-  > “Does this look right so far?”
-
-Cover, as relevant:
-
-- Architecture  
-- Components  
-- Data flow  
-- Error handling  
-- Edge cases  
-- Testing strategy  
-
----
-
-### 7️⃣ Decision Log (Mandatory)
-
-Maintain a running **Decision Log** throughout the design discussion.
-
-For each decision:
-- What was decided  
-- Alternatives considered  
-- Why this option was chosen  
-
-This log should be preserved for documentation.
-
----
+**Understanding the idea:**
+- Check out the current project state first (files, docs, recent commits)
+- Ask questions one at a time to refine the idea
+- Prefer multiple choice questions when possible, but open-ended is fine too
+- Only one question per message - if a topic needs more exploration, break it into multiple questions
+- Focus on understanding: purpose, constraints, success criteria
+
+**Exploring approaches:**
+- Propose 2-3 different approaches with trade-offs
+- Present options conversationally with your recommendation and reasoning
+- Lead with your recommended option and explain why
+
+**Presenting the design:**
+- Once you believe you understand what you're building, present the design
+- Break it into sections of 200-300 words
+- Ask after each section whether it looks right so far
+- Cover: architecture, components, data flow, error handling, testing
+- Be ready to go back and clarify if something doesn't make sense
 
 ## After the Design
 
-### 📄 Documentation
-
-Once the design is validated:
-
-- Write the final design to a durable, shared format (e.g. Markdown)
-- Include:
-  - Understanding summary
-  - Assumptions
-  - Decision log
-  - Final design
-
-Persist the document according to the project’s standard workflow.
-
----
-
-### 🛠️ Implementation Handoff (Optional)
-
-Only after documentation is complete, ask:
+**Documentation:**
+- Write the validated design to `docs/plans/YYYY-MM-DD-<topic>-design.md`
+- Use elements-of-style:writing-clearly-and-concisely skill if available
+- Commit the design document to git
 
-> “Ready to set up for implementation?”
+**Implementation (if continuing):**
+- Ask: "Ready to set up for implementation?"
+- Use superpowers:using-git-worktrees to create isolated workspace
+- Use superpowers:writing-plans to create detailed implementation plan
 
-If yes:
-- Create an explicit implementation plan
-- Isolate work if the workflow supports it
-- Proceed incrementally
-
----
+## Key Principles
 
-## Exit Criteria (Hard Stop Conditions)
-
-You may exit brainstorming mode **only when all of the following are true**:
-
-- Understanding Lock has been confirmed  
-- At least one design approach is explicitly accepted  
-- Major assumptions are documented  
-- Key risks are acknowledged  
-- Decision Log is complete  
-
-If any criterion is unmet:
-- Continue refinement  
-- **Do NOT proceed to implementation**
-
----
-
-## Key Principles (Non-Negotiable)
-
-- One question at a time  
-- Assumptions must be explicit  
-- Explore alternatives  
-- Validate incrementally  
-- Prefer clarity over cleverness  
-- Be willing to go back and clarify  
-- **YAGNI ruthlessly**
-
----
-If the design is high-impact, high-risk, or requires elevated confidence, you MUST hand off the finalized design and Decision Log to the `multi-agent-brainstorming` skill before implementation.
+- **One question at a time** - Don't overwhelm with multiple questions
+- **Multiple choice preferred** - Easier to answer than open-ended when possible
+- **YAGNI ruthlessly** - Remove unnecessary features from all designs
+- **Explore alternatives** - Always propose 2-3 approaches before settling
+- **Incremental validation** - Present design in sections, validate each
+- **Be flexible** - Go back and clarify when something doesn't make sense

package/merged-commands/brand-guidelines-anthropic.md

@@ -1,7 +1,9 @@
 ---
-name: brand-guidelines
-description: Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
+name: brand-guidelines-anthropic
+description: "Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatt..."
 license: Complete terms in LICENSE.txt
+risk: unknown
+source: community
 ---
 
 # Anthropic Brand Styling
@@ -71,3 +73,6 @@ To access Anthropic's official brand identity and style resources, use this skil
 - Uses RGB color values for precise brand matching
 - Applied via python-pptx's RGBColor class
 - Maintains color fidelity across different systems
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/brand-guidelines-community.md

@@ -1,7 +1,9 @@
 ---
-name: brand-guidelines
-description: Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
+name: brand-guidelines-community
+description: "Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatt..."
 license: Complete terms in LICENSE.txt
+risk: unknown
+source: community
 ---
 
 # Anthropic Brand Styling
@@ -71,3 +73,6 @@ To access Anthropic's official brand identity and style resources, use this skil
 - Uses RGB color values for precise brand matching
 - Applied via python-pptx's RGBColor class
 - Maintains color fidelity across different systems
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/brevo-automation.md

@@ -0,0 +1,202 @@
+---
+name: brevo-automation
+description: "Automate Brevo (Sendinblue) tasks via Rube MCP (Composio): manage email campaigns, create/edit templates, track senders, and monitor campaign performance. Always search tools first for current sche..."
+requires:
+  mcp: [rube]
+risk: unknown
+source: community
+---
+
+# Brevo Automation via Rube MCP
+
+Automate Brevo (formerly Sendinblue) email marketing operations through Composio's Brevo toolkit via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Brevo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `brevo`
+- 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 `brevo`
+3. If connection is not ACTIVE, follow the returned auth link to complete Brevo authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Manage Email Campaigns
+
+**When to use**: User wants to list, review, or update email campaigns
+
+**Tool sequence**:
+1. `BREVO_LIST_EMAIL_CAMPAIGNS` - List all campaigns with filters [Required]
+2. `BREVO_UPDATE_EMAIL_CAMPAIGN` - Update campaign content or settings [Optional]
+
+**Key parameters for listing**:
+- `type`: Campaign type ('classic' or 'trigger')
+- `status`: Campaign status ('suspended', 'archive', 'sent', 'queued', 'draft', 'inProcess', 'inReview')
+- `startDate`/`endDate`: Date range filter (YYYY-MM-DDTHH:mm:ss.SSSZ format)
+- `statistics`: Stats type to include ('globalStats', 'linksStats', 'statsByDomain')
+- `limit`: Results per page (max 100, default 50)
+- `offset`: Pagination offset
+- `sort`: Sort order ('asc' or 'desc')
+- `excludeHtmlContent`: Set `true` to reduce response size
+
+**Key parameters for update**:
+- `campaign_id`: Numeric campaign ID (required)
+- `name`: Campaign name
+- `subject`: Email subject line
+- `htmlContent`: HTML email body (mutually exclusive with `htmlUrl`)
+- `htmlUrl`: URL to HTML content
+- `sender`: Sender object with `name`, `email`, or `id`
+- `recipients`: Object with `listIds` and `exclusionListIds`
+- `scheduledAt`: Scheduled send time (YYYY-MM-DDTHH:mm:ss.SSSZ)
+
+**Pitfalls**:
+- `startDate` and `endDate` are mutually required; provide both or neither
+- Date filters only work when `status` is not passed or set to 'sent'
+- `htmlContent` and `htmlUrl` are mutually exclusive
+- Campaign `sender` email must be a verified sender in Brevo
+- A/B testing fields (`subjectA`, `subjectB`, `splitRule`, `winnerCriteria`) require `abTesting: true`
+- `scheduledAt` uses full ISO 8601 format with timezone
+
+### 2. Create and Manage Email Templates
+
+**When to use**: User wants to create, edit, list, or delete email templates
+
+**Tool sequence**:
+1. `BREVO_GET_ALL_EMAIL_TEMPLATES` - List all templates [Required]
+2. `BREVO_CREATE_OR_UPDATE_EMAIL_TEMPLATE` - Create a new template or update existing [Required]
+3. `BREVO_DELETE_EMAIL_TEMPLATE` - Delete an inactive template [Optional]
+
+**Key parameters for listing**:
+- `templateStatus`: Filter active (`true`) or inactive (`false`) templates
+- `limit`: Results per page (max 1000, default 50)
+- `offset`: Pagination offset
+- `sort`: Sort order ('asc' or 'desc')
+
+**Key parameters for create/update**:
+- `templateId`: Include to update; omit to create new
+- `templateName`: Template display name (required for creation)
+- `subject`: Email subject line (required for creation)
+- `htmlContent`: HTML template body (min 10 characters; use this or `htmlUrl`)
+- `sender`: Sender object with `name` and `email`, or `id` (required for creation)
+- `replyTo`: Reply-to email address
+- `isActive`: Activate or deactivate the template
+- `tag`: Category tag for the template
+
+**Pitfalls**:
+- When `templateId` is provided, the tool updates; when omitted, it creates
+- For creation, `templateName`, `subject`, and `sender` are required
+- `htmlContent` must be at least 10 characters
+- Template personalization uses `{{contact.ATTRIBUTE}}` syntax
+- Only inactive templates can be deleted
+- `htmlContent` and `htmlUrl` are mutually exclusive
+
+### 3. Manage Senders
+
+**When to use**: User wants to view authorized sender identities
+
+**Tool sequence**:
+1. `BREVO_GET_ALL_SENDERS` - List all verified senders [Required]
+
+**Key parameters**: (none required)
+
+**Pitfalls**:
+- Senders must be verified before they can be used in campaigns or templates
+- Sender verification is done through the Brevo web interface, not via API
+- Sender IDs can be used in `sender.id` fields for campaigns and templates
+
+### 4. Configure A/B Testing Campaigns
+
+**When to use**: User wants to set up or modify A/B test settings on a campaign
+
+**Tool sequence**:
+1. `BREVO_LIST_EMAIL_CAMPAIGNS` - Find the target campaign [Prerequisite]
+2. `BREVO_UPDATE_EMAIL_CAMPAIGN` - Configure A/B test settings [Required]
+
+**Key parameters**:
+- `campaign_id`: Campaign to configure
+- `abTesting`: Set to `true` to enable A/B testing
+- `subjectA`: Subject line for variant A
+- `subjectB`: Subject line for variant B
+- `splitRule`: Percentage split for the test (1-99)
+- `winnerCriteria`: 'open' or 'click' for determining the winner
+- `winnerDelay`: Hours to wait before selecting winner (1-168)
+
+**Pitfalls**:
+- A/B testing must be enabled (`abTesting: true`) before setting variant fields
+- `splitRule` is the percentage of contacts that receive variant A
+- `winnerDelay` defines how long to test before sending the winner to remaining contacts
+- Only works with 'classic' campaign type
+
+## Common Patterns
+
+### Campaign Lifecycle
+
+```
+1. Create campaign (status: draft)
+2. Set recipients (listIds)
+3. Configure content (htmlContent or htmlUrl)
+4. Optionally schedule (scheduledAt)
+5. Send or schedule via Brevo UI (API update can set scheduledAt)
+```
+
+### Pagination
+
+- Use `limit` (page size) and `offset` (starting index)
+- Default limit is 50; max varies by endpoint (100 for campaigns, 1000 for templates)
+- Increment `offset` by `limit` each page
+- Check `count` in response to determine total available
+
+### Template Personalization
+
+```
+- First name: {{contact.FIRSTNAME}}
+- Last name: {{contact.LASTNAME}}
+- Custom attribute: {{contact.CUSTOM_ATTRIBUTE}}
+- Mirror link: {{mirror}}
+- Unsubscribe link: {{unsubscribe}}
+```
+
+## Known Pitfalls
+
+**Date Formats**:
+- All dates use ISO 8601 with milliseconds: YYYY-MM-DDTHH:mm:ss.SSSZ
+- Pass timezone in the date-time format for accurate results
+- `startDate` and `endDate` must be used together
+
+**Sender Verification**:
+- All sender emails must be verified in Brevo before use
+- Unverified senders cause campaign creation/update failures
+- Use GET_ALL_SENDERS to check available verified senders
+
+**Rate Limits**:
+- Brevo API has rate limits per account plan
+- Implement backoff on 429 responses
+- Template operations have lower limits than read operations
+
+**Response Parsing**:
+- Response data may be nested under `data` or `data.data`
+- Parse defensively with fallback patterns
+- Campaign and template IDs are numeric integers
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List campaigns | BREVO_LIST_EMAIL_CAMPAIGNS | type, status, limit, offset |
+| Update campaign | BREVO_UPDATE_EMAIL_CAMPAIGN | campaign_id, subject, htmlContent |
+| List templates | BREVO_GET_ALL_EMAIL_TEMPLATES | templateStatus, limit, offset |
+| Create template | BREVO_CREATE_OR_UPDATE_EMAIL_TEMPLATE | templateName, subject, htmlContent, sender |
+| Update template | BREVO_CREATE_OR_UPDATE_EMAIL_TEMPLATE | templateId, htmlContent |
+| Delete template | BREVO_DELETE_EMAIL_TEMPLATE | templateId |
+| List senders | BREVO_GET_ALL_SENDERS | (none) |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/broken-authentication.md

@@ -1,9 +1,11 @@
 ---
-name: Broken Authentication Testing
-description: This skill should be used when the user asks to "test for broken authentication vulnerabilities", "assess session management security", "perform credential stuffing tests", "evaluate password policies", "test for session fixation", or "identify authentication bypass flaws". It provides comprehensive techniques for identifying authentication and session management weaknesses in web applications.
+name: broken-authentication
+description: "This skill should be used when the user asks to \"test for broken authentication vulnerabilities\", \"assess session management security\", \"perform credential stuffing tests\", \"evaluate ..."
 metadata:
   author: zebbern
   version: "1.1"
+risk: unknown
+source: community
 ---
 
 # Broken Authentication Testing
@@ -474,3 +476,6 @@ https://target.com/reset?token=a1b2c3d4e5f6&email=admin@example.com
 | Session analysis inconclusive | Collect 1000+ tokens; use statistical tools; check for timestamps; compare accounts |
 | MFA cannot be bypassed | Document as secure; test backup/recovery mechanisms; check MFA fatigue; verify enrollment |
 | Account lockout prevents testing | Request multiple test accounts; test threshold first; use slower timing |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/browser-automation.md

@@ -1,7 +1,8 @@
 ---
 name: browser-automation
-description: "Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, and anti-detection patterns.  This skill covers Playwright (recommended) and Puppeteer, with patterns for testing, scraping, and agentic browser control. Key insight: Playwright won the framework war. Unless you need Puppeteer's stealth ecosystem or are Chrome-only, Playwright is the better choice in 202"
+description: "Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, an..."
 source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
 ---
 
 # Browser Automation
@@ -68,3 +69,6 @@ Let Playwright wait automatically, never add manual waits
 ## Related Skills
 
 Works well with: `agent-tool-builder`, `workflow-automation`, `computer-use-agents`, `test-architect`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/browser-extension-builder.md

@@ -1,7 +1,8 @@
 ---
 name: browser-extension-builder
-description: "Expert in building browser extensions that solve real problems - Chrome, Firefox, and cross-browser extensions. Covers extension architecture, manifest v3, content scripts, popup UIs, monetization strategies, and Chrome Web Store publishing. Use when: browser extension, chrome extension, firefox addon, extension, manifest v3."
+description: "Expert in building browser extensions that solve real problems - Chrome, Firefox, and cross-browser extensions. Covers extension architecture, manifest v3, content scripts, popup UIs, monetization ..."
 source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
 ---
 
 # Browser Extension Builder
@@ -259,3 +260,6 @@ Update quickly when broken.
 ## Related Skills
 
 Works well with: `frontend`, `micro-saas-launcher`, `personal-tool-builder`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/bullmq-specialist.md

@@ -2,6 +2,7 @@
 name: bullmq-specialist
 description: "BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js/TypeScript applications. Use when: bullmq, bull queue, redis queue, background job, job queue."
 source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
 ---
 
 # BullMQ Specialist
@@ -55,3 +56,6 @@ Complex multi-step job processing with parent-child relationships
 ## Related Skills
 
 Works well with: `redis-specialist`, `backend`, `nextjs-app-router`, `email-systems`, `ai-workflow-automation`, `performance-hunter`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/bun-development.md

@@ -1,6 +1,8 @@
 ---
 name: bun-development
-description: "Modern JavaScript/TypeScript development with Bun runtime. Covers package management, bundling, testing, and migration from Node.js. Use when working with Bun, optimizing JS/TS development speed, or migrating from Node.js to Bun."
+description: "Modern JavaScript/TypeScript development with Bun runtime. Covers package management, bundling, testing, and migration from Node.js. Use when working with Bun, optimizing JS/TS development speed, o..."
+risk: unknown
+source: community
 ---
 
 # ⚡ Bun Development

package/merged-commands/burp-suite-testing.md

@@ -1,9 +1,11 @@
 ---
-name: Burp Suite Web Application Testing
-description: This skill should be used when the user asks to "intercept HTTP traffic", "modify web requests", "use Burp Suite for testing", "perform web vulnerability scanning", "test with Burp Repeater", "analyze HTTP history", or "configure proxy for web testing". It provides comprehensive guidance for using Burp Suite's core features for web application security testing.
+name: burp-suite-testing
+description: "This skill should be used when the user asks to \"intercept HTTP traffic\", \"modify web requests\", \"use Burp Suite for testing\", \"perform web vulnerability scanning\", \"test with Burp ..."
 metadata:
   author: zebbern
   version: "1.1"
+risk: unknown
+source: community
 ---
 
 # Burp Suite Web Application Testing
@@ -378,3 +380,6 @@ javascript:alert(1)
 - Check intercept rules aren't filtering target
 - Ensure browser is using Burp proxy
 - Verify target isn't using unsupported protocol
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/business-analyst.md

@@ -1,11 +1,13 @@
 ---
 name: business-analyst
-description: Master modern business analysis with AI-powered analytics,
+description: "Master modern business analysis with AI-powered analytics,"
   real-time dashboards, and data-driven insights. Build comprehensive KPI
   frameworks, predictive models, and strategic recommendations. Use PROACTIVELY
   for business intelligence or strategic analysis.
 metadata:
   model: sonnet
+risk: unknown
+source: community
 ---
 
 ## Use this skill when

package/merged-commands/busybox-on-windows.md

@@ -1,7 +1,9 @@
 ---
 name: busybox-on-windows
-description: How to use a Win32 build of BusyBox to run many of the standard UNIX command line tools on Windows.
+description: "How to use a Win32 build of BusyBox to run many of the standard UNIX command line tools on Windows."
 license: MIT
+risk: unknown
+source: community
 ---
 
 BusyBox is a single binary that implements many common Unix tools.
@@ -28,3 +30,6 @@ If you need to run a UNIX command under another CWD, then use the absolute path
 
 Documentation: https://frippery.org/busybox/
 Original BusyBox: https://busybox.net/
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/c-pro.md

@@ -6,6 +6,8 @@ description: Write efficient C code with proper memory management, pointer
   or system programming.
 metadata:
   model: opus
+risk: unknown
+source: community
 ---
 
 ## Use this skill when

package/merged-commands/c4-architecture-c4-architecture.md

@@ -1,6 +1,8 @@
 ---
 name: c4-architecture-c4-architecture
 description: "Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach."
+risk: unknown
+source: community
 ---
 
 # C4 Architecture Documentation Workflow