Skip to content
Back to search

claude-skills

MarketplaceWorks with Claude CodeGitHub

Shared Claude Code skills and agents, published as a plugin marketplace.

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/20alex02--claude-skills/badge.svg)](/listings/20alex02--claude-skills)

HTML

<a href="/listings/20alex02--claude-skills"><img src="/api/listings/20alex02--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.

Requires access to this repository (Claude Code clones it with your git credentials).

/plugin marketplace add 20alex02/claude-skills
/plugin install dev-pipeline@claude-skills
/plugin install umbraco-tools@claude-skills

Or run `/plugin` and pick from the `claude-skills` marketplace.

Get updates:

/plugin marketplace update claude-skills

To have a project offer these plugins automatically to everyone who opens it, add to that project's committed `.claude/settings.json`:

{
  "extraKnownMarketplaces": {
    "claude-skills": {
      "source": { "source": "github", "repo": "20alex02/claude-skills" }
    }
  },
  "enabledPlugins": {
    "umbraco-tools@claude-skills": 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 · 21 lines
  1. {
  2. "name": "claude-skills",
  3. "owner": {
  4. "name": "Alex Popovic"
  5. },
  6. "metadata": {
  7. "description": "Shared Claude Code skills and agents for day-to-day development work."
  8. },
  9. "plugins": [
  10. {
  11. "name": "dev-pipeline",
  12. "source": "./plugins/dev-pipeline",
  13. "description": "Multi-model /feature and /bugfix pipelines (research, plan or diagnose, implement, review) with pinned-model subagents."
  14. },
  15. {
  16. "name": "umbraco-tools",
  17. "source": "./plugins/umbraco-tools",
  18. "description": "Umbraco launch checklist for dev, stage and production: config, health check, redirects, caching, indexing, SEO, performance, schema.org."
  19. }
  20. ]
  21. }
README.md · README · 92 lines
  1. # claude-skills
  2. Shared [Claude Code](https://docs.claude.com/en/docs/claude-code/overview) skills and agents, published as a plugin marketplace.
  3. ## Plugins
  4. | Plugin | Contents | Usage |
  5. |---|---|---|
  6. | `dev-pipeline` | Skills `feature`, `bugfix`; agents `context-gatherer`, `diagnoser`, `planner`, `implementer`, `reviewer` | `/dev-pipeline:feature <task> [-test]`, `/dev-pipeline:bugfix <bug report>` |
  7. | `umbraco-tools` | Skill `umbraco-launch-check` | `/umbraco-tools:umbraco-launch-check <path/to/Project.csproj> [--stage[=url]] [--prod[=url]] [--pages=url1,url2]` |
  8. ### dev-pipeline
  9. Runs work through subagents pinned to different models:
  10. - **feature**: research (Haiku) -> plan for approval (Opus) -> implement (Sonnet) -> review (Opus). Add `-test` to have tests written or updated.
  11. - **bugfix**: gather context (Haiku) -> diagnose root cause or ask for evidence (Opus) -> approve -> implement with a regression test (Sonnet) -> verify.
  12. Nothing is committed by the pipeline.
  13. ### umbraco-tools
  14. `umbraco-launch-check` verifies an Umbraco site before or after a production launch: Umbraco/ASP.NET config per environment (production runtime mode, debug, logging, IIS `web.config`), Umbraco health check, https/www redirects, caching and security headers, indexing safety (noindex on stage, none on prod), robots.txt, sitemap, on-page SEO, broken links, Lighthouse/PageSpeed, responsiveness and schema.org structured data.
  15. - No flag: dev checks. `--stage` / `--prod`: live checks of that environment; the URL is taken from the flag value or found in the project's config/publish profiles.
  16. - Writes a tickable checklist to `launch-checks/<project>-<date>-<env>.md` in the repo root (git-ignored) and proposes code fixes, applied only after approval.
  17. - Requirements: Node.js and Chrome (for local Lighthouse via `npx lighthouse`), `curl`, .NET SDK.
  18. ## Install
  19. Requires access to this repository (Claude Code clones it with your git credentials).
  20. ```
  21. /plugin marketplace add 20alex02/claude-skills
  22. /plugin install dev-pipeline@claude-skills
  23. /plugin install umbraco-tools@claude-skills
  24. ```
  25. Or run `/plugin` and pick from the `claude-skills` marketplace.
  26. Get updates:
  27. ```
  28. /plugin marketplace update claude-skills
  29. ```
  30. To have a project offer these plugins automatically to everyone who opens it, add to that project's committed `.claude/settings.json`:
  31. ```json
  32. {
  33. "extraKnownMarketplaces": {
  34. "claude-skills": {
  35. "source": { "source": "github", "repo": "20alex02/claude-skills" }
  36. }
  37. },
  38. "enabledPlugins": {
  39. "umbraco-tools@claude-skills": true
  40. }
  41. }
  42. ```
  43. ## Repository layout
  44. ```
  45. .claude-plugin/marketplace.json marketplace definition (list of plugins)
  46. plugins/<plugin>/
  47. .claude-plugin/plugin.json plugin name, version, description
  48. skills/<skill>/SKILL.md skills (plus supporting files)
  49. agents/<agent>.md subagents
  50. ```
  51. ## Contributing
  52. 1. Add or edit a skill under `plugins/<plugin>/skills/<skill>/` (or an agent under `plugins/<plugin>/agents/`). For a new plugin, add its folder with `.claude-plugin/plugin.json` and register it in `.claude-plugin/marketplace.json`.
  53. 2. Bump `version` in that plugin's `plugin.json` so installed copies pick up the change.
  54. 3. Open a pull request.
  55. Skills must not reference files in a personal `~/.claude` folder; refer to agents by name, since installed plugin agents may be listed with the plugin prefix (e.g. `dev-pipeline:reviewer`).
  56. ### Maintainer setup (editing in place)
  57. The maintainer uses the skills straight from this repo instead of installing the plugins, by linking them into the global Claude config with Windows directory junctions (no admin rights needed):
  58. ```powershell
  59. $repo = "C:\projects\claude-skills\plugins"
  60. New-Item -ItemType Junction -Path "$HOME\.claude\skills\bugfix" -Target "$repo\dev-pipeline\skills\bugfix"
  61. New-Item -ItemType Junction -Path "$HOME\.claude\skills\feature" -Target "$repo\dev-pipeline\skills\feature"
  62. New-Item -ItemType Junction -Path "$HOME\.claude\skills\umbraco-launch-check" -Target "$repo\umbraco-tools\skills\umbraco-launch-check"
  63. New-Item -ItemType Junction -Path "$HOME\.claude\agents" -Target "$repo\dev-pipeline\agents"
  64. ```
  65. Edits made through either path are the same files, so there is nothing to sync. Do not also install the plugins on that machine, or the skills appear twice. Note that `~/.claude/agents` points into the `dev-pipeline` plugin, so any new personal agent created there lands in this repo.

Ratings and comments

Sign in to rate this skill.

Sign in

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