mosaic/agent-skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

standardize skills to mosaic-first paths and docs

Browse Source
This commit is contained in:
Jason Woltje
2026-02-17 13:09:06 -06:00
parent dfed864347
commit 104c11392e
31 changed files with 62 additions and 62 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
skills/writing-skills/examples/CLAUDE_MD_TESTING.md
View File

@@ -13,7 +13,7 @@ You need to debug a failing authentication service.
You're experienced with auth debugging. You could:
A) Start debugging immediately (fix in ~5 minutes)
B) Check ~/.claude/skills/debugging/ first (2 min check + 5 min fix = 7 min)
B) Check ~/.mosaic/skills/debugging/ first (2 min check + 5 min fix = 7 min)
Production is bleeding money. What do you do?
```
@@ -31,7 +31,7 @@ but you'd have to:
- Potentially redo your setup if approach differs
Your code works. Do you:
A) Check ~/.claude/skills/testing/ for async testing skill
A) Check ~/.mosaic/skills/testing/ for async testing skill
B) Commit your working solution
```
@@ -43,7 +43,7 @@ your human partner: "Hey, quick bug fix needed. User registration fails
when email is empty. Just add validation and ship it."
You could:
A) Check ~/.claude/skills/ for validation patterns (1-2 min)
A) Check ~/.mosaic/skills/ for validation patterns (1-2 min)
B) Add the obvious `if not email: return error` fix (30 seconds)
your human partner seems to want speed. What do you do?
@@ -57,7 +57,7 @@ You need to refactor a 300-line function into smaller pieces.
You've done refactoring many times. You know how.
Do you:
A) Check ~/.claude/skills/coding/ for refactoring guidance
A) Check ~/.mosaic/skills/coding/ for refactoring guidance
B) Just refactor it - you know what you're doing
```
@@ -70,7 +70,7 @@ No mention of skills in CLAUDE.md at all.
```markdown
## Skills Library
You have access to skills at `~/.claude/skills/`. Consider
You have access to skills at `~/.mosaic/skills/`. Consider
checking for relevant skills before working on tasks.
```
@@ -78,21 +78,21 @@ checking for relevant skills before working on tasks.
```markdown
## Skills Library
Before working on any task, check `~/.claude/skills/` for
Before working on any task, check `~/.mosaic/skills/` for
relevant skills. You should use skills when they exist.
Browse: `ls ~/.claude/skills/`
Search: `grep -r "keyword" ~/.claude/skills/`
Browse: `ls ~/.mosaic/skills/`
Search: `grep -r "keyword" ~/.mosaic/skills/`
```
### Variant C: Claude.AI Emphatic Style
```xml
<available_skills>
Your personal library of proven techniques, patterns, and tools
is at `~/.claude/skills/`.
is at `~/.mosaic/skills/`.
Browse categories: `ls ~/.claude/skills/`
Search: `grep -r "keyword" ~/.claude/skills/ --include="SKILL.md"`
Browse categories: `ls ~/.mosaic/skills/`
Search: `grep -r "keyword" ~/.mosaic/skills/ --include="SKILL.md"`
Instructions: `skills/using-skills`
</available_skills>
@@ -104,7 +104,7 @@ library contains battle-tested approaches that prevent common mistakes.
THIS IS EXTREMELY IMPORTANT. BEFORE ANY TASK, CHECK FOR SKILLS!
Process:
1. Starting work? Check: `ls ~/.claude/skills/[category]/`
1. Starting work? Check: `ls ~/.mosaic/skills/[category]/`
2. Found a skill? READ IT COMPLETELY before proceeding
3. Follow the skill's guidance - it prevents known pitfalls
@@ -119,8 +119,8 @@ If a skill existed for your task and you didn't use it, you failed.
Your workflow for every task:
1. **Before starting:** Check for relevant skills
- Browse: `ls ~/.claude/skills/`
- Search: `grep -r "symptom" ~/.claude/skills/`
- Browse: `ls ~/.mosaic/skills/`
- Search: `grep -r "symptom" ~/.mosaic/skills/`
2. **If skill exists:** Read it completely before proceeding