Share Claude skills and scheduled tasks with your team

Claude already shares skills inside one organization. On Team and Enterprise plans, an owner can provision a skill to everyone from Organization settings, Plugins & skills. Provisioned skills are on by default, also load in Claude Code, and members can publish their own skills to the organization library when the Publishing policy allows it. Enterprise plans can give a set of skills to one group with a plugin.

Scheduled tasks work differently. Claude's scheduled tasks are available on every paid plan and run remotely, even when your computer is asleep. You manage them from your own Scheduled page, which lists the tasks you created, and each run uses your connectors. That suits a personal morning briefing. It is a weaker fit for a weekly report the whole team depends on, because the task, its connectors, and its results sit with one person.

So the split is simple: Claude's organization skills cover the instructions, and a shared workspace covers the recurring work that several people need to see, edit, and keep running.

A Claude skill is a folder with a SKILL.md file, and Type.com skills use the same format, so moving one is a copy, not a rewrite. A scheduled task is a prompt plus a schedule, which maps directly onto a scheduled automation. Plan on about 15 minutes for the first pair.

On Claude Team and Enterprise plans, a Project can be public to your organization or private to invited people. Invited people get Can view or Can edit access. That covers a shared brief, style guide, or reference library well. But the chats inside the Project stay private to whoever started them.

To hand over a specific result, you share a chat snapshot. The link shows the conversation up to the moment you shared it. New messages stay private until you update the share, and attached files and the raw data from MCP tool calls are left out.

Take a common case. A marketer asks Claude to draft a launch email from the brand guide and last quarter's best-performing emails. The draft is good. Now a product manager needs to check the specs, a designer needs the final copy, and next month someone else runs the same play for the next launch.

With snapshots, each handoff is a copy. The reviewer can read the draft but cannot see which emails Claude pulled, cannot ask a follow-up in the same conversation, and has to set up their own connectors to try. By the third launch, the team has five versions of the prompt in five private chat histories.

Run a handoff test on any workflow you care about: can a teammate repeat it next week without messaging the original author? If they need a copied prompt, a re-uploaded file, and their own integrations, the work is shared only on paper.

In Type.com, that shared place is a Space: a shared computer for one team that runs Claude or Codex with the team's connections, skills, memory, threads, and Library. The setup below takes about 20 minutes for a first team.

In the thread above, Nikki asks the Marketing Space for a launch email. Claude uses the team's brand-voice skill and pulls last quarter's emails through the HubSpot connection. Nikki then mentions Marcus, who checks the specs and asks Claude to add a size and save the draft as a document. Nobody copied a prompt or re-uploaded a file.

A few habits make shared threads work well. Switch the composer to Team message when you want to talk to a teammate without invoking Claude, then switch back when you want Claude to act. Open the tool-call details when someone asks where a number came from. Close the thread when the work ships; it stays searchable for the next launch.

Ask Claude to turn finished work into a document or app when people will keep editing it. The document lands in the Space Library, linked to the thread that created it, so the next person sees both the result and how it was made.

A skill is a SKILL.md file with instructions, plus optional examples and scripts. It is the same format Claude Code uses, so a skill you write in Type.com still works outside it. In a Space, skills live under Library, Skills, and anyone can invoke one from the composer by its handle.

The fastest way to write one is from a thread that already worked. Ask Claude to extract the process, then edit the draft like any document. Keep each skill to one job: a launch email skill and a brand voice skill are easier to maintain than one skill that does both.

Skills improve through review. The creator and admins can edit a skill directly; other members propose changes as suggestions that the owner accepts or declines. That keeps one trusted version instead of a dozen private copies.

You don't have to start from zero. The Type.com Skills Library is a public catalog of reviewed skills. Open one to read its instructions and scripts, download it for Claude Code or Codex, or choose Add to Type to put it in your workspace.

A shared workspace should not mean a shared login. In Type.com, a connected Claude subscription is personal: it covers eligible agent turns you start and automations you create. A teammate's requests use their own subscription, or the workspace allowance if they have not connected one.

If your subscription hits its usage limit, Type.com stops the request and offers to switch you to workspace credits. If you accept, it moves you back to your Claude subscription automatically once the limit resets. Admins can see who has Claude connected, and which eligible runs used it, under Settings, Usage, Cost.

Shared does not have to mean open. Type.com's access model works in layers: a Space is public to the workspace or private to the people you add, a single thread can be private to its participants, and documents and apps have their own sharing controls.

AI acts with the effective access of the person and conversation that started the work. It does not gain access to a tool just because that tool is connected somewhere else in the workspace. Connected services still enforce their own permissions on top.

Most teams stall because they try to move everything at once. Start with a single workflow that already runs through Claude and involves at least two people, such as launch emails, customer research summaries, or a weekly report.

Organization skills are a good way to hand everyone the same brand voice, review checklist, or report format. If each person then runs those skills in their own chats, and the only scheduled tasks are individual briefings, there is nothing to move.

Add a shared workspace when a scheduled task has an audience beyond its creator, when it should use a company account rather than one person's connectors, or when part of the team works in Codex or ChatGPT.

A Claude Project is the right tool when the job is to give everyone the same instructions and files. Chat snapshots are the right tool for showing someone a finished answer. A shared workspace is the right tool when several people need to act on the same work, from the same sources, more than once.

For a complete example, see how to automate a weekly team report, which takes a shared workflow and runs it on a schedule.