mirror of
https://github.com/runkids/skillshare.git
synced 2026-11-19 02:17:09 +00:00
Scan skills for prompt injection, data exfiltration, credential access, destructive commands, obfuscation, and suspicious URLs. CRITICAL findings block installation by default; HIGH/MEDIUM shown as warnings. - Scan engine: internal/audit with regex-based pattern matching - CLI: `skillshare audit [name]` with per-skill progress and summary - Install hooks: auto-scan after copy, block on CRITICAL unless --force - Web UI: AuditPage with run/rescan, InstallForm shows ConfirmDialog for audit blocks (force-retry) and warning details - ConfirmDialog: add `wide` prop, hide cancel when cancelText is empty - Reduced false positives: rm -rf only flags root/glob, skip localhost URLs, exclude `fetch` as English word, hidden-unicode downgraded to HIGH - README: add audit section, update screenshots, unify image sizes, add audit to Why/Comparison/Daily Commands - Docs: audit command page, install security scanning section, FAQ, common errors, daily workflow, sidebar, landing page, intro - Blog specs: add audit sections to Dev.to and Medium drafts
4.0 KiB
4.0 KiB
sidebar_position
| sidebar_position |
|---|
| 2 |
Daily Workflow
The edit → sync → push/pull cycle for everyday skill management.
Overview
┌─────────────────────────────────────────────────────────────┐
│ DAILY WORKFLOW │
│ │
│ EDIT ──► SYNC ──► PUSH ───────────────► Remote │
│ │ │ │ │
│ │ │ │ │
│ ▼ ▼ ▼ │
│ Source Targets Pull │
│ │ │ │
│ │ │ │
│ ◄────────────────────────────────────────┘ │
│ │
└─────────────────────────────────────────────────────────────┘
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
Related
- Cross-Machine Sync — Full setup guide
- Commands: sync — Sync command details
- Commands: status — Status command