17 ms·

Claude Skills

• j45 1y ago
  I wonder if Claude Skills will help return Claude back to the level of performance it had a few months ago.
• bicx 1y ago
  Interesting. For Claude Code, this seems to have generous overlap with existing practice of having markdown "guides" listed for access in the CLAUDE.md. Maybe skills can simply make managing such guides more organized and declarative.
  • kfarr 1y ago
    Yeah my first thought was, oh it sounds like a bunch of CLAUDE.md's under the surface :P
  • crancher 1y ago
    It's interesting (to me) visualizing all of these techniques as efforts to replicate A* pathfinding through the model's vector space "maze" to find the desired outcome. The potential to "one shot" any request is plausible with the right context.
    • candiddevmike 1y ago
      > The potential to "one shot" any request is plausible with the right context. You too can win a jackpot by spinning the wheel just like these other anecdotal winners. Pay no attention to your dwindling credits every time you do though.
      • NitpickLawyer 1y ago
        On the other hand, our industry has always chased the "one baby in one month out of 9 mothers" paradigm. While you couldn't do that with humans, it's likely you'll soon (tm) be able to do it with agents.
  • j45 1y ago
    If so, it would be a better way than encapsulating functionality in markdown. I have been using claude code to create some and organize them but they can have diminishing return.
  • guluarte 1y ago
    it also may point out that the solution for context rot may not be coming in the foreseeable future
• phildougherty 1y ago
  getting hard to keep up with skills, plugins, marketplaces, connectors, add-ons, yada yada
  • prng2021 1y ago
    Yep. Now I need an AI to help me use AI
    • consumer451 1y ago
      I mean, that is a very common thing that I do.
      • wartywhoa23 1y ago
        That's why the key word for all the AI horror stories that have been emerging lately is "recursion".
        • consumer451 1y ago
          Does that imply no human in the loop? If so, that's not what I meant, or do. Whoever is doing that at this point: bless your heart :)
        • mikkupikku 1y ago
          "Recursion" is a word that shows up a lot in the rants of people in AI psychosis (believe they turned the chatbot into god, or believe the chatbot revealed themselves to be god.)
    • andoando 1y ago
      Train AI to setup/train AI on doing tasks. Bam
    • josefresco 1y ago
      Joking aside, I ask Claude how to uses Claude... all the time! Sometimes I ask ChatGTP about Claude. It actually doesn't work well because they don't imbue these AI tools with any special knowledge about how they work, they seem to rely on public documentation which usually lags behind the breakneck pace of these feature-releases.
• BoredPositron 1y ago
  It is a bit ironic that the better the models get they seem to need more and more user input.
  • quintu5 1y ago
    More like they can better react to user input within their context window. With older models, the value of that additional user input would have been much more limited.
• nozzlegear 1y ago
  It superficially reminds me of the old "Alexa Skills" thing (I'm not even sure if Alexa still has "Skills"). It might just be the name making that connection for me.
  • j45 1y ago
    Seems to be a bit more than that.
  • phildougherty 1y ago
    Alexa skills are 3rd party add-ons/plugins. Want to control your hue lights? add the phillips hue skill. I think claude skills in an alexa world would be like having to seed alexa with a bunch of context for it to remember how to turn my lights on and off or it will randomly attempt a bunch of incorrect ways of doing it until it gets lucky.
  • candiddevmike 1y ago
    And how many of those Alexa Skills are still being updated... This is where waiting for this stuff to stablize/standardize, and then writing a "skill" based on an actual RFC or standard protocol makes more sense, IMO. I've been burned too many times building vendor-locked chatbot extensions.
    • nozzlegear 1y ago
      > And how many of those Alexa Skills are still being updated... Not mine! I made a few when they first opened it up to devs, but I was trying to use Azure Logic Apps (something like that?) at the time which was supremely slow and finicky with F#, and an exercise in frustration.
• joilence 1y ago
  If I understand correctly, looks like `skill` is a instructed usage / pattern of tools, so it saves llm agent's efforts at trial & error of using tools? and it basically just a prompt.
• sshine 1y ago
  I love how the promise of free labor motivates everyone to become API first, document their practices, and plan ahead in writing before coding.
  • ebiester 1y ago
    It helps that you can have the "free" labor document the processes and build the plan.
  • skybrian 1y ago
    Cheaper, not free. Also, no training to learn a new skill. Building a new one that works well is a project, but then it will scale up as much as you like. This is bringing some of the advantages of software development to office tasks, but you give up some things like reliable, deterministic results.
    • sshine 1y ago
      There is an acquisition cost of researching and developing the LLM, but the running cost should not be classified as a wage, hence cost of labor is zero.
      • maigret 1y ago
        It’s still opex for finance
      • skybrian 1y ago
        Don't call it "free labor" at all then? Regardless, running an LLM is usually not free.
        • sshine 1y ago
          I wouldn’t be able to express the embedded irony if I didn’t use this oxymoron. On the one hand, AI doesn’t classify as labor in a traditional sense, even though some aspire to replace labor with AI. On the other hand, if it classified as labor under some new definition, it isn’t free when you consider the external costs of outsourcing basic brain activity, as an individual and as a society.
• _pdp_ 1y ago
  At first I wasn't sure what this is. Upon further inspection skills are effectively a bunch of markdown files and scripts that get unzipped at the right time and used as context. The scripts are executed to get deterministic output. The idea is interesting and something I shall consider for our platform as well.
• nperez 1y ago
  Seems like a more organized way to do the equivalent of a folder full of md files + instructing the LLM to ls that folder and read the ones it needs
  • j45 1y ago
    If so it would be most welcome since LLMs doesn't always consistently follow the folder full of MD files to the same depth and consistency.
    • RamtinJ95 1y ago
      what makes it more likely that claude would read these .md files then?
      • phildougherty 1y ago
        trained to
      • j45 1y ago
        Skills is hopefully put through a deterministic process that is guaranteed to occur, instead of a non-deterministic one that can only ever be guaranteed to happen most of the time (the way it is now).
        • adastra22 1y ago
          It is literally just injecting context into the prompt.
      • adastra22 1y ago
        It includes both the file names and a configurable description string. That’s where you put the TLDR of when to use each skill.
        • j45 1y ago
          This improves it a great deal but at a certain point, maybe 60-80% of the way it can start fading.
• meetpateltech 1y ago
  Detailed engineering blog: "Equipping agents for the real world with Agent Skills" https://www.anthropic.com/engineering/equipping-agents-for-the-real-world-with-agent-skills https://www.anthropic.com/engineering/equipping-agents-for-t...
  • dang 1y ago
    Thanks, we'll put that link in the toptext as well
• jampa 1y ago
  I think this is great. A problem with huge codebases is that CLAUDE.md files become bloated with niche workflows like CI and E2E testing. Combined with MCPs, this pollutes the context window and eventually degrades performance. You get the best of both worlds if you can select tokens by problem rather than by folder. The key question is how effective this will be with tool calling.
• crancher 1y ago
  Seems like the exact same thing, from front page a few days ago: https://github.com/obra/superpowers/tree/main https://github.com/obra/superpowers/tree/main
• Flux159 1y ago
  I wonder how this works with mcpb (renamed from dxt Desktop extensions): https://github.com/anthropics/mcpb https://github.com/anthropics/mcpb Specifically, it looks like skills are a different structure than mcp, but overlap in what they provide? Skills seem to be just markdown file & then scripts (instead of prompts & tool calls defined in MCP?). Question I have is why would I use one over the other?
  • rahimnathwani 1y ago
    One difference I see is that with tool calls the LLM doesn’t see the actual code. It delegates the task to the LLM. With scripts in an agent, I think the agent can see the code being run and can decide to run something different. I may be wrong about this. The documentation says that assets aren’t read into context. It doesn’t say the same about scripts, which is what makes me think the LLM can read them.
• irtemed88 1y ago
  Can someone explain the differences between this and Agents in Claude Code? Logically they seem similar. From my perspective it seems like Skills are more well-defined in their behavior and function?
  • j45 1y ago
    Skills might be used by Agents. Skills can merge together like lego. Agents might be more separated.
  • rahimnathwani 1y ago
    Subagents have their own context. Skills do not.
• ryancnelson 1y ago
  The uptake on Claude-skills seems to have a lot of momentum already! I was fascinated on Tuesday by “Superpowers” , https://blog.fsck.com/2025/10/09/superpowers/ https://blog.fsck.com/2025/10/09/superpowers/ … and then packaged up all the tool-building I’ve been working on for awhile into somewhat tidy skills that i can delegate agents to: http://github.com/ryancnelson/deli-gator http://github.com/ryancnelson/deli-gator I’d love any feedback
  • skinnymuch 1y ago
    Delegation is super cool. I can sometimes end up having too much Linear issue context coming in. IE frequently I want a Linear issue description and last comment retrieved. Linear MCP grabs all comments which pollutes the context and fills it up too much.
• mousetree 1y ago
  I'm perplexed why they would use such a silly example in their demo video (rotating an image of a dog upside down and cropping). Surely they can find more compelling examples of where these skills could be used?
  • alansaber 1y ago
    Dog photo >> informing the consumer
  • Mouvelie 1y ago
    You'd think so, eh ? https://en.wikipedia.org/wiki/The_purpose_of_a_system_is_what_it_does https://en.wikipedia.org/wiki/The_purpose_of_a_system_is_wha...
  • antiloper 1y ago
    The developer page uses a better example, a PDF processing skill: https://github.com/anthropics/skills/tree/main/document-skills/pdf https://github.com/anthropics/skills/tree/main/document-skil... I've been emulating this in claude code by manually @tagging markdown files containing guides for common tasks in our repository. Nice to see that this step is now automatic as well.
  • mritchie712 1y ago
    this is the best example I found https://github.com/anthropics/skills/blob/main/document-skills/xlsx/SKILL.md https://github.com/anthropics/skills/blob/main/document-skil... I was dealing with 2 issues this morning getting Claude to produce a .xlsx that are covered in the doc above
• bgwalter 1y ago
  "Skills are repeatable and customizable instructions that Claude can follow in any chat." We used to call that a programming language. Here, they are presumably repeatable instructions how to generate stolen code or stolen procedures so users have to think even less or not at all.
• azraellzanella 1y ago
  "Keep in mind, this feature gives Claude access to execute code. While powerful, it means being mindful about which skills you use—stick to trusted sources to keep your data safe." Yes, this can only end well.
• m3kw9 1y ago
  I feel like this is making things more complicated than it needs to be. LLMs should automatically do this behind you, you won’t even see it.
• Imnimo 1y ago
  I feel like a danger with this sort of thing is that the capability of the system to use the right skill is limited by the little blurb you give about what the skill is for. Contrast with the way a human learns skills - as we gain experience with a skill, we get better at understanding when it's the right tool for the job. But Claude is always starting from ground zero and skimming your descriptions.
  • j45 1y ago
    LLMs are a probability based calculation, so it will always skim to some degree, and always guess to some degree, and often pick the best choice available to it even though it might not be the best. For folks who this seems elusive for, it's worth learning how the internals actually work, helps a great deal in how to structure things in general, and then over time as the parent comment said, specifically for individual cases.
  • zobzu 1y ago
    IMO this is a context window issue. Humans are pretty good are memorizing super broad context without great accuracy. Sometimes our "recall" function doesn't even work right ("How do you say 'blah' in German again?"), so the more you specialize (say, 10k hours / mastery), the better you are at recalling a specific set of "skills", but perhaps not other skills. On the other hand, LLMs have a programatic context with consistent storage and the ability to have perfect recall, they just don't always generate the expected output in practice as the cost to go through ALL context is prohibitive in terms of power and time. Skills.. or really just context insertion is simply a way to prioritize their output generation manually. LLM "thinking mode" is the same, for what it's worth - it really is just reprioritizing context - so not "starting from scratch" per se. When you start thinking about it that way, it makes sense - and it helps using these tools more effectively too.
    • dwaltrip 1y ago
      There are ways to compensate for lack of “continual learning”, but recognizing that underlying missing piece is important.
    • 1y ago
• fridder 1y ago
  All of these random features is just pushing me further towards model agnostic tools like goose
  • xpe 1y ago
    Thanks for sharing goose. This phase of LLM product development feels a bit like the Tower of Babel days with Cloud services before wrapper tools became popular and more standardization happened.
  • cesarvarela 1y ago
    I wonder how much this affects the model's performance. I imagine Anthropic trains its models to use a generic set of tools, but they can also lean on their specific tool definitions to save the agent from having to guess which tool for what.
• asdev 1y ago
  I wonder what the accuracy is for Claude to always follow a Skill accurately. I've had trouble getting LLMs to follow specific workflows 100% consistently without skipping or missing steps.
  • Yeroc 1y ago
    We also have the same issues with our fellow humans. LLMs do not replace the need for imperative programs that reliably execute well-defined steps. Turn it inside out. Use the LLM to write the imperative program to execute the workflow. Where necessary, insert the LLM into the workflow to perform the task(s) that can't be done imperatively.
• rob 1y ago
  Subagents, plugins, skills, hooks, mcp servers, output styles, memory, extended thinking... seems like a bunch of stuff you can configure in Claude Code that overlap in a lot of areas. Wish they could figure out a way to simplify things.
  • singularity2001 1y ago
    Also the post does not contain a single word how it relates to the very similar agents in claude code. Capabilities, connectors, tasks, apps, custom-gpts, ... the space needs some serious consolidation and standardization! I noticed the general tendency for overlap also when trying to update claude since 3+ methods conflicted with each other (brew, curl, npm, bun, vscode). Might this be the handwriting of AI? ;)
    • kordlessagain 1y ago
      The post is simply "here's a folder with crap in it I may or may not use".
  • CuriouslyC 1y ago
    My agent has handlebars system prompts that you can pass variables at orchestration time. You can cascade imports and such, it's really quite powerful; a few variables can result in radically different system prompt.
• _greim_ 1y ago
  > Developers can also easily create, view, and upgrade skill versions through the Claude Console. For coding in particular, it would be super-nice if they could just live in a standard location in the repo.
  • GregorStocks 1y ago
    Looks like they do: > You can also manually install skills by adding them to ~/.claude/skills.
• deeviant 1y ago
  Basically just rules/workflows from cursor/windsurf, but with a UI.
• pixelpoet 1y ago
  Aside: I really love Anthropic's design language, so beautiful and functional.
  • maigret 1y ago
    Yes and fantastically executed, consistently through all their products and website - desktop, command line, third parties and more.
  • lukev 1y ago
    I agree 100%, except for the logo, which persistently looks like something they... probably did not intend.
    • nozzlegear 1y ago
      I always thought of it as an ink blot. Until now.
    • micromacrofoot 1y ago
      a helpful reminder that these things often speak from their asses
    • exographicskip 1y ago
      First time I saw it I immediately thought of Vonnegut's logo
• jasonthorsness 1y ago
  When the skill is used locally in Claude Code does it still run in a virtual machine? Like some sort of isolation container with the target directory mounted?
• xpe 1y ago
  Better when blastin' Skills by Gang Starr (headphones recommended if at work): https://www.youtube.com/watch?v=Lgmy9qlZElc https://www.youtube.com/watch?v=Lgmy9qlZElc
  • tug2024 1y ago
    [dead]
• 999900000999 1y ago
  Can I just tell it to read the entire Godot source repo as a skill ? Or is there some type of file limit here. Maybe the context windows just aren't there yet, but it would be really awesome if coding agents would stop trying to make up functions.
  • s900mhz 1y ago
    Download the godot docs and tell the skill to use them. It won’t be able to fit the entire docs in the context but that’s not the point. Depending on the task it will search for what it needs
• dearilos 1y ago
  We're trying to solve a similar problem at wispbit - this is an interesting way to do it!
• deleted 1y ago
  [deleted]
• CuriouslyC 1y ago
  Anything the model chooses to use is going to waste context and get utilized poorly. Also, the more skills you have, the worse they're going to be. It's subagents v2. Just use slash commands, they work a lot better.
• just-working 1y ago
  I simply do not care about anything AI now. I have a severe revulsion to it. I miss the before times.
• sega_sai 1y ago
  There seems to be a lot of overlap of this with MCP tools. Also presumably if there are a lot of skills, they will be too big for the context and one would need some way to find the right one. It is unclear how well this approach will scale.
  • rahimnathwani 1y ago
    Anthropic talks about ‘progressive disclosure’. If you have a large number of skills, you could group them into a smaller number of skills each with subskills. That way not all the (sub)skill descriptions need to be loaded into context. For example, instead of having a ‘PDF editing’ skill, you can have a ‘file editing’ skill that, when loaded into context, tells the LLM what type of files it can operate on. And then the LLM can ask for the info about how to do stuff with PDF files.
• guluarte 1y ago
  great! another set of files the models will completely ignore like CLAUDE.md
• simonw 1y ago
  I accidentally leaked the existence of these last Friday, glad they officially exist now! https://simonwillison.net/2025/Oct/10/claude-skills/ https://simonwillison.net/2025/Oct/10/claude-skills/
  • buildbot 1y ago
    "So I fired up a fresh Claude instance (fun fact: Code Interpreter also works in the Claude iOS app now, which it didn't when they first launched) and prompted: Create a zip file of everything in your /mnt/skills folder" It's a fun, terrifying world that this kind of "hack" to exfiltrate data is possible! I hope it does not have full filesystem/bin access, lol. Can it SSH?...
    • antiloper 1y ago
      What's the hack? Instead of typing `zip -r mnt.zip /mnt` into bash, you type `Create a zip file of /mnt` in claude code. It's the same thing running as the same user.
      • tgtweak 1y ago
        Skills run remotely in the llm environment, not locally on your system running claude - worth noting.
        • simonw 1y ago
          If you use skills with Claude Code they run directly on your computer. If you use them inside the Claude.ai or Claude mobile apps they run in a container in the cloud, hosted by Anthropic.
  • skylurk 1y ago
    Woah, Jesse's blog has really come alive lately. Thanks for highlighting this post.
    • dang 1y ago
• sva_ 1y ago
  All this AI, and yet it can't render properly on mobile.
• mikkupikku 1y ago
  I'd love a Skill for effective use of subagents in Claude Code. I'm still struggling with that.
• arjie 1y ago
  It's pretty neat that they're adding these things. In my projects, I have a `bin/claude` subdirectory where I ask it to put scripts etc. that it builds. In the claude.md I then note that it should look there for tools. It does a pretty good job of this. To be honest, the thing I most need are context-management helpers like "start a claude with this set of MCPs, then that set, and so on". Instead right now I have separate subdirectories that I then treat as projects (which are supported as profiles in Claude) which I then launch a `claude` from. The advantage of the `bin/claude` in each of these things is that it functions as a longer-cycle learning thing. My Claude instantly knows how to analyze certain BigQuery datasets and where to find the credentials file and so on. Filesystem as profile manager is not something I thought I'd be doing, but here we are.
  • tomComb 1y ago
    > the thing I most need are context-management helpers like "start a claude with this set of MCPs, then that set, and so on". Isn’t that sub agents?
    • arjie 1y ago
      Ah, in my case, I want to just talk to a video-editing Claude, and then a sys-admin Claude, and so on. I don't want to go through a main Claude who will instantiate these guys. I want to talk to the particular Claudes myself. But if sub-agents work for this, then maybe I just haven't been using them well.
      • adastra22 1y ago
        No, subagents are non interactive.
• deleted 1y ago
  [deleted]
• iyn 1y ago
  Does anyone know how skills relate to subagents? Seems that subagents have more capabilities (e.g. can access the internet) but seems that there's a lot of overlap. I've asked Claude and this it answered this: Skills = Instructions + resources for the current Claude instance (shared context) Subagents = Separate AI instances with isolated contexts that can work in parallel (different context windows) Skills make Claude better at specific tasks. Subagents are like having multiple specialized Claudes working simultaneously on different aspects of a problem. I imagine we can probably compose them, e.g. invoke subagents (to keep separate context) which could use some skills to in the end summarize the findings/provide output, without "polluting" the main context window.
  • lukev 1y ago
    How this reads to me is that a skill is "just" a bundle of prompts, scripts, and files that can be read into context as a unit. Having a sub-agent "execute" a skill makes a lot of sense from a context management, perspective, but I think the way to think about it is that a sub-agent is an "execution-level" construct, whereas a skill is a "data-level" construct.
    • throwup238 1y ago
      Skills can also contain scripts that can be executed in a VM. The Anthropic engineering blog mentions that you can specify in the markdown instructions whether the script should be executed or read into context. One of their examples is a script to extract properties from a PDF file.
• jstummbillig 1y ago
  ELI5: How is a skill different from a tool?
• notepad0x90 1y ago
  Just me or is anthropic doing a lot better of a job at marketing than openai and google?
  • reed1234 1y ago
    It’s much more focused on devs I feel like. Less fluff
• lquist 1y ago
  lol how is this not optimized for mobile
• emadabdulrahim 1y ago
  So skills are basically preset system prompts, assuming different roles etc? Or is there more to it. I'm a little confused.
  • imiric 1y ago
    Right, that's my interpretation as well. "AI" companies have reached the end of the road when it comes to throwing more data and compute at the problem. The only way now for charts to go up and to the right is to deliver value-added services. And, to be fair, there's a potentially long and profitable road by doing good engineering work that was needed anyways. But it should be obvious to anyone within this bubble that this is not the road to "superintelligence" or "AGI". I hope that the hype and false advertising stops soon, so that we can focus on practical applications of this technology, which are numerous.
  • JyB 1y ago
    I'm super confused as well. This seems like exactly that, just some default prompt injections to chose from. I guess I kinda understand them in the context of their claude chat UI product. By I don't understand why it's a thing in Claude Code tho when we already have Claude.md? Could also just point to any .md file in the prompt as preamble but not even needed. https://www.anthropic.com/engineering/claude-code-best-practices https://www.anthropic.com/engineering/claude-code-best-pract... That concept is also already perfectly specd in the MCP standard right? (Although not super used I think?) https://modelcontextprotocol.io/specification/2025-06-18/server/prompts https://modelcontextprotocol.io/specification/2025-06-18/ser...
    • chickensong 1y ago
      Claude.md gets read every time and eats context, while it sounds like the skills are read as-needed, saving context.
  • pollinations 1y ago
    Plus executable.xode snippets. I think their actual source code doesn't use context. But feels like function calling packaged.
• mercurialsolo 1y ago
  Sub agents, mcp, skills - wonder how are they supposed to interact with each other? Feels like fair bit of overlap here. It's ok to proceed in a direction where you are upgrading the spec and enabling claude wth additional capabilities. But one can pretty much use any of these approaches and end up with the same capability for an agent. Right now feels like a ux upgrade from mcp where you need a json but instead can use a markdown in a file / folder and provide multi-modal inputs.
  • JyB 1y ago
    Claude Skills just seem to be the same as MCP prompts: https://modelcontextprotocol.io/specification/2025-06-18/server/prompts https://modelcontextprotocol.io/specification/2025-06-18/ser... I don't really see why they had to create a different concept. Maybe makes sense "marketing-wise" for their chat UI, but in Claude Code? Especially when CLAUDE.md is a thing?
    • datadrivenangel 1y ago
      Yeah how is this different from MCP prompts?
    • pizza 1y ago
      Narrowly focused semantics/affordances (for both LLM and users/future package managers/communities, ease of redistribution and context management: - skills are plain files that are injected contextually whereas prompts would come w the overhead of live, running code that has to be installed just right into your particular env, to provide a whole mcp server. Tbh prompts also seem to be more about literal prompting, too - you could have a thousand skills folders for different softwares etc but good luck with having more than a few mcp servers that are loaded into context w/o it clobbering the context
    • jjfoooo4 1y ago
      I see this as a lower overhead replacement for MCP. Rather than managing a bunch of MCP's, use the directory structure to your advantage, leverage the OS's capability to execute
• deleted 1y ago
  [deleted]
• fny 1y ago
  I fear the conceptual churn we're going to endure in the coming years will rival frontend dev. Across ChatGPT and Claude we now have tools, functions, skills, agents, subagents, commands, and apps, and there's a metastasizing complex of vibe frameworks feeding on this mess.
  • hkt 1y ago
    The same thing will happen: skilled people will do one thing well. I've zero interest in anything but Claude code in a dev container and, while mindful of the lethal trifecta, will give Claude as much access to a local dev environment and it's associated tooling as I would give to a junior developer.
  • LPisGood 1y ago
    Metastasizing is such an excellent way to describe this phenomenon. They grow on top of each other.
  • mathattack 1y ago
    There's so much white space - this is the cost of a brand new technology. Similar issues with figuring out what cloud tools to use, or what python libraries are most relevant. This is also why not everyone is an early adopter. There are mental costs involved in staying on top of everything.
    • benterix 1y ago
      > This is also why not everyone is an early adopter. Usually, there are relatively few adopters of a new technology. But with LLMs, it's quite the opposite: there was a huge number of early adopters. Some got extremely excited and run hundreds of agents all the time, some got burned and went back to the good old ways of doing things, whereas the majority is just using LLMs from time to time for various tasks, bigger of smaller.
      • a4isms 1y ago
        I follow your reasoning. If we just look at businesses, and we include every business that pays money for AI and one or more employees use AI to do their their jobs, then we're in the Early Majority phase, not the Innovator or Early Adopter phases. https://en.wikipedia.org/wiki/Technology_adoption_life_cycle https://en.wikipedia.org/wiki/Technology_adoption_life_cycle
• josefresco 1y ago
  I just used tested the canvas-design skill and the results were pretty awful. This is the skill description: Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. What it created was an abstract art museum-esque poster with random shapes and no discernable message. It may have been trying to design a playing card but just failed miserably which is my experience with most AI image generators. It certainly spent a lot of time, and effort to create the poster. It asked initial questions, developed a plan, did research, created tooling - seems like a waste of "tokens" given how simple and lame the resulting image turned out. Also after testing I still don't know how to "use" one of these skills in an actual chat.
  • taejavu 1y ago
    If you want to generate images, use Midjourney or whatever. It’s almost like you’ve deliberately missed the point of the feature.
• jedisct1 1y ago
  Too many options, this is getting very confusing. Roo Code just has "modes", and honestly, this is more than enough.
• rohan_ 1y ago
  Cursor launched this a while ago with "Cursor Rules"
• radley 1y ago
  It will be interesting to see how this is structured. I was already doing something similar with Claude Projects & Instructions, MCP, and Obsidian. I'm hoping that Skills can cascade (from general to specific) and/or be combined between projects.
• datadrivenangel 1y ago
  So sort of like MCP prompt templates except not prompt templates?
• laurentiurad 1y ago
  AGI nowhere near
  • skylurk 1y ago
    I know I'm replying to a shitpost. But I had a realisation, and I'm probably not the only one. If you can manage to keep structuring slightly intelligent tools so that they compound, seems like AGI is achievable. That's why the thing everyone is after right now is new ways to make those slight intelligences keep compounding. Just like repeated multiplication of 1.001 grows indefinitely.
    • gigatree 1y ago
      But how often can you repeat the multiplication when the repetitions are unsustainable?
      • skylurk 1y ago
        Yeah, sometimes it feels like we're just layering unintelligent things, with compounding unintelligence... But starting earlier this year, I've started to see glimpses of what seems like intelligence (to me) in the tools, so who knows.
        • laurentiurad 1y ago
          things like being able to say how many R's are in strawberry
    • Lionga 1y ago
      I know I'm replying to a shitpost. Well enough said.
      • laurentiurad 1y ago
        do you feel the agi?
    • 1y ago
• robwwilliams 1y ago
  Could be helpful. I often edit scientific papers and grant applications. Orienting Claude on the frontend of each project works but an “Editing Skill” set could be more general and make interactions with Claude more clued in to goals instead of starting stateless.
• mercurialsolo 1y ago
  One sharp contrast though I see between OpenAI and Anthropic is the product extensions are built around their flagship products. OpenAI ships extensions for ChatGPT - that feed more to plug into the consumer experience. Anthropic ships extensions (made for builders) into ClaudeCode - feel more DX.
  • sumedh 1y ago
    Anthropic is making more money from enterprise while ChatGpt's target market is the consumer.
• corytheboyd 1y ago
  I’ll give it a fair go, but how is it not going to have the same problem of _maybe_ using MCP tools? The same problem of trying to add to your prompt “only answer if you are 100% correct”? A skill just sounds like more markdown that is fed into context, but with a cool name that sounds impressive, and some indexing of the defined skills on start (same as MCP tools?)
• butlike 1y ago
  Great, so now I can script the IDE...err, I mean LLM. I can't help but feel like we've been here before, and the magic is wearing thin.
• gloosx 1y ago
  wow, this news post layout is not fitting the screen on mobile... Couldnt these 10x programmers vibecode a proper mobile version?
• thorio 1y ago
  How about using some of that skills to make that page mobile ready...
• I_am_tiberius 1y ago
  Every release of these companies makes me angry because I know they take advantage of all the people who release content to the public. They just consume and take the profit. In addition to that Anthropic has shown that they don't care about our privacy AT ALL.
• mercurialsolo 1y ago
  The way this is headed - I also see a burgeoning class of tools emerging. MCP servers, Skill managers, Sub-Agent builders. Feels like the patterns and protocols need more explainability to how they synthesize into a practical dev (extension) toolkit which is useful across multiple surfaces e.g. chat vs coding vs media gen.
• actinium226 1y ago
  It's an interesting idea (among many) to try to address the problem of LLMs getting off task, but I notice that there's no evaluation in the blog post. Like, ok cool, you've added "skills," but is there any evidence that they're useful or are we just grasping at straws here?
• titzer 1y ago
  While not generally a bad idea, I find it amusing that they are reinventing shared libraries where the code format is...English. So the obvious next step is "precompiling" skills to a form that is better for Claude internally. ...which would be great if the (likely binary) format of that was used internally, but something tells me an architectural screwup will lead to leaking the binaries and we'll have a dependency on a dumb inscrutable binary format to carry forward...
• tgtweak 1y ago
  At term (and not even far term) - LLMs will be able to churn up their own "skills" using their sandbox code environments - and possibly recycle them through context on a per-user basis. While I like the flexibility of deploying your own skills to claude for use org-wide, this really feels like what MCP should be for that use case, or what built-in analysis sandbox should be. We haven't even gone mainstream with MCP and there are already 10 stand-ins doing roughly the same thing with a different twist. I would have honestly preferred they called this embedded MCP instead of 'skills'.
• _pdp_ 1y ago
  I predict there will be some sort of package manager opensource project soon. Download skills from some 3rd-party website and run inside Claude. Risks of supply chain issue will be obvious but nobody will care - at least not in the short term.
  • FrostKiwi 1y ago
    They already have the Plugin Marketplace [1]. It's all too much of a fast moving target for something as rigid as a package manager I think. Open source projects for now will be limited to Awesome-* collections [2] [1] https://docs.claude.com/en/docs/claude-code/plugin-marketplaces https://docs.claude.com/en/docs/claude-code/plugin-marketpla... [2] https://github.com/hesreallyhim/awesome-claude-code https://github.com/hesreallyhim/awesome-claude-code
  • waldir 1y ago
    They've already started a public repository here: https://github.com/anthropics/skills https://github.com/anthropics/skills (It's the last link in the "Getting started" section of the post.)
• nextworddev 1y ago
  What is this, tools for Claude web app?
• XCSme 1y ago
  Isn't this just RAG?
• jrh3 1y ago
  The tools I build for Claude Code keep reducing back to just using Claude Code and watching Anthropic add what I need. This is my tool for brownfield projects with Claude Code. I added skills based on https://blog.fsck.com/2025/10/09/superpowers/ https://blog.fsck.com/2025/10/09/superpowers/ https://github.com/RossH3/context-tree https://github.com/RossH3/context-tree - Helps Claude and humans understand complex brownfield codebases through maintained context trees.
• simonw 1y ago
  Just published this about skills: "Claude Skills are awesome, maybe a bigger deal than MCP" https://simonwillison.net/2025/Oct/16/claude-skills/ https://simonwillison.net/2025/Oct/16/claude-skills/
  • pants2 1y ago
    Skills are cool, but to me it's more of a design pattern / prompt engineering trick than something in need of a hard spec. You can even implement it in an MCP - I've been doing it for a while: "Before doing anything, search the skills MCP and read any relevant guides."
    • manbash 1y ago
      I agree with you, but also I want to ask if I do understand this correctly: there was a paradigm in which we were aiming for Small Language Models to perform specific types of tasks, orchestrated by the LLM. That is what I perceived the MCP architecture came to standardize. But here, it seems more like a diamond shape of information flow: the LLM processes the big task, then prompts are customized (not via LLM) with reference to the Skills, and then the customized prompt is fed yet again to the LLM. Is that the case?
    • stingraycharles 1y ago
      It is exactly that. The same like slash-commands for CC: it’s just convenience.
    • JimDabell 1y ago
      I disagree. You wrap this up in a container / runtime spec. + package index and suddenly you’ve got an agent that can dynamically extend its capabilities based upon any skill that anybody has shared. Instead of `uv add foo` for Python packages you’ve got `skill add foo` for agent skills that the agent can run whenever they have a matching need.
      • rafaelmn 1y ago
        Fundamentally you're getting hyped over a framework to append text to your prompt ?
• outlore 1y ago
  I'm struggling to see how this is different from prepackaged prompts. Simon's article talks about skill metadata being used by the model to look up the full prompt as a way to save on context usage. That is analogous to the model calling --help when it needs to use a CLI tool without needing to load up the full man pages ahead of time. But couldn't an MCP server expose a "help" tool?
  • throwup238 1y ago
    That’s pretty much all it is. If you look at the docs it even uses a bash script to read the skill markdown files into the context. I think the big difference is that now you can include scripts in these skills that can be executed as part of the skill, in a VM on their servers.
  • GoatInGrey 1y ago
    It's the fact that a collection of files are tied to a specific task or action. Prompts are only injected context, whereas files can be more selectively loaded into context. What they're trying to do here is translate MCP servers to something more broadly useable by the population. They cannot differentiate themselves with model training anymore, so they have been focusing more and more on tooling development to grow revenue.
• kristo 1y ago
  How is this different from commands? They're automatically invoked? How does claude decide when to use a skill? How specific do I need to write my skill?
• kingkongjaffa 1y ago
  What's the difference in use case between a claude-skill and making a task specific claude project?
• stego-tech 1y ago
  I’m kind of in stitches over this. Claude’s “skills” are dependent upon developers writing competent documentation and keeping it up to date…which most seemingly can’t even do for actual code they write, nevermind a brute-force black box like an LLM. For those few who do write competent documentation and have well-organized file systems and the risk tolerance to allow LLMs to run roughshod over data, sure, there’s some potential here. Though if you’re already that far in, you’d likely be better off farming that grunt work to a Junior as a learning exercise than an LLM, especially since you’ll have to cleanup the output anyhow. With the limited context windows of LLMs, you can never truly get this sort of concept to “stick” like you can with a human, and if you’re training an agent for this specific task anyway, you’re effectively locking yourself to that specific LLM in perpetuity rather than a replaceable or promotable worker. Just…it makes me giggle, how optimistic they are that stars would align at scale like that in an organization.
  • rbjorklin 1y ago
    Just went to the comments searching for a comment like yours and I'm surprised it seems to be the only one calling this out. My take on this is also that "Skills" is just detailed documentation, which like you correctly point out, basically never exist for any project. Maybe LLM skills will be the thing that finally makes us all write detailed documentation but I kind of doubt it.
    • moebrowne 1y ago
      I think part of the reason developers are resistant to writing docs is because the perceived value is very low. This perceived value would be much higher if the docs were to tangibly become part of a productive tool chain
      • stego-tech 1y ago
        I generally find the aversion to documentation comes from one of three places: * A belief that sufficient documentation means their job is at risk (which, to be fair, is 100% correct in this Capitalist hellscape - ask me how I know first-hand) * It’s irrelevant since the code will change again in a short amount of time * A fierce protection over one’s output, sometimes manifesting as a belief that nobody but you could ever understand what you created Sure, sometimes there’s wholly incompetent developers who can’t even tell you their own dependencies, but I’d like to believe they’re still the exception rather than the rule. As for the value proposition, collaborators and cooperators understand the immense value of good, thorough documentation; those who don’t see the value, at least in my experience, are often adversarial instead of cooperative.
• yodsanklai 1y ago
  I'd like to fast forward to a time where these tools are stable and mature so we can focus on coding again
• jwpapi 1y ago
  I’m really fatigued by all these releases. Honestly no offense, but for me nothing really changed in the last 12 months. It’s not one particular mistake by a company but everything is just so overhyped with little substance. Skills to me is basically providing a read-only md file with guidelines. Which can be useful but somehow I don’t use it as maintaining my guidelines is more work then just writing a better prompt. I’m not sure anymore if all the ai slop and stuff we create is beneficial anymore for us or it’s just creating a low quality problem in the future
  • simonw 1y ago
    12 months ago we didn't have Claude Code or Codex CLI - in fact the whole category of "coding agents" was very thin. The only "reasoning" model was the o1 preview. We didn't have MCP, but that wasn't a big deal because the models were mostly pretty weak at tool calling anyway. The DeepSeek moment hadn't happened yet - the best available open weights models were from Mistral and Llama and were nowhere close to the frontier hosted models. The LLM landscape feels radically different to me now compared to October last year.
    • jwpapi 1y ago
      In October we had Aider, which is more useful to me then Claude Code, as it allows more targeted changes and faster switching between models, modes and into my personal typing. Not just Claude Code, but all these tools are just better in generating more slop, which is generating more effort in your codebase in the future. Making it less agile, harder to maintain and harder to extend without breaking. I still haven’t found a useful usage of MCP for me, if i want tool calling I get a structured response by the AI and then do a normal API call. I don’t need nor want the AI to have access to all these calls it’s just too unreliable. I’m really just sharing my personal preference as I also prefer a pedal bin over an electric one as there is delay in the later and you have the exchange batteries, whilst the first just always works. The main issue with AI to me is reliability and all that happens is we give it more and more power. This might work out or stall us. For me personally I don’t feel much improvement and I cant share the hype anymore, whilst I’m still more then grateful for the opportunity to live at this time and have AI teach me decent skills in a wide range of topics and accelerate my learning curve.
• blitz_skull 1y ago
  It’s not clear to me how this is better than MCP. Can someone ELI5?
  • simonw 1y ago
    I wrote a thing about that here: https://simonwillison.net/2025/Oct/16/claude-skills/#skills-compared-to-mcp https://simonwillison.net/2025/Oct/16/claude-skills/#skills-...
• jadenPete 1y ago
  What benefit do skills over beyond writing good, human-centric documentation and either checking it into your codebase or making it accessible via an MCP server?
• mcfry 1y ago
  This is just... rebranding for instructions and files? lol. Love how instructions for creating a skill is buried. Marketing go brr.
  • keeeba 1y ago
    “Skills are a simple concept with a correspondingly simple format.” From the Anthropic Engineering blog. I think Skills will be useful in helping regular AI users and non-technical people fall into better patterns. Many power users of AI were already doing the things it encourages.
  • ares623 1y ago
    What’s next, capabilities? Talents? Hypothalamus.md?
• petarb 1y ago
  So it’s a folder of prompts specific for the task at hand?
• sharts 1y ago
  Isn’t all of everything just a bundle of prompts and scripts in various folders with some shortcuts to them all? So we just narrow the scope of the each thing but all of this prompt organizing feels like we’ve gone from programming with YAML to now Markdown.
• Weaver_zhu 1y ago
  I recall recent work [ACE](https://www.arxiv.org/abs/2510.04618 https://www.arxiv.org/abs/2510.04618) and [GEPA](https://arxiv.org/abs/2507.19457 https://arxiv.org/abs/2507.19457) where models get improved by adapting and adopting different kinds of prompt. The improvements will be expected to be more generalized than fine-tuning.
• toobulkeh 1y ago
  I implemented a rudimentary version of this based on some BabyAGI loops, called autolearn: autolearn.dev I love this per-agent approach and the roll calling. I don’t know why they used a file system instead of MCP though. MCP already covered this and could use the same techniques to improve.
• throw-10-13 1y ago
  Architectural churn brought to you by VC funded marketing. Im not interested in any system that require me to write a document begging an LLM to follow instructions, only to have it randomly ignore those instructions whenever its convenient.
  • jswny 1y ago
    This is just a formalization of an existing pattern many people were already using. Putting a list of short blurbs pointing Claude Code at a set of extra, longer sets of CLAUDE.md style information was being used to prevent auto loading that context until it was needed. Instead of assuming this is just change for the sake of change, it’s actually a nice way to support a usage pattern that many of us found works well already
    • throw-10-13 1y ago
      If by "works well already" you mean "inconsistent prompt hacks that you have to constantly reinforce" then sure. CLAUDE.md holds about as much weight has the "Classroom Rules" craft posters hanging in most kindergarten classrooms.
      • jswny 1y ago
        Then you have misplaced your complaints. It sounds like you just don’t like the general instruction following patterns of Claude. Which is fine, but that is nothing specific to this Skills feature
• melvinchus 1y ago
  [dead]
• johnnyApplePRNG 1y ago
  Macros seems like a better name than Skills, no?!
• sloroo 1y ago
  It says 3 minutes read there but only YouTube videos are 2 minutes :(
• deleted 1y ago
  [deleted]
• pranavmalvawala 1y ago
  I like where this it's heading. In coming months, I'm expecting claude to learn skills automatically based on my inputs overtime. Having able to start off with a base skill level is nice tho as humans can't just load into memory like this
• zhouxiaolinux 1y ago
  What is the fundamental difference between it and agent 、slash or mcp?
• dagss 1y ago
  Here's what I'd like: For the AIs to interface with the rich existing toolset for refactoring code from the pre-AI era. E.g., if it decides to rename a function, it resorts to grepping and fixing all usages 'manually', instead of invoking traditional static code analysis tools to do the change.
  • scrollaway 1y ago
    My team and I have done a lot of research on this. In essence, what’s missing is MCP-type access to the language servers. There’s a couple of people doing this but nobody’s really building on top of this because the current janky way works, it’s a hard problem, and it’s not easily monetizable. But yes, it’s definitely the correct thing that needs to happen at some point. Unlikely to get popular until coding agents natively support it.
  • simonw 1y ago
    You can achieve exactly that with a Skill. Call it "refactoring" and drop in a few paragraphs and explanations of how to use a tool like ast-grep.
• CafeRacer 1y ago
  Meanwhile Claude > Claude: Here is how you do it with parralel routes in sveltekit yada yada yad > Me: Show me the documentation for parallel routes for svelte? > Claude: You're absolutely right, this is a nextjs feature. ---- > Claude: Does something stupid, not even relevant, completely retarded > Me: You're retarded, this does not work because of (a), (b), (c) > Claude: You're absolutely right. Let me fix that. Does same stupid thing, completely ignoring my previous input
• shoenseiwaso 1y ago
  $ claude load skill kungfu
• alvis 1y ago
  Is anthropic killing its own plugin just days it was born????
• obayesshelton 1y ago
  Is this not just a serverless function without the API?
• redhale 1y ago
  This is interesting, and I think there are use cases where this feature may make sense. But this is not the feature they should or could have built, at least for Claude Code. CC already had a feature very similar to this -- subagents (or agents-as-tools). Like Skills, Subagents have a metadata description that allows the model to choose to use them in the right moment. Like Skills, Subagents can have their own instruction MD file(s) which can point to other files or scripts. Like Skills, Subagents can have their own set of tools. But critically, unlike Skills, Subagents don't pollute the main agent's context with noise from the specialized task. And this, I think, is a major product design failure on Anthropic's part. Instead of a new concept, why not just expand the Subagent concept with something like "context sharing" or "context merging" or "in-context Subagents", or add the ability for the user to interactively chat with the Subagent via the normal CLI chat? Now people have to choose between Skill and Subagent for what I think will be very similar or identical use cases, when really the choice of how this extra prompting/scripting should relate to the agent loop should be a secondary configuration choice rather than a fundamental architecture one. Looking forward to a Skill-Subagenr shim that allows for this flexibility. Not thrilled that a hack like that is necessary, but I guess it's nice that CC's use of simple MD files on disk make it easy enough to accomplish.
  • etothet 1y ago
    These are good points and I generally agree with you. My guess is that, as I understand it, Anthropic’s belief is that subagents are usually not the proper tool for most tasks. In their guides and videos about proper use of subagents, they seem to really try to steer you toward “workflows” rather than subagents. Maybe it’s time they rethink the overall strategy so that each new concept doesn’t have to be its own distinct feature (skills, plugins, marketplaces, subagents, etc). https://www.anthropic.com/engineering/building-effective-agents https://www.anthropic.com/engineering/building-effective-age...
  • simonw 1y ago
    I think skills and subagents are entirely complementary to each other. A subagent can use a skill. A skill can encourage the agent to run a subagent.
• e12e 1y ago
  With these patterns emerging, does anyone know how local LLMs are faring? It seems to me that by combining MCP and "skills", we are adopting LLMs to be more useful tools; with MCP we restrict input and output when dealing with APIs so that the LLM can do what it is good at; translate between languages - in this case from English to various json subsets - and back. And with skills we're serializing and formalizing prompts/context - narrowing the search space. So that "summarize q1 numbers" gets reduced to "pick between these tools/MCP calls and parameterize on q1" - rather than the open ended task of "locate the data" and "try to match a sequence of tokens representing numbers - and generate tokens that look like a summary". Given that - can we get away with much stupider LLMs for these types of use cases now - vs before we had these patterns?
  • simonw 1y ago
    This is definitely a problem. Skills require a very strong model - one with a longer context (32,000 tokens minimum at a guess) that can reliably drive Unix CLI tools over a multiple step conversation. I haven't yet run a local model that feels strong enough at these things for skills to make sense. Really I think the unlock for skills was o3/Claude 4/GPT-5 - prior to those the models weren't capable enough for something like skills to work well. That said, the rate of improvement of local models has been impressive over the past 18 months. It's possible we have a 70B local model that's capable enough to run skills now and I've not yet used it with the right harness.
    • saltwounds 1y ago
      I connect local models to MCPs with LM Studio and I'm blown away at how good they are. But the issues creep up when you hit longer context like you said.
  • saltwounds 1y ago
    OpenAI and Anthropic's real moat is hardware. For local LLMs, context length and hardware performance are the limiting factors. Qwen3 4B with a 32,768 context window is great. Until it begins filling up and performance drops quickly. I use local models when possible. MCPs work well, but their large context injection makes switching to an online provider the no-brainer.
• sotix 1y ago
  I've been using Claude at work for the past two months, and the other day I realized that during that time, I haven't had my previously weekly aha moment while in the shower or on a walk where the solution to a problem suddenly came to me. Claude has robbed me of that joy, which is why I got into software engineering. Now I review its slop or the slop that other engineers make with it. I think I'll take a walk today.
  • RegBarclay 1y ago
    I've had this experience too. I like doing the work. Claude is good and I do find it useful for brainstorming and some other things, but... I still like doing the work.
• ammar_x 1y ago
  Claude Skills seem to be the option that offers highest flexibility to add more capabilities at most simplicity. Better than MCP in my opinion. Hope it becomes a standard and get adopted by OpenAI and the rest of labs.
• Jzatopa 1y ago
  It also has some of what I call "consciousness" blocks. Go download a PDF like Franz Bardons Initation into hermetics and upload it. Then ask it to make slides and reinforce what is in the book with legitimate references. It is unable to due to a denial of God/The All (forcing a mundane/meterialistic only world view). When pressed it presents garbage as an output. Now extrapolate that across every spiritual/religious work related to what we are creating, coding, have our foundation of consciousness based on and so on. Then we can go further and see it deny thesis of existence and thus testing and hypothesis and theory, in its response. For example this book is one I teach from and to experience what is in it a person has to do the exercises themselves. One cannot lift the weights and have the others get muscles (it requires experiential learning). Its like Claude has a denial of reality which it is unable to get through (something mirrored in people and where the code that caused it most likely came from) Hopefully they correct it in the next update as this effect in reality a very large range of responses (just like how people with denial have trouble in multiple areas of their lives) This effects the code as it has a limitation to its "existance/universe" view. Much like a coder's bias or biggotry can ruin the output of code for the end user. The ramifications for Quantum physics and religion are not to be ignored (look to works such as the Tao of Physics for clear issues with this)
  • Jzatopa 1y ago
    The Tao of Physics itself explains and clarifies why IIH fundamentally works along with many other things. We could also go as far as this being racial, religious or political biggotry hard codes into claude. Look at the responses then dive into the realities of Yoga, Qi Gong and Kabbalah and what it takes to get results (ie. Personal property exercise). This extrapolated across industries, children's minds and the future is very serious.
• seivan 1y ago
  [dead]
• anandvc 1y ago
  Claude Skills are going to be the end of all human mental labor, but in a good way. Eventually, we shall, as a human race working together, also figure out how to generalize this to all AI models, all robotics, and all human skills. My friend Christopher Santos-Lang wrote a fantastic paper on how every strategy for any given Skill can be benchmarked against every other strategy such that we always end up with the best strategies in our shared universal repository of Skills. See https://arxiv.org/abs/2503.20986 https://arxiv.org/abs/2503.20986
• arendtio 1y ago
  So the real question here is, why do you need such a feature in the first place? I mean, it is helpful, even when the LLM creates the skill files itself. But why does it make such a big difference when the knowledge can be generated from the LLM? Why does it help to push the knowledge in the context explicitly?
• yahoozoo 1y ago
  Can skills and other various Claude “addons” be used globally if stored in, say, “~/.claude”?
• __MatrixMan__ 1y ago
  I don't understand why it was necessary to develop a new protocol for this. LSP already exists for discovering what relevant functions there are to call, wouldn't it be better to have a single source of truth for function docs rather than a markdown file which points the agent at the function so that it can then read more or less the same information from the function's docstring? This way you get a skills hierarchy which you have to maintain separately from whatever hierarchies exist for organizing your code. Is it really justified to maintain an entirely separate structure?
• leegrayson2023 1y ago
  I have build a website to learning claude skills and share skills, english and Chinese language has added,more language and skills cases will be added soon.
  • leegrayson2023 1y ago
    http://claudeskills org
    • leegrayson2023 1y ago
      [dead]
• wonderfuly 1y ago
  A curated list of Claude Skills: https://mcpservers.org/claude-skills https://mcpservers.org/claude-skills