Rift Dynamics — Claude Skills & MCPs

Internal collection of Claude Agent Skills and MCP servers for use across the team. Clone it, install what you need, and Claude will apply our workflows and brand automatically.

Contents

Type	Name	What it does
Skill	rift-dynamics-brand	Applies our fonts, colors, and logos to Word docs, decks, PDFs, and web pages.
MCP	(coming)	Server integrations live in mcps/.

claude_skills_MCPs/
├── skills/
│   └── rift-dynamics-brand/   # brand skill (logos, fonts, templates, instructions)
└── mcps/                      # MCP servers (future)

Get the repo

git clone https://forge.riftdynamics.io/MasterPotato/claude_skills_MCPs.git
cd claude_skills_MCPs

---

Installing a skill

A skill is just a folder with a SKILL.md inside. How you install it depends on where you use Claude. Skills do not sync across surfaces — if you use both Claude.ai and Claude Code, install it in each.

Requires a plan with Skills + code execution enabled (Pro, Max, Team, or Enterprise). On Team/Enterprise an admin must enable Skills for the org first.

Claude.ai / desktop / mobile app

Custom skills are uploaded as a zip in Settings.

1. Zip the skill folder (run from the repo root):

   ./package.sh rift-dynamics-brand
   # produces dist/rift-dynamics-brand.zip
   

   (Or zip skills/rift-dynamics-brand yourself — the zip must contain SKILL.md.)
2. In Claude, go to Settings → Features (Capabilities), enable Skills, and upload the zip under custom skills.
3. Start a new chat and ask for something on-brand. Claude loads the skill when relevant.

Note: custom skills on Claude.ai are per-user — each colleague uploads their own copy. Docs: https://support.claude.com/en/articles/12512198-how-to-create-custom-skills

Claude Code

Skills are filesystem-based. Put the folder where Claude Code looks for skills.

• For everyone on your machine (global):

  mkdir -p ~/.claude/skills
  cp -r skills/rift-dynamics-brand ~/.claude/skills/
  

• For a single project (shared via that repo):

  mkdir -p .claude/skills
  cp -r /path/to/claude_skills_MCPs/skills/rift-dynamics-brand .claude/skills/
  

Claude Code picks up new skills in ~/.claude/skills/ or a project .claude/skills/ within the session (you may need to start a session if the directory didn't exist before). Then just ask — e.g. "Use the rift-dynamics-brand skill to draft a proposal." Docs: https://code.claude.com/docs/en/skills

Claude API

Upload via the Skills API (requires the code-execution and skills betas), then reference the returned skill_id in the container of your Messages requests. The Python SDK has a files_from_dir helper that takes the skill folder directly. Docs: https://platform.claude.com/docs/en/build-with-claude/skills-guide

---

Using the brand skill

You don't call it by name. Ask for the deliverable and Claude applies the brand:

• "Write a one-page proposal for the Lista BVLOS trials, on-brand."
• "Make a 6-slide intro deck for a new supplier."
• "Turn these notes into a branded PDF spec sheet."

See skills/rift-dynamics-brand/README.md for details, defaults, and how to add templates.

---

Contributing / updating

1. Branch, make changes inside the relevant skills/<name>/ folder.
2. If you changed brand values, update both references/brand-spec.md and scripts/brand.py so they stay in sync.
3. Keep SKILL.md accurate — its description is what makes Claude trigger the skill.
4. Commit and push; open a merge request. After merging, colleagues re-pull and re-install (skills don't auto-update once uploaded).

Adding a new skill or MCP

• New skill → skills/<lowercase-hyphenated-name>/SKILL.md (+ assets/references/scripts as needed). Add a row to the Contents table above.
• New MCP → mcps/<name>/ with its own README and setup.

Security

These skills can include scripts Claude may execute. Only install skills from this repo or sources you trust, and review changes in merge requests. Never commit secrets (API keys, passwords) — use MCP connections or environment variables instead.

Licensing

The bundled fonts (Space Mono, Inter) are under the SIL Open Font License; see skills/rift-dynamics-brand/assets/fonts/OFL.txt. Logos and brand assets are property of Rift Dynamics for internal and authorized use.