How to Install Your Skills

The same SKILL.md files work across Claude CoWork, Claude Code, and Manus — but each platform has a different install path and invocation method. Pick your platform below.

⚠️

Critical: Claude does not see across sessions or platforms

CoWork and Claude Code are completely isolated from each other. A conversation you had in CoWork is invisible to Claude Code, and vice versa. Each platform starts with a blank slate every session.

Within each platform, individual conversations are also isolated. What Claude learned in your last CoWork chat is gone when you start a new one — unless you have memory features enabled or a CLAUDE.md file loaded.

Skills are the solution to this. A SKILL.md file is context that loads automatically regardless of which session or platform you're in. It's the only reliable way to make Claude behave consistently across sessions. Install your skills everywhere you work — they carry your context so you don't have to repeat yourself.

🖥️

Claude CoWork

Anthropic's desktop app for non-developers. Skills live in a designated folder on your machine and are loaded automatically when their trigger phrases appear in conversation.

No coding required

Download the skills zip from this site

Use the "All skills" or individual board download buttons on the main page. Extract the zip — you'll see folders named after each advisor.

Place the skill folders in the CoWork skills directory

Each advisor folder (containing its SKILL.md) goes inside the user skills path:

# CoWork user skills path
/mnt/skills/user/

# Your folder structure should look like this:
/mnt/skills/user/reid-hoffman-advisor/SKILL.md
/mnt/skills/user/april-dunford-advisor/SKILL.md
/mnt/skills/user/alex-hormozi-advisor/SKILL.md
# ... one folder per advisor

Start a new CoWork session — skills load automatically

CoWork reads the skills directory at the start of each session. You don't need to do anything else. When you use a trigger phrase, the matching skill activates.

Invoke using trigger phrases

Use any of the trigger phrases on the skill cards. CoWork's Claude reads the skill description and activates the right persona automatically.

Example invocations in CoWork

What would Reid say about this? Ask April: how do I position this? Hormozi check on my offer Take this to my strategic board: StoryBrand this:

Remember: Each CoWork conversation is a fresh start. Your previous conversation where you discussed pricing with Chris Do? Claude doesn't remember it in a new session. Your SKILL.md file is what carries continuity — not conversation history.

⌨️

Claude Code

Anthropic's terminal-based coding agent. Skills can be installed globally (available in all your projects) or locally (available only in one project). Also uses CLAUDE.md for persistent memory.

Terminal / CLI

Option A — Global install (recommended for advisor skills)

Create the global skills directory

mkdir -p ~/.claude/skills

Move each advisor folder into the global directory

# One command per advisor — replace paths as needed
mv ~/Downloads/reid-hoffman-advisor ~/.claude/skills/
mv ~/Downloads/april-dunford-advisor ~/.claude/skills/
mv ~/Downloads/alex-hormozi-advisor ~/.claude/skills/

# Or move all at once if extracted to one folder
mv ~/Downloads/skills-public/strategic-board/* ~/.claude/skills/
mv ~/Downloads/skills-public/marketing-board/* ~/.claude/skills/
mv ~/Downloads/skills-public/board-sessions/* ~/.claude/skills/

Verify the install

ls ~/.claude/skills/
# Should show: reid-hoffman-advisor/  april-dunford-advisor/  etc.

Start Claude Code and invoke

claude
# Then type a trigger phrase, or use /skills to see what's loaded
/skills

Option B — Project-specific install

From your project root, create the local skills folder and move skills in

# Run from inside your project folder
mkdir -p .claude/skills
mv ~/Downloads/reid-hoffman-advisor .claude/skills/

# These skills only activate when you run claude from this project

CLAUDE.md — persistent memory across sessions

→

Create a global CLAUDE.md to carry context across every session

CLAUDE.md is a plain text file Claude reads at the start of every session. It's how you get consistent behavior without repeating yourself. Put things here that should always be true: your name, your business, how you like responses formatted, standing instructions.

# Open your global CLAUDE.md in any editor
code ~/.claude/CLAUDE.md

# Or create it from the terminal
touch ~/.claude/CLAUDE.md && nano ~/.claude/CLAUDE.md

Invocations in Claude Code

What would Reid say about /skills Take this to my strategic board: Ask Hormozi: is my offer good enough? StoryBrand this homepage:

Global vs project skills: ~/.claude/skills/ loads in every Claude Code session everywhere on your machine. .claude/skills/ (no tilde) only loads when you run Claude from that specific project folder. Advisor skills belong global — they're about you, not a project.

CoWork ≠ Claude Code context: These are separate products with separate memory. A session in CoWork and a session in Claude Code do not share history. Installing the same SKILL.md files in both is how you get consistent behavior across both.

🤖

Manus

Autonomous AI agent platform. Uses the same Agent Skills Open Standard as Claude — the same SKILL.md files work here. Manus goes further than Claude by executing skills end-to-end in a sandboxed VM, not just guiding you through them.

manus.im

Method 1 — Upload a zip or .skill file (easiest)

Download the skills zip from this site, or use a .skill file

The advisory board skills download as a .zip. Some skills (like Presentation Styles) come as a .skill file — this is Manus's native format, which is also a zip containing a SKILL.md plus bundled reference files and assets. Both formats upload the same way.

In Manus, go to Skills → Upload

Upload the .zip file directly. Manus reads the folder structure and imports each skill automatically. You can also upload individual skill folders.

Invoke with a slash command

# Type / in Manus chat to see your available skills
/reid-hoffman-advisor
/alex-hormozi-advisor
/strategic-advisory-board-session

Method 2 — Import from GitHub

In Manus, go to Skills → Import from GitHub

Paste the GitHub repository URL for the skills cheatsheet. Manus imports the skill folders directly from the repo.

https://github.com/HartfullCo/skills-cheatsheet

Method 3 — Build with Manus (for your own custom skills)

Complete a task you want to repeat

Have Manus do something you'd want to run again — like researching an advisor and building a SKILL.md file.

Tell Manus to package the workflow as a skill

Package this workflow as a Skill.

Manus auto-generates the SKILL.md and bundles any associated scripts. It's saved to your library and available via slash command immediately.

Invocations in Manus

/reid-hoffman-advisor /alex-hormozi-advisor /strategic-advisory-board-session /marketing-advisory-board-session

Manus vs Claude — key difference: Claude reads your skill and guides you. Manus reads your skill and executes it end-to-end in a sandboxed Ubuntu environment. For advisor skills, the behavior is similar. For workflow skills (research, file generation, web scraping), Manus can fully automate the task rather than just describing how to do it.

Feature	Claude CoWork	Claude Code	Manus
Same SKILL.md format	✓	✓	✓
Install path	`/mnt/skills/user/`	`~/.claude/skills/` or `.claude/skills/`	Upload zip / GitHub import / Build with Manus
Invocation	Trigger phrases in conversation	Trigger phrases or `/skill-name`	`/skill-name` slash command
Auto-loads on session start	✓	✓	✓ (once installed)
Persistent memory file	Limited	`~/.claude/CLAUDE.md`	Skill library persists across sessions
Context shared with Claude Code	✗ None	—	✗ None
Context shared with CoWork	—	✗ None	✗ None
Executes code/files autonomously	✗	Via bash tool	✓ Full VM
No-code setup	✓	Needs terminal	✓
Import skills from GitHub	✗	Manual clone	✓ Direct import