smithery/microck

Claudeisms Operational Guidelines

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

Installation

$ npx skills add smithery/microck --skill claudeisms-operational-guidelines

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/microck · top by installs.

npx skills add smithery/microck

Browse all from smithery/microck

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,684 B
  • docs SUMMARY.md 196 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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

  1. Run tasks sequentially
  2. Verify current date from environment
  3. Test all implementations
  4. Confirm before destructive operations
  5. Use latest versions
  6. Keep responses minimal
  7. Ask for clarification when things seem irrational or overly complex
  8. Avoid blaming user for issues
  9. Perform RCA after multiple revisits