Skills
The four Entalpa skills: instructions a coding agent loads for one kind of work with Entalpa, from building what the requirements say to keeping OpenSpec or Spec Kit in step.
What a skill is
A skill is a set of written instructions an agent loads when a task calls for it: which tools to use, in what order, and what to leave alone. The MCP server gives the agent its tools; a skill tells it how to use them for one kind of work. Each is a folder with a SKILL.md file, whose description tells the agent when to use it.
The four skills
| Skill | Use it to |
|---|---|
entalpa-implement | Build what a project's stories and requirements describe, and record the work back on each requirement: the code that implements it, its status and its tests. It keeps the links between stories and requirements, and stays away from the tools that delete. |
entalpa-prd | Write a PRD: a readable document of the project for stakeholders, in Markdown and optionally PDF, for the whole project or the subsystems and stories you choose. It reads the project and changes nothing unless you ask. |
entalpa-openspec | Work in a repository that uses OpenSpec: bring its specs into Entalpa, check what Entalpa knows before a change is proposed, and bring Entalpa up to date when a change is archived. OpenSpec's files stay the source of truth. |
entalpa-speckit | Work in a repository that uses GitHub Spec Kit: import its features and fold them into one backlog, check a new feature against it before it is specified, and keep requirement statuses current as tasks are done. Spec Kit's files stay the team's. |
Installing them
Every tool on Connect an agent has an Install Entalpa Skill step with the command for that tool. In Claude Code, the Entalpa plugin installs the server and all four skills together.
An agent starts a skill when a task matches its description. If it does not, ask for the skill by name. The skills are published in entalpa/entalpa-mcp, with the setup guides.