Skip to content
Back to search

gep-claude-marketplace

MarketplaceWorks with Claude CodeGitHubIncomplete

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/gep--gep-claude-marketplace/badge.svg)](/listings/gep--gep-claude-marketplace)

HTML

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

Install

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 · 24 lines
  1. {
  2. "name": "gep-claude-marketplace",
  3. "owner": {
  4. "name": "Gep"
  5. },
  6. "metadata": {
  7. "description": "Claude Code plugins and skills maintained by Gep",
  8. "version": "0.14.0"
  9. },
  10. "plugins": [
  11. {
  12. "name": "destructive-guard",
  13. "source": "./plugins/destructive-guard",
  14. "description": "Deterministic PreToolUse approval gate, configured through env variables. By default asks before destructive commands on the local machine or cloud services; optional rule packs, an optional Jev classifier and a check skill to dry-run calls.",
  15. "version": "0.6.1"
  16. },
  17. {
  18. "name": "gated-dev-simple-workflow",
  19. "source": "./plugins/gated-dev-simple-workflow",
  20. "description": "File-based ticket-to-PR pipeline: /ticket runs spec, plan, dev and review subagents in a worktree per ticket (git, Orca or iTerm2), with a plan-approval checkpoint and PR creation, plus a launcher that opens one session per ticket and notifies you when a launched session needs you. Treats approval-gate prompts as checkpoints; no gate required.",
  21. "version": "0.6.0"
  22. }
  23. ]
  24. }
README.md · README · 47 lines
  1. # Gep Claude Code Marketplace
  2. A Claude Code plugin marketplace for sharing plugins and skills maintained by
  3. Gep.
  4. ```text
  5. /plugin marketplace add gep/gep-claude-marketplace
  6. /plugin install <plugin-name>@gep-claude-marketplace
  7. ```
  8. ## Plugins
  9. | Plugin | What it does |
  10. | --- | --- |
  11. | [`destructive-guard`](plugins/destructive-guard/README.md) | PreToolUse approval gate: asks before destructive commands and MCP calls (local or cloud), blocks `.env` reads. Zero config; tuned with env variables. |
  12. | [`gated-dev-simple-workflow`](plugins/gated-dev-simple-workflow/README.md) | `/ticket`: file-based ticket → spec → plan → dev → review → PR pipeline in a worktree per ticket. Works with or without the gate. |
  13. ## Repository layout
  14. ```text
  15. .claude-plugin/
  16. marketplace.json # Marketplace catalog
  17. plugins/<name>/ # One directory per plugin
  18. ```
  19. ## Add a plugin
  20. In Claude Code, add this repository as a marketplace:
  21. ```text
  22. /plugin marketplace add gep/gep-claude-marketplace
  23. ```
  24. 1. Create a directory for the plugin.
  25. 2. Add a `.claude-plugin/plugin.json` manifest with a unique plugin name,
  26. version, and description.
  27. 3. Add the plugin to `.claude-plugin/marketplace.json`, using a relative
  28. `source` path to its directory.
  29. 4. Put skills in `skills/<skill-name>/SKILL.md` within the plugin. Each
  30. `SKILL.md` needs YAML frontmatter with a `name` and `description`.
  31. 5. Keep the plugin and marketplace versions and descriptions up to date, then
  32. validate the JSON manifests before submitting.
  33. After a plugin has been added to the catalog, install it with
  34. `/plugin install <plugin-name>@gep-claude-marketplace`. Plugins can also
  35. provide other Claude Code extensions, such as commands, agents, hooks, and MCP
  36. server configuration.

Ratings and comments

Sign in to rate this skill.

Sign in

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