Skip to content
Back to search

stuttgart-things

MarketplaceWorks with Claude CodeGitHub

Claude Code plugins for stuttgart-things: service development and release, LabUL Proxmox operations

Safety scan

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

Checked yesterday
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/stuttgart-things--claude-plugins/badge.svg)](/listings/stuttgart-things--claude-plugins)

HTML

<a href="/listings/stuttgart-things--claude-plugins"><img src="/api/listings/stuttgart-things--claude-plugins/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.

/plugin marketplace add stuttgart-things/claude-plugins
/plugin install sthings-dev@stuttgart-things
/plugin install labul@stuttgart-things

Or from the shell: `claude plugin marketplace add stuttgart-things/claude-plugins`, then `claude plugin install sthings-dev@stuttgart-things`.

Updates: `/plugin marketplace update stuttgart-things`, then `/plugin update <plugin>@stuttgart-things`.

For a whole repo

Put this in the repo's `.claude/settings.json`. Anyone who opens the repo in Claude Code is offered the marketplace and the plugins:

{
  "extraKnownMarketplaces": {
    "stuttgart-things": {
      "source": { "source": "github", "repo": "stuttgart-things/claude-plugins" }
    }
  },
  "enabledPlugins": {
    "sthings-dev@stuttgart-things": true
  }
}

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 · 22 lines
  1. {
  2. "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
  3. "name": "stuttgart-things",
  4. "description": "Claude Code plugins for stuttgart-things: service development and release, LabUL Proxmox operations",
  5. "owner": {
  6. "name": "stuttgart-things"
  7. },
  8. "plugins": [
  9. {
  10. "name": "sthings-dev",
  11. "description": "Build and release stuttgart-things Go services: repo bootstrap like claims/pvectl, start at v0.1.0, Go tests via Dagger",
  12. "source": "./plugins/sthings-dev",
  13. "category": "development"
  14. },
  15. {
  16. "name": "labul",
  17. "description": "LabUL Proxmox operations: the template round (Packer -> promote -> repins) and pvectl for agents",
  18. "source": "./plugins/labul",
  19. "category": "development"
  20. }
  21. ]
  22. }
README.md · README · 70 lines
  1. # claude-plugins
  2. Claude Code plugin marketplace of stuttgart-things: skills from the
  3. everyday platform work, versioned and installed with `/plugin`.
  4. ## Install
  5. ```text
  6. /plugin marketplace add stuttgart-things/claude-plugins
  7. /plugin install sthings-dev@stuttgart-things
  8. /plugin install labul@stuttgart-things
  9. ```
  10. Or from the shell: `claude plugin marketplace add stuttgart-things/claude-plugins`,
  11. then `claude plugin install sthings-dev@stuttgart-things`.
  12. Updates: `/plugin marketplace update stuttgart-things`, then `/plugin update <plugin>@stuttgart-things`.
  13. ### For a whole repo
  14. Put this in the repo's `.claude/settings.json`. Anyone who opens the repo in
  15. Claude Code is offered the marketplace and the plugins:
  16. ```json
  17. {
  18. "extraKnownMarketplaces": {
  19. "stuttgart-things": {
  20. "source": { "source": "github", "repo": "stuttgart-things/claude-plugins" }
  21. }
  22. },
  23. "enabledPlugins": {
  24. "sthings-dev@stuttgart-things": true
  25. }
  26. }
  27. ```
  28. ## Plugins
  29. | Plugin | Skills | For |
  30. | --- | --- | --- |
  31. | [`sthings-dev`](plugins/sthings-dev) | `go-service-bootstrap`, `semver-start-v0`, `dagger-go-test` | building and releasing Go services like claims/pvectl |
  32. | [`labul`](plugins/labul) | `labul-template-round`, `pvectl` | LabUL Proxmox: template round, pvectl for agents |
  33. In Claude Code the skills are named `<plugin>:<skill>`, e.g.
  34. `sthings-dev:semver-start-v0`. Claude loads them by their description when
  35. a task fits, or you call them with `/sthings-dev:semver-start-v0`.
  36. ## Public repo
  37. This repo is public. Skills describe procedures, not secrets: no
  38. passwords, tokens, lab endpoints/IPs or Vault paths. They name credential
  39. **files** (`~/.secrets.d/…`) that are used through `sops exec-env`.
  40. ## Development
  41. ```text
  42. plugins/<plugin>/
  43. .claude-plugin/plugin.json # name, version, description
  44. skills/<skill>/SKILL.md # frontmatter name + description (when to load), then the procedure
  45. README.md
  46. .claude-plugin/marketplace.json # lists the plugins
  47. ```
  48. - Test locally without installing: `claude --plugin-dir plugins/<plugin>`.
  49. - Validate: `claude plugin validate .` and `claude plugin validate plugins/<plugin>` (also in CI).
  50. - A new skill is a new folder under `skills/`; a new plugin also needs an entry in `marketplace.json`.
  51. - **Release:** bump `version` in `plugin.json` (a new plugin starts at `0.1.0`).
  52. After the merge, `claude plugin tag plugins/<plugin> --push` tags it as `<plugin>--v<version>`.
  53. Bump the version with every change to a plugin: installed copies are updated by version.
  54. - PR titles are Conventional Commits.

Ratings and comments

Sign in to rate this skill.

Sign in

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