Land every site-related fix on main, deploy opentraces.ai to Vercel production, and verify it works across all pages (desktop + mobile) and the email-capture flow, fixing and re-deploying until green.
$ npx skills add JayFarei/opentraces --skill deploy-site -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JayFarei/opentraces deploy-site --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/JayFarei/opentraces.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/deploy-site .claude/skills/deploy-site && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "deploy-site" agent skill from https://github.com/JayFarei/opentraces/tree/main/.claude/skills/deploy-site into .claude/skills/deploy-site/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-site", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/JayFarei/opentraces/tree/main/.claude/skills/deploy-siteType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add JayFarei/opentraces --skill deploy-site -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JayFarei/opentraces deploy-site --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JayFarei/opentraces.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/deploy-site .agents/skills/deploy-site && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "deploy-site" agent skill from https://github.com/JayFarei/opentraces/tree/main/.claude/skills/deploy-site into .agents/skills/deploy-site/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-site", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JayFarei/opentraces --skill deploy-site -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JayFarei/opentraces deploy-site --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JayFarei/opentraces.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/deploy-site .cursor/skills/deploy-site && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "deploy-site" agent skill from https://github.com/JayFarei/opentraces/tree/main/.claude/skills/deploy-site into .cursor/skills/deploy-site/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-site", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/JayFarei/opentraces.git --path .claude/skills/deploy-site--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add JayFarei/opentraces --skill deploy-site -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JayFarei/opentraces deploy-site --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JayFarei/opentraces.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/deploy-site .gemini/skills/deploy-site && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "deploy-site" agent skill from https://github.com/JayFarei/opentraces/tree/main/.claude/skills/deploy-site into .gemini/skills/deploy-site/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-site", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install JayFarei/opentraces deploy-siteInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add JayFarei/opentraces --skill deploy-site -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JayFarei/opentraces.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/deploy-site .github/skills/deploy-site && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "deploy-site" agent skill from https://github.com/JayFarei/opentraces/tree/main/.claude/skills/deploy-site into .github/skills/deploy-site/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-site", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JayFarei/opentraces --skill deploy-site -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install JayFarei/opentraces deploy-site --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JayFarei/opentraces.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/deploy-site .opencode/skills/deploy-site && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "deploy-site" agent skill from https://github.com/JayFarei/opentraces/tree/main/.claude/skills/deploy-site into .opencode/skills/deploy-site/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-site", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
deploy-siteLand every site-related fix on main, deploy opentraces.ai to Vercel production, and verify it works across all pages (desktop + mobile) and the email-capture flow, fixing and re-deploying until green.
Deploy Site is an agent skill from JayFarei/opentraces. Land every site-related fix on main, deploy opentraces.ai to Vercel production, and verify it works across all pages (desktop + mobile) and the email-capture flow, fixing and re-deploying until green. Runs as a goal: land - deploy - verify - triage - repeat until safe. Use when the user says "deploy site", "deploy to vercel", "push site", "ship the site", "deploy-site", or "land and verify the site". For a full coordinated release that also bumps the version and publishes the Python packages, use /release-pack…
Its SKILL.md is about 4.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `verify-site-deploy.workflow.js`).
It sits in DevOps & Cloud, covering Deployment. It works with Vercel and Python. The repository describes itself as: A local-first evidence layer for agent work, capturing what the agent sees, does, and changes.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 354755d. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships script files (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
npxgitnpmvercelFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
opentraces.aiFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
WAITLIST_ADMIN_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Deploy Site loads about 4.3k tokens when it runs. Until then it costs about 135 tokens; SKILL.md has 2,143 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 2,143 words (~4,305 tokens).
“Deploy the Next.js marketing site (web/site/) to Vercel production, but treat it as a goal, not a single command: land every site-related fix on main, deploy it, prove it works in production across all pages and the email-capture flow on…”
SKILL.md and 1 other file in .claude/skills/deploy-site of JayFarei/opentraces.
Open the folder on GitHubat commit 354755d
Deploy Site next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Deploy Site this skillJayFarei/opentraces | 100 | — | ~4.3k | Automated safety check: Pass | Custom licence | |
| Memstack Deployment Railway Deploycwinvestments/memstack | 423 | — | ~2.1k | Automated safety check: Pass | Proprietary | |
| Project Toolingalinaqi/maggy | 707 | — | ~2.5k | Automated safety check: Notes | MIT | |
| Deploymentericrisco/rsc-harness | 167 | — | ~4.2k | Automated safety check: Notes | MIT | |
| Vercelremotion-dev/remotion | 62k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| AWS Cdk Developmentzxkane/aws-skills | 367 | 2 repos | ~2.5k | Automated safety check: Pass | MIT |
cwinvestments/memstack
A skill your agent uses when the user says 'deploy to Railway', 'Railway setup', 'railway-deploy', or needs to deploy a Node.js, Python, or Docker application to Railway with environment variables…
alinaqi/maggy
gh, vercel, supabase, render CLI and deployment platform setup
ericrisco/rsc-harness
A skill your agent uses when taking an app from source to live: choosing the deploy target from requirements (Hetzner+Coolify vs Vercel vs a third), then wiring container → CI → registry → host with…
remotion-dev/remotion
Set up a Codex monitor for Vercel deployments and preview URLs.
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
github/awesome-copilot
Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.
JayFarei/opentraces
Generate branded marketing screenshots of opentraces CLI commands — wordmark + CLI card + caption + wallpaper, filename-stamped and auto-copied to the clipboard.
JayFarei/opentraces
Synchronize all documentation surfaces after code changes. An agent skill from JayFarei/opentraces.
JayFarei/opentraces
Sync both git repos in this project: opentraces (root) and closedtraces (kb/).
JayFarei/opentraces
Create a new plan document in kb/plans/ for the opentraces project.
JayFarei/opentraces
Per-commit trace lineage rows for a branch context, deterministic.
JayFarei/opentraces
Derive compact eval rows from command-attributed trace trajectories.
Categories
Land every site-related fix on main, deploy opentraces.ai to Vercel production, and verify it works across all pages (desktop + mobile) and the email-capture flow, fixing and re-deploying until green. Deploy Site is an agent skill from JayFarei/opentraces.ai to Vercel production, and verify it works across all pages (desktop + mobile) and the email-capture flow, fixing and re-deploying until green.
Deploy Site fits situations like: the user says deploy site; deploy to vercel; land and verify the site.
Run `npx skills add JayFarei/opentraces --skill deploy-site -a claude-code`. Or copy the skill folder (.claude/skills/deploy-site in JayFarei/opentraces) into .claude/skills/deploy-site in your project. Claude Code loads it when a task matches its description.
Run `npx skills add JayFarei/opentraces --skill deploy-site -a codex`. Or copy the skill folder (.claude/skills/deploy-site in JayFarei/opentraces) into .agents/skills/deploy-site in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JayFarei/opentraces --skill deploy-site -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deploy-site, .gemini/skills/deploy-site, .github/skills/deploy-site and .opencode/skills/deploy-site in your project.
Going by SKILL.md and its folder, Deploy Site needs JavaScript for the scripts in its folder, the command-line tools its instructions call (npx, git, npm and vercel) and credentials named WAITLIST_ADMIN_TOKEN. Our summary lists: Python 3; Node.js; A credential in WAITLIST_ADMIN_TOKEN.
SKILL.md names 1 domain. In commands or code: opentraces.ai; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Deploy Site has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Deploy Site: Memstack Deployment Railway Deploy (cwinvestments/memstack, 423 stars), Project Tooling (alinaqi/maggy, 707 stars), Deployment (ericrisco/rsc-harness, 167 stars) and Vercel (remotion-dev/remotion, 62k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
JayFarei (a GitHub user) maintains it in JayFarei/opentraces, which has 100 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 6, 2026.
Source: JayFarei/opentraces on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
