Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.niteshift.dev/llms.txt

Use this file to discover all available pages before exploring further.

Plugins are supported for Claude Code. For other model providers, contact support@niteshift.dev.
Plugins ship skills, slash commands, and other agent extensions to your repository’s tasks without committing them inside the repo. Niteshift uses Claude Code’s plugin model directly, so the same configuration works locally and in tasks.

​
How they work

A plugin lives inside a marketplace: a git repo with a .claude-plugin/marketplace.json manifest listing one or more plugins. Configure two things per repository at Settings → Repositories → [repo] → Plugins:
  • Marketplaces: where plugins come from. Add a GitHub shorthand (owner/repo, owner/repo@ref) or a full git URL.
  • Enabled plugins: which plugins to install, identified as plugin-name@marketplace-name. The marketplace name comes from the manifest’s name field.
Niteshift pre-installs the resolved plugins to your environment so they’re available to the agent on task start. We automatically add the claude-plugins-official marketplace, but you should add any others.

​
Importing from .claude/settings.json

If you already have plugins configured locally in Claude Code, drag your .claude/settings.json into the Plugins panel. Niteshift imports extraKnownMarketplaces and enabledPlugins directly, so the same config travels without translation.