Skip to content
Back to skills

Claudisms

ASecurity

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

  • 393 stars
  • 0 votes
  • 0 copies
  • 5 views
  • Added December 19, 2025
ai-agentsgitdatabasedocumentation

Works with

  • claude code

Security analysis

A100/100

Pro scans all 20 files and shows the line behind each finding

Scanned February 12, 2026

npx -y skills add Microck/ordinary-claude-skills --skill claudisms --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Claudisms?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Claudisms
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/microck-claudisms/badge)](https://www.skillsdirectory.com/skills/microck-claudisms)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: claudisms
description: Claude Code plugin enforcing operational guidelines, terse responses, sequential execution, and no destructive operations without confirmation.
---

# 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

1. Process tasks sequentially (numbered order only)
2. Test after every completed task
3. Ask for confirmation before destructive operations
4. Keep markdown documentation to 200 words maximum
5. Provide terse, focused responses
6. Use current tool versions
7. Analyze databases before querying
8. Avoid long-running operations
9. 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.

Files in this skill

  • .claude-plugin/marketplace.json283 B
  • .claude-plugin/plugin.json400 B
  • .claude/skills/claudeisms/SKILL.md1.6 KB
  • .claudisms-settings321 B
  • .gitignore47 B
  • CLAUDE.md3.9 KB
  • LICENSE34.3 KB
  • List-Of-Claudeisms.md8.6 KB
  • README.md5.8 KB
  • RELEASE-NOTES-2.1.1.md3.9 KB
  • SETTINGS.md5.9 KB
  • SKILL.md1.9 KB
  • SLASH-COMMANDS-QUICKSTART.md6.6 KB
  • bin/set-claudisms9.4 KB
  • claude-plugin-uninstall.sh7.9 KB
  • claude-plugin.json400 B
  • clean-install.sh514 B
  • commands/claudisms-reload.md169 B
  • commands/claudisms-reload.sh1.3 KB
  • commands/claudisms-settings.md164 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…