如何建立 Claude Skills:步驟、限制與範例
了解如何撰寫符合工作需求的 Skills,讓 Claude 交出更有用、更符合預期的成果。
Skills 是自訂指示,可擴充 Claude 在特定任務或領域的能力。
透過 SKILL.md 檔案建立 Skill,就能教 Claude 如何更有效地處理特定情境。你可以用 Skills 保存團隊知識、統一輸出格式,也可以處理複雜的多步驟工作流程。否則,這些工作可能每次都要重新解釋,或得投入時間另做自訂代理程式。
你可以使用 Skill Creator 範本,也可以手動撰寫 Skill,讓擔任通用助理的 Claude 熟悉你的特定工作流程。要簡化設定,可以先用這個範本建立 SKILL.md,再依需求調整。
建立 Skill 的五個步驟
依照以下步驟撰寫,能讓 Skill 在需要時更可靠地啟用。
1. 釐清核心需求
動筆前,先釐清這個 Skill 要解決什麼問題。好的 Skill 會對準具體需求,而且能判斷結果是否達標。「從 PDF 擷取財務資料並輸出成 CSV」比「幫我處理財務資料」清楚,因為前一句交代了輸入格式、要做的事和預期輸出。
先問自己:這個 Skill 要完成哪一項任務?什麼情況下該啟用?怎樣才算成功?有哪些邊界情況或限制?
2. 撰寫名稱
Skill 需要三個核心部分:名稱用來辨識,描述說明何時啟用,指示說明怎麼執行。Claude 決定要不要為特定知識或工作流程啟用 Skill 時,只會看 SKILL.md 裡的名稱和描述。
名稱要簡短,讓人一看就知道用途。使用小寫英文字母,單字之間用連字號隔開,例如 pdf-editor 和 brand-guidelines。
3. 撰寫描述欄位
描述決定 Skill 何時啟用,是最關鍵的部分。從 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 有更多判斷依據,包括具體動作(擷取、建立、合併)、適用情境(填表、批次處理),以及界線(單純開啟 PDF 時不用啟用)。
4. 撰寫主要指示
把指示寫得有條理,讓人可以快速找到需要的資訊,也能照著做。用 Markdown 標題分節,用項目清單列選項,用程式碼區塊呈現範例。
讓每節有清楚的用途,例如概述、前置條件、執行步驟、範例、錯誤處理和限制。複雜的工作流程要拆成數個階段,各自交代輸入與輸出。
提供具體範例,示範正確用法。也要說明 Skill 的限制,讓使用者知道在什麼情況下應改用其他方法。SKILL.md 還可以引用補充文件和資源,讓 Claude 啟用 Skill 時知道去哪裡找需要的細節。
5. 上傳 Skill
上傳方式依你使用的 Claude 產品而定。
- Claude.ai(Claude 應用程式)。在設定中加入自訂 Skill。方案須為 Pro、Max、Ultra、Team 或 Enterprise,並已啟用程式碼執行功能。在這裡上傳的 Skill 屬於個別使用者,無法全組織共用或由管理員集中管理。
- Claude Code。在外掛或專案根目錄建立
skills/,在下方為每個 Skill 建立含有SKILL.md的資料夾。外掛裝好後,Claude 會自動找到並使用這些 Skills。目錄結構如下。
my-project/
├── skills/
│ └── my-skill/
│ └── SKILL.md
- Claude Developer Platform。透過 Skills API(
/v1/skills)上傳 Skill。使用 POST 請求,並加上所需的 Beta 標頭。
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. 測試與驗證
部署前,用貼近實際工作的情境試跑 Skill。系統化的測試能找出指示遺漏、描述含糊,以及實際使用時才會遇到的邊界情況。
測試表至少要涵蓋三種情境。
- 正常操作。用 Skill 應能穩定處理的典型指令來測試。若你建立的是財務分析 Skill,可以試「分析 Microsoft 最新的財報」或「把這份 10-K 年報整理成一套資料」。這些基本測試能確認指示是否照預期運作。
- 邊界情況。測試不完整或少見的輸入。如果缺少資料、檔案格式不符預期,或使用者說得不夠清楚,Skill 應該仍能交付有用的部分結果,或說明需要哪些資料才能繼續。
- 範圍之外的請求。測試看似相關但不該啟用 Skill 的任務。若你做的是保密協議審查 Skill,可以試「審查這份聘僱合約」或「分析這份租約」。這個 Skill 應維持停用,由其他 Skill 或 Claude 的一般能力處理。
還可以用以下測試進一步驗證。
- 啟用測試。用明確指定 Skill 的請求(「用財務資料包 Skill 分析這家公司」)和自然表達需求的請求(「幫我了解這家公司的財務狀況」)各測一次。也要測試看似接近但不適用的請求,確認 Skill 知道何時該保持停用。
- 功能測試。比對多次處理相近輸入時,輸出是否一致。不熟悉這個領域的人應能順利使用,文件範例也應符合實際行為。
5. 根據使用結果調整
記錄 Skill 在實際工作中的表現。若啟用時機不一致,就修整描述。若輸出不如預期,就把指示寫得更清楚。和提示詞一樣,Skill 會在一次次使用中逐漸改進。
建立 Skills 的最佳實務
以下原則有助於寫出容易維護、能重複使用,並且能實際派上用場的 Skills。
從實際使用情境出發
遇到真實而且反覆出現的任務,再為它建立 Skill。優先處理你經常遇到的問題。
可以先問自己:這件事我做過至少五次了嗎?以後還會再做至少十次嗎?如果兩者都是,就可以考慮做成 Skill。
定義成功標準,並寫進 Skill
告訴 Claude 成果要長什麼樣子。若要產出財務報告,請明定必備章節、格式規範、驗證項目和品質門檻。把這些標準寫進指示裡,Claude 才能依據它們檢查自己的成果。
使用 Skill Creator
Skill Creator 會引導你建立結構清楚的 Skill。它會提問以釐清需求,建議怎麼改善描述,也會協助整理指示的格式。你可以從 GitHub 上的 Skills 專案 或直接在 Claude.ai 使用。剛開始寫前幾個 Skills 時特別有幫助。
Skills 的限制與注意事項
了解 Skills 怎麼運作、能力到哪裡,才能設計出好用的 Skills,也能讓使用者知道何時適合使用。
Claude 如何判斷是否啟用 Skill
Claude 會把你的請求和各個 Skill 的描述放在一起判斷,根據語意關聯確認是否適用。描述寫得含糊,啟用的準確度就會下降。
如果一項複雜任務涵蓋不同面向,Claude 可以同時啟用多個 Skills。描述範圍太廣,容易在不需要時啟用。漏寫適用情境,又可能在真正需要時沒有啟用。
檔案要多大才合適
撰寫 Skill 時,避免讓不必要的內容占用模型的脈絡視窗。逐項想想哪些資訊每次都要載入,哪些只在特定情況才需要。
如果 Skill 涵蓋多套流程或選項,可以把 SKILL.md 寫成目錄。先列出可用的流程,再以相對路徑指向各自的檔案。Claude 就能依使用者當前的任務,只讀取相關檔案。
這些檔案可以一起使用,彼此無須互斥。重點是把內容拆成大小合宜的區塊,讓 Claude 依任務選讀。
實際的 Skill 範例
範例 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
## Overview
A 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 Content
Use "Text extraction" or "Raw XML access" sections below
### Creating New Document
Use "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 extraction
If 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 access
You 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 document
When creating a new Word document from scratch, use **docx-js**, which allows you to create Word documents using JavaScript/TypeScript.
### Workflow
1. **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 document
When 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.
### Workflow
1. **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 review
This 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 workflow
1. **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 Images
To 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
## Dependencies
Required 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-guidelines
description: 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
## Overview
To 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 原本無從得知、可以直接套用的資訊,例如十六進位色碼、字型名稱和字級門檻。描述也清楚說明了工作內容和啟用時機。
範例 3:前端設計 Skill
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 Thinking
Before 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 Guidelines
Focus 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.
常見問題
怎麼寫描述,Claude 才會在需要時啟用?
著重能做的事和適用情境。加入動作、具體檔案類型和使用案例。例如,「從 PDF 擷取表格並轉成 CSV,供資料分析流程使用」就比「文件處理 Skill」明確。
Claude 怎麼決定要啟用哪些 Skills?
Claude 會從語意判斷請求與描述的關聯。如果有多個 Skills 分別適用於請求的不同部分,可以一起啟用。
描述要寫多細?
讓每個 Skill 聚焦單一用途。「為部落格文章做 SEO 最佳化」足夠具體,可以寫出明確指示,也有足夠廣度供不同文章重複使用。相比之下,「協助內容行銷」太廣,「加上網頁中繼描述」又太窄。
怎麼在整個組織共用 Skills?
不論團隊大小,都建議集中保存 Skill 規格文件,讓團隊成員能一起查閱。
小型團隊可以依統一範本記錄名稱、描述、指示和版本資訊。
中大型團隊可以建立 Skill 管理流程。
- 為財務、法務、行銷等領域指定負責人。
- 用共用的 Wiki 或雲端磁碟集中管理 Skills。
- 加入使用範例與常見問題排除方法。
- 為 Skills 編版本,並用變更記錄說明改了什麼。
- 每季檢視一次,更新或停用過時的 Skills。
適用於所有團隊的做法
- 記錄每個 Skill 的業務用途。
- 指定維護和更新的負責人。
- 準備新進成員的入門材料,示範怎麼使用共用的 Skills。
- 掌握哪些 Skills 帶來最多效益,據此安排維護順序。
- 採用一致的命名方式,方便查找。
企業客戶也可以與 Anthropic 的客戶成功團隊討論其他部署選項與管理方式。
怎麼替 Skills 除錯?
把啟用和執行分開測試。如果 Skill 沒有啟用,調整描述的適用範圍,並補上使用情境。如果結果不一致,就把指示寫得更明確,加入驗證步驟。建立一套測試案例,涵蓋正常使用、邊界情況和不在適用範圍內的請求。
開始使用
可以依你使用的產品開始建立 Skills。
Claude.ai 使用者
- 在「設定」的「功能」中啟用 Skills。
- 前往 claude.ai/projects 建立第一個專案。
- 下次做分析時,試著將專案知識和 Skills 搭配使用。
API 開發者
- 在開發者文件查看 Skills 端點。
- 閱讀 Skills Cookbook。
Claude Code 使用者
- 透過外掛市集安裝 Skills。
- 閱讀 Skills Cookbook。