René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"fix: error when skill/exclude filters are used with native install mode","articleBody":"## Summary\n\nWhen a plugin uses `install: native`, allagents delegates installation to the client's native plugin system (e.g., `claude plugin install`). Native plugin systems install plugins as whole units with no per-artifact filtering — you get all skills, hooks, commands, agents, and MCP servers, or none.\n\nHowever, allagents currently allows users to configure `skills` and `exclude` filters on plugins that use native install mode. These filters silently do nothing, which is misleading.\n\n```yaml\nplugins:\n  - source: superpowers@claude-plugins-official\n    install: native\n    skills:\n      - test-driven-development  # ← has no effect in native mode\n    exclude:\n      - \"hooks/**\"               # ← has no effect in native mode\n```\n\n## Expected behavior\n\n**TUI (interactive mode):** Grey out / hide the skill selection UI when native install mode is selected. Users shouldn't be offered choices that have no effect.\n\n**Headless mode:** Error with a message like: \"skill/exclude filters are not supported for native plugins. Change to `install: file` to use filters.\"\n\n## Context\n\nValidated by testing `claude plugin disable/enable` — Claude Code's native plugin system only supports whole-plugin enable/disable via `settings.json` (`enabledPlugins` map). There is no per-skill, per-hook, per-command, or per-agent toggle.\n\nSimilarly, `npx plugins` (open-plugin format) only supports whole-plugin add/remove with no artifact-level control.","author":{"url":"https://github.com/christso","@type":"Person","name":"christso"},"datePublished":"2026-03-27T03:53:18.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/338/allagents/issues/338"}