"documentation skills" only?

[cwimsatt]

The readme says "enables Claude Code to generate documentation skills directly". So, non documentation skills are excluded? Is this actually claude skills or your own/more general use of the word "skills"?

[yusufkaraaslan]

Good question - the wording is confusing.

These are official Claude Skills (the real ones you upload to Claude). The "documentation" part just refers to one of the sources we can scrape from.

You can actually create skills from:

• Documentation websites (React, Django, etc.)
• GitHub repositories (analyze actual code)
• PDF files (manuals, guides)
• All three combined into one skill

So it's not limited to documentation at all. We probably should've called it "Skill Creator" or something clearer - the name is a bit misleading now that we support multiple sources.

The output is always a proper Claude Skill that you upload to claude.ai and use across all your conversations.

[cwimsatt]

Ok, I've installed and tested on https://docs.docker.com/ai/mcp-catalog-and-toolkit/toolkit/ using claude code example. It created the skill successfully. I uploaded to claude.ai, and asked it to use the new skill to connect to the docker mcp gateway. Claude ai used the skill and responded it was not supported in claude.ai, just claude desktop. When I followed up, it replied it was not intended to work with tools, ala the anthropic excel and pdf skills, just to provide documentation/guidance. Is that what the "documentation skills" references? I'm asking claude code to revamp the skill it created to be able to work with the docker mcp tool.

I love the ideas of your project, especially the multiple pov - docs, code, issues - option.