The three install methods in detail
Install prompt, npx command or ZIP: when to pick each, where files go for each resource type, project or user level, and signing the CLI in for paid resources.
Updated on
Installing a PalateKit resource means copying files to the right place. Nothing runs during installation. This article covers the three methods, the destination folders and how paid resources work. For a first guided install, start with Install your first resource.
The three methods
Install prompt
Read https://palatekit.com/en/skills/landing-page-audit/install.md and follow the instructions to install it.
Terminal
npx --yes palatekit@latest install landing-page-audit
ZIP or folder
Download the ZIP from the resource page, unzip it, then put the resource folder in your agent's skills folder.
The install prompt
You paste the sentence into your agent. It reads the resource's install.md file, which gives it the exact command to run for you. This is the simplest method if your agent can read a URL and run commands. The install.md file tells the agent to show you the sign-in code and never to approve the sign-in on your behalf.
The npx command
You run it yourself in a terminal. It needs Node.js 22 or later, on Windows, macOS or Linux. By default a skill goes to the shared folder ~/.agents/skills/. To target a specific agent, add --agent with its name (for example claude-code, codex or cursor). For a folder of your choice, use --target with the path; never combine the two options.
npx --yes palatekit@latest install landing-page-audit --agent claude-code
The ZIP
You download the archive from the resource page and copy the contents yourself. No terminal, and no account for a free resource. It is also the route for work agents (Claude Cowork, for example), which have no local folder: the agent's page names the menu where the ZIP is uploaded.
Which method to pick
| Situation | Method |
|---|---|
| Your agent reads URLs and runs commands | Install prompt |
| You are comfortable in a terminal, or you script things | npx command |
| No Node.js, a work agent, or you want to check everything by hand | ZIP |
| Free resource, no account wanted | ZIP |
Where the files go
The folder depends on the resource type and, for skills, on the agent.
| Type | What the command writes | Next |
|---|---|---|
| Skill | A folder holding a SKILL.md file, in the agent's skills folder | The agent discovers it on its own |
| DESIGN.md | A DESIGN.md file at the project root | Ask the agent to follow it |
| Prompt | A Markdown file in the current folder | Paste it into your conversation |
| Rule, agent, hook | A folder in the project, nothing merged | You add the content to your configuration |
| Motion template | A folder in the current folder | Open it as a project |
Skills, by agent
These folders come from each vendor's documentation:
- Claude Code:
~/.claude/skills/for you,.claude/skills/for the project. - Codex:
~/.agents/skills/for you,.agents/skills/for the project. - Cursor:
~/.agents/skills/or~/.cursor/skills/for you;.agents/skills/or.cursor/skills/for the project.
Each skill is a folder with at least a SKILL.md file. Every agent page in the catalog lists its folders: Claude Code, Codex, Cursor.
DESIGN.md, prompts, templates
Run the command from the folder you want. For a DESIGN.md, that is the project root. If a DESIGN.md already exists, the CLI stops rather than overwrite it; with --force, the old file is moved to ~/.palatekit/backups/. See the DESIGN.md, motion and prompts catalogs.
Rules, agents and hooks
The CLI writes a folder in the project and never edits your existing configuration. You (or your agent, once you agree) move the content where it belongs. In Claude Code, project instructions live in CLAUDE.md or .claude/CLAUDE.md, and topic rules in .claude/rules/. A hook runs commands on your machine, so read it before enabling it. See the rules catalog.
Project or user level
- Project: the files live in the repository, so you can version them and the whole team gets them. Pick it for a DESIGN.md, rules and skills specific to one product.
- User: the files live in your home folder and apply to every project without adding anything to repositories. Pick it for your own working habits.
The shared ~/.agents/skills/ folder is user level. For project level with the CLI, point --target at the project's folder, or copy the ZIP by hand.
Paid resources
Free resources install without an account through the ZIP. Once you use the CLI, or for any paid resource, an account is required:
- Run
npx --yes palatekit@latest login. The CLI prints a code and a link and opens your browser. - Check that the code in the browser matches, then approve the sign-in.
- Confirm with
npx --yes palatekit@latest status.
You sign in once per machine. There is no API key to copy: the CLI keeps its token in the system keyring (on Linux, a Secret Service keyring such as GNOME Keyring or KWallet). If your plan or purchase does not cover the resource, the CLI says so and points to the pricing page. When your agent runs the install, it must show you the code and wait for your approval.
Check the install
Open a new session of your agent and ask for a task the resource covers. If nothing happens, check the destination folder and the folder name: it must match the name declared in SKILL.md. Next: choose an agent.
Sources
Frequently asked questions
Do the three methods give the same result?
Yes: they copy the same files. Only the way they reach the right folder changes.
Do I need to sign in for a paid resource?
Yes. The install prompt and the command both go through the CLI, which signs in to your account once. The ZIP of a paid resource is limited to accounts that have access to it.
Should I install at project or user level?
Project level for what the whole team should find in the repository, user level for your personal tools that apply to every project.