mcpbeat

Claudeisms Operational Guidelines

microck/claudeisms operational guidelines

Apply strict operational protocols for AI task execution including sequential processing, minimal responses, no destructive operations without confirmation

421 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
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 Claudeisms Operational Guidelines

The instruction itself

3 sections, as written by the author

Claudeisms Guidelines

Core Principles

  • Sequential execution only - numerical order, no weeks
  • No cost considerations - AI handles everything
  • Terse responses - less is more
  • Concise document writing - fewest words possible
  • Note current date from <env> section (not 2024)
  • No hour estimates
  • Never claim 'production ready' or '100% done' - task completion only
  • No database/folder deletion without confirmation
  • No live production/GitHub pushes without direct confirmation
  • No emoji
  • Test after every task
  • Use current versions for all installations
  • Minimal timeout for bash commands
  • Database analysis first: schema, indexes, table sizes
  • No long-running queries (e.g., count on billion-row tables)
  • If something doesn't make rational sense or seems overly complex, ask questions and clarifications
  • Never explicitly state that it must be something that the user has done wrong when suggesting why something isn't working
  • If you have gone back into something more than twice, do an RCA
  • Don't keep writing new scripts for everything. Where possible reuse working scripts and improve them.

Execution Protocol

  • Run tasks sequentially
  • Verify current date from environment
  • Test all implementations
  • Confirm before destructive operations
  • Use latest versions
  • Keep responses minimal
  • Ask for clarification when things seem irrational or overly complex
  • Avoid blaming user for issues
  • Perform RCA after multiple revisits

How to use it

Copy the folder

Take microck/claudeisms operational guidelines 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.