third-party-middleware

Detect third-party middleware usages and generate CURDX-compatible inventory artifacts.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ForeverWorld/curdx-ralph --skill third-party-middleware
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: third-party-middleware
Source: https://github.com/ForeverWorld/curdx-ralph/tree/main/skills/third-party-middleware
Command: npx skills add https://github.com/ForeverWorld/curdx-ralph --skill third-party-middleware

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Integrating, migrating, or stabilizing external middleware often crosses code and infrastructure boundaries and lacks repeatable, runtime-verified artifacts; this Skill exposes the middleware footprint, defines a single safe integration scope, and enforces verification so teams can close work only with runtime evidence.

Core Features & Use Cases

  • Automated detection: repository scanner identifies middleware mentions and produces a machine-readable inventory for planning.
  • Scoped integration planning: guidance for selecting exactly one integration scope (add, migrate, stabilize) with explicit boundaries and failure policies.
  • CURDX artifact generation & verification: templates and recipes to populate research.md and tasks.md with POC/TDD steps, [VERIFY] checkpoints, VE startup/check/cleanup tasks, and runtime verification commands; useful for registries, caches, MQ, search, auth, and observability integrations.

Quick Start

Run the repository middleware detector and save a report by running the detect_middlewares.py scanner against the project root and writing output to a temporary JSON path.

Frequently Asked Questions about third-party-middleware

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect third-party middleware usages in a codebase for migration planning?

Detect third-party middleware usages by running the repository scanner against the project root to identify mentions and produce a machine-readable inventory for integration planning.

What is runtime-verified middleware integration?

Runtime-verified middleware integration defines a single safe scope, generates CURDX-compatible research and tasks with verification checkpoints, and closes work only with runtime evidence.

How do I plan a scoped registry or cache migration with verification tasks?

Plan a scoped cache or registry migration by selecting exactly one integration scope with explicit boundaries, then generating CURDX artifacts with POC steps and runtime verification commands.

Can I use this middleware detection workflow for observability and message broker components?

Yes, the middleware detection and integration workflow applies to message brokers, search, auth, and observability components within a CURDX workflow to inventory usage and enforce verification.

What's the best way to generate CURDX-compatible research and tasks for middleware stabilization?

Generate CURDX-compatible research and tasks for middleware stabilization by using templates to populate research.md and tasks.md with TDD steps, verification checkpoints, and runtime check tasks.