How it works.

Everything you need to know to install, use and contribute to the studio's skills — even if you've never touched a Claude skill before.

01What are skills?

A skill is a set of written instructions that teaches Claude how to do something the Futurdigital way — create an invoice, brief you on a project, scaffold a new web app. No code magic: each skill is a folder containing a SKILL.md file with instructions Claude reads when the skill fires.

skills/management/recap/
└── SKILL.md        # instructions + metadata (name, description, mode)

Skills are grouped into a plugin (a versioned bundle), and plugins are distributed through our marketplace — a git repo that Claude Code knows how to install from and keep updated.

Mental model: the marketplace is the app store, a plugin is an app, a skill is a feature inside the app.

02Auto vs manual

Every skill in the catalog has one of two invocation modes — that's the colored badge on each card:

auto

Model-invoked

Claude triggers it by itself when your request matches. Say "where are we on this project?" and /recap fires — no command needed. You can still type it manually.

manual

User-invoked

Only fires when you type the command, e.g. /fd-invoice-new. Used for actions with consequences (creating invoices, sending sprints to clients) where accidental triggering would be bad.

Why not make everything auto? Every auto skill's description sits permanently in Claude's context. Keeping deliberate actions manual keeps Claude fast and focused — and keeps risky operations under your control.

03Installation

You need Claude Code installed and authenticated, plus read access to the Futurdigital GitHub repo. Then, inside any Claude Code session:

# 1. Register the studio marketplace (one time only)
/plugin marketplace add Futurdigital-SA/internal-agentic-skills

# 2. Install the plugins
/plugin install futurdigital-skills@futurdigital
/plugin install futurdigital-admin@futurdigital

# 3. Verify — your new skills should be listed
/help

Cowork users: in the desktop app, add the marketplace from Settings → Plugins, or ask Claude directly: "install the futurdigital-skills plugin".

04Using skills

Two ways, depending on the skill's mode:

Just talk. Auto skills fire on natural language: "recap", "where are we?", "new web project" → Claude picks the right skill.
Type the command. Plugin skills are namespaced: /futurdigital-skills:recap. Type / in Claude Code to browse everything available.

Click any card in the catalog to copy its command to your clipboard.

Pro tip: add this line to a project's CLAUDE.md to get a briefing at the start of every session:

At the start of each session, run the recap skill and show the briefing first.

05Staying up to date

Plugins are versioned. When someone merges a skill change and bumps the version, everyone gets the update — Claude Code checks automatically, or you can force a refresh:

/plugin marketplace update futurdigital

Where	What updates it
This catalog page	Rebuilt automatically on every push (GitHub Actions)
Your installed plugins	`version` bump in the repo + marketplace update

06Adding a skill

Anyone on the team can contribute. The flow:

Create a branch and add your folder: skills/<category>/<skill-name>/SKILL.md
Write the frontmatter — name, description (what it does + when it should trigger), and disable-model-invocation: true if it must stay manual.
Test it locally before pushing: claude --plugin-dir ./futurdigital-skills
Open a PR. One review required — remember, whatever lands on main runs inside everyone's Claude.
After merge: bump the plugin version, and the catalog + everyone's installs pick it up.

Writing good skills: the description is what makes an auto skill trigger reliably — include the exact phrases people would say. Keep instructions short, explain the why, and prefer one skill that does one thing well over a mega-skill.