Namespace Access Governance

Use for namespace-org topology, namespace linking, Environment Hub inventory, package-developer access, and operation-specific least privilege. Owns Namespace-org topology, namespace linking, Environment Hub inventory, developer access, and least-privilege separation.

24 stars 1 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add forcedotcom/partner-ecosystem-agentic-kit

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add forcedotcom/partner-ecosystem-agentic-kit --skill namespace-access-governance
Manual install
git clone --depth 1 https://github.com/forcedotcom/partner-ecosystem-agentic-kit.git /tmp/partner-ecosystem-agentic-kit
mkdir -p ~/.claude/skills
cp -r /tmp/partner-ecosystem-agentic-kit/skills/namespace-access-governance ~/.claude/skills/namespace-access-governance

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

Follow the instructions below. Read [this skill's contract](references/skill-contract.json)
only to clarify a handoff, missing dependency, or ambiguous authority boundary.
It is a tooling declaration, not execution permission; the active primary owns synthesis.

# Namespace Access Governance

Own the partner decision described in the frontmatter. Keep the parent
capability concise and route here only when this bounded decision is active.

## Operating contract

- Route by the partner's decision, not by document title or keyword alone.
- Preserve the partner's goal across turns. Ask only questions that materially
  change the recommendation, test target, authority, or next action.
- Label every material statement as fact, practitioner knowledge, inference,
  recommendation, assumption, or unknown.
- Read `references/practitioner-knowledge.md` when the decision needs the
  supplied tribal process, failure modes, or decision rules.
- Read `references/source-refresh.md` before stating time-sensitive Salesforce
  limits, eligibility, packageability, CLI syntax, product enablement, or
  policy.
- Prefer practitioner knowledge first. Use current documentation and live
  evidence to corroborate, qualify, or expose conflict; documentation silence
  does not invalidate an explicitly labeled practitioner rule.

## Authority modes

- **Ask:** answer from supplied context and loaded references. Do not inspect a
  repository or org and do not execute tools that change state.
Read the full skill on GitHub

Details

Skill name
namespace-access-governance
Path
skills/namespace-access-governance/SKILL.md
License
Apache-2.0
Repo updated
10 November 2026

FAQ

What does the Namespace Access Governance skill do?

Use for namespace-org topology, namespace linking, Environment Hub inventory, package-developer access, and operation-specific least privilege. Owns Namespace-org topology, namespace linking, Environment Hub inventory, developer access, and least-privilege separation.

How do I install the Namespace Access Governance skill?

Claude Code plugin: /plugin marketplace add forcedotcom/partner-ecosystem-agentic-kit. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Namespace Access Governance popular?

It lives in forcedotcom/partner-ecosystem-agentic-kit, which has 24 GitHub stars and 1 forks.

Related skills

Advisor Capability Preflight

24

forcedotcom/partner-ecosystem-agentic-kit

Check and configure documentation capabilities before an ISV Partner Advisor interaction. Use when the advisor starts, when Salesforce Docs MCP or official-documentation access may be missing, when a customer asks to install or approve documentation tools, or when the active harness changes.

Writing & Content

Agentforce Implementation Advisor

24

forcedotcom/partner-ecosystem-agentic-kit

Use for Agentforce agent, topic, action, prompt template, orchestration, state, testing, packaging, scratch-shape, and UX implementation decisions. Owns Agent, topic, action, orchestration, state, testing, and UX implementation decisions.

AI, LLMs & Agents

Data 360 Implementation Advisor

24

forcedotcom/partner-ecosystem-agentic-kit

Use for Data 360 architecture, data-kit workflow, scratch entitlement, metadata packageability, activation ordering, and partner-solution integration decisions. Owns Data 360 architecture and implementation patterns that affect partner solutions and packaging.

Software Development

Nothing New Under the Sun

9

fahrellgiovanny/nothing-new-under-the-sun

Research-first scouting agent skill that runs BEFORE any build decision, new dependency, new system, or feature request. Search existing solutions (codebase, dependencies, packages, GitHub repos, APIs, SaaS, templates) before writing code. Output a REUSE / USE / FORK / BUY / INTEGRATE / BUILD recommendation with a required schema and evidence matrix. Uses five-component long-term business value framing. Trigger on new features, new systems, new dependencies, build-vs-buy decisions, or "build/add/we need X" requests. Do not trigger for bug fixes, small refactors, routine edits, docs, style/lint

Software Development

Development Environment

24

forcedotcom/partner-ecosystem-agentic-kit

Route and synthesize decisions about PBO Dev Hubs, namespaces, scratch org shape, persistent development orgs, demos, trials, provisioning, developer access, and environment lifecycle. Use when a partner asks which Salesforce org or environment should perform a development, test, demo, packaging, or customer-validation job.

Software Development

Perf Hints

9

omarkilani/perf-hints

Improve C++ (C++11+) performance using Abseil “Performance Hints” (Jeff Dean & Sanjay Ghemawat): estimation + profiling, API/bulk design, algorithmic wins, cache-friendly memory layout, fewer allocations, fast paths, caching, and compiler-friendly hot loops. Use for performance code reviews, refactors, and profiling-driven optimizations. Keywords: performance, latency, throughput, cache, allocation, memory layout, InlinedVector, string_view, Span, flat_hash_map, pprof, perf.

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.