Install marketing skills
for Cursor.
Add the China marketing workflow library to a shared Agent Skills directory or a Cursor-specific directory. Review the package, verify discovery from the slash menu, and start with a non-sensitive task before connecting live systems.
- HOST
- Cursor
- 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.
Cursor supports project skills in .agents/skills and .cursor/skills, plus matching user-level directories. It can also load compatible skill directories used by Claude Code and Codex, but a shared .agents/skills path keeps the project portable.
.agents/skills/<skill-name>/SKILL.md
PROJECT + USER.cursor/skills/<skill-name>/SKILL.md
PROJECT + USER~/.agents/skills or ~/.cursor/skills
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
/ - 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 project uses a non-discovered folder
Prefer .agents/skills for a shared convention or .cursor/skills for Cursor-specific project scope.
- 02The skill package was flattened
Keep each skill in its own directory with SKILL.md and its referenced files at their original relative paths.
- 03The slash menu has not refreshed
Open a new chat or reload Cursor, then check the supported directory and the skill frontmatter.
- 04Imported instructions conflict
Review project rules, personal rules, and skill instructions together. Remove or narrow only the content you own rather than masking the conflict.
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.