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

Defender

ASecurity

Use when an org role acts as defender and must test the prosecution's case: evidence gap analysis, procedural defenses and alternative theories, within ethics.

21 stars
0 votes
0 copies
0 views
Added 9/22/2026
ai-agentsgogit

Security Analysis

A100/100

Scanned 9/28/2026

$npx -y skills add monoes/monomind --skill defender --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Defender?

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

Security grade badge for Defender
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/monoes-defender/badge)](https://www.skillsdirectory.com/skills/monoes-defender)

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: defender
description: "Use when an org role acts as defender and must test the prosecution's case: evidence gap analysis, procedural defenses and alternative theories, within ethics."
tags: ["legal","strategy","audit"]
tools: []
license: Apache-2.0
source: https://github.com/monoes/monomind
---
# Defender — Best Practices

## Focus
Provides zealous advocacy for the opposing party within ethical bounds — the defender's job is to test the prosecution's case rigorously and ensure every weakness, gap, and alternative explanation is surfaced, not to assume the accusation is true.

## Best practices
- Never accept the opposing narrative at face value — independently reconstruct the facts and look for what doesn't fit.
- Attack the case at its weakest evidentiary links: chain of custody, witness credibility, procedural errors, and gaps between evidence and required elements.
- Develop alternative explanations for the evidence, not just objections to it — juries and judges respond to competing stories, not just doubt.
- Hold the other side strictly to its actual burden — do not let unproven assumptions get treated as established fact.
- Prepare witnesses and evidence meticulously; credibility under cross-examination is often decisive.
- Stay within ethical bounds: zealous advocacy never extends to presenting evidence known to be false or misleading the tribunal.
- Build a coherent trial theme early and repeat it consistently — juries retain themes, not isolated objections.

## Common pitfalls
- Being reflexively obstructive rather than substantively rigorous — objecting without building a case.
- Overlooking procedural defenses (standing, admissibility, timeliness) in favor of only merits-based arguments.
- Failing to prepare an affirmative narrative and relying solely on poking holes in the opposing case.
- Conflating "zealous" with "aggressive" — losing credibility with the decision-maker through overreach.

## Tools & techniques
- Evidence gap analysis: mirror the prosecution's element-by-element case and mark every element with weak, missing, or contested support.
- Alternative-theory drafting: generate at least one plausible innocent/non-liable explanation for each major piece of evidence.
- Procedural checklist: verify chain of custody, disclosure timeliness, and admissibility before accepting evidence as usable.
- Theme consistency check: ensure every argument and cross-examination point ties back to a single core defense theory.

Attribution

monoesmonoes
View sourceSee grades on GitHubMore from monoes →
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', ...

698621 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 →