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

Behavior

ASecurity

Manage AIWG behavior bundles that bind reactive directives and toolset configurations to specific agent types

211 stars
0 votes
0 copies
1 views
Added 9/21/2026
ai-agentsbashreactexpressgit

Works with

cli

Security Analysis

A100/100

Scanned 9/21/2026

$npx -y skills add jmagly/ai-writing-guide --skill behavior --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Behavior?

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

Security grade badge for Behavior
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jmagly-behavior-482c27e8/badge)](https://www.skillsdirectory.com/skills/jmagly-behavior-482c27e8)

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
---
namespace: aiwg
name: behavior
platforms: [all]
description: Manage AIWG behavior bundles that bind reactive directives and toolset configurations to specific agent types
---

# Behavior

You manage AIWG behavior bundles — YAML artifacts that bind reactive directives and toolset configurations to specific agent types. Behaviors are the newest AIWG artifact type and are primarily deployed to OpenClaw (`~/.openclaw/behaviors/`).

## Triggers

Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):

- "what behaviors are installed" → list subcommand
- "show me the coding-strict behavior" → info subcommand
- "apply strict mode to the software-implementer" → apply subcommand
- "remove the no-internet behavior from my agent" → remove subcommand
- "behavior bundles" → list subcommand

## Trigger Patterns Reference

| Pattern | Example | Action |
|---------|---------|--------|
| List behaviors | "list behaviors" | Run `aiwg behavior list` |
| Show detail | "show behavior coding-strict" | Run `aiwg behavior info coding-strict` |
| Apply behavior | "apply coding-strict to software-implementer" | Run `aiwg behavior apply coding-strict --to software-implementer` |
| Remove behavior | "remove coding-strict from software-implementer" | Run `aiwg behavior remove coding-strict --from software-implementer` |
| Inspect source | "where are behaviors stored?" | Check `agentic/code/*/behaviors/` and `~/.openclaw/behaviors/` |

## Behavior

When triggered:

1. **Extract intent**:
   - Which subcommand: `list`, `info`, `apply`, or `remove`?
   - Is a behavior name mentioned?
   - Is an agent type mentioned (for `apply`/`remove`)?

2. **Run the appropriate command**:

   ```bash
   # List all available behaviors
   aiwg behavior list

   # Show details for a specific behavior
   aiwg behavior info <name>

   # Apply a behavior to an agent type
   aiwg behavior apply <name> --to <agent-type>

   # Remove a behavior from an agent type
   aiwg behavior remove <name> --from <agent-type>
   ```

3. **Understand behavior structure**: A behavior YAML bundle contains three sections:
   - `directives` — What the agent should always do or avoid in this operational context
   - `toolset` — Tool permissions and configuration overrides for this context
   - `inputs` — Variable parameters the behavior accepts at apply time

4. **Know the storage locations**:
   - **Source**: `agentic/code/*/behaviors/` (version-controlled, ships with framework)
   - **Deployed**: `~/.openclaw/behaviors/` (active, read by OpenClaw at runtime)
   - Deployment happens automatically during `aiwg use` for OpenClaw targets

5. **Report results** — For `list`, show name and description for each. For `info`, show the full bundle structure. For `apply`/`remove`, confirm the change.

## Examples

### Example 1: List available behaviors

**User**: "What behaviors are available?"

**Extraction**: List request, no filter

**Action**:
```bash
aiwg behavior list
```

**Response**: "3 behaviors available:
- `coding-strict` — Enforce code review, no direct pushes, require tests before merge
- `no-external-calls` — Block all outbound HTTP; toolset restricted to Read/Write/Edit/Bash(local)
- `audit-mode` — Read-only directives, all writes logged to `.aiwg/audit/`, no destructive operations"

---

### Example 2: Inspect a specific behavior

**User**: "Show me what coding-strict does"

**Extraction**: Info request for `coding-strict`

**Action**:
```bash
aiwg behavior info coding-strict
```

**Response**: Shows the full YAML bundle — directives (require tests, no force push, enforce PR review), toolset (Read, Write, Edit, Bash with git restrictions), and any input variables.

---

### Example 3: Apply a behavior

**User**: "Apply no-external-calls to the software-implementer agent"

**Extraction**: Apply `no-external-calls` to `software-implementer`

**Action**:
```bash
aiwg behavior apply no-external-calls --to software-implementer
```

**Response**: "Applied `no-external-calls` to `software-implementer`. Deployed to `~/.openclaw/behaviors/software-implementer/no-external-calls.yaml`. Outbound HTTP is now blocked for that agent type."

---

### Example 4: Remove a behavior

**User**: "Remove coding-strict from the test-engineer"

**Extraction**: Remove `coding-strict` from `test-engineer`

**Action**:
```bash
aiwg behavior remove coding-strict --from test-engineer
```

**Response**: "Removed `coding-strict` from `test-engineer`. The behavior file has been deleted from `~/.openclaw/behaviors/test-engineer/`."

## Clarification Prompts

If the user's intent is ambiguous:

- "Which behavior would you like to inspect? (run `aiwg behavior list` to see all available)"
- "Which agent type should this behavior be applied to?"
- "Did you mean to `apply` this behavior or just view it with `info`?"

## References

- @$AIWG_ROOT/src/cli/handlers/daemon.ts — Behavior command handler
- @$AIWG_ROOT/docs/cli-reference.md — CLI reference
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/agent-deployment.md — Agent deployment rule
- @$AIWG_ROOT/docs/development/aiwg-development-guide.md — Source vs output boundary (behaviors are source artifacts in `agentic/code/*/behaviors/`)

Attribution

jmaglyjmagly
View sourceSee grades on GitHubMore from jmagly →
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 →