SPEC SKILLS / Install a skill
How to install and use a skill
Updated 17 November 2026
1. Choose your app and package
To work with files on your computer, use Codex with local tools or Claude Code. You need model access, permission to use the project folder and the tools listed in the skill README. Subscriptions and third-party licences are separate. Russian pages provide a Russian package; all other pages provide English. You can request another conversation language in your first message.
2. Find your platform folder
Extract the full archive into a temporary folder. Find codex/<skill-name>/ or claude/<skill-name>/ containing SKILL.md. Copy the complete selected skill folder with its references, scripts and assets, where present. Keep shared installers and root instructions separately and read them before running anything.
3. Install in Codex
For one project, put the skill folder in <project>/.agents/skills/<skill-name>/. For personal use across projects, use ~/.agents/skills/<skill-name>/. On Windows, ~ means your user profile folder. SKILL.md must be directly inside the skill folder. Open the project in Codex. In the CLI and IDE extension, invoke the skill with $skill-name or the /skills menu. If it does not appear, start a new session or restart the app.
4. Install in Claude
In Claude Code, use <project>/.claude/skills/<skill-name>/ or ~/.claude/skills/<skill-name>/. Invoke /skill-name and confirm that the correct SKILL.md is read. For Claude with Skills uploads, go to Customize → Skills → + → Create skill → Upload a skill. Upload the individual Claude skill ZIP rather than the full RU/EN bundle containing both platforms. If no individual ZIP is supplied, zip only the Claude skill folder containing SKILL.md. Availability depends on your account and organisation settings. Uploading a Skill to Claude does not itself grant access to your PC; Windows diagnosis requires tools actually running on that PC.
5. Verify before your first task
Ask the assistant to read SKILL.md and report the skill name, version and tools it can actually use. Compare the name and version with the archive and product page. If the file is missing, fix the path; do not rely on a claim of capability without reading it. Start with a small task and approve a plan before installing programs, deleting files, changing a website or rendering.
6. Update without losing your rules
Download the latest release from its page; verify your purchase first for a paid package. Back up the current skill outside the active skills directory, along with user rules, settings and project materials. Compare the README and changelog, replace the folder and migrate your settings without overwriting new safety rules. Resolve conflicts explicitly. Check the version in a new session; restore your backup if needed.
Folders in the archive
| Skill | Codex | Claude |
|---|---|---|
| Windows PC Care | codex/windows-pc-care/ | claude/windows-pc-care/ |
| WP Site Architect | codex/wp-site-architect/ | claude/wp-site-architect/claude-upload-wp-site-architect-*.zip |
| Editing for YouTube | codex/video-editing-for-youtube-codex.zipcodex/video-story-codex.zip | video-editing-for-youtube-claude.zipvideo-story-claude.zip |
For Editing for YouTube, first extract your platform’s inner ZIP to obtain the video-editing-for-youtube folder with SKILL.md. Video Story is the separate optional video-story folder. The shared toolkit comes in toolkit-4.1.0.zip: extract it, read the README and run the installer check with -CheckOnly first. Review and approve components before installation. Start with “configure the editing skill”, then agree on a 60–90-second sample.
Archive language: English
First request
Read SKILL.md for <skill-name>. Confirm its name, version and tools you can actually use. Communicate in English. Ask essential questions and propose a plan first. Do not install, delete, change the website or render anything until I explicitly approve.
windows-pc-care · wp-site-architect · video-editing-for-youtube · video-story