You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
First time setup issues Unknown skill: arscontexta:setup #20
changed the title [-]Firs time setup issues Unknown skill: arscontexta:setup[/-][+]First time setup issues Unknown skill: arscontexta:setup[/+]on Feb 24, 2026
Manual installation with install-manifest generation → same issue
Clean CLI install via marketplace → same issue
Stripped plugin.json to minimal {name, description} → same issue
Full Claude Code restart between each attempt
Workaround found:
After multiple restarts of Claude Code (not just session restarts, but full CLI restarts), the skills eventually appeared. This suggests a race condition or caching issue in skill discovery — the plugin files are present but not indexed until some deferred process completes.
Suggestion: Could be related to how .install-manifests are generated or how the skill indexer reads the skills/ directory on startup.
Activity
[-]Firs time setup issues Unknown skill: arscontexta:setup[/-][+]First time setup issues Unknown skill: arscontexta:setup[/+]AnastasiyaW commentedon Mar 3, 2026
Additional findings
Environment: Claude Code CLI (latest), Windows 11
Reproduction steps:
claude plugin marketplace add→ added agenticnotetaking marketplaceclaude plugin install arscontexta@agenticnotetaking→ installed successfullyinstalled_plugins.json~/.claude/plugins/cache/agenticnotetaking/arscontexta/0.8.0/.mdfiles/arscontexta:setupreturns "Unknown skill"What we tried:
plugin.jsonto minimal{name, description}→ same issueWorkaround found:
After multiple restarts of Claude Code (not just session restarts, but full CLI restarts), the skills eventually appeared. This suggests a race condition or caching issue in skill discovery — the plugin files are present but not indexed until some deferred process completes.
Suggestion: Could be related to how
.install-manifestsare generated or how the skill indexer reads theskills/directory on startup.