# Can You Use Claude Skills in SharePoint? I Tested Anthropic's Design Skill > A Claude skill runs in SharePoint as a site skill. With Anthropic's frontend design skill added, Copilot built a bright, animated page from a Microsoft List. - URL: https://www.danielanderson.io/articles/claude-skills-in-sharepoint/ - Author: Daniel Anderson, Microsoft MVP (https://www.danielanderson.io/) - Published: 2026-07-06 - Video: https://www.youtube.com/watch?v=wFzl2MDhoVE ## Key takeaways - A Claude skill from Anthropic's public repository can run in SharePoint as a site skill, because both use a folder with a SKILL.md file. - Site skills live in the site's Agent Assets library at Agent Assets/Skills//SKILL.md. - In my test, Copilot in SharePoint called Anthropic's frontend design skill without being told to and built a bright, animated event page from a Microsoft List. - Two runs of nearly the same prompt gave two different page structures, so save the HTML you like rather than regenerating it. - Verdict: worth adding for event and campaign pages, and read every line of a downloaded skill before it goes into Agent Assets. Yes, you can use a Claude skill in SharePoint. A skill from Anthropic's public repository is a folder with a SKILL.md file, the same shape Copilot in SharePoint uses for site skills, so you can add it to your site's Agent Assets library and Copilot will call it when a prompt matches. I tested it with Anthropic's frontend design skill, and the HTML page Copilot built from a plain Microsoft List came out bright, animated and well away from the usual corporate look. Site skills sit at Agent Assets/Skills//SKILL.md, and by default anyone with Edit permission on the site can create one. Adding a downloaded skill takes a few minutes, which your site owners should know their contributors can do too. If you're new to skills, start with [what SharePoint skills are and how to build one](https://www.danielanderson.io/articles/sharepoint-skills/). ## What did I test, and how was it set up? I hear fairly often that skills in SharePoint and Copilot Cowork lack the flair and creativity of Claude's skills. So I went to Anthropic's [skills repository on GitHub](https://github.com/anthropics/skills), downloaded the frontend-design skill and added it to the Agent Assets library of a demo site. The skill tells the model to work like the design lead at a studio and make deliberate choices about palette, typography and layout instead of templated defaults. It's instructions only, with no code. The data was a Microsoft List I use for event planning: the sessions for a conference, with keynotes, workshops, times and categories. The list already had a grid view and some capacity bars I'd set up earlier with Copilot in SharePoint. Then I gave Copilot in SharePoint one prompt, starting "Can you put together a really bright, colourful HTML interactive page I could use for an event page", with a few lines about what the page should cover. ## Did Copilot in SharePoint actually use the Claude skill? It did. While the page was building, the chat showed Copilot calling the front-end design skill, and I never named the skill in my prompt. Asking for a bright, interactive HTML page was enough for Copilot to match the request to the skill's description and load it. ## What did the skill change about the page? The first run produced a playful event landing page built from the list: confetti falling down the screen, a ticker, filter pills for keynotes and workshops, a search box, modal dialog boxes when you open a session, an "at a glance" flow and a picks section. I didn't ask for the confetti, the ticker or any animation. The colours and shapes were nowhere near the blues, greens, whites and rounded corners Copilot usually reaches for. For the second run I added a line asking for balloons or confetti and some animation, and told it to push the boundaries. It came back titled "Playfest Event Sessions", with balloons, confetti and a strong colour scheme, sessions grouped into run sheets under categories like Play, Connect and Create, tabs, times and a reveal for each session's details. This version had no modal dialogs, so nearly the same prompt with the same skill gave a different structure. ## What didn't it do? It isn't repeatable to the pixel. Each run builds a different page, and features from the first run didn't carry into the second. If you need a page people come back to, keep the version you like and edit that, rather than generating a fresh one each time. I also didn't run a control. I don't have the same prompt without the skill side by side, so I can't tell you how much of the result came from the skill and how much from a prompt that asked for bright and colourful. What I can tell you is that the chat showed the skill being called, and the output does what the skill asks for. Site skills can't connect to external systems or run custom code. They work by chaining what Copilot in SharePoint can already do, such as reading lists and building pages. Some skills in Anthropic's repository bundle scripts, and I haven't tested one of those, but I'd expect the script part not to run in SharePoint. Instruction-only skills like frontend-design are the ones to try first. ## Read a downloaded skill before it goes into Agent Assets My verdict is that Claude skills are worth bringing into SharePoint, and this design skill earns its place on the pages where personality helps: event pages, launches, internal campaigns, a social club site, a welcome page for new starters. I wouldn't use it for policies or anything that has to match your brand. For those I'd write a site skill with your own colours, fonts and layout rules, using Anthropic's as the model for how to phrase design direction. [Turning SharePoint policies into interactive HTML pages](https://www.danielanderson.io/articles/sharepoint-html-policy-pages/) shows the kind of page I'd keep plain. The governance side is where I'd slow down. A SKILL.md is plain text, so you can read every line, and you should, because once it's in Agent Assets it becomes instructions Copilot follows for anyone on the site whose prompt matches. Check the licence too. Anthropic ships a LICENSE.txt with each skill, and it travels with the folder. Then decide who gets to add skills. The default is Edit to create a site skill and View to run one, which on a busy team site means every contributor can add instructions. If that's not what you want, break permission inheritance on the Agent Assets library and keep it to site owners, as I set out in [who should own a SharePoint skill](https://www.danielanderson.io/articles/sharepoint-skills/). If you're weighing up where your skills should live in the first place, I built the same assistant both ways in [Claude skills vs Copilot agents](https://www.danielanderson.io/articles/claude-skills-vs-copilot-agents/). For skills that follow you across sites instead of living in one, see [Copilot personal skills in SharePoint and OneDrive](https://www.danielanderson.io/articles/copilot-personal-skills-sharepoint-onedrive/), and for standing site context that isn't a task, [what SHAREPOINT.md does](https://www.danielanderson.io/articles/sharepoint-md/). ## Frequently asked questions **Where do I put a Claude skill in SharePoint?** Upload the whole skill folder, named after the skill with SKILL.md inside, into the Skills folder of the site's Agent Assets library. The library is created automatically with the first site skill and can't be deleted. Give it a few minutes, then start a new Copilot in SharePoint conversation so the skill is picked up. **Will a downloaded skill let Copilot see content I can't?** No. A skill doesn't expand permissions. It can only act on content the person running it can already access, whoever wrote the skill. **How do I know a skill actually ran?** Look for the skill indicator in the Copilot in SharePoint chat. You can also name the skill in your prompt, for example "Run frontend-design on this list", if you want to be sure it's used.