Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Claudeisms

ASecurity

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

393 stars
0 votes
0 copies
4 views
Added 12/19/2025
ai-agentsgobashgitdatabase

Security Analysis

A100/100

Scanned 2/12/2026

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

Installs into .claude/skills of the current project.

Are you the author of Claudeisms?

Add the live security badge to your README — it updates automatically with every re-scan.

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

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

Download with Pro
Files
SKILL.md
---
name: Claudeisms Operational Guidelines
description: Apply strict operational protocols for AI task execution including sequential processing, minimal responses, no destructive operations without confirmation
---

# 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

Attribution

MicrockMicrock
View sourceSee grades on GitHubMore from Microck →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

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 (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →