mcpbeat

Claudisms

microck/claudisms

Claude Code plugin enforcing operational guidelines, terse responses, sequential execution, and no destructive operations without confirmation.

32k tokens
context cost
the whole folder, loaded on every use
28
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
320
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Microck/ordinary-claude-skills --skill claudisms

What comes with it

122 525 bytes besides the instruction
.claude-plugin/marketplace.json
.claude-plugin/plugin.json
.claudisms-settings
.gitignore
CLAUDE.md
LICENSE
List-Of-Claudeisms.md
README.md
RELEASE-NOTES-2.1.1.md
SETTINGS.md
SLASH-COMMANDS-QUICKSTART.md
bin/set-claudisms
claude-plugin-uninstall.sh
claude-plugin.json
clean-install.sh
commands/claudisms-reload.md
commands/claudisms-reload.sh
commands/claudisms-settings.md
commands/claudisms-settings.sh
examples/destructive-guard-demo.sh
hooks-handlers/before-destructive.sh
hooks-handlers/before-md-write.sh
hooks-handlers/session-start.sh
hooks.json
repair-install.sh
settings.example.json

The instruction itself

5 sections, as written by the author

Claudisms Operational Guidelines

A Claude Code plugin that enforces disciplined operational protocols for efficient, safe task execution with terse responses and sequential processing.

Core Principles

  • Sequential Execution: Process tasks numerically in strict order
  • Terse Responses: Keep responses to 1-2 sentences maximum
  • Code-First Approach: Prioritize code and automation over documentation
  • Safety First: No destructive operations without explicit confirmation
  • Conciseness: Minimal documentation (200 words max for markdown files)
  • Test Always: Test after every task completion
  • No False Claims: Never claim "production ready" or "100% complete"
  • Verification Required: No live production or GitHub pushes without direct confirmation

Key Features

  • Sequential execution protocols
  • Terse, efficient responses
  • Destructive operation safeguards
  • Test-after-every-task enforcement
  • RCA (Root Cause Analysis) requirement after 2+ revisits
  • No emojis or marketing language
  • Script reuse preference over recreation
  • Unix tool optimization (fd/rg over find/grep)

Operational Checklist

  • Process tasks sequentially (numbered order only)
  • Test after every completed task
  • Ask for confirmation before destructive operations
  • Keep markdown documentation to 200 words maximum
  • Provide terse, focused responses
  • Use current tool versions
  • Analyze databases before querying
  • Avoid long-running operations
  • Reuse and improve existing scripts

10. Conduct RCA on repeated issues

Installation

Install as a Claude Code plugin from the marketplace:

/plugin install claudisms

Then configure your settings as needed for your workflow.

How to use it

Copy the folder

Take microck/claudisms from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.