Install marketing skills
for Codex.
Add the complete China marketing workflow library to a Codex project, or install only the skill needed for the current job. This guide separates the repository installer from Codex's official skill discovery paths so the result is easy to inspect and verify.
- HOST
- Codex
- FORMAT
- AGENT SKILLS
- MODULES
- 10 SKILLS
- UPDATED
- 2026-08-09
See every available module before changing the project.
The command below asks this repository's installer to list compatible skills. It is a repository distribution route, not a vendor-owned command. Review the source and stable slugs before choosing all ten modules or one skill.
npx skills add fffffrost/market-skills --listRun the installer from the target project directory.
Install the complete library when you need several connected workflows. For a smaller trial, open a skill detail page and use its --skill command.
npx skills add fffffrost/market-skillsConfirm the files landed where the host looks.
Codex searches project-level .agents/skills directories from the current working directory up through the repository root. User-level skills belong in ~/.agents/skills; administrators can provision /etc/codex/skills.
.agents/skills/<skill-name>/SKILL.md
PROJECT + USER~/.agents/skills/<skill-name>/SKILL.md
PROJECT + USER/etc/codex/skills/<skill-name>/SKILL.md
PROJECT + USERProve the host can see the skill before using live work.
Use the host's manual invocation route, then ask for the skill name, expected inputs, and first safe step. Discovery is not the same as permission: review every tool or connector separately.
- 01
SKILLS MENU
/skills - 02
DIRECT REFERENCE
$skill-name
Use one synthetic or public marketing job.
Start with a narrow task that has known inputs and a reviewable output. The goal is to verify discovery, references, boundaries, and handoffs—not to hand the new method confidential work immediately.
Read SKILL.md and every linked reference or script.
Use public or synthetic materials with no accounts, keys, or client documents.
Compare the result with the skill's stated template and boundaries.
Keep a named owner for claims, approvals, commitments, and external actions.
Use research-competitors for a synthetic China market scenario. Before researching, list the decision, minimum inputs, evidence categories, and human checkpoints. Do not use private data or make current market claims without sources.Check scope, shape, refresh, then permissions.
- 01The skill is outside the project search path
Move it into .agents/skills under the working directory or a parent through the repository root, or use ~/.agents/skills for user scope.
- 02The directory has an extra nesting level
The expected shape is <skill-name>/SKILL.md. Preserve referenced files beside it without wrapping the skill in another directory.
- 03The skill is present but not listed
Restart Codex, then use /skills and inspect the skill's name and description frontmatter.
- 04The skill starts but cannot complete the job
Check the referenced files and required tools. A skill supplies a method; it does not automatically grant file, network, or connector permissions.
Installation questions
01Can I install only one marketing skill?
Yes. Open a skill page and run the command containing --skill and its stable slug.
02Does installation give the skill access to private data?
No. Access depends on the host, enabled tools, connectors, and permissions. Review them independently.
03Should the skill live in the repository?
Use project scope when the team should review and version the method together. Use user scope only for a personally reviewed skill needed across projects.
04How do I update the library?
Review upstream changes first, rerun the installer or replace the directory, and repeat the discovery and safe-test checks.
The method is portable; discovery is host-specific.
Compare the other host paths or return to the general installation and trust guide.