How do I install the Polpo skill?

Run npx skillmds@latest add lumea-labs/polpo 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 Polpo safe to use?

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

Which AI agents work with Polpo?

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 Polpo free to use?

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

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

Polpo by lumea-labs — Agent Skill

Name: Polpo
Author: lumea-labs

Polpo

Set up, inspect, link, and deploy Polpo projects using the current .polpo directory layout and CLI. Use for project bootstrap, project files, cloud linking, deployment, or deciding whether behavior belongs to Polpo OSS or Polpo Cloud. For agent design, runtime calls, Channels, integrations, or React UI, use the corresponding specialized Polpo skill.

lumea-labs 21fca92 6 files · 9.4 KB Updated Sep 17, 2026

File contents

Polpo Projects

Treat the checked-out project and the installed CLI as authoritative. Do not recreate legacy .polpo/polpo.json or .polpo/agents.json layouts except when explicitly migrating them.

Workflow

Inspect the repository, .polpo/, package.json, and the installed polpo CLI version.
Preserve an existing linked project. Create or link only when the user requests it or no project exists.
Author resources in layout v2: project metadata, one directory per agent, project Loop definitions, teams, skills, and the skill lockfile.
Validate locally before deployment. Resolve unknown references and packaging failures rather than relying on a second identical deploy.
Deploy through the CLI or supported workflow. Never place provider secrets in project files.
Report the project, resources changed, validation performed, and whether anything still requires Cloud provisioning or rollout.

Project Boundaries

OSS owns portable contracts, schemas, runtime behavior, SDKs, CLI behavior, and self-hosted adapters.
Cloud owns managed tenancy, billing, rollout, hosted storage, provider automation, secure credential custody, and managed reconciliation.
A Cloud feature should consume an OSS primitive when the behavior is generally useful to a self-hosted runtime. Do not model portable runtime behavior as dashboard-only configuration.

References

Read references/project-layout.md before creating or migrating .polpo/ files.
Read references/cli-and-deploy.md for bootstrap, linking, validation, deployment, pull, skills, and failure semantics.
Read references/platform-boundaries.md when deciding OSS versus Cloud ownership or diagnosing managed-only behavior.
Read references/contract-version.md before relying on exact fields or commands in a different Polpo release.

Specialized Skills

polpo-agents: agent definitions, models, policies, skills, memory, and sandbox defaults.
polpo-runtime: completions, Sessions, durable runs, Project Loops, steering, and schedules.
polpo-channels: messaging providers, provisioning, routing, media, and trusted identity.
polpo-integrations: Connections, custom tools, hidden bindings, MCP, and OAuth.
polpo-react: React hooks, chat UI, durable reconnect, interactions, and client tools.

---name: polpodescription: Set up, inspect, link, and deploy Polpo projects using the current .polpo directory layout and CLI. Use for project bootstrap, project files, cloud linking, deployment, or deciding whether behavior belongs to Polpo OSS or Polpo Cloud. For agent design, runtime calls, Channels, integrations, or React UI, use the corresponding specialized Polpo skill.---# Polpo ProjectsTreat the checked-out project and the installed CLI as authoritative. Do not recreate legacy`.polpo/polpo.json` or `.polpo/agents.json` layouts except when explicitly migrating them.## Workflow1. Inspect the repository, `.polpo/`, `package.json`, and the installed `polpo` CLI version.2. Preserve an existing linked project. Create or link only when the user requests it or no project exists.3. Author resources in layout v2: project metadata, one directory per agent, project Loop definitions, teams, skills, and the skill lockfile.4. Validate locally before deployment. Resolve unknown references and packaging failures rather than relying on a second identical deploy.5. Deploy through the CLI or supported workflow. Never place provider secrets in project files.6. Report the project, resources changed, validation performed, and whether anything still requires Cloud provisioning or rollout.## Project Boundaries- OSS owns portable contracts, schemas, runtime behavior, SDKs, CLI behavior, and self-hosted adapters.- Cloud owns managed tenancy, billing, rollout, hosted storage, provider automation, secure credential custody, and managed reconciliation.- A Cloud feature should consume an OSS primitive when the behavior is generally useful to a self-hosted runtime. Do not model portable runtime behavior as dashboard-only configuration.## References- Read [references/project-layout.md](references/project-layout.md) before creating or migrating `.polpo/` files.- Read [references/cli-and-deploy.md](references/cli-and-deploy.md) for bootstrap, linking, validation, deployment, pull, skills, and failure semantics.- Read [references/platform-boundaries.md](references/platform-boundaries.md) when deciding OSS versus Cloud ownership or diagnosing managed-only behavior.- Read [references/contract-version.md](references/contract-version.md) before relying on exact fields or commands in a different Polpo release.## Specialized Skills- `polpo-agents`: agent definitions, models, policies, skills, memory, and sandbox defaults.- `polpo-runtime`: completions, Sessions, durable runs, Project Loops, steering, and schedules.- `polpo-channels`: messaging providers, provisioning, routing, media, and trusted identity.- `polpo-integrations`: Connections, custom tools, hidden bindings, MCP, and OAuth.- `polpo-react`: React hooks, chat UI, durable reconnect, interactions, and client tools.

Frequently asked questions