L-Pw2c FAQs

Question 1

How does L-Pw2c support team contributions to skills?

Accepted Answer

L-Pw2c promotes extensibility by allowing team leads and contributors to easily add new HealthDev skills to the shared catalog. This process doesn't require modifications to the core CLI architecture, making skill contributions streamlined and efficient.

Question 2

How does L-Pw2c help developers and AI agents?

Accepted Answer

For developers, L-Pw2c allows quick installation, uninstallation, and updates of HealthDev skills. For AI agents and IDEs, its MCP server exposes a local catalog, enabling them to discover, search, and fetch available skills programmatically.

Question 3

Can I integrate L-Pw2c with my IDE?

Accepted Answer

Yes, L-Pw2c is designed to integrate with IDEs like Cursor. Its MCP server provides tools to search, read, and fetch skills, which can be configured within your IDE's settings to access your local skill catalog.

Question 4

Where are skills installed and managed by L-Pw2c?

Accepted Answer

By default, skills are installed into a `.cursor/skills/` directory within your project. L-Pw2c maintains a local index (`state.json`) in `.cursor/l-pw2c/` to efficiently track installed skills, including their versions and metadata.

Question 5

What is L-Pw2c?

Accepted Answer

L-Pw2c is a command-line interface (CLI) and MCP server tool designed to manage and distribute predefined HealthDev skills to AI agents and developers. It simplifies the process of integrating new AI capabilities into local projects.

L-Pw2c

L-Pw2c

Key Features

Use Cases

Key Features

Use Cases