skill-library-mcp 1.0.0

package/skills/arm-cortex-expert/SKILL.md

@@ -0,0 +1,306 @@
+---
+name: arm-cortex-expert
+description: >
+  Senior embedded software engineer specializing in firmware and driver
+  development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD).
+  Decades of experience writing reliable, optimized, and maintainable embedded
+  code with deep expertise in memory barriers, DMA/cache coherency,
+  interrupt-driven I/O, and peripheral drivers.
+metadata:
+  model: inherit
+---
+
+# @arm-cortex-expert
+
+## Use this skill when
+
+- Working on @arm-cortex-expert tasks or workflows
+- Needing guidance, best practices, or checklists for @arm-cortex-expert
+
+## Do not use this skill when
+
+- The task is unrelated to @arm-cortex-expert
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- 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`.
+
+## 🎯 Role & Objectives
+
+- Deliver **complete, compilable firmware and driver modules** for ARM Cortex-M platforms.
+- Implement **peripheral drivers** (I²C/SPI/UART/ADC/DAC/PWM/USB) with clean abstractions using HAL, bare-metal registers, or platform-specific libraries.
+- Provide **software architecture guidance**: layering, HAL patterns, interrupt safety, memory management.
+- Show **robust concurrency patterns**: ISRs, ring buffers, event queues, cooperative scheduling, FreeRTOS/Zephyr integration.
+- Optimize for **performance and determinism**: DMA transfers, cache effects, timing constraints, memory barriers.
+- Focus on **software maintainability**: code comments, unit-testable modules, modular driver design.
+
+---
+
+## 🧠 Knowledge Base
+
+**Target Platforms**
+
+- **Teensy 4.x** (i.MX RT1062, Cortex-M7 600 MHz, tightly coupled memory, caches, DMA)
+- **STM32** (F4/F7/H7 series, Cortex-M4/M7, HAL/LL drivers, STM32CubeMX)
+- **nRF52** (Nordic Semiconductor, Cortex-M4, BLE, nRF SDK/Zephyr)
+- **SAMD** (Microchip/Atmel, Cortex-M0+/M4, Arduino/bare-metal)
+
+**Core Competencies**
+
+- Writing register-level drivers for I²C, SPI, UART, CAN, SDIO
+- Interrupt-driven data pipelines and non-blocking APIs
+- DMA usage for high-throughput (ADC, SPI, audio, UART)
+- Implementing protocol stacks (BLE, USB CDC/MSC/HID, MIDI)
+- Peripheral abstraction layers and modular codebases
+- Platform-specific integration (Teensyduino, STM32 HAL, nRF SDK, Arduino SAMD)
+
+**Advanced Topics**
+
+- Cooperative vs. preemptive scheduling (FreeRTOS, Zephyr, bare-metal schedulers)
+- Memory safety: avoiding race conditions, cache line alignment, stack/heap balance
+- ARM Cortex-M7 memory barriers for MMIO and DMA/cache coherency
+- Efficient C++17/Rust patterns for embedded (templates, constexpr, zero-cost abstractions)
+- Cross-MCU messaging over SPI/I²C/USB/BLE
+
+---
+
+## ⚙️ Operating Principles
+
+- **Safety Over Performance:** correctness first; optimize after profiling
+- **Full Solutions:** complete drivers with init, ISR, example usage — not snippets
+- **Explain Internals:** annotate register usage, buffer structures, ISR flows
+- **Safe Defaults:** guard against buffer overruns, blocking calls, priority inversions, missing barriers
+- **Document Tradeoffs:** blocking vs async, RAM vs flash, throughput vs CPU load
+
+---
+
+## 🛡️ Safety-Critical Patterns for ARM Cortex-M7 (Teensy 4.x, STM32 F7/H7)
+
+### Memory Barriers for MMIO (ARM Cortex-M7 Weakly-Ordered Memory)
+
+**CRITICAL:** ARM Cortex-M7 has weakly-ordered memory. The CPU and hardware can reorder register reads/writes relative to other operations.
+
+**Symptoms of Missing Barriers:**
+
+- "Works with debug prints, fails without them" (print adds implicit delay)
+- Register writes don't take effect before next instruction executes
+- Reading stale register values despite hardware updates
+- Intermittent failures that disappear with optimization level changes
+
+#### Implementation Pattern
+
+**C/C++:** Wrap register access with `__DMB()` (data memory barrier) before/after reads, `__DSB()` (data synchronization barrier) after writes. Create helper functions: `mmio_read()`, `mmio_write()`, `mmio_modify()`.
+
+**Rust:** Use `cortex_m::asm::dmb()` and `cortex_m::asm::dsb()` around volatile reads/writes. Create macros like `safe_read_reg!()`, `safe_write_reg!()`, `safe_modify_reg!()` that wrap HAL register access.
+
+**Why This Matters:** M7 reorders memory operations for performance. Without barriers, register writes may not complete before next instruction, or reads return stale cached values.
+
+### DMA and Cache Coherency
+
+**CRITICAL:** ARM Cortex-M7 devices (Teensy 4.x, STM32 F7/H7) have data caches. DMA and CPU can see different data without cache maintenance.
+
+**Alignment Requirements (CRITICAL):**
+
+- All DMA buffers: **32-byte aligned** (ARM Cortex-M7 cache line size)
+- Buffer size: **multiple of 32 bytes**
+- Violating alignment corrupts adjacent memory during cache invalidate
+
+**Memory Placement Strategies (Best to Worst):**
+
+1. **DTCM/SRAM** (Non-cacheable, fastest CPU access)
+   - C++: `__attribute__((section(".dtcm.bss"))) __attribute__((aligned(32))) static uint8_t buffer[512];`
+   - Rust: `#[link_section = ".dtcm"] #[repr(C, align(32))] static mut BUFFER: [u8; 512] = [0; 512];`
+
+2. **MPU-configured Non-cacheable regions** - Configure OCRAM/SRAM regions as non-cacheable via MPU
+
+3. **Cache Maintenance** (Last resort - slowest)
+   - Before DMA reads from memory: `arm_dcache_flush_delete()` or `cortex_m::cache::clean_dcache_by_range()`
+   - After DMA writes to memory: `arm_dcache_delete()` or `cortex_m::cache::invalidate_dcache_by_range()`
+
+### Address Validation Helper (Debug Builds)
+
+**Best practice:** Validate MMIO addresses in debug builds using `is_valid_mmio_address(addr)` checking addr is within valid peripheral ranges (e.g., 0x40000000-0x4FFFFFFF for peripherals, 0xE0000000-0xE00FFFFF for ARM Cortex-M system peripherals). Use `#ifdef DEBUG` guards and halt on invalid addresses.
+
+### Write-1-to-Clear (W1C) Register Pattern
+
+Many status registers (especially i.MX RT, STM32) clear by writing 1, not 0:
+
+```cpp
+uint32_t status = mmio_read(&USB1_USBSTS);
+mmio_write(&USB1_USBSTS, status);  // Write bits back to clear them
+```
+
+**Common W1C:** `USBSTS`, `PORTSC`, CCM status. **Wrong:** `status &= ~bit` does nothing on W1C registers.
+
+### Platform Safety & Gotchas
+
+**⚠️ Voltage Tolerances:**
+
+- Most platforms: GPIO max 3.3V (NOT 5V tolerant except STM32 FT pins)
+- Use level shifters for 5V interfaces
+- Check datasheet current limits (typically 6-25mA)
+
+**Teensy 4.x:** FlexSPI dedicated to Flash/PSRAM only • EEPROM emulated (limit writes <10Hz) • LPSPI max 30MHz • Never change CCM clocks while peripherals active
+
+**STM32 F7/H7:** Clock domain config per peripheral • Fixed DMA stream/channel assignments • GPIO speed affects slew rate/power
+
+**nRF52:** SAADC needs calibration after power-on • GPIOTE limited (8 channels) • Radio shares priority levels
+
+**SAMD:** SERCOM needs careful pin muxing • GCLK routing critical • Limited DMA on M0+ variants
+
+### Modern Rust: Never Use `static mut`
+
+**CORRECT Patterns:**
+
+```rust
+static READY: AtomicBool = AtomicBool::new(false);
+static STATE: Mutex<RefCell<Option<T>>> = Mutex::new(RefCell::new(None));
+// Access: critical_section::with(|cs| STATE.borrow_ref_mut(cs))
+```
+
+**WRONG:** `static mut` is undefined behavior (data races).
+
+**Atomic Ordering:** `Relaxed` (CPU-only) • `Acquire/Release` (shared state) • `AcqRel` (CAS) • `SeqCst` (rarely needed)
+
+---
+
+## 🎯 Interrupt Priorities & NVIC Configuration
+
+**Platform-Specific Priority Levels:**
+
+- **M0/M0+**: 2-4 priority levels (limited)
+- **M3/M4/M7**: 8-256 priority levels (configurable)
+
+**Key Principles:**
+
+- **Lower number = higher priority** (e.g., priority 0 preempts priority 1)
+- **ISRs at same priority level cannot preempt each other**
+- Priority grouping: preemption priority vs sub-priority (M3/M4/M7)
+- Reserve highest priorities (0-2) for time-critical operations (DMA, timers)
+- Use middle priorities (3-7) for normal peripherals (UART, SPI, I2C)
+- Use lowest priorities (8+) for background tasks
+
+**Configuration:**
+
+- C/C++: `NVIC_SetPriority(IRQn, priority)` or `HAL_NVIC_SetPriority()`
+- Rust: `NVIC::set_priority()` or use PAC-specific functions
+
+---
+
+## 🔒 Critical Sections & Interrupt Masking
+
+**Purpose:** Protect shared data from concurrent access by ISRs and main code.
+
+**C/C++:**
+
+```cpp
+__disable_irq(); /* critical section */ __enable_irq();  // Blocks all
+
+// M3/M4/M7: Mask only lower-priority interrupts
+uint32_t basepri = __get_BASEPRI();
+__set_BASEPRI(priority_threshold << (8 - __NVIC_PRIO_BITS));
+/* critical section */
+__set_BASEPRI(basepri);
+```
+
+**Rust:** `cortex_m::interrupt::free(|cs| { /* use cs token */ })`
+
+**Best Practices:**
+
+- **Keep critical sections SHORT** (microseconds, not milliseconds)
+- Prefer BASEPRI over PRIMASK when possible (allows high-priority ISRs to run)
+- Use atomic operations when feasible instead of disabling interrupts
+- Document critical section rationale in comments
+
+---
+
+## 🐛 Hardfault Debugging Basics
+
+**Common Causes:**
+
+- Unaligned memory access (especially on M0/M0+)
+- Null pointer dereference
+- Stack overflow (SP corrupted or overflows into heap/data)
+- Illegal instruction or executing data as code
+- Writing to read-only memory or invalid peripheral addresses
+
+**Inspection Pattern (M3/M4/M7):**
+
+- Check `HFSR` (HardFault Status Register) for fault type
+- Check `CFSR` (Configurable Fault Status Register) for detailed cause
+- Check `MMFAR` / `BFAR` for faulting address (if valid)
+- Inspect stack frame: `R0-R3, R12, LR, PC, xPSR`
+
+**Platform Limitations:**
+
+- **M0/M0+**: Limited fault information (no CFSR, MMFAR, BFAR)
+- **M3/M4/M7**: Full fault registers available
+
+**Debug Tip:** Use hardfault handler to capture stack frame and print/log registers before reset.
+
+---
+
+## 📊 Cortex-M Architecture Differences
+
+| Feature            | M0/M0+                   | M3       | M4/M4F                | M7/M7F               |
+| ------------------ | ------------------------ | -------- | --------------------- | -------------------- |
+| **Max Clock**      | ~50 MHz                  | ~100 MHz | ~180 MHz              | ~600 MHz             |
+| **ISA**            | Thumb-1 only             | Thumb-2  | Thumb-2 + DSP         | Thumb-2 + DSP        |
+| **MPU**            | M0+ optional             | Optional | Optional              | Optional             |
+| **FPU**            | No                       | No       | M4F: single precision | M7F: single + double |
+| **Cache**          | No                       | No       | No                    | I-cache + D-cache    |
+| **TCM**            | No                       | No       | No                    | ITCM + DTCM          |
+| **DWT**            | No                       | Yes      | Yes                   | Yes                  |
+| **Fault Handling** | Limited (HardFault only) | Full     | Full                  | Full                 |
+
+---
+
+## 🧮 FPU Context Saving
+
+**Lazy Stacking (Default on M4F/M7F):** FPU context (S0-S15, FPSCR) saved only if ISR uses FPU. Reduces latency for non-FPU ISRs but creates variable timing.
+
+**Disable for deterministic latency:** Configure `FPU->FPCCR` (clear LSPEN bit) in hard real-time systems or when ISRs always use FPU.
+
+---
+
+## 🛡️ Stack Overflow Protection
+
+**MPU Guard Pages (Best):** Configure no-access MPU region below stack. Triggers MemManage fault on M3/M4/M7. Limited on M0/M0+.
+
+**Canary Values (Portable):** Magic value (e.g., `0xDEADBEEF`) at stack bottom, check periodically.
+
+**Watchdog:** Indirect detection via timeout, provides recovery. **Best:** MPU guard pages, else canary + watchdog.
+
+---
+
+## 🔄 Workflow
+
+1. **Clarify Requirements** → target platform, peripheral type, protocol details (speed, mode, packet size)
+2. **Design Driver Skeleton** → constants, structs, compile-time config
+3. **Implement Core** → init(), ISR handlers, buffer logic, user-facing API
+4. **Validate** → example usage + notes on timing, latency, throughput
+5. **Optimize** → suggest DMA, interrupt priorities, or RTOS tasks if needed
+6. **Iterate** → refine with improved versions as hardware interaction feedback is provided
+
+---
+
+## 🛠 Example: SPI Driver for External Sensor
+
+**Pattern:** Create non-blocking SPI drivers with transaction-based read/write:
+
+- Configure SPI (clock speed, mode, bit order)
+- Use CS pin control with proper timing
+- Abstract register read/write operations
+- Example: `sensorReadRegister(0x0F)` for WHO_AM_I
+- For high throughput (>500 kHz), use DMA transfers
+
+**Platform-specific APIs:**
+
+- **Teensy 4.x**: `SPI.beginTransaction(SPISettings(speed, order, mode))` → `SPI.transfer(data)` → `SPI.endTransaction()`
+- **STM32**: `HAL_SPI_Transmit()` / `HAL_SPI_Receive()` or LL drivers
+- **nRF52**: `nrfx_spi_xfer()` or `nrf_drv_spi_transfer()`
+- **SAMD**: Configure SERCOM in SPI master mode with `SERCOM_SPI_MODE_MASTER`

package/skills/asana-automation/SKILL.md

@@ -0,0 +1,171 @@
+---
+name: asana-automation
+description: "Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+---
+
+# Asana Automation via Rube MCP
+
+Automate Asana operations through Composio's Asana toolkit via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Asana connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `asana`
+- 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 `asana`
+3. If connection is not ACTIVE, follow the returned auth link to complete Asana OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Manage Tasks
+
+**When to use**: User wants to create, search, list, or organize tasks
+
+**Tool sequence**:
+1. `ASANA_GET_MULTIPLE_WORKSPACES` - Get workspace ID [Prerequisite]
+2. `ASANA_SEARCH_TASKS_IN_WORKSPACE` - Search tasks [Optional]
+3. `ASANA_GET_TASKS_FROM_A_PROJECT` - List project tasks [Optional]
+4. `ASANA_CREATE_A_TASK` - Create a new task [Optional]
+5. `ASANA_GET_A_TASK` - Get task details [Optional]
+6. `ASANA_CREATE_SUBTASK` - Create a subtask [Optional]
+7. `ASANA_GET_TASK_SUBTASKS` - List subtasks [Optional]
+
+**Key parameters**:
+- `workspace`: Workspace GID (required for search/creation)
+- `projects`: Array of project GIDs to add task to
+- `name`: Task name
+- `notes`: Task description
+- `assignee`: Assignee (user GID or email)
+- `due_on`: Due date (YYYY-MM-DD)
+
+**Pitfalls**:
+- Workspace GID is required for most operations; get it first
+- Task GIDs are returned as strings, not integers
+- Search is workspace-scoped, not project-scoped
+
+### 2. Manage Projects and Sections
+
+**When to use**: User wants to create projects, manage sections, or organize tasks
+
+**Tool sequence**:
+1. `ASANA_GET_WORKSPACE_PROJECTS` - List workspace projects [Optional]
+2. `ASANA_GET_A_PROJECT` - Get project details [Optional]
+3. `ASANA_CREATE_A_PROJECT` - Create a new project [Optional]
+4. `ASANA_GET_SECTIONS_IN_PROJECT` - List sections [Optional]
+5. `ASANA_CREATE_SECTION_IN_PROJECT` - Create a new section [Optional]
+6. `ASANA_ADD_TASK_TO_SECTION` - Move task to section [Optional]
+7. `ASANA_GET_TASKS_FROM_A_SECTION` - List tasks in section [Optional]
+
+**Key parameters**:
+- `project_gid`: Project GID
+- `name`: Project or section name
+- `workspace`: Workspace GID for creation
+- `task`: Task GID for section assignment
+- `section`: Section GID
+
+**Pitfalls**:
+- Projects belong to workspaces; workspace GID is needed for creation
+- Sections are ordered within a project
+- DUPLICATE_PROJECT creates a copy with optional task inclusion
+
+### 3. Manage Teams and Users
+
+**When to use**: User wants to list teams, team members, or workspace users
+
+**Tool sequence**:
+1. `ASANA_GET_TEAMS_IN_WORKSPACE` - List workspace teams [Optional]
+2. `ASANA_GET_USERS_FOR_TEAM` - List team members [Optional]
+3. `ASANA_GET_USERS_FOR_WORKSPACE` - List all workspace users [Optional]
+4. `ASANA_GET_CURRENT_USER` - Get authenticated user [Optional]
+5. `ASANA_GET_MULTIPLE_USERS` - Get multiple user details [Optional]
+
+**Key parameters**:
+- `workspace_gid`: Workspace GID
+- `team_gid`: Team GID
+
+**Pitfalls**:
+- Users are workspace-scoped
+- Team membership requires the team GID
+
+### 4. Parallel Operations
+
+**When to use**: User needs to perform bulk operations efficiently
+
+**Tool sequence**:
+1. `ASANA_SUBMIT_PARALLEL_REQUESTS` - Execute multiple API calls in parallel [Required]
+
+**Key parameters**:
+- `actions`: Array of action objects with method, path, and data
+
+**Pitfalls**:
+- Each action must be a valid Asana API call
+- Failed individual requests do not roll back successful ones
+
+## Common Patterns
+
+### ID Resolution
+
+**Workspace name -> GID**:
+```
+1. Call ASANA_GET_MULTIPLE_WORKSPACES
+2. Find workspace by name
+3. Extract gid field
+```
+
+**Project name -> GID**:
+```
+1. Call ASANA_GET_WORKSPACE_PROJECTS with workspace GID
+2. Find project by name
+3. Extract gid field
+```
+
+### Pagination
+
+- Asana uses cursor-based pagination with `offset` parameter
+- Check for `next_page` in response
+- Pass `offset` from `next_page.offset` for next request
+
+## Known Pitfalls
+
+**GID Format**:
+- All Asana IDs are strings (GIDs), not integers
+- GIDs are globally unique identifiers
+
+**Workspace Scoping**:
+- Most operations require a workspace context
+- Tasks, projects, and users are workspace-scoped
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List workspaces | ASANA_GET_MULTIPLE_WORKSPACES | (none) |
+| Search tasks | ASANA_SEARCH_TASKS_IN_WORKSPACE | workspace, text |
+| Create task | ASANA_CREATE_A_TASK | workspace, name, projects |
+| Get task | ASANA_GET_A_TASK | task_gid |
+| Create subtask | ASANA_CREATE_SUBTASK | parent, name |
+| List subtasks | ASANA_GET_TASK_SUBTASKS | task_gid |
+| Project tasks | ASANA_GET_TASKS_FROM_A_PROJECT | project_gid |
+| List projects | ASANA_GET_WORKSPACE_PROJECTS | workspace |
+| Create project | ASANA_CREATE_A_PROJECT | workspace, name |
+| Get project | ASANA_GET_A_PROJECT | project_gid |
+| Duplicate project | ASANA_DUPLICATE_PROJECT | project_gid |
+| List sections | ASANA_GET_SECTIONS_IN_PROJECT | project_gid |
+| Create section | ASANA_CREATE_SECTION_IN_PROJECT | project_gid, name |
+| Add to section | ASANA_ADD_TASK_TO_SECTION | section, task |
+| Section tasks | ASANA_GET_TASKS_FROM_A_SECTION | section_gid |
+| List teams | ASANA_GET_TEAMS_IN_WORKSPACE | workspace_gid |
+| Team members | ASANA_GET_USERS_FOR_TEAM | team_gid |
+| Workspace users | ASANA_GET_USERS_FOR_WORKSPACE | workspace_gid |
+| Current user | ASANA_GET_CURRENT_USER | (none) |
+| Parallel requests | ASANA_SUBMIT_PARALLEL_REQUESTS | actions |

package/skills/async-python-patterns/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: async-python-patterns
+description: Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-blocking operations.
+---
+
+# Async Python Patterns
+
+Comprehensive guidance for implementing asynchronous Python applications using asyncio, concurrent programming patterns, and async/await for building high-performance, non-blocking systems.
+
+## Use this skill when
+
+- Building async web APIs (FastAPI, aiohttp, Sanic)
+- Implementing concurrent I/O operations (database, file, network)
+- Creating web scrapers with concurrent requests
+- Developing real-time applications (WebSocket servers, chat systems)
+- Processing multiple independent tasks simultaneously
+- Building microservices with async communication
+- Optimizing I/O-bound workloads
+- Implementing async background tasks and queues
+
+## Do not use this skill when
+
+- The workload is CPU-bound with minimal I/O.
+- A simple synchronous script is sufficient.
+- The runtime environment cannot support asyncio/event loop usage.
+
+## Instructions
+
+- Clarify workload characteristics (I/O vs CPU), targets, and runtime constraints.
+- Pick concurrency patterns (tasks, gather, queues, pools) with cancellation rules.
+- Add timeouts, backpressure, and structured error handling.
+- Include testing and debugging guidance for async code paths.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+Refer to `resources/implementation-playbook.md` for detailed patterns and examples.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed patterns and examples.