project-name

Extract project names from pyproject.toml or package.json into ${PROJECT_NAME}.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/mesca/claude-plugins --skill project-name
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-name
Source: https://github.com/mesca/claude-plugins/tree/main/plugins/wf/skills/project-name
Command: npx skills add https://github.com/mesca/claude-plugins --skill project-name

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extracts and exposes the project name from root configuration files for downstream use in imports, paths, and documentation, providing ${PROJECT_NAME} where needed.

Core Features & Use Cases

  • Detects project name from pyproject.toml (Python projects) and package.json (Node.js projects).
  • Exposes a normalized form suitable for Python imports and templating.
  • Supports fallback prompts when no name can be determined.

Quick Start

Invoke the skill in a project directory to retrieve ${PROJECT_NAME} and its source (pyproject.toml or package.json).

Frequently Asked Questions about project-name

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

FAQPage Schema
How do I extract the project name from pyproject.toml for Python imports?

You can extract the project name from package.json by using this skill to parse the root configuration file. It automatically detects the Node.js project name and exposes it as the ${PROJECT_NAME} variable for downstream templating and paths.

What happens if no project name is found in root configuration files?

If no project name is found in root configuration files like pyproject.toml or package.json, the skill triggers a user prompt fallback. This interactive fallback ensures you can manually provide the name to be normalized and exposed as ${PROJECT_NAME}.

Can I use one extracted project name for both Python imports and Node.js paths?

Yes, you can use one extracted project name for both Python imports and Node.js paths because the skill normalizes the detected name. It reads from either pyproject.toml or package.json and outputs a standardized ${PROJECT_NAME} for consistent cross-tool usage.

How do I normalize a Python project name for imports and templating?

To normalize a Python project name for imports and templating, this skill extracts the raw name from pyproject.toml and converts it into a normalized form. This standardized output is exposed as ${PROJECT_NAME} for immediate use in downstream tasks.