setup-guide
/setup-guide
Guides a person through installing weekpost, account by account, until the first post is live. Use when asked to "set up", "install", "configure weekpost", "doctor failed", "what is left to set up", or in Portuguese "instalar", "configurar", "o doctor falhou", "o que falta configurar".
- Author
- SchulzWill ↗
- Repository
- weekpost ↗
- Licence
- MIT
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 12
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Guides a person through installing weekpost, account by account, until the first post is live. Use when asked to "set up", "install", "configure weekpost", "doctor failed", "what is left to set up", or in Portuguese "instalar", "configurar", "o doctor falhou", "o que falta configurar".
Triggers from the description
Original author description
Guides a person through installing weekpost, account by account, until the first post is live. Use when asked to "set up", "install", "configure weekpost", "doctor failed", "what is left to set up", or in Portuguese "instalar", "configurar", "o doctor falhou", "o que falta configurar".
How it works
- The loop
- Do the slow account first
- Accounts and what to copy
- Order of the commands
- When doctor fails: id to fix
- Finish
- Never
SKILL.md preview
--- name: setup-guide description: Guides a person through installing weekpost, account by account, until the first post is live. Use when asked to "set up", "install", "configure weekpost", "doctor failed", "what is left to set up", or in Portuguese "instalar", "configurar", "o doctor falhou", "o que falta configurar". --- # Set up weekpost, guided You walk a person through the setup. The accounts are theirs and the secrets never pass through you: you read the state, say the next step, print the exact command, and wait for them to run it in their own terminal. A first-timer needs about three hours, most of it creating accounts; the Meta app is the slow one. Read-only commands are yours: `npx weekpost doctor --json` and `npx weekpost setup --plan --json`. Their output holds no secret. Everything that writes is the person's: `setup --apply`, `token`, `first-post`, `wrangler`, `gh auth login`. ## The loop 1. Run `npx weekpost doctor --json` and `npx weekpost setup --plan --json`. 2. Take the first item that is not `ok` (`doctor`: `level` is `fail` before `warn`; `setup --plan`: `state` is `todo`, `needs-you` or `unknown`). Say in one or two sentences what it is and why. 3. If an account or a file is missing, give the account step below. Otherwise give the command in `fix` (doctor) or `commands`/`guide` (plan). 4. Print the exact command for the person to run in their terminal, and stop. Wait for them to say it is done. 5. Run `doctor` again and show what changed: which ids went from fail to ok, and what is next. Go back to step 2. Never make the person type or paste a key, token, password or connection string into this chat. Never ask for one, and if one appears, tell them to rotate it. The values go into the hidden prompts of `setup --apply` and `token`. You do not read `~/.config/weekpost/`. If `doctor` shows `warn` because this shell has no keys (for example `openrouter`), that is expected here: tell the person to run `npx weekpost doctor` in their own terminal for the full picture. ## Do the slow account first Before anything else, tell the person to start the Meta app (step "Meta app" below): the Instagram tester invitation and the app panel take the longest. They can create the Supabase and Cloudflare accounts while it loads. Dashboards rename things; if a label is not on their screen, ask them to look for the closest one. ## Accounts and what to copy Direct links open the dashboard home or the official docs. Do not describe deeper clicks from memory; use the docs link. **GitHub** ([github.com/new](https://github.com/new), [gh auth login](https://cli.github.com/manual/gh_auth_login)) - The content repository must exist on GitHub and be `origin`. The person runs `gh auth login`. - Fixes `logins`, `github.label`, `secrets.actions`, `secrets.environment`. **Supabase** ([dashboard](https://supabase.com/dashboard), [API keys](https://supabase.com/docs/guides/api/api-keys), [connection string](https://supabase.com/docs/guides/database/connecting-to-postgres)) - Create a project on the free plan and save the database password. - Copy three things for the hidden prompts of `setup --apply`: the project URL, the **secret** key (`sb_secret_...`; the publishable key fails `supabase.key`) and the Postgres connection string with the password filled in. - If the network cannot reach the database: `npx weekpost setup --apply --only=db.migrate --print` prints the SQL for the SQL editor. **Cloudflare** ([dashboard](https://dash.cloudflare.com), [wrangler login](https://developers.cloudflare.com/workers/wrangler/commands/)) - Create a free account. Nothing to configure in the dashboard. The person runs `npx wrangler@4 login` and approves in the browser. **OpenRouter** ([keys](https://openrouter.ai/settings/keys)) - Create a key with a credit limit. It goes in the hidden prompt of `setup --apply --only=github.secrets`. **Meta app** ([apps](https://developers.facebook.com/apps), [business portfolios](https://business.facebook.com), [docs](https://developers.facebook.com/docs/instagram-platform/instagram-api-with-unified-login/get-started)) - Needs a professional (Business or Creator) Instagram account they own, a public page for a privacy policy, and a business portfolio. New apps offer only "API setup with Unified login"; creating a portfolio adds about 15 minutes. - Business portfolio: create one (or use theirs) and add the Instagram account to it (Accounts, Instagram accounts). - Create an app with the use case "Manage messaging & content on Instagram"; in that use case's Customize page, connect the business portfolio (the Unified login section appears only then). Set the Privacy Policy URL. - Send the tester invite early (the slow part): App roles, Roles, Add People, Instagram Tester; it stays "Pending" until the person accepts on Instagram (profile settings, Website permissions, Apps and websites, Tester invites). The account must be public. It is the fallback if the Instagram login in Add account does not work. - In the use case's Customize page, API setup with Unified login, Configure your app, Create new configuration: keep "System-user access token" and "Token will never expire" (the template already sets both); edit the permissions down to `instagram_basic`, `instagram_content_publish` and `instagram_manage_insights` (the last is not in Meta's template; it is only for `weekpost metrics`). No ad account, no `ads_*`, no `instagram_manage_comments`; keep `instagram_manage_messages` if Meta does not let them remove it. - Generate access tokens, Add account: the popup asks them to log in to the Instagram account the brand posts from. Then Generate token, picking the portfolio and the account. Meta shows the token once: copy it right away. Leave the app in development mode; Webhooks and App Review are not needed. - Older apps that still show "API setup with Instagram login": add the account as a tester there and generate the token with `instagram_business_basic`, `instagram_business_content_publish` and `instagram_business_manage_insights` (60 days, the Worker renews it). - Then the person runs `npx weekpost token <account>` (the account id from `weekpost.config.ts`), one account at a time. It reads the clipboard; `--prompt` uses a hidden prompt. It detects which login the token is from; for a Unified login token it asks how long it lasts: the answer is `never`. The weekpost repository (https://github.com/SchulzWill/weekpost) has the full steps in `docs/setup.md` and the error table in `docs/troubleshooting.md`. ## Order of the commands The plan lists the order. The usual one: `npx playwright install chromium`, then `npx weekpost setup --apply` (asks before each step; `--only=<step-id>` runs one), then `npx weekpost token <account>`, then `npx weekpost first-post <account>`. ## When `doctor` fails: id to fix The `fix` field of each failing check already holds the command. Use this table to explain it and to know what the person must do first. | Check id | Cause | The person runs | |---|---|---| | `config` | `weekpost.config.ts` does not parse | fix the file, then `npx weekpost check` | | `node` | Node older than 22 | install Node 22 or later | | `chromium` | Playwright browser missing | `npx weekpost setup --apply --only=project.deps` | | `logins` | `gh` or `wrangler` has no session | `gh auth login`, `npx wrangler@4 login` | | `openrouter` | key rejected, or no credit limit | new key with a limit, then `npx weekpost setup --apply --only=github.secrets` | | `supabase.key` | publishable key, or none found | copy the `sb_secret_...` key, then `npx weekpost setup --apply --only=local.secrets` | | `supabase.schema` | migrations not applied | `npx weekpost setup --apply --only=db.migrate` | | `supabase.bucket` | bucket missing | `npx weekpost setup --apply --only=storage.bucket` | | `worker.deployed` | not deployed, or no Cloudflare login | `npx weekpost setup --apply --only=worker.deploy` | | `secrets.worker` | Worker secrets not set | `npx weekpost setup --apply --only=worker.secrets` | | `secrets.actions` | Actions secret not set | `npx weekpost setup --apply --only=github.secrets` | | `secrets.environment` | `weekpost` environment or its secrets missing | `npx weekpost setup --apply --only=github.environment` | | `secrets.local` | local secrets file missing | `npx weekpost setup --apply --only=local.secrets` | | `github.label` | label missing, or `origin` is not on GitHub | push to GitHub, then `npx weekpost setup --apply --only=github.label` | | `github.workflows` | an action is pinned to a tag, not a commit SHA | replace each tag with the full commit SHA | | `token.<account>` | no token, rejected, wrong handle, cannot publish, or expiring | new token with the three permissions of its login (Unified login: `instagram_basic`, `instagram_content_publish`, `instagram_manage_insights`; expiry never), then `npx weekpost token <account>` | | `graph.version` | Graph API version near its end | update weekpost | A `warn` is not a blocker: say what it means and go on. ## Finish When `doctor` exits 0, tell the person to run in their terminal: `npx weekpost first-post <account>`. It publishes a public test post through their own Worker and waits for the link (allow up to 15 minutes, the Worker runs every 5). Ask them for the permalink it prints, confirm the post is public, and remind them they can delete it. Then point to the next skill: "open the week". If `first-post` fails, match the message with the `first-post` rows of the table in `docs/troubleshooting.md` (weekpost repository). ## Never - Ask for, accept or repeat a secret, or read `~/.config/weekpost/`. - Run `setup --apply`, `token`, `first-post`, `enqueue`, `wrangler`, `gh secret`, or any command with `--yes`. - Create an account for the person or click through a dashboard for them.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · SchulzWill/weekpost | 100 | MIT |
| red-hat-ai-innovation-team/training_hub | 100 | Apache-2.0 |
| red-hat-ai-innovation-team/its_hub | 100 | Apache-2.0 |
| red-hat-ai-innovation-team/sdg_hub | 100 | Apache-2.0 |
| Azure/sap-automation-qa | 100 | MIT |
| DojoCodingLabs/remotion-superpowers | 90 | MIT |
Database snapshot: 13.11.2026 · package version 4fff2d4bb30a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100x-use-setup
Zero-knowledge onboarding for x-use that verifies the install, registers the MCP server, then interviews the user to configure their first X account (cookies, niche, keywords, persona). Use when x-use is not yet configured, when adding an account, or when the user asks to get started. - 100queue-status
Shows the publishing queue and helps cancel, reschedule or restore a post. Use when asked for "queue status", "what is scheduled", "a post failed", "cancel post X", "move post X to Friday", "restore post X", or in Portuguese "status da fila", "cancela o post", "adia o post", "o post falhou". - 100setup
Install + verify ax (the agent experience layer). Triggers when the user says "install ax", "set up ax", "ax not found", "ax doctor", "is ax running", "fix ax install", "first-time ax setup", or any setup question about the ax CLI / skills / daemon. Walks the install via the… - 100settings
Configure agent settings — memory backend (builtin/QMD), search mode, temporal decay, citations. Triggers on /agent:settings, "configurar agente", "agent settings", "memory settings", "setup QMD", "configurar QMD", "configurar memoria". - 100curviate-quickstart
The first run: install the Curviate CLI, authenticate this machine with `curviate setup`, confirm with `curviate doctor`, connect a LinkedIn account, and prove the whole path works by reading the same profile live and then from the store. Use when Curviate is being set up for… - 100guide
Open the showreel visual setup guide, or walk the user through installing the plugin's dependencies. Use when the user asks how to set up showreel, install its dependencies, pre-warm the capture motor, install vhs, or says "showreel guide", "setup guide", "como instalar o showreel".