Add files via upload
This commit is contained in:
mohitagw15856
GitHub
@@ -0,0 +1,405 @@
|
||||
# Customization Guide
|
||||
|
||||
Learn how to adapt PM Claude Skills to match your company's specific processes and standards.
|
||||
|
||||
## Why Customize?
|
||||
|
||||
Every company has different:
|
||||
- Document formats and templates
|
||||
- Communication styles
|
||||
- Approval processes
|
||||
- Tools and systems
|
||||
- Terminology and jargon
|
||||
|
||||
These Skills are designed as starting points. Customizing them ensures Claude produces outputs that match YOUR standards, not generic ones.
|
||||
|
||||
## What Can Be Customized
|
||||
|
||||
### 1. Document Structure
|
||||
- Section order and naming
|
||||
- Required vs. optional sections
|
||||
- Level of detail
|
||||
|
||||
### 2. Formatting & Style
|
||||
- Tone (formal vs. casual)
|
||||
- Length preferences
|
||||
- Visual elements (tables, bullets, etc.)
|
||||
|
||||
### 3. Process & Workflow
|
||||
- Approval steps
|
||||
- Stakeholder requirements
|
||||
- Tool integrations
|
||||
|
||||
### 4. Terminology
|
||||
- Company-specific terms
|
||||
- Product names
|
||||
- Team names and roles
|
||||
|
||||
### 5. Examples
|
||||
- Your actual past documents (anonymized)
|
||||
- Company-specific scenarios
|
||||
- Real data formats
|
||||
|
||||
## How to Customize a Skill
|
||||
|
||||
### Step 1: Download the Skill
|
||||
|
||||
1. Navigate to the skill folder (e.g., `skills/prd-template`)
|
||||
2. Download the `SKILL.md` file
|
||||
3. Open in any text editor
|
||||
|
||||
### Step 2: Understand the Structure
|
||||
|
||||
Every `SKILL.md` has two parts:
|
||||
|
||||
```markdown
|
||||
---
|
||||
name: skill-name
|
||||
description: When Claude should use this skill
|
||||
---
|
||||
|
||||
# Skill Content
|
||||
|
||||
[Instructions for Claude]
|
||||
```
|
||||
|
||||
**Frontmatter** (between `---`):
|
||||
- `name`: The skill identifier (keep unchanged)
|
||||
- `description`: When to trigger this skill (customize if needed)
|
||||
|
||||
**Body** (after `---`):
|
||||
- Instructions Claude follows
|
||||
- Templates and formats
|
||||
- Examples
|
||||
|
||||
### Step 3: Make Your Changes
|
||||
|
||||
Edit the body to match your needs. Here are common customizations:
|
||||
|
||||
## Common Customizations
|
||||
|
||||
### Example 1: Customize PRD Template
|
||||
|
||||
**Change the section structure:**
|
||||
|
||||
Original:
|
||||
```markdown
|
||||
### 1. Overview
|
||||
- Problem Statement
|
||||
- Proposed Solution
|
||||
- Success Metrics
|
||||
```
|
||||
|
||||
Your Company's Format:
|
||||
```markdown
|
||||
### 1. Executive Summary
|
||||
- Business Objective
|
||||
- Customer Problem
|
||||
- Proposed Solution
|
||||
- Success Criteria (OKRs)
|
||||
```
|
||||
|
||||
**Add company-specific requirements:**
|
||||
|
||||
```markdown
|
||||
### Company-Specific Requirements
|
||||
|
||||
**Compliance:**
|
||||
- GDPR compliance assessment
|
||||
- Security review sign-off
|
||||
- Legal approval required
|
||||
|
||||
**Stakeholders to Consult:**
|
||||
- Engineering Lead (architecture)
|
||||
- Design Director (UX)
|
||||
- Security Team (if handling PII)
|
||||
```
|
||||
|
||||
**Add your actual template:**
|
||||
|
||||
```markdown
|
||||
## Your Company PRD Template
|
||||
|
||||
Use this exact structure:
|
||||
|
||||
# [Feature Name] - Product Requirements
|
||||
|
||||
## 1. Executive Summary (Max 1 page)
|
||||
[Your specific requirements]
|
||||
|
||||
## 2. Customer Research
|
||||
[Your specific requirements]
|
||||
|
||||
[Continue with your actual template]
|
||||
```
|
||||
|
||||
### Example 2: Customize Stakeholder Updates
|
||||
|
||||
**Match your metrics:**
|
||||
|
||||
Original:
|
||||
```markdown
|
||||
| Metric | Current | Target | Trend | Status |
|
||||
```
|
||||
|
||||
Your Company:
|
||||
```markdown
|
||||
| OKR | Progress | Goal | Confidence | Owner |
|
||||
```
|
||||
|
||||
**Add your status indicators:**
|
||||
|
||||
```markdown
|
||||
**Status Levels:**
|
||||
- 🟢 On Track: >90% confidence in hitting goals
|
||||
- 🟡 At Risk: 60-90% confidence, mitigation needed
|
||||
- 🔴 Off Track: <60% confidence, escalation required
|
||||
- ⚪ Not Started: Work hasn't begun
|
||||
```
|
||||
|
||||
**Match your communication style:**
|
||||
|
||||
If your executives prefer different tone:
|
||||
|
||||
```markdown
|
||||
## Communication Style
|
||||
|
||||
**Tone**: Data-driven and factual (no marketing language)
|
||||
**Length**: Maximum 5 bullets per section
|
||||
**Focus**: Always lead with customer impact, then business metrics
|
||||
**Avoid**: Jargon, acronyms without explanation
|
||||
```
|
||||
|
||||
### Example 3: Customize Meeting Notes
|
||||
|
||||
**Add your tools:**
|
||||
|
||||
```markdown
|
||||
### Action Item Format
|
||||
|
||||
Use our Jira/Asana/Monday format:
|
||||
|
||||
- [ ] **[JIRA-123] [Action item]** - @Owner - Due: [Date] - Priority: [High/Med/Low]
|
||||
```
|
||||
|
||||
**Add your meeting types:**
|
||||
|
||||
```markdown
|
||||
### Sprint Retrospective Notes
|
||||
|
||||
**What Went Well:**
|
||||
- [List items]
|
||||
|
||||
**What Didn't Go Well:**
|
||||
- [List items]
|
||||
|
||||
**Action Items:**
|
||||
- [Improvements to implement]
|
||||
|
||||
**Team Morale:** [Score 1-10]
|
||||
```
|
||||
|
||||
### Example 4: Add Domain-Specific Context
|
||||
|
||||
For SaaS PM:
|
||||
```markdown
|
||||
## SaaS Metrics Context
|
||||
|
||||
When analyzing metrics, always include:
|
||||
- MRR/ARR impact
|
||||
- Churn rate implications
|
||||
- CAC payback impact
|
||||
- NRR (Net Revenue Retention) effect
|
||||
```
|
||||
|
||||
For B2B PM:
|
||||
```markdown
|
||||
## Enterprise Sales Context
|
||||
|
||||
When writing features, consider:
|
||||
- Enterprise security requirements
|
||||
- Compliance needs (SOC2, GDPR, HIPAA)
|
||||
- Multi-tenant implications
|
||||
- Admin controls needed
|
||||
```
|
||||
|
||||
## Advanced Customization
|
||||
|
||||
### Adding Examples from Your Company
|
||||
|
||||
The most powerful customization: add YOUR actual examples.
|
||||
|
||||
```markdown
|
||||
## Example PRD from Our Company
|
||||
|
||||
Here's how we documented our last major feature:
|
||||
|
||||
[Paste anonymized version of your actual PRD]
|
||||
|
||||
Key elements to notice:
|
||||
- How we structured the problem statement
|
||||
- Level of technical detail
|
||||
- How we documented success metrics
|
||||
```
|
||||
|
||||
### Adding Your Tools & Systems
|
||||
|
||||
```markdown
|
||||
## Our Tech Stack References
|
||||
|
||||
When mentioning systems, use our actual names:
|
||||
- Internal tool for analytics: "DataHub"
|
||||
- Our design system: "Atlas"
|
||||
- Our API gateway: "Gateway Pro"
|
||||
|
||||
Always link to relevant docs:
|
||||
- PRD templates: [internal wiki link]
|
||||
- User research database: [internal link]
|
||||
- Product metrics dashboard: [internal link]
|
||||
```
|
||||
|
||||
### Adding Your Processes
|
||||
|
||||
```markdown
|
||||
## Our Approval Process
|
||||
|
||||
Every PRD must be reviewed by:
|
||||
1. Engineering Lead (technical feasibility)
|
||||
2. Design Lead (UX implications)
|
||||
3. Product Director (strategic alignment)
|
||||
4. Security (if handling sensitive data)
|
||||
|
||||
Include sign-off section:
|
||||
|
||||
### Approvals
|
||||
- [ ] Engineering: [Name] - [Date]
|
||||
- [ ] Design: [Name] - [Date]
|
||||
- [ ] Product: [Name] - [Date]
|
||||
- [ ] Security: [Name] - [Date] (if applicable)
|
||||
```
|
||||
|
||||
## Testing Your Customizations
|
||||
|
||||
After customizing:
|
||||
|
||||
1. **Package the updated Skill** (see [Installation Guide](installation.md))
|
||||
2. **Remove the old version** from Claude
|
||||
3. **Upload the new version**
|
||||
4. **Test with real examples**
|
||||
|
||||
Test prompts:
|
||||
- Use actual requests you'd make
|
||||
- Try edge cases
|
||||
- Verify outputs match your expectations
|
||||
|
||||
## Iteration Process
|
||||
|
||||
Skills improve through iteration:
|
||||
|
||||
1. **Use the Skill** in real work
|
||||
2. **Notice issues** or improvements
|
||||
3. **Update SKILL.md**
|
||||
4. **Re-upload**
|
||||
5. **Test again**
|
||||
|
||||
Keep a "changelog" in your Skill:
|
||||
|
||||
```markdown
|
||||
## Changelog
|
||||
|
||||
### v1.2 (Jan 25, 2026)
|
||||
- Added security review requirement
|
||||
- Changed metric names to match company OKRs
|
||||
- Added example from Q4 2025 project
|
||||
|
||||
### v1.1 (Jan 15, 2026)
|
||||
- Updated to match new PRD template
|
||||
- Added stakeholder approval section
|
||||
|
||||
### v1.0 (Jan 1, 2026)
|
||||
- Initial version
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
### ✅ Do:
|
||||
- Start with small changes
|
||||
- Test thoroughly before sharing with team
|
||||
- Use real examples from your company
|
||||
- Document what you changed and why
|
||||
- Version your Skills
|
||||
|
||||
### ❌ Don't:
|
||||
- Make the Skill too prescriptive (keep some flexibility)
|
||||
- Include sensitive/proprietary information
|
||||
- Assume one format works for all scenarios
|
||||
- Over-customize before testing the default
|
||||
|
||||
## Sharing Customized Skills
|
||||
|
||||
### Within Your Team
|
||||
|
||||
For Team/Enterprise plans:
|
||||
1. Customize and test individually
|
||||
2. Share with 2-3 teammates for feedback
|
||||
3. Iterate based on feedback
|
||||
4. Have admin upload to organization library
|
||||
5. Document any team-specific conventions
|
||||
|
||||
### Contributing Back
|
||||
|
||||
If your customization would help others:
|
||||
1. Remove company-specific details
|
||||
2. Generalize the improvements
|
||||
3. Submit a Pull Request
|
||||
4. Include explanation of why the change helps
|
||||
|
||||
## Templates for Common Customizations
|
||||
|
||||
### Add Company Values
|
||||
|
||||
```markdown
|
||||
## Our Company Values
|
||||
|
||||
When writing any document, reflect these values:
|
||||
- **Customer-First**: Always lead with customer impact
|
||||
- **Data-Driven**: Include quantitative backing
|
||||
- **Bias for Action**: Propose concrete next steps
|
||||
- **Transparent**: Be honest about risks and unknowns
|
||||
```
|
||||
|
||||
### Add Regulatory Requirements
|
||||
|
||||
```markdown
|
||||
## Regulatory Considerations
|
||||
|
||||
For any feature involving [X], include:
|
||||
- GDPR compliance assessment
|
||||
- Data retention policy
|
||||
- User consent requirements
|
||||
- Right to deletion implementation
|
||||
```
|
||||
|
||||
### Add Workflow Integrations
|
||||
|
||||
```markdown
|
||||
## Integration with Our Tools
|
||||
|
||||
When creating action items:
|
||||
- Format for Jira: [TEAM-###] Action
|
||||
- Tag relevant Slack channels: #product, #engineering
|
||||
- Link to relevant Notion pages
|
||||
- Add to project board: [Board link]
|
||||
```
|
||||
|
||||
## Need Help?
|
||||
|
||||
- 💬 [Ask in Discussions](https://github.com/yourusername/pm-claude-skills/discussions)
|
||||
- 📧 Email: your-email@example.com
|
||||
- 🐛 [Report issues](https://github.com/yourusername/pm-claude-skills/issues)
|
||||
|
||||
## Next Steps
|
||||
|
||||
- [Create Your Own Skills](creating-skills.md)
|
||||
- [Troubleshooting Guide](troubleshooting.md)
|
||||
- [Back to Installation](installation.md)
|
||||
@@ -0,0 +1,192 @@
|
||||
# Installation Guide
|
||||
|
||||
Complete guide to installing and using PM Claude Skills.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
### Required
|
||||
- **Claude Account**: Pro, Team, or Enterprise plan
|
||||
- **Code Execution**: Must be enabled (see below)
|
||||
- **Access**: claude.ai, Claude Code, or API access
|
||||
|
||||
### Check Your Account Type
|
||||
1. Go to [claude.ai](https://claude.ai)
|
||||
2. Click your profile in bottom-left
|
||||
3. See "Claude Pro" / "Claude Team" / "Claude Enterprise"
|
||||
|
||||
If you have Free plan: Skills are not available. [Upgrade here](https://claude.ai/upgrade)
|
||||
|
||||
## Step 1: Enable Code Execution
|
||||
|
||||
Skills require Code Execution to be enabled.
|
||||
|
||||
1. Go to claude.ai
|
||||
2. Click profile icon (bottom-left)
|
||||
3. Click **Settings**
|
||||
4. Click **Features**
|
||||
5. Toggle on **"Code Execution and File Creation"**
|
||||
6. Click **Save**
|
||||
|
||||
|
||||
|
||||
## Step 2: Download Skills
|
||||
|
||||
### Option A: Download Individual Skills (Recommended)
|
||||
|
||||
1. Navigate to the skill you want (e.g., [`skills/prd-template`](../skills/prd-template))
|
||||
2. Click the skill folder
|
||||
3. Download the `SKILL.md` file
|
||||
4. If there are other files in the folder, download those too
|
||||
|
||||
### Option B: Clone the Entire Repository
|
||||
|
||||
```bash
|
||||
git clone https://github.com/yourusername/pm-claude-skills.git
|
||||
cd pm-claude-skills
|
||||
```
|
||||
|
||||
### Option C: Download Pre-packaged Skills (When Available)
|
||||
|
||||
Check the [Releases](https://github.com/yourusername/pm-claude-skills/releases) page for `.skill` files ready to upload.
|
||||
|
||||
## Step 3: Package the Skill
|
||||
|
||||
Skills must be packaged as `.skill` files (which are just renamed .zip files).
|
||||
|
||||
### On Mac/Linux:
|
||||
|
||||
```bash
|
||||
# Navigate to the skill folder
|
||||
cd pm-claude-skills/skills/prd-template
|
||||
|
||||
# Create a zip of the folder contents
|
||||
zip -r prd-template.skill .
|
||||
|
||||
# Move it somewhere convenient
|
||||
mv prd-template.skill ~/Downloads/
|
||||
```
|
||||
|
||||
### On Windows:
|
||||
|
||||
1. Navigate to the skill folder (e.g., `skills/prd-template`)
|
||||
2. Select all files inside the folder
|
||||
3. Right-click → "Send to" → "Compressed (zipped) folder"
|
||||
4. Rename from `.zip` to `.skill`
|
||||
|
||||
### Important Notes:
|
||||
- ⚠️ The `.skill` file should contain the files directly, NOT a parent folder
|
||||
- ✅ Correct: `prd-template.skill` contains `SKILL.md` at root
|
||||
- ❌ Wrong: `prd-template.skill` contains `prd-template/SKILL.md`
|
||||
|
||||
## Step 4: Upload to Claude
|
||||
|
||||
1. Go to [claude.ai](https://claude.ai)
|
||||
2. Click your profile icon (bottom-left)
|
||||
3. Click **Settings**
|
||||
4. Click **Skills** in the left sidebar
|
||||
5. Click **Upload Skill** button
|
||||
6. Select your `.skill` file
|
||||
7. Wait for "Skill uploaded successfully"
|
||||
|
||||
|
||||
|
||||
That's it! The Skill is now available.
|
||||
|
||||
## Step 5: Test the Skill
|
||||
|
||||
Start a new conversation and test:
|
||||
|
||||
**For PRD Template:**
|
||||
> "Help me write a PRD for a mobile app onboarding feature"
|
||||
|
||||
**For Meeting Notes:**
|
||||
> "Create meeting notes from this discussion: [paste transcript]"
|
||||
|
||||
**For Stakeholder Update:**
|
||||
> "Create a stakeholder update for our Q1 progress"
|
||||
|
||||
Claude should automatically recognize when to use the Skill and apply it.
|
||||
|
||||
## Verification
|
||||
|
||||
To verify a Skill is installed:
|
||||
|
||||
1. Go to Settings → Skills
|
||||
2. You should see your uploaded Skills listed
|
||||
3. Each Skill shows:
|
||||
- Name
|
||||
- Description
|
||||
- Date uploaded
|
||||
|
||||
## Managing Skills
|
||||
|
||||
### View Installed Skills
|
||||
Settings → Skills → See all installed Skills
|
||||
|
||||
### Remove a Skill
|
||||
Settings → Skills → Click skill → Click "Remove"
|
||||
|
||||
### Update a Skill
|
||||
1. Remove the old version
|
||||
2. Upload the new version
|
||||
|
||||
### Disable a Skill Temporarily
|
||||
Currently not possible - you must remove and re-upload
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### "Code Execution must be enabled"
|
||||
- Go to Settings → Features → Enable "Code Execution and File Creation"
|
||||
|
||||
### "Invalid skill file"
|
||||
- Make sure you're uploading a `.skill` file (renamed .zip)
|
||||
- Ensure SKILL.md has proper frontmatter (see [Creating Skills](creating-skills.md))
|
||||
- Check that files are at root level, not in a subfolder
|
||||
|
||||
### "Skill uploaded but not working"
|
||||
- Try starting a new conversation
|
||||
- Make sure your request matches the Skill's description triggers
|
||||
- Check that the Skill's frontmatter `description` field is clear
|
||||
|
||||
### Skill triggers at wrong times
|
||||
- The `description` field controls when Skills trigger
|
||||
- Edit SKILL.md to make triggers more specific
|
||||
- Re-package and re-upload
|
||||
|
||||
### Cannot find uploaded Skill
|
||||
- Check Settings → Skills
|
||||
- Try refreshing the page
|
||||
- Try logging out and back in
|
||||
|
||||
## For Team/Enterprise Plans
|
||||
|
||||
### Sharing Skills with Your Team
|
||||
|
||||
Team/Enterprise admins can provision Skills organization-wide:
|
||||
|
||||
1. Go to Admin Console
|
||||
2. Navigate to Skills management
|
||||
3. Upload Skills to organization library
|
||||
4. All team members will have access
|
||||
|
||||
### Private vs. Shared Skills
|
||||
|
||||
- **Private Skills**: Only visible to you
|
||||
- **Shared Skills**: Visible to entire organization
|
||||
- Team admins can make Skills shared
|
||||
|
||||
## Next Steps
|
||||
|
||||
- [Customize Skills](customization.md) to match your workflow
|
||||
- [Create your own Skills](creating-skills.md)
|
||||
- [Troubleshooting Guide](troubleshooting.md)
|
||||
|
||||
## Video Tutorial
|
||||
|
||||
[Coming Soon] Watch a 5-minute video walkthrough of the installation process.
|
||||
|
||||
## Need Help?
|
||||
|
||||
- 🐛 [Report an issue](https://github.com/yourusername/pm-claude-skills/issues)
|
||||
- 💬 [Ask in Discussions](https://github.com/yourusername/pm-claude-skills/discussions)
|
||||
- ✉️ Email: your-email@example.com
|
||||
@@ -0,0 +1,421 @@
|
||||
# Troubleshooting Guide
|
||||
|
||||
Common issues and solutions when using PM Claude Skills.
|
||||
|
||||
## Table of Contents
|
||||
- [Installation Issues](#installation-issues)
|
||||
- [Skill Not Triggering](#skill-not-triggering)
|
||||
- [Skill Triggering at Wrong Times](#skill-triggering-at-wrong-times)
|
||||
- [Output Quality Issues](#output-quality-issues)
|
||||
- [Performance Issues](#performance-issues)
|
||||
- [Team/Enterprise Issues](#teamenterprise-issues)
|
||||
|
||||
## Installation Issues
|
||||
|
||||
### "Code Execution must be enabled"
|
||||
|
||||
**Problem**: You get an error about Code Execution when trying to use Skills.
|
||||
|
||||
**Solution**:
|
||||
1. Go to claude.ai
|
||||
2. Click profile icon → Settings
|
||||
3. Click "Features"
|
||||
4. Toggle ON "Code Execution and File Creation"
|
||||
5. Click Save
|
||||
6. Refresh the page
|
||||
|
||||
### "Invalid skill file"
|
||||
|
||||
**Problem**: Upload fails with "Invalid skill file" error.
|
||||
|
||||
**Possible Causes & Solutions**:
|
||||
|
||||
1. **File extension is wrong**
|
||||
- Must be `.skill` not `.zip`
|
||||
- Rename: `prd-template.zip` → `prd-template.skill`
|
||||
|
||||
2. **Folder structure is wrong**
|
||||
- ❌ Wrong: `skill.skill` contains `folder/SKILL.md`
|
||||
- ✅ Correct: `skill.skill` contains `SKILL.md` at root
|
||||
- Repackage with files at root level
|
||||
|
||||
3. **SKILL.md frontmatter is malformed**
|
||||
```markdown
|
||||
---
|
||||
name: skill-name
|
||||
description: Clear description
|
||||
---
|
||||
```
|
||||
- Must have both `name` and `description`
|
||||
- Must be valid YAML
|
||||
- Must have `---` before and after
|
||||
|
||||
4. **File is corrupted**
|
||||
- Try redownloading
|
||||
- Try different compression tool
|
||||
- Check file size (shouldn't be 0 bytes)
|
||||
|
||||
### Cannot find upload button
|
||||
|
||||
**Problem**: Can't find where to upload Skills.
|
||||
|
||||
**Solution**:
|
||||
1. Make sure you have Pro/Team/Enterprise (not Free)
|
||||
2. Go to Settings (profile icon → Settings)
|
||||
3. Look for "Skills" in left sidebar
|
||||
4. If you don't see it, try:
|
||||
- Refreshing the page
|
||||
- Logging out and back in
|
||||
- Contacting Anthropic support
|
||||
|
||||
### Skill uploaded but not visible
|
||||
|
||||
**Problem**: Upload succeeds but Skill doesn't appear in list.
|
||||
|
||||
**Solution**:
|
||||
1. Refresh the page (Cmd+R or Ctrl+R)
|
||||
2. Log out and log back in
|
||||
3. Check Settings → Skills again
|
||||
4. Try a different browser
|
||||
5. Clear browser cache
|
||||
|
||||
## Skill Not Triggering
|
||||
|
||||
### Skill doesn't activate when expected
|
||||
|
||||
**Problem**: You ask for something that should trigger the Skill, but Claude doesn't use it.
|
||||
|
||||
**Diagnosis**:
|
||||
1. Check the Skill's `description` field in frontmatter
|
||||
2. Compare your request to the description
|
||||
3. Claude only triggers Skills when request matches description
|
||||
|
||||
**Solutions**:
|
||||
|
||||
1. **Be more explicit in your request**
|
||||
- Instead of: "Help me write a doc"
|
||||
- Try: "Help me write a PRD for feature X"
|
||||
|
||||
2. **Update the Skill description**
|
||||
- Edit SKILL.md frontmatter
|
||||
- Make `description` more comprehensive
|
||||
- Include all trigger scenarios
|
||||
|
||||
Example:
|
||||
```markdown
|
||||
---
|
||||
description: Use when user asks to create, write, draft, format, or help with a PRD, product requirements document, product spec, feature specification, feature doc, or product documentation for a new feature or product.
|
||||
---
|
||||
```
|
||||
|
||||
3. **Start a new conversation**
|
||||
- Skills are loaded at conversation start
|
||||
- Start fresh conversation after uploading Skill
|
||||
|
||||
4. **Mention the Skill type explicitly**
|
||||
- "Using the PRD template, help me write..."
|
||||
- "Create a stakeholder update following the standard format"
|
||||
|
||||
### Claude says it doesn't have access to Skills
|
||||
|
||||
**Problem**: Claude responds "I don't have access to that Skill" or similar.
|
||||
|
||||
**Solutions**:
|
||||
1. Verify Skill is uploaded (Settings → Skills)
|
||||
2. Start a new conversation
|
||||
3. Check Code Execution is enabled
|
||||
4. Re-upload the Skill
|
||||
5. Try different phrasing in your request
|
||||
|
||||
## Skill Triggering at Wrong Times
|
||||
|
||||
### Skill activates when it shouldn't
|
||||
|
||||
**Problem**: Skill triggers for requests where it's not appropriate.
|
||||
|
||||
**Solution**:
|
||||
1. Make the `description` more specific
|
||||
2. Add negative conditions
|
||||
|
||||
Example:
|
||||
```markdown
|
||||
---
|
||||
description: Create meeting notes ONLY when user provides meeting transcript, discussion summary, or asks to document a meeting. Do NOT use for general note-taking or todo lists.
|
||||
---
|
||||
```
|
||||
|
||||
3. If problem persists, consider splitting into multiple more specific Skills
|
||||
|
||||
### Multiple Skills trigger simultaneously
|
||||
|
||||
**Problem**: Multiple Skills activate and create conflicts.
|
||||
|
||||
**This is expected behavior** - Claude can use multiple Skills together.
|
||||
|
||||
**If it's causing issues**:
|
||||
1. Make Skill descriptions more mutually exclusive
|
||||
2. Remove redundant Skills
|
||||
3. Combine overlapping Skills into one
|
||||
|
||||
## Output Quality Issues
|
||||
|
||||
### Outputs are too generic
|
||||
|
||||
**Problem**: Skill produces generic content that doesn't match your needs.
|
||||
|
||||
**Solutions**:
|
||||
|
||||
1. **Add more specific examples to SKILL.md**
|
||||
```markdown
|
||||
## Example Output
|
||||
|
||||
[Paste your actual anonymized example]
|
||||
|
||||
Key elements:
|
||||
- Specific tone we use
|
||||
- Level of detail expected
|
||||
- Format preferences
|
||||
```
|
||||
|
||||
2. **Add company-specific context**
|
||||
```markdown
|
||||
## Our Standards
|
||||
|
||||
- Always include 3-5 metrics
|
||||
- Use data from last 30 days
|
||||
- Reference specific tools (Jira, Mixpanel)
|
||||
```
|
||||
|
||||
3. **Provide more context in your request**
|
||||
- Include relevant background
|
||||
- Mention specific requirements
|
||||
- Reference past examples
|
||||
|
||||
### Outputs are too long/short
|
||||
|
||||
**Problem**: Generated content doesn't match your preferred length.
|
||||
|
||||
**Solutions**:
|
||||
|
||||
1. **Add length guidelines to SKILL.md**
|
||||
```markdown
|
||||
## Length Guidelines
|
||||
|
||||
- PRD: 3-6 pages for features, 8-12 for products
|
||||
- Stakeholder updates: 1 page maximum
|
||||
- Meeting notes: 1-2 pages typical
|
||||
```
|
||||
|
||||
2. **Specify in your request**
|
||||
- "Create a brief stakeholder update (under 1 page)"
|
||||
- "Write a detailed PRD (5-6 pages)"
|
||||
|
||||
### Skill missing key information
|
||||
|
||||
**Problem**: Outputs don't include sections you need.
|
||||
|
||||
**Solution**: Update SKILL.md to be more explicit:
|
||||
|
||||
```markdown
|
||||
## Required Sections
|
||||
|
||||
EVERY output MUST include:
|
||||
1. [Section name]
|
||||
2. [Section name]
|
||||
3. [Section name]
|
||||
|
||||
Optional sections (include when relevant):
|
||||
- [Section name]
|
||||
- [Section name]
|
||||
```
|
||||
|
||||
### Format is wrong
|
||||
|
||||
**Problem**: Skill uses wrong formatting, structure, or style.
|
||||
|
||||
**Solutions**:
|
||||
|
||||
1. **Add explicit formatting rules**
|
||||
```markdown
|
||||
## Formatting Rules
|
||||
|
||||
- Use markdown tables for comparisons
|
||||
- Use bullet points for lists
|
||||
- Use numbered lists for sequential steps
|
||||
- Bold key terms and metrics
|
||||
```
|
||||
|
||||
2. **Include template in SKILL.md**
|
||||
```markdown
|
||||
## Exact Template
|
||||
|
||||
Use this structure exactly:
|
||||
|
||||
# [Title]
|
||||
|
||||
## Section 1
|
||||
[Content guidelines]
|
||||
|
||||
## Section 2
|
||||
[Content guidelines]
|
||||
```
|
||||
|
||||
## Performance Issues
|
||||
|
||||
### Skills make Claude slower
|
||||
|
||||
**Problem**: Responses take longer when Skills are active.
|
||||
|
||||
**This is normal** - Skills add context that Claude processes.
|
||||
|
||||
**Mitigation**:
|
||||
1. Only upload Skills you actively use
|
||||
2. Remove unused Skills
|
||||
3. Keep SKILL.md files concise
|
||||
4. Use Progressive Disclosure (reference files instead of putting everything in SKILL.md)
|
||||
|
||||
### Skill uses wrong/outdated information
|
||||
|
||||
**Problem**: Skill references old information or outdated examples.
|
||||
|
||||
**Solution**:
|
||||
1. Update SKILL.md with current information
|
||||
2. Remove outdated examples
|
||||
3. Re-package and re-upload
|
||||
4. Document update in changelog
|
||||
|
||||
## Team/Enterprise Issues
|
||||
|
||||
### Teammates can't see my Skill
|
||||
|
||||
**Problem**: You uploaded a Skill but teammates don't have it.
|
||||
|
||||
**Explanation**: Skills are user-specific by default.
|
||||
|
||||
**Solutions**:
|
||||
|
||||
For Team/Enterprise plans:
|
||||
1. Have admin access Admin Console
|
||||
2. Navigate to Skills management
|
||||
3. Upload to organization library
|
||||
4. Skill becomes available to all team members
|
||||
|
||||
For Pro plans:
|
||||
- Skills are private only
|
||||
- Share the .skill file with teammates
|
||||
- They must upload individually
|
||||
|
||||
### Organization Skill conflicts with my custom version
|
||||
|
||||
**Problem**: Organization uploaded a Skill but you have customizations.
|
||||
|
||||
**Current Limitation**: No easy override mechanism.
|
||||
|
||||
**Workarounds**:
|
||||
1. Request admin update organization Skill with your changes
|
||||
2. Remove your custom version and use organization version
|
||||
3. Give your custom version a different name to avoid conflicts
|
||||
|
||||
### Different team members get different outputs
|
||||
|
||||
**Problem**: Same Skill produces different results for different people.
|
||||
|
||||
**Possible Causes**:
|
||||
|
||||
1. **Different Skill versions**
|
||||
- Solution: Standardize on organization Skill
|
||||
|
||||
2. **Different custom instructions**
|
||||
- Solution: Check Settings → Custom Instructions
|
||||
|
||||
3. **Different prompting**
|
||||
- Solution: Document standard prompts to use
|
||||
|
||||
4. **Skills updated at different times**
|
||||
- Solution: Admin pushes updates to all simultaneously
|
||||
|
||||
## Still Having Issues?
|
||||
|
||||
### Before Asking for Help
|
||||
|
||||
1. **Try the basics**:
|
||||
- Log out and back in
|
||||
- Try different browser
|
||||
- Clear cache
|
||||
- Disable browser extensions
|
||||
- Try incognito mode
|
||||
|
||||
2. **Gather information**:
|
||||
- Which Skill is having issues?
|
||||
- What exactly are you trying to do?
|
||||
- What happens vs. what should happen?
|
||||
- Your Claude plan (Pro/Team/Enterprise)
|
||||
- Screenshots if applicable
|
||||
|
||||
3. **Check existing issues**:
|
||||
- [GitHub Issues](https://github.com/yourusername/pm-claude-skills/issues)
|
||||
- [Discussions](https://github.com/yourusername/pm-claude-skills/discussions)
|
||||
|
||||
### Getting Help
|
||||
|
||||
1. **For Skill-specific issues**:
|
||||
- [Open a GitHub Issue](https://github.com/yourusername/pm-claude-skills/issues/new)
|
||||
- Include Skill name, what you expected, what happened
|
||||
|
||||
2. **For Claude platform issues**:
|
||||
- Contact Anthropic support: support@anthropic.com
|
||||
- Check [Anthropic documentation](https://docs.anthropic.com)
|
||||
|
||||
3. **For general questions**:
|
||||
- [Start a Discussion](https://github.com/yourusername/pm-claude-skills/discussions)
|
||||
- Email: your-email@example.com
|
||||
|
||||
### Reporting a Bug
|
||||
|
||||
Use this template when reporting issues:
|
||||
|
||||
```markdown
|
||||
**Skill Name**: [which skill]
|
||||
**Claude Plan**: [Pro/Team/Enterprise]
|
||||
**Browser**: [Chrome/Firefox/Safari]
|
||||
|
||||
**Expected Behavior**:
|
||||
[What should happen]
|
||||
|
||||
**Actual Behavior**:
|
||||
[What actually happens]
|
||||
|
||||
**Steps to Reproduce**:
|
||||
1. [Step 1]
|
||||
2. [Step 2]
|
||||
3. [Step 3]
|
||||
|
||||
**Screenshots** (if applicable):
|
||||
[Attach images]
|
||||
|
||||
**Additional Context**:
|
||||
[Any other relevant information]
|
||||
```
|
||||
|
||||
## Common Error Messages
|
||||
|
||||
### "Skill execution failed"
|
||||
- Restart conversation
|
||||
- Check Skill isn't corrupted
|
||||
- Try re-uploading Skill
|
||||
|
||||
### "Unable to load Skill"
|
||||
- Check Code Execution is enabled
|
||||
- Verify Skill is in your Skills list
|
||||
- Try uploading again
|
||||
|
||||
### "Invalid YAML frontmatter"
|
||||
- Check frontmatter syntax in SKILL.md
|
||||
- Ensure `---` markers are present
|
||||
- Verify `name` and `description` fields exist
|
||||
|
||||
## Next Steps
|
||||
|
||||
- [Back to Installation](installation.md)
|
||||
- [Customization Guide](customization.md)
|
||||
- [Creating Your Own Skills](creating-skills.md)
|
||||
Reference in New Issue
Block a user