ourdigital/our-claude-skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Add installation tool, Claude.ai export, and skill standardization (#1)

Browse Source 
## Summary

- Add portable installation tool (`install.sh`) for cross-machine setup
- Add Claude.ai export files with proper YAML frontmatter
- Add multi-agent-guide v2.0 with consolidated framework template
- Rename `00-claude-code-setting` → `00-our-settings-audit` (avoid reserved word)
- Add YAML frontmatter to 25+ SKILL.md files for Claude Desktop compatibility

## Commits Included

- `93f604a` feat: Add portable installation tool for cross-machine setup
- `9b84104` feat: Add Claude.ai export for portable skill installation
- `f7ab973` fix: Add YAML frontmatter to Claude.ai export files
- `3fed49a` feat(multi-agent-guide): Add v2.0 with consolidated framework
- `3be26ef` refactor: Rename settings-audit skill and add YAML frontmatter

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Andrew Yim
2026-02-03 16:48:06 +07:00
committed by GitHub
parent 0bc24d00b9
commit b6a478e1df
72 changed files with 4770 additions and 803 deletions
Download Patch File Download Diff File Expand all files Collapse all files

80
reference/SKILL-FORMAT-REQUIREMENTS.md
View File

@@ -4,15 +4,15 @@
This document describes the format requirements for Claude Skills in this repository. Skills support dual-platform development (Claude Code and Claude Desktop) with separated concerns.
## Desktop Skill Structure (Recommended)
## Desktop Skill Structure
For Claude Desktop skills, metadata is stored in a separate `skill.yaml` file:
For Claude Desktop skills:
```
skill-name/
└── desktop/
├── skill.yaml # Metadata (name, description, allowed-tools, license)
├── SKILL.md # Content only (no frontmatter)
├── SKILL.md # MUST have YAML frontmatter (name, description)
├── skill.yaml # Optional extended metadata
├── tools/ # MCP tool documentation
│ ├── firecrawl.md # Tool-specific docs
│ └── notion.md
@@ -20,10 +20,35 @@ skill-name/
└── examples/ # Usage examples
```
### skill.yaml Format
### SKILL.md Format (REQUIRED)
**Claude Desktop REQUIRES YAML frontmatter** with at least `name` and `description`.
```markdown
---
name: skill-name-here
description: |
Brief description of what the skill does.
Include trigger keywords in the description.
Triggers: keyword1, keyword2.
---
# Skill Name
Purpose and overview...
## Workflow
Step-by-step instructions...
## MCP Tool Usage
Tool-specific guidance...
```
### skill.yaml (Optional, for extended metadata)
```yaml
# Required fields
name: skill-name-here
description: Brief description of what the skill does and trigger keywords
@@ -46,24 +71,6 @@ triggers:
- keyword2
```
### SKILL.md Content
With metadata separated into skill.yaml, SKILL.md contains only the skill directive:
```markdown
# Skill Name
Purpose and overview...
## Workflow
Step-by-step instructions...
## MCP Tool Usage
Tool-specific guidance...
```
### tools/ Directory
Document MCP tools used by the skill:
@@ -145,18 +152,21 @@ The script:
3. Creates `tools/` directory
4. Generates tool stub files based on `allowed-tools`
## Legacy Format (Deprecated)
## Required vs Optional Fields
The old format with frontmatter embedded in SKILL.md is deprecated:
### SKILL.md Frontmatter (Required)
```yaml
---
name: skill-name
description: Description
allowed-tools: mcp__firecrawl__*, Read, Write
---
| Field | Required | Description |
|-------|----------|-------------|
| `name` | **Yes** | Skill identifier in kebab-case |
| `description` | **Yes** | Multi-line, include trigger keywords |
# Skill content...
```
### skill.yaml (Optional)
Use the migration script to convert to the new format.
| Field | Description |
|-------|-------------|
| `name` | Same as SKILL.md |
| `description` | Same or extended |
| `allowed-tools` | List of permitted tools |
| `license` | MIT, Internal-use Only |
| `triggers` | Explicit trigger list |