Skip to content
Back to search

thematthub

MarketplaceWorks with Claude CodeGitHub

Skills for Claude Code from real project work: writing, document export, publishing repositories, shareable web pages, presentations, simulation studies, plant data and LLM integration.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/thematthub--claude-skills/badge.svg)](/listings/thematthub--claude-skills)

HTML

<a href="/listings/thematthub--claude-skills"><img src="/api/listings/thematthub--claude-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

You need Claude Code installed and signed in ([guide 2](docs/2-using-claude-code.md) shows how). Then, inside Claude Code, type:

/plugin marketplace add TheMattHub/claude-skills

Claude Code adds the marketplace, which is named `thematthub`. Run `/plugin` and open the Marketplaces tab to see it listed. Then install one plugin:

/plugin install writing-toolkit@thematthub

Claude Code opens a details page for the plugin. Read it, choose "Install for you (user scope)", and the plugin is active. Type `/` to see its skills in the list.

The same commands work in a shell: `claude plugin marketplace add TheMattHub/claude-skills`, then `claude plugin install writing-toolkit@thematthub`.

The plugin folders' own READMEs use a one-step form that adds the marketplace and installs in one command: `/plugin install <name> --marketplace TheMattHub/claude-skills`. It needs Claude Code 2.1.275 or later.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 113 lines
  1. {
  2. "name": "thematthub",
  3. "description": "Skills for Claude Code from real project work: writing, document export, publishing repositories, shareable web pages, presentations, simulation studies, plant data and LLM integration.",
  4. "owner": {
  5. "name": "Matteo Brunetti"
  6. },
  7. "renames": {
  8. "thematthub-writing-toolkit": "writing-toolkit",
  9. "thematthub-repo-publishing": "repo-publishing",
  10. "thematthub-web-pages": "web-pages",
  11. "thematthub-docs-export": "docs-export",
  12. "thematthub-plant-data": "plant-data",
  13. "thematthub-llm-integration": "llm-integration",
  14. "thematthub-decks": "decks",
  15. "thematthub-naga": "naga",
  16. "thematthub-agent-waves": null,
  17. "agent-waves": null,
  18. "system1": null
  19. },
  20. "plugins": [
  21. {
  22. "name": "writing-toolkit",
  23. "source": "./plugins/writing-toolkit",
  24. "description": "Write texts a reader can follow without the author: handbooks, documentation sites, research papers, Italian texts, competitor analyses.",
  25. "category": "productivity"
  26. },
  27. {
  28. "name": "repo-publishing",
  29. "source": "./plugins/repo-publishing",
  30. "description": "Turn a private repository into a safe public release, and cut versioned releases with draft notes.",
  31. "category": "development"
  32. },
  33. {
  34. "name": "web-pages",
  35. "source": "./plugins/web-pages",
  36. "description": "Build shareable HTML pages (dashboards, viewers, monitors, reports) and choose interface colours that are validated instead of eyeballed.",
  37. "category": "development"
  38. },
  39. {
  40. "name": "docs-export",
  41. "source": "./plugins/docs-export",
  42. "description": "Export a project's markdown documentation to Word and PDF, with your own templates and rendered Mermaid diagrams. The script is written for Windows.",
  43. "category": "productivity"
  44. },
  45. {
  46. "name": "plant-data",
  47. "source": "./plugins/plant-data",
  48. "description": "Connect apps and simulations to live plant data (OPC UA, MQTT, MES, SQL) without leaking credentials or sending unsafe commands.",
  49. "category": "development"
  50. },
  51. {
  52. "name": "llm-integration",
  53. "source": "./plugins/llm-integration",
  54. "description": "Add language-model calls (Claude, OpenAI, Ollama, LM Studio) to an app, with reliable JSON output and guidance on choosing a local model.",
  55. "category": "development"
  56. },
  57. {
  58. "name": "decks",
  59. "displayName": "Decks",
  60. "source": {
  61. "source": "github",
  62. "repo": "TheMattHub/decks"
  63. },
  64. "description": "Make presentations: brief and structure by kind, design in Claude Slides, finish and edit natively in PowerPoint, build on company templates. The PowerPoint steps need Windows with desktop PowerPoint.",
  65. "category": "productivity",
  66. "metadata": {
  67. "icon": "./icons/decks.png"
  68. }
  69. },
  70. {
  71. "name": "naga",
  72. "displayName": "Naga simulation study",
  73. "source": {
  74. "source": "git-subdir",
  75. "url": "https://github.com/TheMattHub/naga.git",
  76. "path": "nagasim/skills"
  77. },
  78. "description": "Run a simulation study for a capacity or what-if decision (how many machines, staff or docks; will a change cope with demand) with the Naga engine. Needs the engine installed: pip install \"nagasim[mcp]\".",
  79. "category": "productivity",
  80. "skills": [
  81. "./simulation-study"
  82. ],
  83. "mcpServers": {
  84. "naga": {
  85. "command": "naga",
  86. "args": [
  87. "mcp",
  88. "--tools",
  89. "study",
  90. "--root",
  91. "${CLAUDE_PROJECT_DIR}"
  92. ]
  93. }
  94. },
  95. "author": {
  96. "name": "Matteo Brunetti"
  97. },
  98. "license": "Apache-2.0",
  99. "homepage": "https://github.com/TheMattHub/naga",
  100. "repository": "https://github.com/TheMattHub/naga",
  101. "keywords": [
  102. "simulation",
  103. "discrete-event",
  104. "capacity planning",
  105. "what-if",
  106. "mcp"
  107. ],
  108. "metadata": {
  109. "icon": "./icons/naga.png"
  110. }
  111. }
  112. ]
  113. }
README.md · README · 109 lines
  1. # Claude skills
  2. A catalogue (a "marketplace") of plugins for Claude Code, Anthropic's coding assistant. Each plugin adds skills: short instruction sets that make Claude work in a way we found reliable on real simulation, operations research and industrial automation projects.
  3. If you have never used Claude Code, plugins or skills, start with the guides under [New to Claude?](#new-to-claude) and come back here.
  4. ## Example
  5. Here is what a plugin does for you. With `writing-toolkit` (the first plugin in the table below) installed, you type:
  6. ```text
  7. Write the day-one setup guide for the course participants. They install the simulator and run the first model on their own.
  8. ```
  9. Claude recognises that the request matches the skill `writing-course-handbooks`. It then writes for a reader who cannot ask you questions: every term is explained before it is used, every step shows the exact command and what the reader should see afterwards, and the guide ends with a table of what to do when a step fails.
  10. ## Quick start
  11. You need Claude Code installed and signed in ([guide 2](docs/2-using-claude-code.md) shows how). Then, inside Claude Code, type:
  12. ```text
  13. /plugin marketplace add TheMattHub/claude-skills
  14. ```
  15. Claude Code adds the marketplace, which is named `thematthub`. Run `/plugin` and open the Marketplaces tab to see it listed. Then install one plugin:
  16. ```text
  17. /plugin install writing-toolkit@thematthub
  18. ```
  19. Claude Code opens a details page for the plugin. Read it, choose "Install for you (user scope)", and the plugin is active. Type `/` to see its skills in the list.
  20. The same commands work in a shell: `claude plugin marketplace add TheMattHub/claude-skills`, then `claude plugin install writing-toolkit@thematthub`.
  21. The plugin folders' own READMEs use a one-step form that adds the marketplace and installs in one command: `/plugin install <name> --marketplace TheMattHub/claude-skills`. It needs Claude Code 2.1.275 or later.
  22. ## Plugins
  23. | &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Plugin | What it helps with | Who should install it |
  24. | --- | --- | --- | --- |
  25. | <img src="plugins/writing-toolkit/.claude-plugin/icon.png" width="72" alt=""> | `writing-toolkit` | Writing texts a reader can follow without you: handbooks, documentation sites, research papers, Italian texts, competitor analyses | Everyone who writes reports, guides or papers |
  26. | <img src="plugins/repo-publishing/.claude-plugin/icon.png" width="72" alt=""> | `repo-publishing` | Turning a private repository into a safe public release, and cutting versioned releases with draft notes | Anyone who publishes code |
  27. | <img src="plugins/web-pages/.claude-plugin/icon.png" width="72" alt=""> | `web-pages` | Building shareable HTML pages (dashboards, viewers, monitors, reports) and choosing interface colours that are validated instead of eyeballed | Anyone who builds dashboards or viewers |
  28. | <img src="plugins/docs-export/.claude-plugin/icon.png" width="72" alt=""> | `docs-export` | Exporting a project's markdown documentation to Word and PDF, with your own templates and rendered Mermaid diagrams | Anyone who sends documentation to clients or colleagues. Written for Windows |
  29. | <img src="plugins/plant-data/.claude-plugin/icon.png" width="72" alt=""> | `plant-data` | Connecting apps, simulations and digital twins to plant systems (OPC UA, MQTT, MES, historians) safely | Simulation and automation engineers |
  30. | <img src="plugins/llm-integration/.claude-plugin/icon.png" width="72" alt=""> | `llm-integration` | Adding language-model calls to an app: provider-agnostic client, validated JSON output, local models, a fake for tests | Developers who build apps that call a model |
  31. | <img src="icons/decks.png" width="72" alt=""> | `decks` | Making presentations: brief and structure, design in Claude Slides, finishing in PowerPoint, company templates | Anyone who builds slide decks. The PowerPoint steps need Windows with desktop PowerPoint |
  32. | <img src="icons/naga.png" width="72" alt=""> | `naga` | Running a simulation study for a decision (how many machines, staff or docks; will a change cope with demand) with the Naga engine | Anyone with a capacity or what-if question. Needs Python and the engine: `pip install "nagasim[mcp]"` |
  33. The last two live in their own repositories and are only listed here, so installing them fetches from those repositories:
  34. - `decks` comes from [TheMattHub/decks](https://github.com/TheMattHub/decks). Its scripts drive the PowerPoint installed on your machine, and `uv` downloads their Python packages on first run; its README lists the requirements.
  35. - `naga` takes the `simulation-study` skill from [TheMattHub/naga](https://github.com/TheMattHub/naga) (Apache-2.0) and follows that repository's main branch. While the plugin is enabled, Claude Code starts the engine's tool server on your machine in every session (`naga mcp --tools study --root <your project folder>`). The server reads and writes model and study files only inside that folder, and network access is off. If the `naga` command is not installed, `/mcp` shows the plugin's server as failed to connect until you install the engine; the skill still loads. Keep the engine up to date (`pip install -U "nagasim[mcp]"`) so it matches the skill.
  36. ## Which ones should I install first?
  37. Install the few plugins you will use: `writing-toolkit` plus one that matches your work is a good start. Claude reads the short description of every installed skill on every request, so each plugin costs a little context (the text Claude holds in view) on every turn. Run `/skill-doctor` or `claude plugin details <plugin>` to see the cost, and after a few weeks remove what you did not use. [Guide 3](docs/3-skills-and-plugins.md) explains how.
  38. ## Official plugins worth adding
  39. These come from Anthropic's official marketplace, which Claude Code already knows, so there is no marketplace to add first.
  40. | Plugin | What it gives you | What it costs |
  41. | --- | --- | --- |
  42. | `superpowers` | A plan-first way of working: `brainstorming` (clarify a request before building), `writing-plans` (turn it into a step-by-step plan), `systematic-debugging` (find the root cause before fixing), and twelve more skills | About 850 tokens in every session for 15 skills, plus a session-start hook that tells Claude to look for a matching skill before each task. |
  43. | `frontend-design` | Design guidance for web interfaces. The `web-pages` skills use it when it is installed | One skill |
  44. ```text
  45. /plugin install superpowers@claude-plugins-official
  46. ```
  47. ## New to Claude?
  48. Four short pages, each readable on its own:
  49. - [Using Claude](docs/1-using-claude.md): the Claude apps, asking well, projects, files and artifacts, connectors, checking the answers.
  50. - [Using Claude Code](docs/2-using-claude-code.md): install, a first session, and the habits that matter most.
  51. - [Skills and plugins](docs/3-skills-and-plugins.md): what they are, how to install, update and review them, and how to write your own.
  52. - [Memory](docs/4-memory.md): what Claude remembers between sessions, where it is stored, and what to write in a `CLAUDE.md`. A starter file to copy is in [docs/starter-CLAUDE.md](docs/starter-CLAUDE.md).
  53. ## Sharing with a team
  54. To offer this marketplace to everyone who works in one repository, add these keys to that repository's `.claude/settings.json` (create the file if it does not exist):
  55. ```json
  56. {
  57. "extraKnownMarketplaces": {
  58. "thematthub": {
  59. "source": { "source": "github", "repo": "TheMattHub/claude-skills" }
  60. }
  61. },
  62. "enabledPlugins": { "writing-toolkit@thematthub": true }
  63. }
  64. ```
  65. People who open the repository and accept Claude Code's trust dialog get the marketplace. Each person still runs `claude plugin install writing-toolkit@thematthub --scope project` once, because the setting marks the plugin as enabled for the project, but each person's Claude Code downloads it only on install. On a Team or Enterprise plan, an Owner (the person who administers the organisation's Claude account) can also provision plugins from the claude.ai organisation settings; see [Manage Claude Code plugins for your organization](https://code.claude.com/docs/en/plugins/org.md).
  66. ## Reporting a problem or proposing a change
  67. Open an issue on this repository. Before a pull request, run both checks and fix what they report:
  68. ```text
  69. python -I tools/check_repo.py
  70. claude plugin validate . --strict
  71. ```
  72. ## Licence and credits
  73. [MIT](LICENSE). The two plugins listed from other repositories carry their own licences (`decks`: MIT; `naga`: Apache-2.0).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.