Overview
Teams lose time when everyone briefs Claude from scratch. This course shows how to give a team a shared starting point: Projects that hold your team’s knowledge and instructions, Artifacts that turn Claude’s output into documents, overviews and simple tools you can edit and share, and Skills that capture a recurring task so it is done the same way every time.
You leave with one working Project and one Skill for your own team, and a plan for rolling shared ways of working out to colleagues.
Who it's for
Any team that wants to share knowledge and recurring ways of working in Claude, whatever the department. It is especially suited to:
- Team leaders and managers
- Operations and administration teams
- Project and programme managers
- HR and learning and development teams
- Knowledge managers
Prerequisites
- Basic experience with Claude or ChatGPT
- No programming knowledge needed
By the end of this course you will be able to
- Set up Claude Projects with team knowledge and clear project instructions
- Share Projects with the right permissions and keep sensitive content apart
- Use Artifacts for documents, overviews and simple tools that colleagues can edit and share
- Create a reusable Skill for a recurring task
- Roll out shared ways of working in a team, with owners and a plan to keep them current
Course outline
Times show the standard running order and can be adjusted when we tailor the course to your team. The trainer stays available during breaks to help anyone finish an exercise.
Welcome & orientation 10 min
The shape of the day and the team challenge you will work on.
The shared toolkit: chat, Projects, Skills and Artifacts 30 min
How the pieces differ and where each belongs: a one-off chat, a Project for ongoing context, a Skill for a repeatable procedure, and an Artifact for something you will edit and share. Where memory fits, and which plans you need.
Try it: Map three recurring tasks from your team to the feature that suits each.
Projects: structure, instructions and knowledge files 50 min
Setting a Project up so it stays useful: a clear scope, project instructions written with GCES (Goal, Context, Expectations, Source), and knowledge files that are well named, current and relevant. How Claude uses your files, including how a large knowledge base is handled.
Try it: Create a Project with instructions and three knowledge files for your team, ask five test questions and tighten the instructions.
Team knowledge in Projects: sharing, permissions and memory 40 min
Sharing a Project with colleagues as viewers or editors, individually or across the organisation, and what owners can switch on or off. How a Project’s memory stays separate from your other work, and keeping sensitive content apart. What cannot be shared, such as chats with content synced from connectors.
Try it: Share your Project with a partner, set “can view” or “can edit”, and have them ask a question from a team member’s point of view.
Artifacts: documents, overviews and simple tools 50 min
Using Artifacts for documents, overviews and simple tools: a team handbook page, a one-page status overview, a checklist or a small interactive tracker. Editing with Claude, exporting to common formats, and sharing within your organisation.
Try it: Create a one-page team overview and a simple tracker as Artifacts, edit one section with Claude, then share them.
Skills: turning recurring tasks into reusable building blocks 50 min
What a Skill is and how it differs from project instructions. The Skills built into Claude for creating Word, Excel, PowerPoint and PDF files, and how Claude chooses a Skill from its description. The anatomy of a custom Skill and how organisation owners make Skills available to a team. Testing, versioning and maintaining Skills in depth is covered in our dedicated Skills course.
Try it: Use a ready-made Skill to turn rough notes into a formatted document, then draft a Skill for one recurring task with Claude’s help.
Rolling out shared ways of working 45 min
A practical rollout plan: who owns each Project and Skill, naming conventions, a review rhythm that keeps knowledge files up to date, and how to bring colleagues on board.
Try it: Draft a one-page rollout plan for your team covering owners, naming, review rhythm and your first three adopters.
Hands-on: one Project and one Skill for your team 60 min
Bring it together on your own team’s work.
• Finish your team Project and test it with five realistic questions.
• Write a Skill for one recurring task and test it on two real cases.
• Share both with a colleague and have them use them without your help.
Close 10 min
Agree what to roll out first and who will own it.
What you'll need
Claude
- A Claude account on a Team or Enterprise plan, which is needed to share Projects and to make Skills available to a team. Individual exercises also work on a Pro or Max plan.
- Code execution and file creation enabled in your settings, which Artifacts and Skills need. On Team and Enterprise plans, an owner enables this in organisation settings.
- Optional: memory enabled by your organisation’s owner, if you want to see how Project memory behaves.
Practice files are provided for every exercise. You are welcome to use your own everyday documents where your organisation's policy allows.