Run any Skill in Manus with one click

$pwd:

vercel-env-vars

Name: Vercel Env Vars
Author: different-ai

// Manage Vercel environment variables for OpenWork projects from the CLI, including linking the local app directory first. Triggers when user mentions: - "add a vercel env var" - "set a vercel env var" - "vercel environment variable"

Run Skill in Manus

$ git log --oneline --stat

stars:51

forks:8

updated:March 23, 2026 at 14:40

File Explorer

3 files

SKILL.md

readonly

name	vercel-env-vars
description	Manage Vercel environment variables for OpenWork projects from the CLI, including linking the local app directory first. Triggers when user mentions: - "add a vercel env var" - "set a vercel env var" - "vercel environment variable"

Quick Usage (Already Configured)

1) Check Vercel access

npx vercel whoami
npx vercel teams ls

2) Link the local app directory to the target project

npx vercel link --yes --scope prologe --project openwork-landing

3) Add an env var to production

npx vercel env add MY_ENV_VAR production --scope prologe --value "value" --yes

4) Add the same env var to preview and development

npx vercel env add MY_ENV_VAR preview "" --scope prologe --value "value" --yes
npx vercel env add MY_ENV_VAR development --scope prologe --value "value" --yes

5) Verify env vars on the linked project

npx vercel env ls production --scope prologe
npx vercel env ls preview --scope prologe
npx vercel env ls development --scope prologe

Never paste real secret values or real production identifiers into this skill. Use placeholders in examples and provide the actual value only at execution time.

OpenWork Defaults

Team scope / team id to use: prologe
Default landing project: openwork-landing
Use the app directory you actually want to affect before linking; for landing this is usually _repos/openwork/ee/apps/landing or the equivalent worktree path.

Common Gotchas

Always point to team id prologe when working on OpenWork Vercel config.
vercel may not be globally installed; npx vercel ... is the safe default.
vercel env ls and vercel env add expect the current directory to be linked to the target project.
For preview env vars across all branches, pass an empty third positional branch argument: preview "".
If Vercel says the codebase is not linked, run npx vercel link --yes --scope prologe --project openwork-landing first.

First-Time Setup (If Not Configured)

Confirm Vercel auth works:

npx vercel whoami

Change into the target app directory.
Link it to the OpenWork project using scope prologe.
Add env vars for the environments you need.
Verify with npx vercel env ls ....

Example: app feedback template id

npx vercel link --yes --scope prologe --project openwork-landing
npx vercel env add LOOPS_TRANSACTIONAL_ID_APP_FEEDBACK production --scope prologe --value "<transactional-id>" --yes
npx vercel env add LOOPS_TRANSACTIONAL_ID_APP_FEEDBACK preview "" --scope prologe --value "<transactional-id>" --yes
npx vercel env add LOOPS_TRANSACTIONAL_ID_APP_FEEDBACK development --scope prologe --value "<transactional-id>" --yes

related-skills.json

same repository

using-openwork-with-chrome-mcp.md

from "different-ai/the-factory"

Drive the OpenWork dev renderer with Chrome MCP and verify workspace UI flows. Triggers when user mentions: - "use Chrome MCP with OpenWork" - "hook up to pnpm dev renderer" - "add an OpenWork workspace through the UI"

2026-05-0651

make-pr.md

from "different-ai/the-factory"

Create a PR with structured evidence: build verification, UI screenshots uploaded to an ephemeral host, API test results, and a verification comment. No screenshots committed to the repo. Triggers when user mentions: - "create a pr" - "make a pr" - "open a pr" - "push and pr"

2026-05-0551

den-test-instructions.md

from "different-ai/the-factory"

Boot up the Den dev stack and the OpenWork desktop app locally, then test common flows like sign-in, dashboard, and telemetry. Triggers when user mentions: - "test den" - "test the app locally" - "boot up den" - "den dev flow" - "test sign in"

2026-05-0551

changelog-release-tracker.md

from "different-ai/the-factory"

Generate or update the internal OpenWork release changelog tracker as plain markdown release sections. Triggers when user mentions: - "generate changelog markdown" - "track this release" - "add a changelog entry"

2026-04-0551

cupid-app-architecture.md

from "different-ai/the-factory"

CUPID app architecture guidance for apps/app/src/app/**

2026-03-2951

update-context-repo-to-latest.md

from "different-ai/the-factory"

Fetch and fast-forward the OpenWork enterprise repo and its subrepos to their latest remote heads when it is safe to do so. Triggers when user mentions: - "get latest changes" - "update context repo to latest" - "pull all subrepos"

2026-03-1751

package.json

"author": "different-ai"

"repository": "different-ai/the-factory"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Network and Computer Systems AdministratorsComputer and Mathematical Occupations15-1244L4

Software DevelopersL4

name	vercel-env-vars
description	Manage Vercel environment variables for OpenWork projects from the CLI, including linking the local app directory first. Triggers when user mentions: - "add a vercel env var" - "set a vercel env var" - "vercel environment variable"

Quick Usage (Already Configured)

1) Check Vercel access

npx vercel whoami
npx vercel teams ls

2) Link the local app directory to the target project

npx vercel link --yes --scope prologe --project openwork-landing

3) Add an env var to production

npx vercel env add MY_ENV_VAR production --scope prologe --value "value" --yes

4) Add the same env var to preview and development

npx vercel env add MY_ENV_VAR preview "" --scope prologe --value "value" --yes
npx vercel env add MY_ENV_VAR development --scope prologe --value "value" --yes

5) Verify env vars on the linked project

npx vercel env ls production --scope prologe
npx vercel env ls preview --scope prologe
npx vercel env ls development --scope prologe

Never paste real secret values or real production identifiers into this skill. Use placeholders in examples and provide the actual value only at execution time.

OpenWork Defaults

Team scope / team id to use: prologe
Default landing project: openwork-landing
Use the app directory you actually want to affect before linking; for landing this is usually _repos/openwork/ee/apps/landing or the equivalent worktree path.

Common Gotchas

Always point to team id prologe when working on OpenWork Vercel config.
vercel may not be globally installed; npx vercel ... is the safe default.
vercel env ls and vercel env add expect the current directory to be linked to the target project.
For preview env vars across all branches, pass an empty third positional branch argument: preview "".
If Vercel says the codebase is not linked, run npx vercel link --yes --scope prologe --project openwork-landing first.

First-Time Setup (If Not Configured)

Confirm Vercel auth works:

npx vercel whoami

Change into the target app directory.
Link it to the OpenWork project using scope prologe.
Add env vars for the environments you need.
Verify with npx vercel env ls ....

Example: app feedback template id

npx vercel link --yes --scope prologe --project openwork-landing
npx vercel env add LOOPS_TRANSACTIONAL_ID_APP_FEEDBACK production --scope prologe --value "<transactional-id>" --yes
npx vercel env add LOOPS_TRANSACTIONAL_ID_APP_FEEDBACK preview "" --scope prologe --value "<transactional-id>" --yes
npx vercel env add LOOPS_TRANSACTIONAL_ID_APP_FEEDBACK development --scope prologe --value "<transactional-id>" --yes

vercel-env-vars

Quick Usage (Already Configured)

1) Check Vercel access

2) Link the local app directory to the target project

3) Add an env var to production

4) Add the same env var to preview and development

5) Verify env vars on the linked project

OpenWork Defaults

Common Gotchas

First-Time Setup (If Not Configured)

Example: app feedback template id

More from this repository

More from this repository

Quick Usage (Already Configured)

1) Check Vercel access

2) Link the local app directory to the target project

3) Add an env var to production

4) Add the same env var to preview and development

5) Verify env vars on the linked project

OpenWork Defaults

Common Gotchas

First-Time Setup (If Not Configured)

Example: app feedback template id