ClaudeProjects, Skills and workflows

Claude Projects, Skills and custom workflows

Most of the value is in the work you repeat. We turn it into Projects (shared instructions and reference files) and Skills (step-by-step procedures Claude loads when needed), then connect them to your systems and automations.

Who it fits

Works on: Any plan; project sharing and organization-wide Skills on Team and Enterprise.

Solo owners and individuals

Get a working setup in one sitting: the right individual plan, your apps connected, a few Projects and Skills for the jobs you repeat every week.

Usual plan: Pro, Max or Ultra
Small teams

One shared workspace with central billing and single sign-on, shared Projects, a short staff workshop and a one-page AI use policy people actually read.

Usual plan: Team
Mid-size companies

Role-based training by department, connectors to your CRM, files and field systems, organization-wide Skills, and usage analytics to see what is being adopted.

Usual plan: Team, or Enterprise when you need SCIM, audit logs or custom retention
Large organizations

A governed rollout: SSO and SCIM, role-based access, audit logs and the Compliance API wired into your controls, a champions network, and Claude Code for engineering.

Usual plan: Enterprise

What we do

  • Make
  • Zapier
  • n8n
  • Finding the repeatable work worth building first: proposals, quotes, reports, replies, onboarding, analysis.
  • Projects with your instructions, examples, templates and reference files.
  • Custom Skills in plain language, with scripts attached where a step needs them.
  • On Team and Enterprise, sharing Projects and deploying Skills to the whole organization.
  • Linking the output to your automations (Make, Zapier or n8n) where a person should not have to copy and paste.
  • A short guide so your people can edit and add Skills themselves.

What you have at the end

  1. 1Projects for each repeatable job
  2. 2A library of Skills your team owns
  3. 3Consistent output across people
  4. 4Fewer copy-and-paste steps

The Claude features this uses

As Anthropic describes them; each card links to the source.

Projects

Workspaces with their own instructions and knowledge files; the Free plan allows up to 5, paid plans include Projects, and Team and Enterprise add project sharing.

Source: claude.com/pricing
Skills

Folders of instructions, scripts and resources that Claude loads when a task needs them, so a repeatable job is done the same way each time.

Source: Claude Help Center
Organization-wide Skills

Owners can provision Skills for the whole organization on Team and Enterprise.

Source: claude.com/pricing

How it runs

The same stages, in this order. For a small business several happen in one session.

  1. 1
    Demo and discovery

    A 15-minute demo on work like yours, then a short conversation about who would use Claude, for what, and with which systems.

  2. 2
    Pick the plan and the first uses

    The plan that fits your size and the two or three jobs that pay back first. Small businesses usually stop here and go straight to setup.

  3. 3
    Set up and connect

    Accounts, and for teams single sign-on and admin settings; connectors and the Business Suite MCP connection; a one-page AI use policy.

  4. 4
    Train on your own work

    Hands-on sessions built from your tasks, with role-based tracks for larger teams and Claude Code sessions for engineers.

  5. 5
    Build Projects, Skills and workflows

    The repeatable work becomes Projects and Skills, connected to your systems and automations where it saves a step.

  6. 6
    Measure and hand over

    What people use and where they get stuck, a library your team owns, and office hours for questions afterwards.

Frequently asked questions

What is the difference between a Project and a Skill?

A Project holds background knowledge that is loaded whenever you chat inside it. A Skill is a procedure for a specific task that Claude loads when the task calls for it, anywhere in Claude, including Claude Code.

Do Skills need code?

No. A simple Skill is instructions written in Markdown. Scripts can be attached for steps that need them.

Can these workflows run without a person?

Some can. Where a step should happen automatically, we connect it to Make, Zapier or n8n, or build it with Claude through the API, and keep a person on the steps that need judgment.

Consultants in a Box is an independent consultancy; this page is ours, not published or reviewed by Anthropic. Claude and Anthropic are trademarks of Anthropic PBC; other names and logos belong to their owners. Plan and feature facts are from Anthropic's pages linked above, reviewed November 6, 2026.

Talk about projects, skills and workflows

Book a 15-minute demo. We will show you Claude on work like yours and the first step that fits your size.

Book a free consultation

Tell us about your team and the software you need help with. We'll follow up to schedule a time to talk.

Open the form on its own page

Talk to a person

The fastest way is to pick a time. Prefer to write? Leave a message and we will email you back, usually the same business day.

Book a free call

By sending this you agree to our Terms and Privacy Policy.