René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"feat: separate plugin and skills","articleBody":"## Problem\n\nCurrently skills, hooks, and other artifacts need to be uniquely named otherwise links break — when conflicts are detected, a plugin-name or hash prefix is appended to the artifact folder name. This only works for specific marketplaces where they follow unique naming standards.\n\nThis is fine for internal plugins since we control the naming. But doesn't work for public plugins like superpowers which have names conflicting with other plugins.\n\n## Current Behavior\n\nWhen plugins are synced, skills are copied to client skill directories (e.g., `.claude/skills/`, `.agents/skills/`). The **folder name** on disk becomes the skill's identity — it's how clients discover and reference skills.\n\n**Current dedup logic** (`src/utils/skill-name-resolver.ts`):\n- No conflict → folder name as-is (e.g., `coding-standards/`)\n- Folder name conflicts across plugins → `{plugin}_{skill}` (e.g., `plugin-a_coding-standards/`)\n- Folder AND plugin name conflict → `{org}_{plugin}_{skill}` (e.g., `acme_plugin-a_coding-standards/`)\n\n### Why this breaks\n\nDedup only kicks in **when there's a conflict**. This means the same skill gets **different names depending on what other plugins are installed**:\n\n1. User installs `superpowers` plugin → skill lands as `brainstorming/`\n2. User installs another plugin that also has `brainstorming/` → both get renamed to `superpowers_brainstorming/` and `other_brainstorming/`\n\nAny hardcoded references to `brainstorming` (in AGENTS.md, other skills, etc.) **break silently** when step 2 happens.\n\n## Proposed Solution: Always-Namespaced Mode\n\nAdd a config option to **always prefix skill names** with the plugin namespace, regardless of conflicts:\n\n```yaml\n# workspace.yaml\nskillNamespace: always   # default: \"auto\" (current behavior)\n```\n\n| Mode | Behavior |\n|------|----------|\n| `auto` (default) | Current behavior — only prefix on conflict |\n| `always` | Every skill gets `{plugin}_{skill}` naming |\n\n## Implementation Guide\n\n### Key files\n\n| File | Change |\n|------|--------|\n| `src/models/workspace-config.ts` | Add `skillNamespace` field to schema |\n| `src/utils/skill-name-resolver.ts` | Add `mode` param to `resolveSkillNames()`, always-qualify path |\n| `src/core/sync.ts` | Thread config through `buildPluginSkillNameMaps()` calls (~lines 1841 and 2220) |\n| `tests/unit/utils/skill-name-resolver.test.ts` | Add `always` mode tests (existing tests cover current tiers) |\n| `docs/src/content/docs/reference/configuration.mdx` | Document new option |\n| `docs/src/content/docs/guides/plugins.mdx` | Update dedup section |\n\n### Implementation detail\n\nIn `src/utils/skill-name-resolver.ts`, add a `mode` parameter to `resolveSkillNames()`. When `always`, skip the \"no conflict\" fast path (line 90-101) and always qualify with plugin name.\n\n### Scope boundaries\n\n- Skills that reference other skills by name in their content (e.g., \"run the `brainstorming` skill first\") would still need to use the namespaced name. This is a documentation/convention problem, not a code problem.\n- The `{org}_{plugin}_{skill}` tier 3 disambiguator is still needed even in `always` mode if two plugins from different orgs have the same plugin name.\n\n## Related\n\n- PR #339 fixed a separate issue: **repository skills** (discovered from workspace repos, embedded as an index in AGENTS.md) had duplicates. Those now deduplicate by picking a winner (`.agents/` priority, then largest file). That is a different mechanism from plugin skill dedup — repo skills are pointers in an index, not copied files.","author":{"url":"https://github.com/christso","@type":"Person","name":"christso"},"datePublished":"2026-03-22T11:41:40.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/311/allagents/issues/311"}