Install marketing skills
for Claude Code.
Install the China marketing library at project or personal scope, review every instruction, and verify the skill with a low-risk task. The repository command is one distribution route; Claude Code's official skill directories remain the source of truth for discovery.
- HOST
- Claude Code
- 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.
Project skills live in .claude/skills and travel with the repository. Personal skills live in ~/.claude/skills and are available across the user's projects. Plugins can also ship skills in their own skills directory.
.claude/skills/<skill-name>/SKILL.md
PROJECT + USER~/.claude/skills/<skill-name>/SKILL.md
PROJECT + USER<plugin>/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
DIRECT INVOCATION
/skill-name - 02
AUTOMATIC
Describe a matching task
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 was installed for the wrong scope
Use .claude/skills for repository-specific behavior or ~/.claude/skills when the same reviewed skill should be available across projects.
- 02SKILL.md is not at the expected level
Confirm the directory shape is <skill-name>/SKILL.md and that linked references keep their relative paths.
- 03A newly created skill is not discovered
Restart Claude Code after creating a new top-level skill directory, then invoke /skill-name or describe the matching task.
- 04The wrong skill activates
Tighten the name and description so the trigger explains both the intended job and the cases that should not use it.
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.