SMK Claude Code Plugins

Everything I have built for Claude Code, in one marketplace. Most of it exists because I hit the same problem twice and got tired of solving it by hand.

Persian and RTL are first-class here, not an afterthought.

Install

Most people use these in the Claude desktop app, not the terminal, so that comes first. Adding the marketplace and installing a plugin are two separate steps: the first one only registers the catalog, it installs nothing.

1. Add the marketplace, once

Customize → Plugins → Personal plugins → +  →  Add marketplace → Add from a repository

Paste this as the repository:

smk-labs/claude-plugins

2. Install the plugins you want

Customize → Plugins → Browse plugins → readable → Install

Repeat per plugin. When it asks for a scope: User for every project, Project to share with everyone on the repo, Local for this repo only.

Quicker, without leaving the chat: the + button next to the prompt box → Plugins → Add plugin.

3. Keep them current

The marketplace is called smk, not claude-plugins. You need that name here.

Third-party marketplaces do not auto-update by default, so nothing arrives on its own. Either update when you feel like it:

/plugin marketplace update smk
/reload-plugins

Or switch it on once and stop thinking about it:

/plugin → Marketplaces → smk → Enable auto-update

Enable, disable, remove

+ → Plugins → Manage plugins

Removing the marketplace uninstalls every plugin that came from it.

If you do live in the terminal

/plugin marketplace add smk-labs/claude-plugins
/plugin install readable@smk

The catalog

Get work done somewhere else

Plugin	What it does
cursor-delegate	Runs coding and writing tasks on your Cursor subscription's quota instead of Claude's. Claude plans and reviews, Cursor workers execute, one task or a parallel fleet. Long jobs run as short resumable legs, so a dropped connection costs one leg and never the work. Carries copy-writing-fa for Persian web copy, with fa-lint as the gate.

Keep a codebase honest

Plugin	What it does
spring-clean	Deep-cleans a repo, then gives it rules at both layers. spring-clean declares a scoreboard, deletes dead surfaces, moves dev docs out of the code tree, splits oversized files and draws package boundaries, and writes its plan to a numbered unit list so a long pass survives a dead context. workspace-rules then works out that repo's own rules from its own evidence and sorts each by what it hands the model: information a model cannot infer gets told where a session starts, anything a script could count gets counted as a linter setting, a test or a hook, proved red by name and green on an untouched tree, and the cap goes inside the check file itself.
portal-skills	Platform engineering and security. GitLab CI/CD and Helm charts for Kubernetes, pod rightsizing from real Prometheus data, a secure-coding baseline that applies while you write, and a deep OWASP reference.

Make the output readable