How do I install the Wasp Plugin Init skill?

Run npx skillmds add wasp-lang/wasp-plugin-init in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Wasp Plugin Init safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Wasp Plugin Init?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Wasp Plugin Init free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Wasp Plugin Init?

wasp-lang (@wasp-lang) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Wasp Plugin Init by wasp-lang — Agent Skill

Name: Wasp Plugin Init
Rating: 4.2 (5 reviews)
Author: wasp-lang

File contents

inform the user that this process will give their agent (Claude, Codex, Copilot, etc.) access to knowledge on Wasp's features, commands, workflows, and best practices by importing the general-wasp-knowledge.md file into the user's AGENTS.md or CLAUDE.md file. Use the AskUserQuestion tool (or equivalent) to: a) ask the user if they want to continue, b) ask if they are using Claude Code (CLAUDE.md) or other agents like Codex, Gemini, Copilot, etc. (AGENTS.md).
if the user is using Claude Code, follow the Claude Code memory instructions. If the user is using other agents, follow the Other agents memory instructions.
inform the user that process is complete and they can run /wasp-plugin-help to see the plugin's available skills and features.
recommend the user do the following for the best Wasp development experience with Claude, Codex, Copilot, etc.:
- Start the dev server: Tell it to run the 'start-dev-server' skill to start the Wasp app and give it access to server logs, build errors, and Wasp CLI commands
- Enable Chrome DevTools: Prompt it to use the Chrome DevTools MCP server to give it visibility into browser console logs, network requests, and runtime errors
Explain that together these provide end-to-end insight (backend + frontend) for faster debugging and development.

Claude Code memory

get the plugin version from ${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json (version field). Use it below as {VERSION}.
check if .claude/wasp/.wasp-plugin-initialized-v{VERSION} already exists. If it does, inform the user the plugin is already initialized for this version and skip the remaining steps.
check for any old marker files matching the pattern .wasp-plugin-initialized* in .claude/wasp/. If found, remove them — this is a version upgrade:

rm -f .claude/wasp/.wasp-plugin-initialized*

copy general-wasp-knowledge.md to the user's project root .claude/wasp directory:

mkdir -p .claude/wasp && cp ./general-wasp-knowledge.md .claude/wasp/general-wasp-knowledge.md

if the CLAUDE.md file does not already contain a # Wasp Knowledge section, append it as an import:

# Wasp Knowledge

Wasp knowledge can be found at @.claude/wasp/general-wasp-knowledge.md

create the versioned marker file so the plugin knows this version's init has been run:

touch .claude/wasp/.wasp-plugin-initialized-v{VERSION}

Other agents memory

get the plugin version from ${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json (version field). Use it below as {VERSION}.
if the AGENTS.md file already contains a section starting with # Wasp Knowledge [GENERATED BY WASP, remove that entire section (from the heading to the next # heading or end of file) before adding the new one.
append the entire contents of general-wasp-knowledge.md into the user's AGENTS.md file:
- Append a new section at the end of the file with the title # Wasp Knowledge [GENERATED BY WASP v{VERSION}].
- Copy and paste the contents of general-wasp-knowledge.md into this new section.

---name: wasp-plugin-initdescription: Adds Wasp knowledge, LLM-friendly documentation fetching instructions, and best practices to your project's CLAUDE.md or AGENTS.md file---0. inform the user that this process will give their agent (Claude, Codex, Copilot, etc.) access to knowledge on Wasp's features, commands, workflows, and best practices by importing the [`general-wasp-knowledge.md`](./general-wasp-knowledge.md) file into the user's AGENTS.md or CLAUDE.md file. Use the AskUserQuestion tool (or equivalent) to: a) ask the user if they want to continue, b) ask if they are using Claude Code (CLAUDE.md) or other agents like Codex, Gemini, Copilot, etc. (AGENTS.md).1. if the user is using Claude Code, follow the [Claude Code memory](#claude-code-memory) instructions. If the user is using other agents, follow the [Other agents memory](#other-agents-memory) instructions.2. inform the user that process is complete and they can run `/wasp-plugin-help` to see the plugin's available skills and features.3. recommend the user do the following for the best Wasp development experience with Claude, Codex, Copilot, etc.: - **Start the dev server**: Tell it to run the 'start-dev-server' skill to start the Wasp app and give it access to server logs, build errors, and Wasp CLI commands - **Enable Chrome DevTools**: Prompt it to *`use the Chrome DevTools MCP server`* to give it visibility into browser console logs, network requests, and runtime errors Explain that together these provide end-to-end insight (backend + frontend) for faster debugging and development.## Claude Code memory- get the plugin version from [`${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json`](${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json) (`version` field). Use it below as `{VERSION}`.- check if `.claude/wasp/.wasp-plugin-initialized-v{VERSION}` already exists. If it does, inform the user the plugin is already initialized for this version and skip the remaining steps.- check for any old marker files matching the pattern `.wasp-plugin-initialized*` in `.claude/wasp/`. If found, remove them — this is a version upgrade:```bashrm -f .claude/wasp/.wasp-plugin-initialized*```- copy [`general-wasp-knowledge.md`](./general-wasp-knowledge.md) to the user's project root `.claude/wasp` directory:```bashmkdir -p .claude/wasp && cp ./general-wasp-knowledge.md .claude/wasp/general-wasp-knowledge.md```- if the CLAUDE.md file does not already contain a `# Wasp Knowledge` section, append it as an import:```markdown# Wasp KnowledgeWasp knowledge can be found at @.claude/wasp/general-wasp-knowledge.md```- create the versioned marker file so the plugin knows this version's init has been run:```bashtouch .claude/wasp/.wasp-plugin-initialized-v{VERSION}```## Other agents memory- get the plugin version from [`${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json`](${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json) (`version` field). Use it below as `{VERSION}`.- if the AGENTS.md file already contains a section starting with `# Wasp Knowledge [GENERATED BY WASP`, remove that entire section (from the heading to the next `#` heading or end of file) before adding the new one.- append the entire contents of [`general-wasp-knowledge.md`](./general-wasp-knowledge.md) into the user's AGENTS.md file: - Append a new section at the end of the file with the title `# Wasp Knowledge [GENERATED BY WASP v{VERSION}]`. - Copy and paste the contents of [`general-wasp-knowledge.md`](./general-wasp-knowledge.md) into this new section.

Frequently asked questions