Skills
Skill 20 of 38
Set up Encore Go from scratch. Install the CLI, log in, create an app, check that it runs, and connect Encore’s MCP servers, with a pointer to the skill for each step.
2 minutes · 435 words · 8 sections
Install
npx skills add encoredev/skills --skill encore-go-getting-startednpx skills add encoredev/skills/plugin marketplace add encoredev/skillsThe first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.
This guide is for Encore Go. For Encore.ts, use encore-getting-started. If the user hasn’t said which language they want, ask.
Do the steps in order. Each step says how to tell it worked. If a step fails, load the skill it names.
encore versionencore version v...: go to step 2.encore-install), then go to step 2.Skip this step if the user only wants to run the app locally.
encore auth whoamilogged in as <email>: go to step 3.not logged in.: start encore auth login in the background. Send the user the pairing code and URL it prints, and ask them to approve it in a browser on any device. Wait for Successfully logged in! (encore-login).logged in as app <app-id>, or no person can approve a login (CI): an auth key can’t create apps. Ask the user to create the app in the Cloud Dashboard, then run encore app clone <app-id>, cd into it, and go to step 4.encore app create my-app --example=hello-world
cd my-appSuccessfully created app my-app!: go to step 4.--example=empty instead, and skip step 4.encore-create-app.encore check 'curl /hello/world'"Message": "Hello, world!" and exits 0: go to step 5.encore-run.To keep the app running for the user, start encore run in the background, never in the foreground (encore-run). The API is at http://localhost:4000, and the local development dashboard, with a trace of every request, is at http://localhost:9400.
The MCP servers let you inspect and call the app while you build it, and read its deploys once it’s on Encore Cloud. If the user created the app with --llm-rules=<tool>, the local server may already be configured for that tool: check before adding it again.
Local server: from the app’s root directory, run encore mcp start. It prints MCP stdio Command: encore mcp run --app=<app-id>. Add that command to the user’s tool. In Claude Code:
claude mcp add --transport stdio encore-local -- encore mcp run --app=<app-id>Encore Cloud server (only if you logged in at step 2):
claude mcp add --transport http --scope user encore-cloud https://api.encore.dev/mcpCursor, VS Code, other tools, or an API key instead of signing in: see encore-mcp.
Setup is done. Tell the user:
https://app.encore.dev/<app-id>.encore-cloud, they also need to authenticate it once: in Claude Code, /mcp, select encore-cloud, and choose Authenticate.To build on the app, load the skill for the task. The hello-world app has one service, hello, in hello/.
| To | Load |
|---|---|
| Add endpoints, validation, and errors | encore-go-api |
| Add services or call one service from another | encore-go-service |
| Add a SQL database | encore-go-database |
| Require login on endpoints | encore-go-auth |
| Add Pub/Sub, cron jobs, buckets, secrets, or caching | encore-go-pubsub, encore-go-cron, encore-go-bucket, encore-go-secret, encore-go-cache |
| Write tests | encore-go-testing |
Deploy: commit, then git push encore | encore-deploy |
Set up Encore Go from scratch. Install the CLI, log in, create an app, check that it runs, and connect Encore's MCP servers, with a pointer to the skill for each step. Ends where building starts. Not for architecture or feature questions.
The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.
main, last pushed 26 October 2026.SKILL.md, not by matching a directory convention. One layout observed: encore/*/SKILL.md.h1 and no skipped levels:.claude-plugin/marketplace.json by Encore, declaring 1 plugin. It is read for editorial metadata only — never as the skill index, which is always the repository tree./encoredev/skills.md, and each skill at its own .md URL.