<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Plugins on Devops Monk</title><link>https://devops-monk.com/tags/plugins/</link><description>Recent content in Plugins on Devops Monk</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 17 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://devops-monk.com/tags/plugins/index.xml" rel="self" type="application/rss+xml"/><item><title>Claude Code Plugins: The Complete Guide to Building and Sharing Extensions</title><link>https://devops-monk.com/2026/05/claude-code-plugins-guide/</link><pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate><guid>https://devops-monk.com/2026/05/claude-code-plugins-guide/</guid><description>Skills, agents, and hooks you add to .claude/ are powerful — but they are locked to one project. Every time you start a new repo you copy the same files, maintain them in multiple places, and drift out of sync. Claude Code plugins solve this: a plugin is a shareable, versioned package that carries all your customisations and can be installed in any project with one command.
This post covers what plugins are, when to use them, and how to build a real one from scratch — a DevOps helper that ships a deployment skill, a pre-deploy safety hook, and an MCP server connection to your Kubernetes cluster.</description></item></channel></rss>