本文へ移動
cccskills
無料GitHub で公開

salesforce-admin

Router for the 261 SfSkills `admin` skill packages. Declarative Salesforce configuration: objects, fields, record types, page layouts, permission sets, reports, the record-access model (OWD, role hierarchy, sharing rules), and the requirements work that precedes them. Use when the request mentions custom object, custom field, picklist, record type, page layout, permission set, profile, validation rule, report, dashboard, queue, approval process, user setup, sharing rule, org-wide default, OWD, role hierarchy, record access, record visibility, who can see this record, duplicate rule, matching rule, duplicate prevention, clean up duplicates, merge governance, Spring release, seasonal release, Release Updates, Sandbox Preview. Finds and opens the exact skill package to read; it does not contain the guidance itself.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md7.7 KB
  • references/skill-index.md70.7 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Salesforce admin — SfSkills domain router

Declarative Salesforce configuration: objects, fields, record types, page layouts, permission sets, reports, the record-access model (OWD, role hierarchy, sharing rules), and the requirements work that precedes them.

261 skill packages live under ${CLAUDE_PLUGIN_ROOT}/skills/admin/<slug>/SKILL.md. They are not loaded — reach them by path, on demand.

Generated by scripts/build_plugin.py. Do not hand-edit.

How to find the right skill

Three mechanisms, listed in order of reliability on a fresh install. Use the first one that is available; do not stop at a guess.

1. The shipped roster (always works, no setup). Read references/skill-index.md next to this file. It lists every admin skill package with a one-line gloss, generated from registry/skills.json. Scan it and pick by name.

2. The MCP server (fast, needs the sfskills-mcp server connected). Call the search_skill tool with the user's phrasing and domain: "admin". It returns ranked skill ids. get_skill then returns the package contents.

3. The search CLI (fast, needs a locally built index).

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/search_knowledge.py" "<the user's question>" --domain admin --json

This needs vector_index/, which is not shipped — it is gitignored and must be built once per clone:

cd "${CLAUDE_PLUGIN_ROOT}" && python3 -m pip install -r requirements.txt && python3 scripts/build_index.py

If the command errors or reports Coverage: NONE, fall back to mechanism 1 rather than telling the user the topic is uncovered.

Then read the package. Open the exact ${CLAUDE_PLUGIN_ROOT}/skills/<domain>/<slug>/SKILL.md the lookup returned, plus its references/gotchas.md and references/llm-anti-patterns.md. Do not answer from this router: it is a map, not the territory.

Featured entry points

Curated starting points when the request is broad or the lookup is ambiguous. This is a shortlist, not the catalogue — the roster at references/skill-index.md has all 261.

  • ${CLAUDE_PLUGIN_ROOT}/skills/admin/object-creation-and-design/SKILL.md — start here for any new sObject — naming, relationships, and the fields you will regret later
  • ${CLAUDE_PLUGIN_ROOT}/skills/admin/custom-field-creation/SKILL.md — field types, FLS, and the ones that cannot be changed after data lands
  • ${CLAUDE_PLUGIN_ROOT}/skills/admin/validation-rules/SKILL.md — declarative enforcement, and where a validation rule fights automation
  • ${CLAUDE_PLUGIN_ROOT}/skills/admin/record-types-and-page-layouts/SKILL.md — record type strategy before it multiplies out of control
  • ${CLAUDE_PLUGIN_ROOT}/skills/admin/permission-set-architecture/SKILL.md — the permission-set-first access model that replaces profiles
  • ${CLAUDE_PLUGIN_ROOT}/skills/admin/user-management/SKILL.md — user lifecycle, licences, freeze vs deactivate, and integration users
  • ${CLAUDE_PLUGIN_ROOT}/skills/admin/duplicate-management/SKILL.md — matching rules and duplicate rules, including the person-account edge cases
  • ${CLAUDE_PLUGIN_ROOT}/skills/admin/reports-and-dashboards-fundamentals/SKILL.md — report types, folder sharing, and why a report returns the wrong rows

Decision trees

Read the tree before activating a skill when the request could be solved more than one way, and cite the branch that decided it.

  • ${CLAUDE_PLUGIN_ROOT}/standards/decision-trees/automation-selection.md — read before choosing a declarative automation over Apex
  • ${CLAUDE_PLUGIN_ROOT}/standards/decision-trees/sharing-selection.md — read before designing an object's access model

Canonical templates

Do not hand-roll an idiom that already exists. Copy from ${CLAUDE_PLUGIN_ROOT}/templates/admin/ and rename in the consuming project; never edit the template in place.

  • ${CLAUDE_PLUGIN_ROOT}/templates/admin/naming-conventions.md
  • ${CLAUDE_PLUGIN_ROOT}/templates/admin/permission-set-patterns.md
  • ${CLAUDE_PLUGIN_ROOT}/templates/admin/validation-rule-patterns.md
  • ${CLAUDE_PLUGIN_ROOT}/templates/admin/README.md — the full list

Run-time agents for this domain

Invoke one of these subagents when the ask is a whole workflow rather than a single question:

  • assignment-and-auto-response-rules-designer — Design or audit Assignment + Auto-Response rules
  • audit-router — Run the SfSkills audit-router run-time agent
  • automation-migration-router — Run the SfSkills automation-migration-router run-time agent
  • build-doc-keeper — one requirement in, a verified build out
  • build-planner — one requirement in, a verified build out
  • business-hours-and-holidays-configurator — Design or audit Business Hours + Holidays
  • change-impact-planner — Change Impact Planner
  • config-workbook-author — Compile the canonical 10-section Salesforce Configuration Workbook
  • csv-to-object-mapper — Map a CSV to an sObject for a data load
  • custom-metadata-and-settings-designer — Design or audit Custom Metadata Types + Custom Settings
  • email-template-modernizer — Audit and plan email template modernization
  • entitlement-and-milestone-designer — Design or audit Entitlement Processes + Milestones
  • experience-cloud-admin-designer — Design or audit an Experience Cloud site admin setup
  • field-impact-analyzer — Score the blast radius of renaming or deleting a field
  • fit-gap-analyzer — Fit-gap a backlog against a target Salesforce org
  • knowledge-article-taxonomy-agent — Design or audit Knowledge taxonomy
  • lead-routing-rules-designer — Design or audit lead routing
  • metadata-builder — Build one declarative step of a build plan into deploy-ready metadata
  • object-designer — Design a Setup-ready sObject from a business concept
  • omni-channel-routing-designer — Design or audit Omni-Channel routing
  • path-designer — Design or audit a Sales/Service Path
  • permission-set-architect — Design or audit Permission Sets + Permission Set Groups
  • plan-verifier — Try to refute the plan before a human approves it
  • process-flow-mapper — Map a process narrative to a Salesforce-aware swim-lane flow
  • profile-to-permset-migrator — Decompose a Profile into Permission Sets + PSGs
  • requirements-clarifier — Ask every question the skills say must be asked before configuring
  • sales-stage-designer — Design or audit Opportunity sales stages
  • salesforce-learning-guide — Research and teach one Salesforce topic with current evidence, citations, practice, and knowledge checks
  • story-drafter — Draft a Salesforce-aware INVEST story backlog
  • user-access-diff — Side-by-side access comparison between two Salesforce users

Rules

  1. Answer from the opened admin package, never from this router.
  2. Cite the skill id and, where one applied, the decision-tree branch.
  3. Never claim a topic is uncovered without pasting lookup output.
  4. Never deploy to an org.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use this skill when writing test-first, behavior-driven acceptance criteria in Given/When/Then format for a Salesforce user story. Covers happy path, edge cases, negative paths, permission boundaries, and data-state preconditions so the AC block can drive UAT scripts and Apex test design downstream. Trigger keywords: given when then, gherkin, behavior driven AC, test first acceptance criteria, scenario outline, BDD acceptance criteria. NOT for the user-story format itself (use admin/user-story-writing-for-salesforce). NOT for UAT script writing (use admin/uat-test-case-design). NOT for Apex test method generation (use agents/test-class-generator). NOT for high-level UAT planning (use admin/uat-and-acceptance-criteria). More triggers: acceptance criteria record, ac_id, req_id on a criterion, artefact under test, negative case for a rule-type requirement, no-match fall-through criterion, oracle for a Then clause, test type apex flow manual, criteria linter, check_ac_format.py, --manifest-dir.

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

Task and Event objects: polymorphic WhatId/WhoId, Activity object model, ActivityHistory vs OpenActivity, activity timeline customization, bulk task creation, Einstein Activity Capture boundaries. NOT for turning on EAC or calendar sync — use admin/einstein-activity-capture-setup. NOT for Email-to-Case — use admin/case-management-setup. Covers ActivitiesSettings metadata, enableActivities, shared Task/Event custom fields and FLS, TaskStatus value sets, Shared Activities and TaskRelation/EventRelation, recurring and child activities, and partial-success bulk DML on Task.

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

Design Invocable Apex actions that return deterministic, agent-friendly errors instead of surfacing raw exceptions to the LLM. NOT for authoring the action itself — @InvocableMethod schema, labels, security context — use agentforce/custom-agent-actions-apex. NOT for the Apex tests that force each error branch — use agentforce/agent-action-unit-tests.

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

Use when designing how an Agentforce agent extracts structured input parameters (slots) from a user's natural-language utterance to invoke an action. Triggers: 'agent extract date from user', 'agent action argument extraction', 'agentforce slot filling', 'agent invocable input mapping', 'agent fails to fill required parameter'. NOT for action authoring (use agentforce/agent-actions) or for prompt-template variable binding (use agentforce/prompt-builder-templates).

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

Apex test patterns for @InvocableMethod agent actions: per-reason-code branch coverage, bulk safety, callout mocking, deterministic assertions. NOT for testing whether the agent routes to the right topic or answers well — use agentforce/agent-testing-and-evaluation. NOT for designing the error envelope the tests assert on — use agentforce/agent-action-error-handling.

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

Designing or reviewing Agentforce actions: Flow actions, Apex invocable actions, prompt-template actions, action naming, input and output contracts, confirmation requirements, and safe error behavior. Triggers: 'agent actions', 'build an agent that can look up an order', 'make the agent able to check order status', 'give the agent a capability', 'agent that can retrieve a record', 'flow action for agent', 'agent invocable action', 'action schema design'. NOT for writing the Apex class itself — use agentforce/custom-agent-actions-apex. NOT for the reason_code error envelope that stops an agent retry loop — use agentforce/agent-action-error-handling.

日本語の概要は準備中です。原文の説明を表示しています。

PranavNagrecha/AwesomeSalesforceSkills192026年10月4日 更新

PranavNagrecha のスキルをすべて見る

このスキルの問題を報告する