config-guide
Reference guide for configuring @Claude agents — agents, agent scopes, identity profiles, presets, connections, rules, GitHub repositories, and custom instructions. Explains the inheritance model and configuration best practices.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-10
- Stars
- ★ 77
- Forks
- 22
01 前言 Front Matter
- name
- config-guide
- description
- Reference guide for configuring @Claude agents — agents, agent scopes, identity profiles, presets, connections, rules, GitHub repositories, and custom instructions. Explains the inheritance model and configuration best practices.
- when_to_use
- A user asks how to set up @Claude, how agent scopes/agents/profiles work, how configuration inherits across workspace and channels, how to add a GitHub repo or connection, or what the best practice is for read vs write access.
- allowed-tools
- Read
02 资源文件 5
- 参考文档agents-and-scopes.md2.3 KB
- 参考文档best-practices.md1.5 KB
- 参考文档connections-and-presets.md1.2 KB
- 参考文档github-and-instructions.md1.6 KB
- 参考文档identity-profiles.md2.0 KB
03 SKILL.md 正文
@Claude — Configuration Guide
@Claude is configured through a small set of layered objects in the claude.ai admin settings: agents, agent scopes, identity profiles, and the presets / connections / repos / instructions attached to them. The layering decides what any given session can see and do.
This guide is currently written for the Slack surface.
This skill is an index. Read the relevant reference file below for the topic the user is asking about — each is short and self-contained.
| Topic | Reference file |
|---|---|
| Agents, agent scopes, the resolution chain, and per-field inheritance | agents-and-scopes.md |
| Identity profiles, scopes, rules, credentials, repo permissions | identity-profiles.md |
| Presets, connections (OAuth / MCP), how to install one | connections-and-presets.md |
| GitHub repositories and custom instructions | github-and-instructions.md |
| Best practices: profile layout, read-only vs read/write, rollout | best-practices.md |
All reference files live alongside this SKILL.md in the same directory.
After explaining configuration, you can suggest the user run the
debug-plugins skill in a new Slack thread to confirm the change actually
took effect inside the container.
04 同仓库更多 Skills
snowflake-api
Run SQL against Snowflake — submit statements, poll async handles, fetch result partitions, cancel, and browse warehouses/databases/schemas/tables. Use this whenever the user wants to query Snowflake, ask "what tables are in this schema", check a warehouse's status, or mentions `snowflakecomputing.com`, `/api/v2/statements`, or a Snowflake account identifier (like `xy12345.us-east-1`). Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
sentry-api
Query and manage Sentry error-tracking data — list and search issues, drill into events and stack traces, inspect projects and releases, resolve/ignore issues, and pull stats. Use this whenever the user mentions a Sentry issue, crash, error group, or exception; pastes a sentry.io or self-hosted Sentry URL; asks "why is this erroring", "how many times has this happened", "what's the top error in {project}", "resolve this issue", or wants a Sentry-based digest — even if they don't say "API". Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
salesforce-api
Query, read, create, update, and describe Salesforce records — Accounts, Contacts, Opportunities, Leads, Cases, and custom objects. Use this whenever the user wants to look up a Salesforce record, run a SOQL query, update an Opportunity, check an object's fields, or asks "what's in Salesforce" — even if they don't say "API". Also use it for any URL under *.salesforce.com / *.lightning.force.com or a mention of a Salesforce record ID or SOQL. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
redshift-api
Run SQL against Amazon Redshift — submit statements, poll status, page through results, and browse databases/schemas/tables. Use this whenever the user wants to query Redshift (provisioned cluster or Serverless), ask "what tables are in this schema", check a query's status, or mentions `redshift-data`, a Redshift cluster identifier / workgroup name, or a `redshift-data.{region}.amazonaws.com` endpoint. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
pagerduty-api
Query and manage PagerDuty — find out who's on call, list and manage incidents, read escalation policies and schedules, trace who got paged and why, acknowledge/resolve/snooze/escalate incidents, and create or update services. Use this whenever the user mentions PagerDuty, on-call, paging, escalation, an incident ID like `PXXXXXX` or `Q...`, asks "who's on call", "page the on-call", "ack this incident", "why wasn't I paged", or pastes a pagerduty.com URL — even if they don't say "API". Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
notion-api
Search, read, and write Notion pages, databases, and blocks. Use this whenever the user wants to find a page in Notion, read a database, add a row, create or append content to a page, or asks "what's in my Notion" — even if they don't say "API". Also use it for any URL under notion.so or a mention of a Notion page/database ID. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.