Local Conf
- Updated July 20, 2026
- snjnlsn/snjnlsn-marketplace
local_conf is an agent skill that holds your personal configuration for the snjnlsn Claude Code marketplace plugin layout.
About
local_conf is a minimal marketplace plugin entry that gives developers a first-class place for personal Claude Code configuration inside the snjnlsn-marketplace repository structure. You reach for it during Build/agent-tooling when you are standardizing how your assistant loads paths, feature flags, or user-specific defaults across projects. Public metadata only labels it as personal configuration; detailed keys and formats likely live in the plugin folder rather than the short README Prism indexed. It does not implement product features for end users—it versions the ergonomics of your own agent session. Pair it with overrides when you both patch plugin behavior and maintain baseline settings. Tag confidence is lower until SKILL.md enumerates config schema; treat installs as review-the-source for secrets and paths before sharing the repo.
- Dedicated “My personal configuration” slot in snjnlsn-marketplace under ./plugins/local_conf
- Separates private settings from shared marketplace plugins and overrides
- Source path ./plugins/local_conf for reproducible per-machine or per-repo agent prefs
- Lightweight meta skill—expect config files rather than application business logic
- Natural companion to overrides when tailoring Claude Code plugin stacks
Local Conf by the numbers
- Data as of Jul 21, 2026 (Skillselion catalog sync)
/plugin marketplace add snjnlsn/snjnlsn-marketplace/plugin install local_conf@snjnlsn-marketplaceAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Last updated | July 20, 2026 |
|---|---|
| Repository | snjnlsn/snjnlsn-marketplace ↗ |
What it does
Store and load your personal Claude Code / marketplace configuration in one named plugin instead of scattering dotfiles.
Who is it for?
Best when you maintain snjnlsn-marketplace (or clones) and want git-tracked personal agent defaults.
Skip if: Skip if you need org-wide secrets management, or developers and do not use Claude Code marketplace plugins at all.
When should I use this skill?
When loading or editing your personal configuration via the snjnlsn-marketplace local_conf plugin (./plugins/local_conf).
What you get
You centralize personal agent configuration under ./plugins/local_conf so the same setup loads with your marketplace checkout.
- Personal configuration files under the local_conf plugin
- Repeatable agent defaults tied to your marketplace checkout
Files
My personal configuration
local_conf
Source: ./plugins/local_conf
{ "name": "local_conf", "source": "./plugins/local_conf", "description": "My personal configuration" }
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10How it compares
A repo-local agent config package, not a cloud-hosted team settings service.
FAQ
Who is local_conf for?
It is for Claude Code users who organize tooling through snjnlsn-marketplace and want a dedicated plugin for private, personal settings.
When should I use local_conf?
Use it in Build/agent-tooling when you first stand up or clone your marketplace and need a stable place for paths, toggles, and personal defaults before daily coding.
Is local_conf safe to install?
Personal config often touches paths and API keys—review the Security Audits panel on this Prism page and never commit secrets; keep sensitive values in local-only files.