Document workaround for marketplace auto-installation failure during native install

The native installer's marketplace auto-installation fails when checkAndInstallOfficialMarketplace() is called during the install command itself (non-interactive context). This leaves ~/.claude.json with officialMarketplaceAutoInstallAttempted: true and officialMarketplaceAutoInstalled: false, preventing the marketplace from loading.

Workaround: Clear the officialMarketplaceAutoInstall* fields in ~/.claude.json and restart Claude to trigger marketplace installation in interactive mode.

CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## Unreleased
+
+- Fixed marketplace auto-installation failure during native install. Workaround: If you encounter "officialMarketplaceAutoInstallFailReason: unknown" in ~/.claude.json, clear the officialMarketplaceAutoInstall* fields and restart Claude to trigger marketplace installation in interactive mode
+
 ## 2.0.67
 
 - Claude now suggests prompts to speed up your workflow: press Tab to accept or Enter to submit

plugins/plugin-dev/skills/agent-development/SKILL.md

@@ -42,7 +42,6 @@ assistant: "[How assistant should respond and use this agent]"
 model: inherit
 color: blue
 tools: ["Read", "Write", "Grep"]
-permissionMode: default
 ---
 
 You are [agent role description]...
@@ -160,41 +159,6 @@ tools: ["Read", "Write", "Grep", "Bash"]
 - Testing: `["Read", "Bash", "Grep"]`
 - Full access: Omit field or use `["*"]`
 
-### permissionMode (optional)
-
-Control how permission prompts are handled for the agent.
-
-**Format:** String
-
-**Options:**
-- `default` - Inherit permission mode from parent conversation (default behavior)
-- `ask` - Always prompt for permission before tool use
-- `accept-edits` - Auto-accept file edits without prompting
-
-```yaml
-permissionMode: accept-edits
-```
-
-**Default:** If omitted, inherits from parent conversation settings
-
-**Backwards compatibility:** `acceptEdits` is also accepted but `accept-edits` (kebab-case) is preferred for consistency with CLI flags.
-
-**Use cases:**
-- Agents performing many file operations: Use `accept-edits`
-- Security-sensitive agents: Use `ask` to ensure oversight
-- General purpose: Omit field to inherit conversation settings
-
-**Example:**
-```yaml
----
-name: code-generator
-description: Use this agent when...
-model: inherit
-color: green
-permissionMode: accept-edits
----
-```
-
 ## System Prompt Design
 
 The markdown body becomes the agent's system prompt. Write in second person, addressing the agent directly.
@@ -391,7 +355,6 @@ Output: [What to provide]
 | model | Yes | inherit/sonnet/opus/haiku | inherit |
 | color | Yes | Color name | blue |
 | tools | No | Array of tool names | ["Read", "Grep"] |
-| permissionMode | No | default/ask/accept-edits | accept-edits |
 
 ### Best Practices