mirror of
https://github.com/runkids/skillshare.git
synced 2026-11-20 20:34:19 +00:00
ASCII box-drawing characters (┌─┐│└─┘) render inconsistently on
Windows due to monospace font width differences. Replace all 30+
diagrams across docs with Mermaid flowcharts rendered as SVG.
- Add Mermaid handDrawn config (Rough.js sketchy style, seed 42)
- Add CSS fix for foreignObject overflow clipping in handDrawn mode
- Convert supported-targets grid to HTML with anchor navigation
- Simplify all node labels to short, readable single-line text
- Strip redundant %%{init}%% directives (covered by global config)
3.0 KiB
3.0 KiB
sidebar_position
| sidebar_position |
|---|
| 2 |
Daily Workflow
The edit → sync → push/pull cycle for everyday skill management.
Overview
flowchart LR
EDIT["EDIT"] --> SYNC["SYNC"] --> PUSH["PUSH"] --> REMOTE["Remote"]
EDIT --- SRC["Source"]
SYNC --- TGT["Targets"]
REMOTE --> PULL["Pull"]
PULL -.-> EDIT
Editing Skills
Option 1: Edit in source (recommended)
$EDITOR ~/.config/skillshare/skills/my-skill/SKILL.md
Changes are immediately visible in all targets (via symlinks).
Option 2: Edit in target
$EDITOR ~/.claude/skills/my-skill/SKILL.md
Because targets are symlinked, this edits the source file directly.
Syncing
After editing, sync is usually not needed because of symlinks. However, run sync when:
- You've installed or removed skills
- You've changed sync mode
- You've added or removed targets
- You see "out of sync" in status
skillshare sync
:::tip Why is sync a separate step?
Sync is intentionally decoupled from install/update/uninstall. This lets you batch multiple changes (e.g., install 3 skills → sync once), preview with --dry-run before propagating, and keep full control of when targets update. See Source & Targets: Why Sync is a Separate Step for details.
:::
Preview first
skillshare sync --dry-run
Cross-Machine Sync
If you use git remote:
Push changes (from this machine)
skillshare push -m "Add new skill"
This runs:
git add .git commit -m "Add new skill"git push
Pull changes (to this machine)
skillshare pull
This runs:
git pullskillshare sync
Common Daily Tasks
Create a new skill
skillshare new code-review
$EDITOR ~/.config/skillshare/skills/code-review/SKILL.md
skillshare sync
Update a tracked repo
skillshare update _team-skills
skillshare sync
Update all tracked repos
skillshare update --all
skillshare sync
Check status
skillshare status
Shows:
- Source directory status
- Git status (commits ahead/behind)
- Target sync status
Tips
Make it automatic
Add to your shell startup:
# ~/.bashrc or ~/.zshrc
alias ss="skillshare"
alias sss="skillshare sync"
alias ssp="skillshare push"
alias ssl="skillshare pull"
Check before important work
# Start of day
skillshare pull
skillshare status
# Before committing
skillshare diff
Keep things clean
# Weekly maintenance
skillshare audit # Scan for security threats
skillshare backup --cleanup # Remove old backups
skillshare doctor # Check for issues
See Also
- sync — Core sync command
- status — Check sync state
- push / pull — Cross-machine sync
- Skill Discovery — Find new skills