## 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>
3.6 KiB
3.6 KiB
name, description
| name | description |
|---|---|
| ourdigital-skill-creator | Meta skill for creating and managing new skills. Triggers (ourdigital or our prefix): - "our skill create", "our 스킬 만들기" |
OurDigital Skill Creator
Purpose: Creating new skills Triggers: Use "our" or "ourdigital" prefix
OurDigital Skill Creator
Meta skill for creating, validating, and managing OurDigital Claude Skills.
Activation
Activate with "ourdigital" or "our" prefix:
- "ourdigital 스킬 만들어줘" / "our 스킬 만들어줘"
- "ourdigital skill creator" / "our skill creator"
- "our skill create [name]"
Do NOT activate for generic "make a skill" requests (without our/ourdigital prefix).
Interactive Workflow
Phase 1: Need Assessment
When user requests a new skill:
- Acknowledge the initial request
- Ask clarifying questions (max 3 per turn):
- What is the core purpose?
- What triggers this skill?
- What outputs do you expect?
Phase 2: Suitability Check
Evaluate against Claude Skill criteria:
| Criterion | Question to Ask |
|---|---|
| Clear trigger | When exactly should this skill activate? |
| Focused scope | Can you describe 1-3 core functions? |
| Reusable resources | What scripts, templates, or references are needed? |
| Domain knowledge | What specialized knowledge does Claude lack? |
| Clear boundaries | How does this differ from existing skills? |
Decision: If ≥3 criteria pass → proceed. Otherwise, suggest alternatives.
Phase 3: Requirements Definition
Guide user through structured Q&A:
Q1. 스킬 목적과 핵심 기능은 무엇인가요?
(What is the skill's purpose and core functions?)
Q2. 어떤 상황에서 이 스킬이 트리거되어야 하나요?
(When should this skill be triggered?)
Q3. 필요한 외부 도구나 API가 있나요?
(Any external tools or APIs needed?)
Q4. 기대하는 출력 형식은 무엇인가요?
(What output format do you expect?)
Q5. Desktop, Code, 또는 Both 환경이 필요한가요?
(Which environment: Desktop, Code, or Both?)
Phase 4: Skill Generation
Generate skill structure following OurDigital standards:
XX-ourdigital-{skill-name}/
├── desktop/
│ └── SKILL.md # Desktop version
├── code/
│ └── SKILL.md # Code version (CLAUDE.md pattern)
├── shared/
│ ├── references/ # Common documentation
│ ├── templates/ # Shared templates
│ └── scripts/ # Utility scripts
├── docs/
│ ├── CHANGELOG.md # Version history
│ └── logs/ # Update logs
└── README.md # Overview
Phase 5: Validation
Before finalizing, verify:
- YAML frontmatter includes "ourdigital" trigger keywords
- Description clearly states activation conditions
- Body content is 800-1,200 words
- shared/ resources are properly referenced
- No overlap with existing ourdigital skills
Phase 6: Notion Sync
Record to Working with AI database:
- Database: f8f19ede-32bd-43ac-9f60-0651f6f40afe
- Properties:
- Name:
ourdigital-{skill-name} v{version} - Status: In progress → Done
- AI used: Claude Desktop
- AI summary: Brief skill description
- Name:
YAML Frontmatter Template
---
name: ourdigital-{skill-name}
description: |
[Purpose summary]
Activated when user includes "ourdigital" keyword.
Triggers:
- "ourdigital {keyword1}", "ourdigital {keyword2}"
Features:
- Feature 1
- Feature 2
version: "1.0"
author: OurDigital
environment: Desktop | Code | Both
---
[... see full documentation for more ...]