openclaw - 💡(How to fix) Fix Feature Request: Per-binding skill filtering [1 comments, 2 participants]

Summary

Add a skills field to bindings, allowing the same agent to load different skill sets depending on which channel/binding is active.

Motivation

Currently, skill filtering is only available at the agent level (agents.list[].skills). This means if you want different skills in different channels, you need separate agents — each requiring its own bot token, session management, and config overhead.

A per-binding skills field would allow a single agent to adapt its capabilities based on context:

• Archive channel → loads archive/translate skills
• Art channel → loads image-generation skills
• Code review channel → loads GitHub/coding skills
• General channel → loads all skills

This is especially useful for setups with many specialized channels but limited agent slots (e.g., Discord bot token limits).

Proposed Config

{
  "bindings": [
    {
      "channel": "discord:123456",
      "agent": "shrimp-cracker",
      "skills": ["archive-reader-v2", "translate", "content-fetcher"]
    },
    {
      "channel": "discord:789012",
      "agent": "shrimp-cracker",
      "skills": ["image-generator", "openai-image-gen"]
    }
  ]
}

Behavior

• When skills is set on a binding, it overrides the agent-level skills for that session
• When skills is null or absent, falls back to the agent-level skills setting
• The agent-level skills remains as the default/fallback

Benefits

• Reduced agent overhead — one agent, many roles
• Context savings — only relevant skill descriptions are injected into the system prompt
• Cleaner architecture — no need to create dummy agents just for skill routing
• Familiar pattern — similar to how Claude Code filters tools per sub-agent

Current Workaround

Create separate agents per skill-set, each bound to specific channels. Works but does not scale well.