如何为Claude创建Skills：步骤与示例

如何创建技能：关键步骤、局限性和示例

了解如何编写定制技能，使Claude提供更强大、更有效的输出。

• 类别Claude Code代理
• 产品Claude应用
• 日期2025年11月19日
• 阅读时间5分钟
• 分享复制链接https://claude.com/blog/how-to-create-skills-key-steps-limitations-and-examples

技能 是扩展Claude在特定任务或领域能力的自定义指令。

当你通过SKILL.md文件创建技能时，你正在教Claude如何更有效地处理特定场景。技能的力量在于它们能够编码机构知识、标准化输出，并处理复杂的多步骤工作流程，而这些工作流程原本需要重复解释或投资构建自定义代理。

了解如何创建技能，将Claude从通用助手转变为针对你特定工作流程的专家，可以使用我们的技能创建器模板或手动创建。（专业提示：为了方便，我们建议使用此模板构建你的SKILL.md文件并在此基础上进行调整）。

5步创建技能

遵循此结构化方法，构建更可靠触发的技能。

1. 理解核心要求

在编写任何内容之前，明确你的技能解决什么问题。强大的技能解决具体需求，并具有可衡量的结果。“从PDF提取财务数据并格式化为CSV”优于“帮助我处理财务事务”，因为它指定了输入格式、操作和预期输出。

首先问自己：这个技能完成什么特定任务？什么触发条件应该激活它？成功是什么样的？边缘情况或局限性是什么？

2. 编写名称

你的技能需要三个核心组件：名称（清晰标识符）、描述（何时激活）和指令（如何执行）。实际上，名称和描述是SKILL.md文件中唯一影响触发的部分，也就是说，影响Claude为专业知识或工作流程调用技能的能力。

名称应该直接且具有描述性。使用小写字母和连字符（例如，pdf-editor、brand-guidelines）。保持简短清晰。

3. 编写描述字段

描述决定技能何时激活，使其成为最关键的部分。从Claude的角度编写，关注触发条件、能力和用例。

强大的描述平衡了多个要素：具体能力、清晰触发条件、相关背景和边界。

弱描述：

This skill helps with PDFs and documents.

强描述：

Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale. Use for document workflows and batch operations. Not for simple PDF viewing or basic conversions.

更强的版本为Claude提供了多个数据点：具体动词（提取、创建、合并）、具体用例（表单填写、批量操作）和清晰边界（不用于简单查看）。

4. 编写主要指令

你的指令应该结构化、可扫描且可操作。使用Markdown标题、项目符号表示选项，以及代码块表示示例。

使用清晰的分层结构：概述、前提条件、执行步骤、示例、错误处理和局限性。将复杂工作流程分解为具有清晰输入和输出的独立阶段。

包括展示正确用法的具体示例。指定技能不能做什么，以防止误用和管理期望。你的SKILL.md文件还可以包含额外的参考文件和资源，为触发技能时你要求代理执行的任务提供更多清晰度和指导。

5. 上传你的技能

取决于你在哪个Claude平台上构建，以下是如何上传技能以供使用：

• Claude.ai（Claude应用）：前往设置并在那里添加自定义技能。自定义技能需要Pro、Max、Team或Enterprise计划，并启用代码执行。此处上传的技能对每个用户是个人的——它们不会在组织范围内共享，也无法由管理员集中管理。
• Claude Code：在插件或项目根目录中创建

my-project/
├── skills/
│   └── my-skill/
│       └── SKILL.md

• Claude 开发者平台：通过 Skills API（/v1/skills 端点）上传技能。使用带有必需 beta 头部的 POST 请求：

curl -X POST "https://api.anthropic.com/v1/skills" \
  -H "x-api-key: $ANTHROPIC_API_KEY" \
  -H "anthropic-version: 2023-06-01" \
  -H "anthropic-beta: skills-2025-10-02" \
  -F "display_title=My Skill Name" \
  -F "files[]=@my-skill/SKILL.md;filename=my-skill/SKILL.md"

4. 测试与验证

在部署前，使用实际场景测试你的技能。系统性测试能揭示指令中的漏洞、描述中的歧义，以及只有在实际使用中才会出现的意外边缘情况。

创建一个涵盖三种场景的测试矩阵：

• 正常操作：使用技能应完美处理的典型请求进行测试。如果你构建了一个财务分析技能，尝试“分析微软最新财报”或“为这份 10-K 文件构建数据包”。这些基线测试确认你的指令按预期工作。
• 边缘情况：使用不完整或不寻常的输入进行测试。当数据缺失时会发生什么？当文件格式意外时？当用户提供模糊指令时？你的技能应优雅地处理这些情况——要么产生降级但有用的输出，要么解释需要什么才能继续。
• 超范围请求：使用看似相关但不应触发你的技能的任务进行测试。如果你构建了 NDA 审查技能，尝试请求“审查这份雇佣协议”或“分析这份租约”。技能应保持休眠，让其他技能或 Claude 通用能力处理该请求。

考虑实施以下测试以进行更深入验证：

• 触发测试： 技能是否在预期时激活？使用显式请求（“使用财务数据包技能分析这家公司”）和自然请求（“帮我了解这家公司的财务状况”）进行测试。当不相关时，它是否保持不激活？一个范围明确的技能知道何时不激活。测试相似但不同的请求以验证边界。
• 功能测试： 这些包括输出一致性（多次运行类似输入是否产生可比结果？）、可用性（不熟悉该领域的人能否成功使用？）以及文档准确性（你的示例是否与实际行为匹配？）。

5. 根据使用情况迭代

监控技能在实际使用中的表现。如果触发不一致，优化描述。如果输出意外变化，澄清指令。与提示词一样，最好的技能通过实际应用不断演进。

创建技能的一般最佳实践

这些原则有助于你创建可维护、可重用且真正有用的技能，而非理论性的技能。

从用例开始

不要投机性地编写技能。当你有真实、重复的任务时再构建它们。最好的技能解决你经常遇到的问题。

在创建技能之前，问问自己：我是否至少做过这个任务五次？我是否还会再做至少十次？如果是，那么技能就有意义。

定义成功标准——并将其包含在技能中

告诉Claude什么算是好的输出。如果你在创建财务报告，指定所需的章节、格式标准、验证检查和质量阈值。将这些标准包含在你的指令中，以便Claude能够自我检查。

使用技能创建者技能

该技能创建者技能 指导你创建结构良好的技能。它会提出澄清问题、建议描述改进，并帮助正确格式化指令。可在GitHub上的技能仓库 和直接通过Claude.ai获取，对于你的前几个技能尤其有价值。

技能的限制与考量

理解技能的工作方式及其边界，有助于你设计更有效的技能并设定合理的期望。

技能触发

Claude会根据你的请求评估技能描述以确定相关性。这不是关键词匹配——Claude理解语义关系。然而，模糊的描述会降低触发准确性。

如果多个技能涉及复杂任务的不同方面，它们可以同时激活。过于通用的描述会导致不适当的激活，而缺少用例则会导致漏触发。

适当的文件大小

编写技能时，避免用不必要的内容膨胀上下文窗口。考虑每条信息是否每次都需要加载，还是仅在有条件时加载。

使用"菜单"方法：如果你的技能涵盖多个不同的流程或选项，SKILL.md应描述可用的内容，并使用相对路径引用每个单独的文件。然后Claude只读取与用户任务相关的文件，而在此次对话中不涉及其他文件。

这些单独的文件不必代表互斥的路径。关键原则是将内容分解为合理的块，并让Claude根据手头任务选择所需内容。

‍真实世界的技能示例

技能示例#1：docx创建技能

#---name: docx
description: "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks"
license: Proprietary. LICENSE.txt has complete terms
---# DOCX creation, editing, and analysis## OverviewA user may ask you to create, edit, or analyze the contents of a .docx file. A .docx file is essentially a ZIP archive containing XML files and other resources that you can read or edit. You have different tools and workflows available for different tasks.
## Workflow Decision Tree### Reading/Analyzing ContentUse "Text extraction" or "Raw XML access" sections below
### Creating New DocumentUse "Creating a new Word document" workflow
### Editing Existing Document-**Your own document + simple changes**  Use "Basic OOXML editing" workflow
-**Someone else's document**  Use **"Redlining workflow"** (recommended default)
-**Legal, academic, business, or government docs**  Use **"Redlining workflow"** (required)
## Reading and analyzing content### Text extractionIf you just need to read the text contents of a document, you should convert the document to markdown using pandoc. Pandoc provides excellent support for preserving document structure and can show tracked changes:
```bash
# Convert document to markdown with tracked changes
pandoc --track-changes=all path-to-file.docx -o output.md
# Options: --track-changes=accept/reject/all
```### Raw XML accessYou need raw XML access for: comments, complex formatting, document structure, embedded media, and metadata. For any of these features, you'll need to unpack a document and read its raw XML contents.
#### Unpacking a file`python ooxml/scripts/unpack.py <office_file> <output_directory>`#### Key file structures*`word/document.xml` - Main document contents
*`word/comments.xml` - Comments referenced in document.xml
*`word/media/` - Embedded images and media files
* Tracked changes use `<w:ins>` (insertions) and `<w:del>` (deletions) tags
## Creating a new Word documentWhen creating a new Word document from scratch, use **docx-js**, which allows you to create Word documents using JavaScript/TypeScript.
### Workflow1.**MANDATORY - READ ENTIRE FILE**: Read [`docx-js.md`](docx-js.md) (~500 lines) completely from start to finish. **NEVER set any range limits when reading this file.** Read the full file content for detailed syntax, critical formatting rules, and best practices before proceeding with document creation.
2. Create a JavaScript/TypeScript file using Document, Paragraph, TextRun components (You can assume all dependencies are installed, but if not, refer to the dependencies section below)
3. Export as .docx using Packer.toBuffer()
## Editing an existing Word documentWhen editing an existing Word document, use the **Document library** (a Python library for OOXML manipulation). The library automatically handles infrastructure setup and provides methods for document manipulation. For complex scenarios, you can access the underlying DOM directly through the library.
### Workflow1.**MANDATORY - READ ENTIRE FILE**: Read [`ooxml.md`](ooxml.md) (~600 lines) completely from start to finish. **NEVER set any range limits when reading this file.** Read the full file content for the Document library API and XML patterns for directly editing document files.
2. Unpack the document: `python ooxml/scripts/unpack.py <office_file> <output_directory>`3. Create and run a Python script using the Document library (see "Document Library" section in ooxml.md)
4. Pack the final document: `python ooxml/scripts/pack.py <input_directory> <office_file>`The Document library provides both high-level methods for common operations and direct DOM access for complex scenarios.
## Redlining workflow for document reviewThis workflow allows you to plan comprehensive tracked changes using markdown before implementing them in OOXML. **CRITICAL**: For complete tracked changes, you must implement ALL changes systematically.
**Batching Strategy**: Group related changes into batches of 3-10 changes. This makes debugging manageable while maintaining efficiency. Test each batch before moving to the next.
**Principle: Minimal, Precise Edits**When implementing tracked changes, only mark text that actually changes. Repeating unchanged text makes edits harder to review and appears unprofessional. Break replacements into: [unchanged text] + [deletion] + [insertion] + [unchanged text]. Preserve the original run's RSID for unchanged text by extracting the `<w:r>` element from the original and reusing it.
Example - Changing "30 days" to "60 days" in a sentence:
```python
# BAD - Replaces entire sentence
'<w:del><w:r><w:delText>The term is 30 days.</w:delText></w:r></w:del><w:ins><w:r><w:t>The term is 60 days.</w:t></w:r></w:ins>'
# GOOD - Only marks what changed, preserves original <w:r> for unchanged text
'<w:r w:rsidR="00AB12CD"><w:t>The term is </w:t></w:r><w:del><w:r><w:delText>30</w:delText></w:r></w:del><w:ins><w:r><w:t>60</w:t></w:r></w:ins><w:r w:rsidR="00AB12CD"><w:t> days.</w:t></w:r>'
```### Tracked changes workflow1.**Get markdown representation**: Convert document to markdown with tracked changes preserved:
```bash
   pandoc --track-changes=all path-to-file.docx -o current.md
   ```2.**Identify and group changes**: Review the document and identify ALL changes needed, organizing them into logical batches:
**Location methods** (for finding changes in XML):
   - Section/heading numbers (e.g., "Section 3.2", "Article IV")
   - Paragraph identifiers if numbered
   - Grep patterns with unique surrounding text
   - Document structure (e.g., "first paragraph", "signature block")
   -**DO NOT use markdown line numbers** - they don't map to XML structure
**Batch organization** (group 3-10 related changes per batch):
   - By section: "Batch 1: Section 2 amendments", "Batch 2: Section 5 updates"
   - By type: "Batch 1: Date corrections", "Batch 2: Party name changes"
   - By complexity: Start with simple text replacements, then tackle complex structural changes
   - Sequential: "Batch 1: Pages 1-3", "Batch 2: Pages 4-6"
3.**Read documentation and unpack**:
   -**MANDATORY - READ ENTIRE FILE**: Read [`ooxml.md`](ooxml.md) (~600 lines) completely from start to finish. **NEVER set any range limits when reading this file.** Pay special attention to the "Document Library" and "Tracked Change Patterns" sections.
   -**Unpack the document**: `python ooxml/scripts/unpack.py <file.docx> <dir>`   -**Note the suggested RSID**: The unpack script will suggest an RSID to use for your tracked changes. Copy this RSID for use in step 4b.
4.**Implement changes in batches**: Group changes logically (by section, by type, or by proximity) and implement them together in a single script. This approach:
   - Makes debugging easier (smaller batch = easier to isolate errors)
   - Allows incremental progress
   - Maintains efficiency (batch size of 3-10 changes works well)
**Suggested batch groupings:**   - By document section (e.g., "Section 3 changes", "Definitions", "Termination clause")
   - By change type (e.g., "Date changes", "Party name updates", "Legal term replacements")
   - By proximity (e.g., "Changes on pages 1-3", "Changes in first half of document")
   For each batch of related changes:
**a. Map text to XML**: Grep for text in `word/document.xml` to verify how text is split across `<w:r>` elements.
**b. Create and run script**: Use `get_node` to find nodes, implement changes, then `doc.save()`. See **"Document Library"** section in ooxml.md for patterns.
**Note**: Always grep `word/document.xml` immediately before writing a script to get current line numbers and verify text content. Line numbers change after each script run.
5.**Pack the document**: After all batches are complete, convert the unpacked directory back to .docx:
```bash
   python ooxml/scripts/pack.py unpacked reviewed-document.docx
   ```6.**Final verification**: Do a comprehensive check of the complete document:
   - Convert final document to markdown:
     ```bash
     pandoc --track-changes=all reviewed-document.docx -o verification.md
     ```
   - Verify ALL changes were applied correctly:
     ```bash
     grep "original phrase" verification.md  # Should NOT find it
     grep "replacement phrase" verification.md  # Should find it
     ```
   - Check that no unintended changes were introduced
## Converting Documents to ImagesTo visually analyze Word documents, convert them to images using a two-step process:
1.**Convert DOCX to PDF**:
```bash
   soffice --headless --convert-to pdf document.docx
   ```2.**Convert PDF pages to JPEG images**:
```bash
   pdftoppm -jpeg -r 150 document.pdf page
   ```   This creates files like `page-1.jpg`, `page-2.jpg`, etc.
Options:
-`-r 150`: Sets resolution to 150 DPI (adjust for quality/size balance)
-`-jpeg`: Output JPEG format (use `-png` for PNG if preferred)
-`-f N`: First page to convert (e.g., `-f 2` starts from page 2)
-`-l N`: Last page to convert (e.g., `-l 5` stops at page 5)
-`page`: Prefix for output files
Example for specific range:
```bash
pdftoppm -jpeg -r 150 -f 2 -l 5 document.pdf page  # Converts only pages 2-5
```## Code Style Guidelines**IMPORTANT**: When generating code for DOCX operations:
- Write concise code
- Avoid verbose variable names and redundant operations
- Avoid unnecessary print statements
## DependenciesRequired dependencies (install if not available):
-**pandoc**: `sudo apt-get install pandoc` (for text extraction)
-**docx**: `npm install -g docx` (for creating new documents)
-**LibreOffice**: `sudo apt-get install libreoffice` (for PDF conversion)
-**Poppler**: `sudo apt-get install poppler-utils` (for pdftoppm to convert PDF to images)
-**defusedxml**: `pip install defusedxml` (for secure XML parsing)

它的强项: 提供了清晰的决策树，根据任务类型将Claude引导至正确的工作流程，使用渐进式披露保持主文件精简，仅在需要时引用详细实现文件，并包含具体的正/反例，精确展示如何实现诸如跟踪更改之类的复杂模式。

技能示例#2：品牌指南

#name: brand-guidelinesdescription: Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
license: Complete terms in LICENSE.txt
---# Anthropic Brand Styling## OverviewTo access Anthropic's official brand identity and style resources, use this skill.
**Keywords**: branding, corporate identity, visual identity, post-processing, styling, brand colors, typography, Anthropic brand, visual formatting, visual design
## Brand Guidelines### Colors**Main Colors:**- Dark: `#141413` - Primary text and dark backgrounds
- Light: `#faf9f5` - Light backgrounds and text on dark
- Mid Gray: `#b0aea5` - Secondary elements
- Light Gray: `#e8e6dc` - Subtle backgrounds
**Accent Colors:**- Orange: `#d97757` - Primary accent
- Blue: `#6a9bcc` - Secondary accent
- Green: `#788c5d` - Tertiary accent
### Typography-**Headings**: Poppins (with Arial fallback)
-**Body Text**: Lora (with Georgia fallback)
-**Note**: Fonts should be pre-installed in your environment for best results
## Features### Smart Font Application- Applies Poppins font to headings (24pt and larger)
- Applies Lora font to body text
- Automatically falls back to Arial/Georgia if custom fonts unavailable
- Preserves readability across all systems
### Text Styling- Headings (24pt+): Poppins font
- Body text: Lora font
- Smart color selection based on background
- Preserves text hierarchy and formatting
### Shape and Accent Colors- Non-text shapes use accent colors
- Cycles through orange, blue, and green accents
- Maintains visual interest while staying on-brand
## Technical Details### Font Management- Uses system-installed Poppins and Lora fonts when available
- Provides automatic fallback to Arial (headings) and Georgia (body)
- No font installation required - works with existing system fonts
- For best results, pre-install Poppins and Lora fonts in your environment
### Color Application- Uses RGB color values for precise brand matching
- Applied via python-pptx's RGBColor class
- Maintains color fidelity across different systems

它的强项: 提供Claude本身不具备的精确、可操作的信息（精确的十六进制颜色代码、字体名称、大小阈值），并附有清晰的描述，既告诉Claude它的功能，也告诉Claude何时触发它。

它的强项: 具有明确边界的创意能力、内置版权保护、为非音乐人提供的技术框架、质量标准。

技能示例#3：前端设计技能

name: frontend-design
description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
license: Complete terms in LICENSE.txt
---This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
## Design ThinkingBefore coding, understand the context and commit to a BOLD aesthetic direction:
-**Purpose**: What problem does this interface solve? Who uses it?
-**Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
-**Constraints**: Technical requirements (framework, performance, accessibility).
-**Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?
**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is:
- Production-grade and functional
- Visually striking and memorable
- Cohesive with a clear aesthetic point-of-view
- Meticulously refined in every detail
## Frontend Aesthetics GuidelinesFocus on:
-**Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
-**Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
-**Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
-**Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
-**Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.
Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.
**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.
Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.

它的强项: 具有明确边界的创意能力、内置版权保护、为非音乐人提供的技术框架、质量标准。

常见问题

如何编写能真正触发技能的描述？

专注于能力和场景，而不是通用关键词。包含动作动词、特定文件类型和明确用例。不要写"文档处理技能"，而应写"从PDF中提取表格并转换为CSV格式，用于数据分析工作流"。

Claude如何决定调用哪些技能？

Claude使用语义理解根据技能描述评估你的请求。这不是关键词匹配——Claude会确定上下文相关性。如果多个技能涉及你请求的不同方面，它们可以激活。

我的描述应该细化到什么程度？

瞄准单一用途的技能。"博客文章的SEO优化"对于具体指令足够聚焦，同时又足够广泛以可重用。太宽泛："内容营销助手"。太狭窄："添加元描述"。

如何在组织内共享技能？

无论你的团队规模如何，我们建议创建一个共享文档存储库，包含技能规范。

对于较小的团队, 使用带有名称、描述、指令和版本信息的模板格式。

对于中大型团队, 建立技能治理流程：

• 为每个领域（财务、法律、营销）指定技能所有者
• 维护一个中央维基或共享驱动器作为技能库
• 为每个技能包含使用示例和常见故障排查
• 对你的技能进行版本控制，并在变更日志中记录更改
• 安排季度审查，以更新或淘汰过时的技能

适用于所有团队规模的最佳实践：

• 记录每个技能的业务目的
• 明确分配维护和更新的所有权
• 创建入门材料，向新团队成员展示如何实施共享技能
• 跟踪哪些技能带来最大价值，以优先安排维护工作
• 使用一致的命名约定，使技能易于查找

企业客户可以与Anthropic的客户成功团队合作，探索额外的部署选项和治理框架。

如何调试技能？

分别测试触发和执行。如果技能未激活，扩大描述并添加用例。如果结果不一致，增加指令的明确性并包含验证步骤。创建一个测试用例库，涵盖正常使用、边缘情况和超出范围的请求。

如何在组织内共享技能？

‍在Claude.ai，目前技能对每个用户都是独立的，不过组织级的管理和共享功能即将推出。与此同时，无论你的团队规模如何，我们建议创建一个包含技能规范的共享文档库。这既为即将推出的功能做好准备，又能在今天就建立良好的治理实践。

开始使用

准备好用技能构建了吗？以下是如何开始：

Claude.ai用户：

• 在设置 → 功能中启用技能
• 在 claude.ai/projects 创建你的第一个项目
• 尝试将项目知识与技能结合用于你的下一个分析任务

API 开发者：

• 在以下位置探索技能端点文档
• 查看我们的 技能手册

Claude Code 用户：

• 通过 插件市场
• 查看我们的 技能手册

未找到项目。

上一页

0/5

下一页

电子书

代理技能

立即开始使用 Claude 的技能，构建更强大的应用程序。

开始使用

开始使用

常见问题

未找到项目。

相关文章

探索更多产品新闻和最佳实践，助力团队使用 Claude 进行构建。

2026年8月7日

自动模式现已成为 Claude Code 中 Pro、Max 和团队计划的默认模式

Claude Code

自动模式现已成为 Claude Code 中 Pro、Max 和团队计划的默认模式

自动模式现已成为 Claude Code 中 Pro、Max 和团队计划的默认模式

2026年8月7日

在生产环境中运行自动模式

Claude Code

在生产环境中运行自动模式

在生产环境中运行自动模式

2026年8月6日

Millennium 和 Anthropic 正在用 Claude 构建数字风险分析师

企业 AI

Millennium 和 Anthropic 正在用 Claude 构建数字风险分析师

Millennium 和 Anthropic 正在用 Claude 构建数字风险分析师

2026年7月24日

Claude 模型解析：为你的使用场景选择最佳模型

企业 AI

Claude 模型解析：为你的使用场景选择最佳模型

Claude 模型解析：为你的使用场景选择最佳模型

用 Claude 改变你组织的运作方式

查看定价

查看定价

联系销售

联系销售

获取开发者通讯

产品更新、操作指南、社区亮点等。每月投递到你的收件箱。

谢谢！你已订阅。

抱歉，你的提交出现问题，请稍后重试。