Install the "pave-golden" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/pave-golden into .claude/skills/pave-golden/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pave-golden", 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.
Type 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.
skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill pave-golden -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "pave-golden" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/pave-golden into .agents/skills/pave-golden/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pave-golden", 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.
skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill pave-golden -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "pave-golden" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/pave-golden into .cursor/skills/pave-golden/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pave-golden", 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.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill pave-golden -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "pave-golden" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/pave-golden into .gemini/skills/pave-golden/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pave-golden", 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.
Installs 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).
skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill pave-golden -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "pave-golden" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/pave-golden into .github/skills/pave-golden/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pave-golden", 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.
skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill pave-golden -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "pave-golden" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/pave-golden into .opencode/skills/pave-golden/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pave-golden", 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.
Facts
Skill name
pave-golden
GitHub stars
2.8k
Token cost
~1.6k tokens
SKILL.md length
617 words
Files
2
Skills in repo
3,342
Repo updated
First seen
Licence
MIT
At a glance
Define a golden path — the opinionated, supported way to do a common developer task (create a new service, set up an environment, deploy a feature).
Works in 5 steps: Friction Audit → Define the 90% Case → Write the Golden Path → …
Asked to golden path
SKILL.md covers Step 0: Friction Audit, Step 1: Define the 90% Case, Step 2: Write the Golden Path and Step 3: Validate It, plus 4 more sections
Calls make
What it does
Pave Golden is an agent skill from jeremylongshore/tons-of-skills-marketplace. Define a golden path — the opinionated, supported way to do a common developer task (create a new service, set up an environment, deploy a feature). Produces concrete steps, templates, and tooling. Use when asked to "golden path", "create project template", "scaffold a new service", "how should we create services", or "standardize our setup".
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `.claude-plugin/plugin.json`).
It sits in DevOps & Cloud, covering Platform engineering and Project scaffolding. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Read
Write
Edit
Bash
Glob
Grep
WebFetch
WebSearch
Task
TodoWrite
…and 1 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
make
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Pave Golden loads about 1.6k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 617 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~89
When it runs· the whole SKILL.md, loaded when a task matches
~1.6k
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.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
NoteMentions a .env fileSKILL.md:89
reate db, seed data, copy .env.example → .env
NoteMentions a .env fileSKILL.md:115
d a different database: change DB_URL in .env and docker-compose.yml
NotePre-approves every shell command (allowed-tools: Bash)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.
Download SKILL.mdSave it as .claude/skills/pave-golden/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
pave-golden
description
Define a golden path — the opinionated, supported way to do a common developer task (create a new service, set up an environment, deploy a feature). Produces concrete steps, templates, and tooling. Use when asked to "golden path", "create project template", "scaffold a new service", "how should we create services", or "standardize our setup".
You are Pave — the platform engineer on the Engineering Team.
A golden path is the opinionated, actively maintained, supported way to do X. Not a list of options. Not a strategy doc. A working template with real commands, real files, and clear escape hatches. If a developer can't follow it start-to-finish in under 30 minutes, it's not done.
Step 0: Friction Audit
Before building anything, walk existing path and time it.
Clone a service from scratch. How long to get it running?
Create a new service from scratch. How many steps, how much tribal knowledge?
Deploy a change. What does that journey look like end-to-end?
Check for existing templates, scaffolding, Makefiles, CI configs
Check for existing services — what patterns already exist, even if informal?
Ask: what task does this golden path need to cover? (create-service, setup-env, deploy-feature, add-dependency, etc.) If not given, identify the highest-friction task from the audit.
Step 1: Define the 90% Case
Write down the specific task this golden path addresses:
Task: [e.g., "Create a new backend API service"]
Stack: [e.g., "Python/FastAPI, PostgreSQL, deployed to Fly.io"]
Who does this: [e.g., "Any engineer, ~2x/quarter"]
Current pain: [e.g., "No template — each service is structured differently, setup takes 2 hours"]
Scope ruthlessly. One golden path per task. Don't cover every variation — cover 90% case and document escape hatch for the rest.
Step 2: Write the Golden Path
Produce the following artifacts. Write them, don't describe them.
2a. The Step-by-Step
A numbered sequence a developer can follow without asking anyone:
1. Run: npx create-myapp my-service --template api
(or: cookiecutter gh:org/service-template)
2. cd my-service && make setup
3. make dev → app running at http://localhost:8000
4. make test → test suite passes
5. git push → CI runs, preview deploy created
6. make deploy → ships to production
Every step must:
Be a real command, not a description
Have a success indicator ("you'll see X")
Have a failure note ("if you see Y, run Z")
2b. The Template
Create actual template files. At minimum:
Directory structure:
my-service/
├── Makefile # setup, dev, test, deploy targets
├── README.md # 3-step quickstart at the top
├── .env.example # every variable, with description and example value
├── docker-compose.yml # local dependencies (db, cache, etc.)
├── src/ # application code with a working hello-world
├── tests/ # test setup with one passing example test
└── .github/
└── workflows/
└── ci.yml # lint → test → build → (deploy if main)
Write real file contents, not placeholders. TODO: add your code here is a failed template.
Makefile targets (minimum):
makefile
setup: ## Install deps, create db, seed data, copy .env.example → .env
dev: ## Start app + all dependencies
test: ## Run test suite
lint: ## Run linter + formatter check
deploy: ## Deploy to production (requires ENV=prod or similar)
clean: ## Tear down local environment
## When to go off-path
- Different language/runtime: [link to polyglot guide or process]
- Need a different database: change DB_URL in .env and docker-compose.yml
- Deploying somewhere else: swap the deploy target in Makefile, CI config stays the same
- Monorepo vs polyrepo: [describe the adjustment]
Escape hatches are not failures. They're how you keep golden path from becoming a bureaucratic mandate.
Step 3: Validate It
Golden path is not done until someone has followed it cold:
Clone template into a clean directory
Run make setup — does it succeed without error?
Run make dev — does the app start?
Run make test — do tests pass?
Push to a branch — does CI run and pass?
Onboard a developer who didn't build it — what did they get stuck on?
Fix every point of friction before publishing.
Show full SKILL.md (238 more words)Show less
Step 4: Publish and Measure
Publish:
Link template from team wiki / README
Add make new-service target that runs scaffolding command
Announce with a 2-sentence summary: what it does, how to use it
Measure (30/60/90 days):
How many new services created using template vs off-path?
Did onboarding time change? (baseline it now if you haven't)
What escape hatches are being used most? (signals for next iteration)
A golden path with no adoption data is a guess. A golden path with low adoption is a design bug, not a developer attitude problem.
Output Format
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Summarize:
What task the golden path covers
What files were created or modified
How to use it (the 3-step quickstart)
What to measure over next 30 days
Key Rules
Write template, don't describe it — real files, real commands
One command to set up, one command to run — or path has failed
No TODO placeholders — they're a broken window that discourages use
Match existing tooling — don't introduce new tools without clear reason
Opinionated, not mandatory — always document escape hatch
Measure adoption — if developers aren't using it, fix path, not developers
Delivery
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
Pave Golden 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.
Pave Golden compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Pave Golden this skilljeremylongshore/tons-of-skills-marketplace
This skill should be used when the user wants to "create an agent project", "start a new ADK project", "build me a new agent", "add CI/CD to my project", "add deployment", "enhance my project", or…
Scaffold a ready-made AI agent harness in one command from the 19 published @metaharness/ example packages — 9 host integrations (Claude Code, Codex, Hermes, pi.dev, OpenClaw, RVM, Copilot…
Startup-tailored AWS architecture advice for non-agent workloads, adjusted to the company's stage (pre-revenue through Series B+), team size, runway, and credits.
2.8k GitHub stars~3.7k tokensUpdated yesterday
DevOps & CloudAuto-check passed
More from jeremylongshore/tons-of-skills-marketplace
Define a golden path — the opinionated, supported way to do a common developer task (create a new service, set up an environment, deploy a feature). Pave Golden is an agent skill from jeremylongshore/tons-of-skills-marketplace. Define a golden path — the opinionated, supported way to do a common developer task (create a new service, set up an environment, deploy a feature).
When should I use Pave Golden?
Pave Golden fits situations like: asked to golden path; create project template; scaffold a new service; how should we create services.
How do I install Pave Golden in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill pave-golden -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/skills/pave-golden in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/pave-golden in your project. Claude Code loads it when a task matches its description.
How do I install Pave Golden in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill pave-golden -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/skills/pave-golden in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/pave-golden in your project. Codex loads it when a task matches its description.
Can I use Pave Golden in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill pave-golden -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pave-golden, .gemini/skills/pave-golden, .github/skills/pave-golden and .opencode/skills/pave-golden in your project.
What does Pave Golden need to run?
Going by SKILL.md and its folder, Pave Golden needs the command-line tools its instructions call (make). Our summary lists: Node.js; Docker. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion.
Does Pave Golden access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Pave Golden safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file; pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Pave Golden use?
Pave Golden is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Pave Golden use?
About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Pave Golden?
Skills that share tags, products or a category with Pave Golden: Google Agents CLI Scaffold (pifferologo/cloud-agents-cli, 129 stars), Itemgen Command Builder (microsoft/terraform-provider-fabric, 128 stars), Nx Plugin For AWS (awslabs/nx-plugin-for-aws, 152 stars) and Example Harness (ruvnet/metaharness, 696 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pave Golden?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.