#1377 Kiro CLI v3 permissions: no capability covers disclose_context (skill loading)

Problem

When using Kiro CLI v3's permissions system (~/.kiro/settings/permissions.yaml), there is no documented capability value that covers the disclose_context tool (skill activation). Even with a fully permissive config that allows fs_read, fs_write, shell, web_search, web_fetch, and mcp, the agent still prompts for permission every time it loads a skill.

This affects any swamp user who relies on the swamp skill loading at session start (per the AGENTS.md / swamp-rules guidance). The prompt fires on every single session, which defeats the purpose of declarative permissions.

Context

• Kiro CLI v3 permissions docs: https://kiro.dev/docs/cli/v3/permissions/
• The disclose_context tool is how skills load their full instructions into context
• The swamp skill is configured to auto-activate when swamp models exist in a repo
• Users who set up allow-by-default permissions still get prompted because disclose_context doesn't match any configured capability

Impact

Every swamp user on Kiro CLI v3 will hit this friction on every session start. The more skills a workspace defines, the more prompts fire before the agent can do anything useful.

Request

1. Document which capability name in permissions.yaml covers skill/context loading (if one exists today)
2. If none exists, add one (e.g. skill or context) so users can pre-authorize skill activation
3. Consider whether workspace-defined skills (in .kiro/skills/) should be implicitly trusted without requiring a permission rule — they're already in the user's repo and version-controlled